Skip to content

Latest commit

 

History

History
78 lines (55 loc) · 2.45 KB

README.md

File metadata and controls

78 lines (55 loc) · 2.45 KB

##uci deployment

As an advanced use of kcli, i have created a deployment plan and specific scripts that will deploy the following elements. As they are the upstream for Red Hat Cloud Infrastructure products, i m using the term "Upstream Cloud Infrastructure" to refer to them:

  • openstack rdo
  • ovirt
  • manageiq
  • openshift origin
  • foreman

Note that a single vm is deployed for every project and as such all services are provided in a "allinone" fashion

##installation

  • The deployment makes use of a private routed network on your libvirt host, named cinet, with dhcp, using 192.168.5.0, reserving ips starting from 192.168.5.200 as openstack floating ip pool. To define it, You can save the corresponding XML:
<network><name>cinet</name>
<forward mode='nat'>
  <nat>
    <port start='1024' end='65535'/>
  </nat>
</forward>
<domain name='cinet'/>
<ip address='192.168.5.1' netmask='255.255.255.0'>
  <dhcp>
    <range start='192.168.5.100' end='192.168.5.199'/>
  </dhcp>
</ip>
</network>

And create it with those commands

virsh net-define cinet.xml
virsh net-start cinet
  • You can then use the plan files and scripts in the uci directory
kcli plan -f uci.yml uci

##i want rhci

Provided you have the subscriptions, you can save the sample register.sh script to your home directory, edit it to match your credentials and pool info and launch the deployment:

kcli plan -f rhci.yml rhci

##Launching single product

You can also easily launch individual upstream/downstream product directly from the corresponding directory . For instance to launch upstream ovirt, run the following commands (optionally specifying a plan name)

cd uci/ovirt
kcli plan -f upstream.yml

You can do the same for downstream. Note that for openstack, there are per version downstream plan files to ease testing ( currently kilo, liberty and mitaka )

##limitations

  • Using static networking with rhel/centos cloud images is complicated as those images are per default configured to have a single dhcp nic. Best Solution is to run virt-customize in those images to enable BOOTPROTO=static
  • I had issues injecting cloudinit beyond network configuration in the manageiq image. Ideally one would use appliance_console_cli and curl calls to set it up, but it refuses to work....

##Problems?

Send me a mail at [email protected] !

Mac Fly!!!

karmab