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
Backups
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