
Training labs parser will allow us to automatically parse RST code to BASH. This BASH code in turn will be invoked by install-guides for validating the install guides. To provide the correct information to the parser for generating BASH code, there are a few changes required to the RST syntax. Introduces the following changes to RST syntax: - `.. end` This tag provides information for the parser to stop extracting the given block which could be code, file injection or configuration file edit. - `.. endonly` This tag provides information for the parser with the correct distro-switch logic for identifying distro-specific code. For .. only:: tags, it is better to avoid nesting. If nesting is not avoidable then it is preferable to add the .. endonly tag to close the outer block immediately. - Extra new lines in code-blocks Some commands in the code-blocks provides the expected output of the given command. This is not a BASH command which we want to run but rather some visual niceness for the users. These new lines provides the parser information to identify the end of the command. This basic logic would be something similar to find '\r\n' which at least for python means new empty line. - `mysql>` Introducing this operator for mysql commands. This could potentially be changed to `pgsql>` or similar for other SQL type databases. This allows the parser to identify mysql commands and then run them in mysql instead of in 'sh' or 'bash'. - `.. path` Introducing this tag to provide the parser with the information with the path of the configuration file. Using the description text for the same is not reliable since the description text may not be consistent. This commit should ideally introduce all the syntax changes required for the parser to convert the code-blocks in here to BASH code. These changes should have no impact on the HTML output of the RST code. Change-Id: I47830b1bc61c8b1a0f3350932d15aa3ce88fa672
6.4 KiB
OpenStack packages
Distributions release OpenStack packages as part of the distribution or using other methods because of differing release schedules. Perform these procedures on all nodes.
Note
The set up of OpenStack packages described here needs to be done on all nodes: controller, compute, and Block Storage nodes.
Warning
Your hosts must contain the latest versions of base installation packages available for your distribution before proceeding further.
Note
Disable or remove any automatic update services because they can impact your OpenStack environment.
ubuntu
Enable the OpenStack repository
# apt-get install software-properties-common
# add-apt-repository cloud-archive:newton
Note
For pre-release testing, use the staging repository:
# add-apt-repository cloud-archive:newton-proposed
rdo
Prerequisites
Warning
We recommend disabling EPEL when using RDO packages due to updates in
EPEL breaking backwards compatibility. Or, preferably pin package
versions using the yum-versionlock
plugin.
Note
CentOS does not require the following steps.
On RHEL, register your system with Red Hat Subscription Management, using your Customer Portal user name and password:
# subscription-manager register --username="USERNAME" --password="PASSWORD"
Find entitlement pools containing the channels for your RHEL system:
# subscription-manager list --available
Use the pool identifiers found in the previous step to attach your RHEL entitlements:
# subscription-manager attach --pool="POOLID"
Enable required repositories:
# subscription-manager repos --enable=rhel-7-server-optional-rpms \ --enable=rhel-7-server-extras-rpms --enable=rhel-7-server-rh-common-rpms
rdo
Enable the OpenStack repository
On CentOS, the
extras
repository provides the RPM that enables the OpenStack repository. CentOS includes theextras
repository by default, so you can simply install the package to enable the OpenStack repository.# yum install centos-release-openstack-newton
On RHEL, download and install the RDO repository RPM to enable the OpenStack repository.
# yum install https://rdoproject.org/repos/rdo-release.rpm
obs
Enable the OpenStack repository
Enable the Open Build Service repositories based on your openSUSE or SLES version:
On openSUSE:
# zypper addrepo -f obs://Cloud:OpenStack:Newton/openSUSE_Leap_42.1 Newton
Note
The openSUSE distribution uses the concept of patterns to represent collections of packages. If you selected 'Minimal Server Selection (Text Mode)' during the initial installation, you may be presented with a dependency conflict when you attempt to install the OpenStack packages. To avoid this, remove the minimal_base-conflicts package:
# zypper rm patterns-openSUSE-minimal_base-conflicts
On SLES:
# zypper addrepo -f obs://Cloud:OpenStack:Newton/SLE_12_SP2 Newton
Note
The packages are signed by GPG key
D85F9316
. You should verify the fingerprint of the imported GPG key before using it.Key Name: Cloud:OpenStack OBS Project <Cloud:OpenStack@build.opensuse.org> Key Fingerprint: 35B34E18 ABC1076D 66D5A86B 893A90DA D85F9316 Key Created: 2015-12-16T16:48:37 CET Key Expires: 2018-02-23T16:48:37 CET
debian
Enable the backports repository
The Newton release is available directly through the official Debian backports repository. To use this repository, follow the instruction from the official Debian website, which basically suggest doing the following steps:
On all nodes, adding the Debian 8 (Jessie) backport repository to the source list:
# echo "deb http://http.debian.net/debian jessie-backports main" \ >>/etc/apt/sources.list
Note
Later you can use the following command to install a package:
# apt-get -t jessie-backports install ``PACKAGE``
Finalize the installation
Upgrade the packages on your host:
ubuntu or debian
# apt-get update && apt-get dist-upgrade
rdo
# yum upgrade
obs
# zypper refresh && zypper dist-upgrade
Note
If the upgrade process includes a new kernel, reboot your host to activate it.
Install the OpenStack client:
debian or ubuntu
# apt-get install python-openstackclient
rdo
# yum install python-openstackclient
obs
# zypper install python-openstackclient
rdo
RHEL and CentOS enable
SELinux
by default. Install theopenstack-selinux
package to automatically manage security policies for OpenStack services:# yum install openstack-selinux