Overcloud

This page details how to deploy and use an Overcloud once the Undercloud is installed.

There are 3 scripts for convenience.

Note that deploy-overcloud can be configured for individual environments via environment variables. The variables you can set are documented below before the calls to the script. For their default values, see the deploy-overcloud script itself.

You must source the contents of /root/stackrc into your shell before running the instack-* scripts that interact with the undercloud and overcloud. In order to do that you can copy that file to a more convenient location or use sudo to cat the file and copy/paste the lines into your shell environment.
Run the prepare-for-overcloud script to get setup. This script will re-downloading images if they already exist in the current working directory. If you want to force a redownload of the images, delete them first.
```
 instack-prepare-for-overcloud
```
If you're testing an all VM setup, make sure you have copied the public key portion of the virtual power ssh key into the virtual power user's ~/.ssh/authorized_keys on the virsh host.

Run the deploy-overcloud script to actually deploy the overcloud. Note that the variables must be exported so that their values are picked up by deploy-overcloud. If you put them in an rc file that you intend to source, make sure there are exports in that file as well.

 # CPU: number of cpus on baremetal nodes
 # MEM: amount of ram on baremetal nodes, in MB
 # DISK: amount of disk on baremetal nodes, in GB
 # ARCH: architecture of baremetal nodes, amd64 or i386
 # MACS: list of MAC addresses of baremetal nodes
 # PM_IPS: list of Power Management IP addresses
 # PM_USERS: list of Power Management Users
 # PM_PASSWORDS: list of Power Management Passwords
 # NeutronPublicInterface: Overcloud management interface name
 # OVERCLOUD_LIBVIRT_TYPE: Overcloud libvirt type, qemu or kvm
 # NETWORK_CIDR: neutron network cidr
 # FLOATING_IP_START: floating ip allocation start
 # FLOATING_IP_END: floating ip allocation end
 # FLOATING_IP_CIDR: floating ip network cidr
 instack-deploy-overcloud-tuskarcli

####Scailing To scale the Compute, Block Storage or Swift Storage nodes, you can override the default values from the deploy-overcloud scripts in your rc file. The defaults for those scripts are:

 COMPUTESCALE=${COMPUTESCALE:-1}
 BLOCKSTORAGESCALE=${BLOCKSTORAGESCALE:-1}
 SWIFTSTORAGESCALE=${SWIFTSTORAGESCALE:-0}

Run the test-overcloud script to launch a cirros image on the overcloud and wait until it pings successfully
```
 instack-test-overcloud
```

2.7 KiB Raw Blame History

Overcloud

2.7 KiB

Raw Blame History