openstack-ansible/deploy-guide/source/targethosts-prepare.rst
Dmitriy Rabotyagov 3cd9819992 [doc] Adjust deploy-guide to install py3
As we don't need py2 now, we should adjust host preparation guide
to install py3 isntead.
Additionally patch extends explanation regarding lvm usage for lxc storage

Change-Id: Idc9897d634e06df4c1084b3a3876b3a3971a0a6d
2020-05-04 11:42:16 +00:00

245 lines
7.1 KiB
ReStructuredText

Configuring the operating system
================================
This section describes the installation and configuration of operating
systems for the target hosts, as well as deploying SSH keys and
configuring storage.
Installing the operating system
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Install one of the following supported operating systems on the
target host:
* Ubuntu server 18.04 (Bionic Beaver) LTS 64-bit
* Debian 10 64-bit
* Centos 7 64-bit
* openSUSE 15.X 64-bit
Configure at least one network interface to access the Internet or
suitable local repositories.
We recommend adding the Secure Shell (SSH) server packages to the
installation on target hosts that do not have local (console) access.
.. note::
We also recommend setting your locale to `en_US.UTF-8`. Other locales might
work, but they are not tested or supported.
Configure Ubuntu
~~~~~~~~~~~~~~~~
#. Update package source lists
.. code-block:: shell-session
# apt-get update
#. Upgrade the system packages and kernel:
.. code-block:: shell-session
# apt-get dist-upgrade
#. Reboot the host.
#. Ensure that the kernel version is ``3.13.0-34-generic`` or later:
.. code-block:: shell-session
# uname -r
#. Install additional software packages:
.. code-block:: shell-session
# apt-get install bridge-utils debootstrap ifenslave ifenslave-2.6 \
lsof lvm2 chrony openssh-server sudo tcpdump vlan python3
#. Install the kernel extra package if you have one for your kernel version \
.. code-block:: shell-session
# apt install linux-image-extra-$(uname -r)
#. Add the appropriate kernel modules to the ``/etc/modules`` file to
enable VLAN and bond interfaces:
.. code-block:: shell-session
# echo 'bonding' >> /etc/modules
# echo '8021q' >> /etc/modules
#. Configure Network Time Protocol (NTP) in ``/etc/chrony/chrony.conf`` to
synchronize with a suitable time source and restart the service:
.. code-block:: shell-session
# service chrony restart
#. Reboot the host to activate the changes and use the new kernel.
Configure CentOS
~~~~~~~~~~~~~~~~
#. Upgrade the system packages and kernel:
.. code-block:: shell-session
# yum upgrade
#. Disable SELinux. Edit ``/etc/sysconfig/selinux``, make sure that
``SELINUX=enforcing`` is changed to ``SELINUX=disabled``.
.. note::
SELinux enabled is not currently supported in OpenStack-Ansible
for CentOS/RHEL due to a lack of maintainers for the feature.
#. Reboot the host.
#. Ensure that the kernel version is ``3.10`` or later:
.. code-block:: shell-session
# uname -r
#. Install additional software packages:
.. code-block:: shell-session
# yum install bridge-utils iputils lsof lvm2 \
chrony openssh-server sudo tcpdump python3
#. Add the appropriate kernel modules to the ``/etc/modules-load.d`` file to
enable VLAN and bond interfaces:
.. code-block:: shell-session
# echo 'bonding' >> /etc/modules-load.d/openstack-ansible.conf
# echo '8021q' >> /etc/modules-load.d/openstack-ansible.conf
#. Configure Network Time Protocol (NTP) in ``/etc/chrony.conf`` to
synchronize with a suitable time source and start the service:
.. code-block:: shell-session
# systemctl enable chronyd.service
# systemctl start chronyd.service
#. (Optional) Reduce the kernel log level by changing the printk
value in your sysctls:
.. code-block:: shell-session
# echo "kernel.printk='4 1 7 4'" >> /etc/sysctl.conf
#. Reboot the host to activate the changes and use the new kernel.
Configure openSUSE
~~~~~~~~~~~~~~~~~~
#. Upgrade the system packages and kernel:
.. code-block:: shell-session
# zypper up
#. Reboot the host.
#. Ensure that the kernel version is ``4.4`` or later:
.. code-block:: shell-session
# uname -r
#. Install additional software packages:
.. code-block:: shell-session
# zypper install bridge-utils iputils lsof lvm2 \
chrony opensshr sudo tcpdump python3
#. Add the appropriate kernel modules to the ``/etc/modules-load.d`` file to
enable VLAN and bond interfaces:
.. code-block:: shell-session
# echo 'bonding' >> /etc/modules-load.d/openstack-ansible.conf
# echo '8021q' >> /etc/modules-load.d/openstack-ansible.conf
#. Configure Network Time Protocol (NTP) in ``/etc/chrony.conf`` to
synchronize with a suitable time source and start the service:
.. code-block:: shell-session
# systemctl enable chronyd.service
# systemctl start chronyd.service
#. Reboot the host to activate the changes and use the new kernel.
Configure SSH keys
==================
Ansible uses SSH to connect the deployment host and target hosts.
#. Copy the contents of the public key file on the deployment host to
the ``/root/.ssh/authorized_keys`` file on each target host.
#. Test public key authentication from the deployment host to each target
host by using SSH to connect to the target host from the deployment host.
If you can connect and get the shell without authenticating, it
is working. SSH provides a shell without asking for a
password.
For more information about how to generate an SSH key pair, as well as best
practices, see `GitHub's documentation about generating SSH keys`_.
.. _GitHub's documentation about generating SSH keys: https://help.github.com/articles/generating-ssh-keys/
.. important::
OpenStack-Ansible deployments require the presence of a
``/root/.ssh/id_rsa.pub`` file on the deployment host.
The contents of this file is inserted into an
``authorized_keys`` file for the containers, which is a
necessary step for the Ansible playbooks. You can
override this behavior by setting the
``lxc_container_ssh_key`` variable to the public key for
the container.
Configuring the storage
=======================
`Logical Volume Manager (LVM)`_ enables a single device to be split into
multiple logical volumes that appear as a physical storage device to the
operating system. The Block Storage (cinder) service, and LXC containers
that optionally run the OpenStack infrastructure,
can optionally use LVM for their data storage.
.. note::
OpenStack-Ansible automatically configures LVM on the nodes, and
overrides any existing LVM configuration. If you had a customized LVM
configuration, edit the generated configuration file as needed.
#. To use the optional Block Storage (cinder) service, create an LVM
volume group named ``cinder-volumes`` on the storage host. Specify a metadata
size of 2048 when creating the physical volume. For example:
.. code-block:: shell-session
# pvcreate --metadatasize 2048 physical_volume_device_path
# vgcreate cinder-volumes physical_volume_device_path
#. Optionally, create an LVM volume group named ``lxc`` for container file
systems and set ``lxc_container_backing_store: lvm`` in user_variables.yml
if you want to use LXC with LVM. If the ``lxc`` volume group does not
exist, containers are automatically installed on the file system under
``/var/lib/lxc`` by default.
.. _Logical Volume Manager (LVM): https://en.wikipedia.org/wiki/Logical_Volume_Manager_(Linux)