Remove installation guide for openSUSE/SLES
openSUSE stopped providing OpenStack packages some time ago. Co-authored-by: Takashi Kajinami <kajinamit@oss.nttdata.com> Change-Id: I60fcbac1cb6ec370de565903375be411e8fc3415
This commit is contained in:
@@ -1,45 +0,0 @@
|
||||
.. _controller-obs:
|
||||
|
||||
Install and configure the controller node for openSUSE and SUSE Linux Enterprise
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
This section describes how to install and configure the proxy service that
|
||||
handles requests for the account, container, and object services operating
|
||||
on the storage nodes. For simplicity, this guide installs and configures
|
||||
the proxy service on the controller node. However, you can run the proxy
|
||||
service on any node with network connectivity to the storage nodes.
|
||||
Additionally, you can install and configure the proxy service on multiple
|
||||
nodes to increase performance and redundancy. For more information, see the
|
||||
`Deployment Guide <https://docs.openstack.org/swift/latest/deployment_guide.html>`__.
|
||||
|
||||
This section applies to openSUSE Leap 42.2 and SUSE Linux Enterprise Server
|
||||
12 SP2.
|
||||
|
||||
.. include:: controller-common_prerequisites.txt
|
||||
|
||||
Install and configure components
|
||||
--------------------------------
|
||||
|
||||
.. note::
|
||||
|
||||
Default configuration files vary by distribution. You might need
|
||||
to add these sections and options rather than modifying existing
|
||||
sections and options. Also, an ellipsis (``...``) in the configuration
|
||||
snippets indicates potential default configuration options that you
|
||||
should retain.
|
||||
|
||||
#. Install the packages:
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
# zypper install openstack-swift-proxy python-swiftclient \
|
||||
python-keystoneclient python-keystonemiddleware \
|
||||
python-xml memcached
|
||||
|
||||
.. note::
|
||||
|
||||
Complete OpenStack environments already include some of these
|
||||
packages.
|
||||
|
||||
2. .. include:: controller-include.txt
|
||||
|
||||
@@ -12,7 +12,6 @@ Note that installation and configuration vary by distribution.
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
controller-install-obs.rst
|
||||
controller-install-rdo.rst
|
||||
controller-install-ubuntu.rst
|
||||
controller-install-debian.rst
|
||||
|
||||
@@ -1,80 +0,0 @@
|
||||
.. _finalize-obs:
|
||||
|
||||
Finalize installation for openSUSE and SUSE Linux Enterprise
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. note::
|
||||
|
||||
Default configuration files vary by distribution. You might need
|
||||
to add these sections and options rather than modifying existing
|
||||
sections and options. Also, an ellipsis (``...``) in the configuration
|
||||
snippets indicates potential default configuration options that you
|
||||
should retain.
|
||||
|
||||
This section applies to openSUSE Leap 42.2 and SUSE Linux Enterprise Server
|
||||
12 SP2.
|
||||
|
||||
#. Edit the ``/etc/swift/swift.conf`` file and complete the following
|
||||
actions:
|
||||
|
||||
* In the ``[swift-hash]`` section, configure the hash path prefix and
|
||||
suffix for your environment.
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
[swift-hash]
|
||||
...
|
||||
swift_hash_path_suffix = HASH_PATH_SUFFIX
|
||||
swift_hash_path_prefix = HASH_PATH_PREFIX
|
||||
|
||||
Replace HASH_PATH_PREFIX and HASH_PATH_SUFFIX with unique values.
|
||||
|
||||
.. warning::
|
||||
|
||||
Keep these values secret and do not change or lose them.
|
||||
|
||||
* In the ``[storage-policy:0]`` section, configure the default
|
||||
storage policy:
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
[storage-policy:0]
|
||||
...
|
||||
name = Policy-0
|
||||
default = yes
|
||||
|
||||
#. Copy the ``swift.conf`` file to the ``/etc/swift`` directory on
|
||||
each storage node and any additional nodes running the proxy service.
|
||||
|
||||
3. On all nodes, ensure proper ownership of the configuration directory:
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
# chown -R root:swift /etc/swift
|
||||
|
||||
4. On the controller node and any other nodes running the proxy service,
|
||||
start the Object Storage proxy service including its dependencies and
|
||||
configure them to start when the system boots:
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
# systemctl enable openstack-swift-proxy.service memcached.service
|
||||
# systemctl start openstack-swift-proxy.service memcached.service
|
||||
|
||||
5. On the storage nodes, start the Object Storage services and configure
|
||||
them to start when the system boots:
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
# systemctl enable openstack-swift-account.service openstack-swift-account-auditor.service \
|
||||
openstack-swift-account-reaper.service openstack-swift-account-replicator.service
|
||||
# systemctl start openstack-swift-account.service openstack-swift-account-auditor.service \
|
||||
openstack-swift-account-reaper.service openstack-swift-account-replicator.service
|
||||
# systemctl enable openstack-swift-container.service openstack-swift-container-auditor.service \
|
||||
openstack-swift-container-replicator.service openstack-swift-container-updater.service
|
||||
# systemctl start openstack-swift-container.service openstack-swift-container-auditor.service \
|
||||
openstack-swift-container-replicator.service openstack-swift-container-updater.service
|
||||
# systemctl enable openstack-swift-object.service openstack-swift-object-auditor.service \
|
||||
openstack-swift-object-replicator.service openstack-swift-object-updater.service
|
||||
# systemctl start openstack-swift-object.service openstack-swift-object-auditor.service \
|
||||
openstack-swift-object-replicator.service openstack-swift-object-updater.service
|
||||
@@ -8,6 +8,5 @@ Finalizing installation varies by distribution.
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
finalize-installation-obs.rst
|
||||
finalize-installation-rdo.rst
|
||||
finalize-installation-ubuntu-debian.rst
|
||||
|
||||
@@ -1,145 +0,0 @@
|
||||
.. _storage-obs:
|
||||
|
||||
Install and configure the storage nodes for openSUSE and SUSE Linux Enterprise
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
This section describes how to install and configure storage nodes
|
||||
that operate the account, container, and object services. For
|
||||
simplicity, this configuration references two storage nodes, each
|
||||
containing two empty local block storage devices. The instructions
|
||||
use ``/dev/sdb`` and ``/dev/sdc``, but you can substitute different
|
||||
values for your particular nodes.
|
||||
|
||||
Although Object Storage supports any file system with
|
||||
extended attributes (xattr), testing and benchmarking
|
||||
indicate the best performance and reliability on XFS. For
|
||||
more information on horizontally scaling your environment, see the
|
||||
`Deployment Guide <https://docs.openstack.org/swift/latest/deployment_guide.html>`_.
|
||||
|
||||
This section applies to openSUSE Leap 42.2 and SUSE Linux Enterprise Server
|
||||
12 SP2.
|
||||
|
||||
Prerequisites
|
||||
-------------
|
||||
|
||||
Before you install and configure the Object Storage service on the
|
||||
storage nodes, you must prepare the storage devices.
|
||||
|
||||
.. note::
|
||||
|
||||
Perform these steps on each storage node.
|
||||
|
||||
#. Install the supporting utility packages:
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
# zypper install xfsprogs rsync
|
||||
|
||||
#. Format the ``/dev/sdb`` and ``/dev/sdc`` devices as XFS:
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
# mkfs.xfs /dev/sdb
|
||||
# mkfs.xfs /dev/sdc
|
||||
|
||||
#. Create the mount point directory structure:
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
# mkdir -p /srv/node/sdb
|
||||
# mkdir -p /srv/node/sdc
|
||||
|
||||
#. Find the UUID of the new partitions:
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
# blkid
|
||||
|
||||
#. Edit the ``/etc/fstab`` file and add the following to it:
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
UUID="<UUID-from-output-above>" /srv/node/sdb xfs noatime 0 2
|
||||
UUID="<UUID-from-output-above>" /srv/node/sdc xfs noatime 0 2
|
||||
|
||||
#. Mount the devices:
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
# mount /srv/node/sdb
|
||||
# mount /srv/node/sdc
|
||||
|
||||
#. Create or edit the ``/etc/rsyncd.conf`` file to contain the following:
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
uid = swift
|
||||
gid = swift
|
||||
log file = /var/log/rsyncd.log
|
||||
pid file = /var/run/rsyncd.pid
|
||||
address = MANAGEMENT_INTERFACE_IP_ADDRESS
|
||||
|
||||
[account]
|
||||
max connections = 2
|
||||
path = /srv/node/
|
||||
read only = False
|
||||
lock file = /var/lock/account.lock
|
||||
|
||||
[container]
|
||||
max connections = 2
|
||||
path = /srv/node/
|
||||
read only = False
|
||||
lock file = /var/lock/container.lock
|
||||
|
||||
[object]
|
||||
max connections = 2
|
||||
path = /srv/node/
|
||||
read only = False
|
||||
lock file = /var/lock/object.lock
|
||||
|
||||
Replace ``MANAGEMENT_INTERFACE_IP_ADDRESS`` with the IP address of the
|
||||
management network on the storage node.
|
||||
|
||||
.. note::
|
||||
|
||||
The ``rsync`` service requires no authentication, so consider running
|
||||
it on a private network in production environments.
|
||||
|
||||
7. Start the ``rsyncd`` service and configure it to start when the
|
||||
system boots:
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
# systemctl enable rsyncd.service
|
||||
# systemctl start rsyncd.service
|
||||
|
||||
Install and configure components
|
||||
--------------------------------
|
||||
|
||||
.. note::
|
||||
|
||||
Default configuration files vary by distribution. You might need
|
||||
to add these sections and options rather than modifying existing
|
||||
sections and options. Also, an ellipsis (``...``) in the configuration
|
||||
snippets indicates potential default configuration options that you
|
||||
should retain.
|
||||
|
||||
.. note::
|
||||
|
||||
Perform these steps on each storage node.
|
||||
|
||||
#. Install the packages:
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
# zypper install openstack-swift-account \
|
||||
openstack-swift-container openstack-swift-object python-xml
|
||||
|
||||
2. .. include:: storage-include1.txt
|
||||
3. .. include:: storage-include2.txt
|
||||
4. .. include:: storage-include3.txt
|
||||
5. Ensure proper ownership of the mount point directory structure:
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
# chown -R swift:swift /srv/node
|
||||
@@ -11,6 +11,5 @@ Note that installation and configuration vary by distribution.
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
storage-install-obs.rst
|
||||
storage-install-rdo.rst
|
||||
storage-install-ubuntu-debian.rst
|
||||
|
||||
Reference in New Issue
Block a user