deep_scrub_choked
This commit is contained in:
a.pivkin
@@ -0,0 +1,64 @@
|
||||
Containerized deployment
|
||||
========================
|
||||
|
||||
Ceph-ansible supports docker and podman only in order to deploy Ceph in a containerized context.
|
||||
|
||||
Configuration and Usage
|
||||
-----------------------
|
||||
|
||||
To deploy ceph in containers, you will need to set the ``containerized_deployment`` variable to ``true`` and use the site-container.yml.sample playbook.
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
containerized_deployment: true
|
||||
|
||||
The ``ceph_origin`` and ``ceph_repository`` variables aren't needed anymore in containerized deployment and are ignored.
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
$ ansible-playbook site-container.yml.sample
|
||||
|
||||
.. note::
|
||||
|
||||
The infrastructure playbooks are working for both non containerized and containerized deployment.
|
||||
|
||||
Custom container image
|
||||
----------------------
|
||||
|
||||
You can configure your own container register, image and tag by using the ``ceph_docker_registry``, ``ceph_docker_image`` and ``ceph_docker_image_tag`` variables.
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
ceph_docker_registry: quay.io
|
||||
ceph_docker_image: ceph/ceph
|
||||
ceph_docker_image_tag: v19
|
||||
|
||||
.. note::
|
||||
|
||||
``ceph_docker_image`` should have both image namespace and image name concatenated and separated by a slash character.
|
||||
|
||||
``ceph_docker_image_tag`` should be set to a fixed tag, not to any "latest" tags unless you know what you are doing. Using a "latest" tag
|
||||
might make the playbook restart all the daemons deployed in your cluster since these tags are intended to be updated periodically.
|
||||
|
||||
Container registry authentication
|
||||
---------------------------------
|
||||
|
||||
When using a container registry with authentication then you need to set the ``ceph_docker_registry_auth`` variable to ``true`` and provide the credentials via the
|
||||
``ceph_docker_registry_username`` and ``ceph_docker_registry_password`` variables
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
ceph_docker_registry_auth: true
|
||||
ceph_docker_registry_username: foo
|
||||
ceph_docker_registry_password: bar
|
||||
|
||||
Container registry behind a proxy
|
||||
---------------------------------
|
||||
|
||||
When using a container registry reachable via a http(s) proxy then you need to set the ``ceph_docker_http_proxy`` and/or ``ceph_docker_https_proxy`` variables. If you need
|
||||
to exclude some host for the proxy configuration to can use the ``ceph_docker_no_proxy`` variable.
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
ceph_docker_http_proxy: http://192.168.42.100:8080
|
||||
ceph_docker_https_proxy: https://192.168.42.100:8080
|
||||
@@ -0,0 +1,12 @@
|
||||
Installation methods
|
||||
====================
|
||||
|
||||
ceph-ansible can deploy Ceph either in a non-containerized context (via packages) or in a containerized context using ceph-container images.
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
non-containerized
|
||||
containerized
|
||||
|
||||
The difference here is that you don't have the rbd command on the host when using the containerized deployment so everything related to ceph needs to be executed within a container. So in the case there is software like e.g. Open Nebula which requires that the rbd command is accessible directly on the host (non-containerized) then you have to install the rbd command by yourself on those servers outside of containers (or make sure that this software somehow runs within containers as well and that it can access rbd).
|
||||
@@ -0,0 +1,58 @@
|
||||
Non containerized deployment
|
||||
============================
|
||||
|
||||
The following are all of the available options for the installing Ceph through different channels.
|
||||
|
||||
We support 3 main installation methods, all managed by the ``ceph_origin`` variable:
|
||||
|
||||
- ``repository``: means that you will get Ceph installed through a new repository. Later below choose between ``community`` or ``dev``. These options will be exposed through the ``ceph_repository`` variable.
|
||||
- ``distro``: means that no separate repo file will be added and you will get whatever version of Ceph is included in your Linux distro.
|
||||
- ``local``: means that the Ceph binaries will be copied over from the local machine (not well tested, use at your own risk)
|
||||
|
||||
Origin: Repository
|
||||
------------------
|
||||
|
||||
If ``ceph_origin`` is set to ``repository``, you now have the choice between a couple of repositories controlled by the ``ceph_repository`` option:
|
||||
|
||||
- ``community``: fetches packages from http://download.ceph.com, the official community Ceph repositories
|
||||
- ``dev``: fetches packages from shaman, a gitbuilder based package system
|
||||
- ``uca``: fetches packages from Ubuntu Cloud Archive
|
||||
- ``custom``: fetches packages from a specific repository
|
||||
|
||||
Community repository
|
||||
~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
If ``ceph_repository`` is set to ``community``, packages you will be by default installed from http://download.ceph.com, this can be changed by tweaking ``ceph_mirror``.
|
||||
|
||||
|
||||
UCA repository
|
||||
~~~~~~~~~~~~~~
|
||||
|
||||
If ``ceph_repository`` is set to ``uca``, packages you will be by default installed from http://ubuntu-cloud.archive.canonical.com/ubuntu, this can be changed by tweaking ``ceph_stable_repo_uca``.
|
||||
You can also decide which OpenStack version the Ceph packages should come from by tweaking ``ceph_stable_openstack_release_uca``.
|
||||
For example, ``ceph_stable_openstack_release_uca: queens``.
|
||||
|
||||
Dev repository
|
||||
~~~~~~~~~~~~~~
|
||||
|
||||
If ``ceph_repository`` is set to ``dev``, packages you will be by default installed from https://shaman.ceph.com/, this can not be tweaked.
|
||||
You can obviously decide which branch to install with the help of ``ceph_dev_branch`` (defaults to 'main').
|
||||
Additionally, you can specify a SHA1 with ``ceph_dev_sha1``, defaults to 'latest' (as in latest built).
|
||||
|
||||
Custom repository
|
||||
~~~~~~~~~~~~~~~~~
|
||||
|
||||
If ``ceph_repository`` is set to ``custom``, packages you will be by default installed from a desired repository.
|
||||
This repository is specified with ``ceph_custom_repo``, e.g: ``ceph_custom_repo: https://server.domain.com/ceph-custom-repo``.
|
||||
|
||||
|
||||
Origin: Distro
|
||||
--------------
|
||||
|
||||
If ``ceph_origin`` is set to ``distro``, no separate repo file will be added and you will get whatever version of Ceph is included in your Linux distro.
|
||||
|
||||
|
||||
Origin: Local
|
||||
-------------
|
||||
|
||||
If ``ceph_origin`` is set to ``local``, the ceph binaries will be copied over from the local machine (not well tested, use at your own risk)
|
||||
Reference in New Issue
Block a user