[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
This commit is contained in:
Dmitriy Rabotyagov 2020-05-01 15:53:56 +03:00 committed by Dmitriy Rabotyagov (noonedeadpunk)
parent d719094a04
commit 3cd9819992

View File

@ -55,7 +55,7 @@ Configure Ubuntu
.. code-block:: shell-session .. code-block:: shell-session
# apt-get install bridge-utils debootstrap ifenslave ifenslave-2.6 \ # apt-get install bridge-utils debootstrap ifenslave ifenslave-2.6 \
lsof lvm2 chrony openssh-server sudo tcpdump vlan python lsof lvm2 chrony openssh-server sudo tcpdump vlan python3
#. Install the kernel extra package if you have one for your kernel version \ #. Install the kernel extra package if you have one for your kernel version \
@ -110,7 +110,7 @@ Configure CentOS
.. code-block:: shell-session .. code-block:: shell-session
# yum install bridge-utils iputils lsof lvm2 \ # yum install bridge-utils iputils lsof lvm2 \
chrony openssh-server sudo tcpdump python chrony openssh-server sudo tcpdump python3
#. Add the appropriate kernel modules to the ``/etc/modules-load.d`` file to #. Add the appropriate kernel modules to the ``/etc/modules-load.d`` file to
enable VLAN and bond interfaces: enable VLAN and bond interfaces:
@ -160,7 +160,7 @@ Configure openSUSE
.. code-block:: shell-session .. code-block:: shell-session
# zypper install bridge-utils iputils lsof lvm2 \ # zypper install bridge-utils iputils lsof lvm2 \
chrony opensshr sudo tcpdump python chrony opensshr sudo tcpdump python3
#. Add the appropriate kernel modules to the ``/etc/modules-load.d`` file to #. Add the appropriate kernel modules to the ``/etc/modules-load.d`` file to
enable VLAN and bond interfaces: enable VLAN and bond interfaces:
@ -236,9 +236,9 @@ can optionally use LVM for their data storage.
# vgcreate cinder-volumes physical_volume_device_path # vgcreate cinder-volumes physical_volume_device_path
#. Optionally, create an LVM volume group named ``lxc`` for container file #. Optionally, create an LVM volume group named ``lxc`` for container file
systems if you want to use LXC with LVM. systems and set ``lxc_container_backing_store: lvm`` in user_variables.yml
If the ``lxc`` volume group does not exist, containers are if you want to use LXC with LVM. If the ``lxc`` volume group does not
automatically installed on the file system under ``/var/lib/lxc`` by exist, containers are automatically installed on the file system under
default. ``/var/lib/lxc`` by default.
.. _Logical Volume Manager (LVM): https://en.wikipedia.org/wiki/Logical_Volume_Manager_(Linux) .. _Logical Volume Manager (LVM): https://en.wikipedia.org/wiki/Logical_Volume_Manager_(Linux)