Bug 1412160 - RFE for RHOS 10 Director Installation and Usage
Summary: RFE for RHOS 10 Director Installation and Usage
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Dan Macpherson
QA Contact: RHOS Documentation Team
Depends On:
TreeView+ depends on / blocked
Reported: 2017-01-11 12:14 UTC by Nikhil Shetty
Modified: 2018-04-09 03:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-04-09 03:41:08 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Nikhil Shetty 2017-01-11 12:14:46 UTC
Version-Release number of selected component (if applicable):RHOS 10

Description of problem:

The RHOS 10 Undercloud installation Requires us to go back and forth to start. Further Recommendation is based on moving Certain Portions of document to a different Page for convenience and simplicity

Actual results:

The following command creates the undercloud virtual machine on the KVM host and create two virtual NICs that connect to the respective bridges:

$ virt-install --name undercloud --memory=16384 --vcpus=4 --location /var/lib/libvirt/images/rhel-server-7.3-x86_64-dvd.iso --disk size=100 --network bridge=br-ex --network bridge=br-ctlplane --graphics=vnc --hvm --os-variant=rhel7

This starts a libvirt domain. Connect to it with virt-manager and walk through the install process. Alternatively, you can perform an unattended installation using the following options to include a kickstart file:

--initrd-inject=/root/ks.cfg --extra-args "ks=file:/ks.cfg"

Once installation completes, SSH into the instance as the root user and follow the instructions in Chapter 4, Installing the Undercloud
To back up a virtualized undercloud, there are multiple solutions:

    Option 1: Follow the instructions in the Back Up and Restore the Director Undercloud Guide.
    Option 2: Shut down the undercloud and take a copy of the undercloud virtual machine storage backing.
    Option 3: Take a snapshot of the undercloud VM is your hypervisor supports live or atomic snapshots. 

If using a KVM server, use the following procedure to take a snapshot:

    Make sure qemu-guest-agent is running on the undercloud guest VM.
    Create a live snapshot of the running VM: 

$ virsh snapshot-create-as --domain undercloud --disk-only --atomic --quiesce

    Take a copy of the (now read-only) QCOW backing file 

$ rsync --sparse -avh --progress /var/lib/libvirt/images/undercloud.qcow2 1.qcow2

    Merge the QCOW overlay file into the backing file and switch the undercloud VM back to using the original file: 

$ virsh blockcommit undercloud vda --active --verbose --pivot

Expected results:

The entire above portion should be moved to Page 4, Point 4.1

This will make the Installation work in 1 go and makes it easy to record and understand the installation Steps

Comment 1 Dan Macpherson 2018-04-09 03:41:08 UTC
Closing this RFE because I don't see a strong rationale for moving the virtualization requirements to the undercloud installation section. Configuring the virtual infrastructure for the is purely preparation work before installing the undercloud. The section its currently in seems appropriate for customers wishing to prepare a virtual machine for the undercloud. This way chapter 4 can be used for a virtual or bare metal undercloud.

Note You need to log in before you can comment on or make changes to this bug.