Name: rpc-openstack
Owner: rcbops
Description: Rackspace Private Cloud Offering based on OpenStack || Submit bugs to: https://bit.ly/RPC-openstack-template
Created: 2015-01-31 02:51:12.0
Updated: 2018-05-21 23:01:50.0
Pushed: 2018-05-24 19:12:17.0
Size: 4306
Language: Shell
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Most Recent Commit | # Commits |
|---|
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:
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:
opt/rpc-openstack
rt DEPLOY_AIO=true
rt RPC_PRODUCT_RELEASE="queens" # This is optional, if unset the current stable product will be used
ripts/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:
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:
opt/rpc-openstack
rt RPC_PRODUCT_RELEASE="queens" # This is optional, if unset the current stable product will be used
ripts/deploy.sh
To configure the installation please refer to the upstream OpenStack-Ansible documentation regarding basic system setup.
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.
opt/rpc-openstack
rt RPC_PRODUCT_RELEASE="queens" # This is optional, if unset the current stable product will be used
stack-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.
stack-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.
opt/rpc-openstack
stack-ansible site-logging.yml
Post deployment run the optional site-openstack.yml playbooks to setup
default flavors and images.
opt/rpc-openstack
stack-ansible site-openstack.yml
To run a basic system upgrade set the ${RPC_PRODUCT_RELEASE} option, re-run
deploy.sh.
opt/rpc-openstack
rt RPC_PRODUCT_RELEASE="queens" # This is optional, if unset the current stable product will be used
ripts/deploy.sh
stack-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.
opt/rpc-openstack
rt RPC_PRODUCT_RELEASE="master" # This needs to be set to the new product
ripts/deploy.sh
stack-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