diff options
Diffstat (limited to 'doc/install')
| -rw-r--r-- | doc/install/clone-source.rst | 74 | ||||
| -rw-r--r-- | doc/install/get-packages.rst | 11 | ||||
| -rw-r--r-- | doc/install/index.rst | 9 | ||||
| -rw-r--r-- | doc/install/manual-deployment.rst | 46 |
4 files changed, 66 insertions, 74 deletions
diff --git a/doc/install/clone-source.rst b/doc/install/clone-source.rst index 2d09ef9eb..9dbf335f1 100644 --- a/doc/install/clone-source.rst +++ b/doc/install/clone-source.rst @@ -98,59 +98,7 @@ repository. Updating Submodules ------------------- -#. Determine whether your submodules are out of date: - - .. prompt:: bash $ - - git status - - A. If your submodules are up to date - If your submodules are up to date, the following console output will - appear: - - :: - - On branch main - Your branch is up to date with 'origin/main'. - - nothing to commit, working tree clean - - If you see this console output, then your submodules are up to date. - You do not need this procedure. - - - B. If your submodules are not up to date - If your submodules are not up to date, you will see a message that - includes a list of "untracked files". The example here shows such a - list, which was generated from a real situation in which the - submodules were no longer current. Your list of files will not be the - same as this list of files, but this list is provided as an example. - If in your case any untracked files are listed, then you should - continue to the next step of this procedure. - - :: - - On branch main - Your branch is up to date with 'origin/main'. - - Untracked files: - (use "git add <file>..." to include in what will be committed) - src/pybind/cephfs/build/ - src/pybind/cephfs/cephfs.c - src/pybind/cephfs/cephfs.egg-info/ - src/pybind/rados/build/ - src/pybind/rados/rados.c - src/pybind/rados/rados.egg-info/ - src/pybind/rbd/build/ - src/pybind/rbd/rbd.c - src/pybind/rbd/rbd.egg-info/ - src/pybind/rgw/build/ - src/pybind/rgw/rgw.c - src/pybind/rgw/rgw.egg-info/ - - nothing added to commit but untracked files present (use "git add" to track) - -#. If your submodules are out of date, run the following commands: +If your submodules are out of date, run the following commands: .. prompt:: bash $ @@ -158,24 +106,10 @@ Updating Submodules git clean -fdx git submodule foreach git clean -fdx - If you still have problems with a submodule directory, use ``rm -rf - [directory name]`` to remove the directory. Then run ``git submodule update - --init --recursive`` again. - -#. Run ``git status`` again: - - .. prompt:: bash $ - - git status - - Your submodules are up to date if you see the following message: - - :: +If you still have problems with a submodule directory, use ``rm -rf [directory +name]`` to remove the directory. Then run ``git submodule update --init +--recursive --progress`` again. - On branch main - Your branch is up to date with 'origin/main'. - - nothing to commit, working tree clean Choose a Branch =============== diff --git a/doc/install/get-packages.rst b/doc/install/get-packages.rst index d6edc177b..ca7168310 100644 --- a/doc/install/get-packages.rst +++ b/doc/install/get-packages.rst @@ -251,6 +251,17 @@ openSUSE Tumbleweed The newest major release of Ceph is already available through the normal Tumbleweed repositories. There's no need to add another package repository manually. +openEuler +^^^^^^^^^ + +There are two major versions supported in normal openEuler repositories. They are ceph 12.2.8 in openEuler-20.03-LTS series and ceph 16.2.7 in openEuler-22.03-LTS series. There’s no need to add another package repository manually. +You can install ceph just by executing the following: + +.. prompt:: bash $ + + sudo yum -y install ceph + +Also you can download packages manually from https://repo.openeuler.org/openEuler-{release}/everything/{arch}/Packages/. Ceph Development Packages ------------------------- diff --git a/doc/install/index.rst b/doc/install/index.rst index 58ef92a27..7076eb355 100644 --- a/doc/install/index.rst +++ b/doc/install/index.rst @@ -4,14 +4,13 @@ Installing Ceph =============== -There are multiple ways to install Ceph. +There are multiple ways to install Ceph. Recommended methods ~~~~~~~~~~~~~~~~~~~ -:ref:`Cephadm <cephadm_deploying_new_cluster>` installs and manages a Ceph -cluster that uses containers and systemd and is tightly integrated with the CLI -and dashboard GUI. +:ref:`Cephadm <cephadm_deploying_new_cluster>` is a tool that can be used to +install and manage a Ceph cluster. * cephadm supports only Octopus and newer releases. * cephadm is fully integrated with the orchestration API and fully supports the @@ -59,6 +58,8 @@ tool that can be used to quickly deploy clusters. It is deprecated. `github.com/openstack/puppet-ceph <https://github.com/openstack/puppet-ceph>`_ installs Ceph via Puppet. +`OpenNebula HCI clusters <https://docs.opennebula.io/stable/provision_clusters/hci_clusters/overview.html>`_ deploys Ceph on various cloud platforms. + Ceph can also be :ref:`installed manually <install-manual>`. diff --git a/doc/install/manual-deployment.rst b/doc/install/manual-deployment.rst index 6716ecb5b..0eb759de7 100644 --- a/doc/install/manual-deployment.rst +++ b/doc/install/manual-deployment.rst @@ -461,6 +461,52 @@ In the below instructions, ``{id}`` is an arbitrary name, such as the hostname o #. Now you are ready to `create a Ceph file system`_. +Manually Installing RADOSGW +=========================== + +For a more involved discussion of the procedure presented here, see `this +thread on the ceph-users mailing list +<https://lists.ceph.io/hyperkitty/list/ceph-users@ceph.io/message/LB3YRIKAPOHXYCW7MKLVUJPYWYRQVARU/>`_. + +#. Install ``radosgw`` packages on the nodes that will be the RGW nodes. + +#. From a monitor or from a node with admin privileges, run a command of the + following form: + + .. prompt:: bash # + + ceph auth get-or-create client.short-hostname-of-rgw mon 'allow rw' osd 'allow rwx' + +#. On one of the RGW nodes, do the following: + + a. Create a ``ceph-user``-owned directory. For example: + + .. prompt:: bash # + + install -d -o ceph -g ceph /var/lib/ceph/radosgw/ceph-$(hostname -s) + + b. Enter the directory just created and create a ``keyring`` file: + + .. prompt:: bash # + + touch /var/lib/ceph/radosgw/ceph-$(hostname -s)/keyring + + Use a command similar to this one to put the key from the earlier ``ceph + auth get-or-create`` step in the ``keyring`` file. Use your preferred + editor: + + .. prompt:: bash # + + $EDITOR /var/lib/ceph/radosgw/ceph-$(hostname -s)/keyring + + c. Repeat these steps on every RGW node. + +#. Start the RADOSGW service by running the following command: + + .. prompt:: bash # + + systemctl start ceph-radosgw@$(hostname -s).service + Summary ======= |