When you install OpenStack in a production environment, we recommend using a separate deployment host that contains Ansible and orchestrates the OpenStack-Ansible (OSA) installation on the target hosts. In a test environment, we recommend using one of the infrastructure target hosts as the deployment host.
To use a target host as a deployment host, follow the steps in Prepare the target hosts on the deployment host.
Install one of the following supported operating systems on the deployment hosts:
Configure at least one network interface to access the Internet or suitable local repositories.
Install additional software packages and configure Network Time Protocol (NTP). Before you begin, we recommend upgrading your system packages and kernel.
Update package source lists:
# apt-get update
Upgrade the system packages and kernel:
# apt-get dist-upgrade
Reboot the host.
Install additional software packages if they were not installed during the operating system installation:
# apt-get install aptitude build-essential git ntp ntpdate openssh-server python-dev sudo
Configure NTP to synchronize with a suitable time source.
Install additional software packages and configure Network Time Protocol (NTP). Before you begin, we recommend upgrading your system packages and kernel.
Upgrade the system packages and kernel
# yum upgrade
Reboot the host.
Install additional software packages if they were not installed during the operating system installation:
# yum install https://rdoproject.org/repos/openstack-pike/rdo-release-pike.rpm # yum install git ntp ntpdate openssh-server python-devel sudo '@Development Tools'
Configure NTP to synchronize with a suitable time source.
The firewalld
service is enabled on most CentOS systems by default and
its default ruleset prevents OpenStack components from communicating
properly. Stop the firewalld
service and mask it to prevent it from
starting:
# systemctl stop firewalld
# systemctl mask firewalld
Note
There is future work planned to create proper firewall rules for OpenStack services in OpenStack-Ansible deployments. Until that work is complete, deployers must maintain their own firewall rulesets or disable the firewall entirely.
Install additional software packages and configure Network Time Protocol (NTP). Before you begin, we recommend upgrading your system packages and kernel.
Upgrade the system packages and kernel
# zypper up
Reboot the host.
Install additional software packages if they were not installed during the operating system installation:
# zypper ar http://download.opensuse.org/repositories/Cloud:/OpenStack:/Pike/openSUSE_Leap_42.3 OBS:Cloud:OpenStack:Pike # zypper install git-core ntp openssh python-devel sudo gcc libffi-devel libopenssl-devel
Configure NTP to synchronize with a suitable time source.
Ansible deployments fail if the deployment server can’t use Secure Shell (SSH) to connect to the containers.
Configure the deployment host (where Ansible is executed) to be on
the same layer 2 network as the network designated for container management. By
default, this is the br-mgmt
network. This configuration reduces the rate
of failure caused by connectivity issues.
Select an IP address from the following example range to assign to the deployment host:
Container management: 172.29.236.0/22 (VLAN 10)
Install the source and dependencies for the deployment host.
Note
If you are installing with limited connectivity, please review Appendix H: Installing with limited connectivity before proceeding.
Clone the latest stable release of the OpenStack-Ansible Git repository in
the /opt/openstack-ansible
directory:
# git clone -b pike-em https://git.openstack.org/openstack/openstack-ansible /opt/openstack-ansible
If git.openstack.org can not be accessed to run git clone, github.com can be used as an alternative repo:
# git clone -b pike-em https://github.com/openstack/openstack-ansible.git /opt/openstack-ansible
Change to the /opt/openstack-ansible
directory, and run the
Ansible bootstrap script:
# scripts/bootstrap-ansible.sh
Ansible uses SSH with public key authentication to connect the
deployment host and target hosts. To reduce user
interaction during Ansible operations, do not include passphrases with
key pairs. However, if a passphrase is required, consider using the
ssh-agent
and ssh-add
commands to temporarily store the
passphrase before performing Ansible operations.
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.