The RPC-OpenStack repository contains additional scripts, variables, and options for deploying an OpenStack cloud. It is a thin wrapper around the OpenStack-Ansible deployment framework that is part of the OpenStack namespace.

There are two different types of RPC-OpenStack deployments available:

• All-In-One (AIO) Deployment. An AIO is a quick way to test a RPC-OpenStack deployment. All of the cloud's internal services are deployed on the same server, which could be a physical server or a virtual machine.

• Production Deployment. Production deployments should be done on more than one server with at least three nodes available to run the internal cloud services.

• Upgrading the RPC-OpenStack Product. Upgrading the RPC-OpenStack Product using intra-series releases.

Clone the RPC-OpenStack repository:

git clone https://github.com/rcbops/rpc-openstack /opt/rpc-openstack

Start a screen or tmux session (to ensure that the deployment continues even if the ssh connection is broken) and run deploy.sh:

Run the deploy.sh script within a tmux or screen session:

tmux
cd /opt/rpc-openstack
export DEPLOY_AIO=true
export RPC_PRODUCT_RELEASE="pike"  # This is optional, if unset the current stable product will be used
./scripts/deploy.sh

The deploy.sh script will run all of the necessary playbooks to deploy an AIO cloud and it normally completes in 90 to 120 minutes.

Clone the RPC-OpenStack repository:

git clone https://github.com/rcbops/rpc-openstack /opt/rpc-openstack

Start a screen or tmux session (to ensure that the deployment continues even if the ssh connection is broken) and run deploy.sh:

Run the deploy.sh script within a tmux or screen session:

cd /opt/rpc-openstack
export RPC_PRODUCT_RELEASE="pike"  # This is optional, if unset the current stable product will be used
./scripts/deploy.sh

To configure the installation please refer to the upstream OpenStack-Ansible documentation regarding basic system setup.

Prior to running the OpenStack-Ansible playbooks ensure your system(s) are using the latest artifacts. To ensure all hosts have are using the same artifacted release, run the site-artifacts.yml playbook.

cd /opt/rpc-openstack
export RPC_PRODUCT_RELEASE="pike"  # This is optional, if unset the current stable product will be used
openstack-ansible site-artifacts.yml

It is possible to disable parts of the artifact deployment system RPC-OpenStack provides. To disable the artifact components any of the following variables can be set to false when running the site-artifacts.yml playbook.

• apt_artifact_enabled
• container_artifact_enabled
• py_artifact_enabled

If these variables are unset, they will automatically flip to true when the respective artifacts are found. These settings are stored in the local fact file /etc/ansible/facts.d/rpc_openstack.fact. If a deployer needs to completely reset the state of artifacts, this file can be removed or modified as needed.

openstack-ansible site-artifacts.yml -e 'apt_artifact_enabled=false' \
                                     -e 'container_artifact_enabled=false' \
                                     -e 'py_artifact_enabled=false'

OpenStack-Ansible will need to be installed. While you can simply run the bootstrap-ansible.sh script provided by the OpenStack-Ansible community you may also run the openstack-ansible-install.yml playbook which was created for convenience and will maintain impotency.

cd /opt/rpc-openstack
export RPC_PRODUCT_RELEASE="pike"  # This is optional, if unset the current stable product will be used
openstack-ansible openstack-ansible-install.yml

It is possible to set the OSA release outside of the predefined "stable" release curated by the RPC-OpenStack product. To set the release define the Ansible variable osa_release to a SHA, Branch, or Tag and run the site-release.yml and openstack-ansible-install.yml playbooks to install the correct version.

openstack-ansible site-release.yml openstack-ansible-install.yml -e 'osa_release=master'

Once the deploy configuration has been completed please refer to the OpenStack-Ansible documentation regarding running the playbooks.

Upon completion of the deployment run scripts/deploy-rpco.sh script to apply the RPC-OpenStack value added services; you may also run the playbooks site-logging.yml to accomplish much of the same things.

cd /opt/rpc-openstack
openstack-ansible site-logging.yml

Post deployment run the optional site-openstack.yml playbooks to setup default flavors and images.

cd /opt/rpc-openstack
openstack-ansible site-openstack.yml

To run a basic system upgrade set the ${RPC_PRODUCT_RELEASE} option, re-run deploy.sh, and setup the artifact configuration for the deployment.

tmux
cd /opt/rpc-openstack
export RPC_PRODUCT_RELEASE="pike"  # This is optional, if unset the current stable product will be used
./scripts/deploy.sh
openstack-ansible site-artifacts.yml
openstack-ansible openstack-ansible-install.yml

Once basic system configuration has completed, run through the upgrade process for the specified product release.

To run a major upgrade set the ${RPC_PRODUCT_RELEASE} option, re-run deploy.sh, and setup the artifact configuration for the deployment.

tmux
cd /opt/rpc-openstack
export RPC_PRODUCT_RELEASE="master"  # This needs to be set to the new product
./scripts/deploy.sh
openstack-ansible site-artifacts.yml
openstack-ansible openstack-ansible-install.yml

Once the deployment is ready either run the major upgrade script or run the manual upgrade process.

Please see the documentation in rpc-gating/README.md