From 71daea0c38225950a5c9815c2464b3f037f9f235 Mon Sep 17 00:00:00 2001 From: Peter Matulis Date: Tue, 17 Nov 2020 17:01:41 +0000 Subject: [PATCH] Revert "Begin refactor of CDG" Hypothesis is that the .htaccess file has caused a 500 code internal server error. This reverts commit 6e8487816b52514b94f428ae9ef1a69337d85960. Change-Id: I3f16562ddfd095f3a29b0fe6f6c7588762e37a85 --- deploy-guide/source/1 | 152 ++++++++++++++++++ deploy-guide/source/_extra/.htaccess | 3 - deploy-guide/source/app-masakari.rst | 2 +- deploy-guide/source/app.rst | 31 ++++ deploy-guide/source/conf.py | 1 - ...ure-openstack.rst => config-openstack.rst} | 3 + deploy-guide/source/index.rst | 104 ++++++------ deploy-guide/source/install-juju.rst | 3 + deploy-guide/source/install-maas.rst | 8 +- .../source/install-openstack-bundle.rst | 2 +- deploy-guide/source/install-openstack.rst | 6 +- deploy-guide/source/install-overview.rst | 26 --- 12 files changed, 256 insertions(+), 85 deletions(-) create mode 100644 deploy-guide/source/1 delete mode 100644 deploy-guide/source/_extra/.htaccess create mode 100644 deploy-guide/source/app.rst rename deploy-guide/source/{configure-openstack.rst => config-openstack.rst} (99%) delete mode 100644 deploy-guide/source/install-overview.rst diff --git a/deploy-guide/source/1 b/deploy-guide/source/1 new file mode 100644 index 0000000..9c04f1b --- /dev/null +++ b/deploy-guide/source/1 @@ -0,0 +1,152 @@ +Appendix M: Ceph Erasure Coding and Device Classing +=================================================== + +Overview +++++++++ + +Ceph pools supporting applications within an OpenStack deployment are +by default configured as replicated pools which means that every object +stored is copied to multiple hosts or zones to allow the pool to survive +the loss of an OSD. + +Ceph also supports Erasure Coded pools which can be used instead to save +raw space within the storage cluster. The following charms can be +configured to use Erasure Coded pools: + + * glance + * cinder-ceph + * nova-compute + * ceph-fs + * ceph-radosgw + +Configuring charms for Erasure Coding ++++++++++++++++++++++++++++++++++++++ + +All charms that support use with Erasure Coded pools support a consistent +set of configuration options to enable and tune the Erasure Coding profile +used to configure the Erasure Coded pool. + +Erasure Coding is enabled by setting the 'pool-type' option to 'erasure-coded'. +By default the JErasure plugin is used with K=1 and M=2. This does not +actually save any raw storage compared to a replicated pool with 3 replicas +(and is designd to allow use on a three node Ceph cluster) so most deployments +using Erasure Coded pools will need to tune the K and M values based on either +the number of hosts deployed or the number of zones in the deployment if +the 'customize-failure-domain' option is enabled on the ceph-osd and ceph-mon +charms. + +The K value defines the number of data chunks that will be used for each object +and the M value defines the number of coding chunks generated for each object. +The M value also defines the number of OSD's that may be lost before the pool +goes into a degraded state. + +K + M must always be less than or equal to the number of hosts or zones in the +deployment (depending on the configuration of 'customize-failure-domain'. + +In the example below, the Erasure Coded pool used by the glance application +will sustain the loss of two hosts or zones while only consuming 2TB instead +of 3TB of storage to store 1TB of data. + +.. code-block:: yaml + + glance: + options: + pool-type: erasure-coded + ec-profile-k: 2 + ec-profile-m: 2 + +The full list of Erasure Coding configuration options is detailed below. + +.. list-table:: Erasure Coding charm options + :widths: 25 5 15 55 + :header-rows: 1 + + * - Option + - Type + - Default Value + - Description + * - pool-type + - string + - replicated + - Ceph pool type to use for storage - valid values are 'replicated' and 'erasure-coded'. + * - ec-profile-name + - string + - + - Name for the EC profile to be created for the EC pools. If not defined a profile name will be generated based on the name of the pool used by the application. + * - ec-rbd-metadata-pool + - string + - + - Name of the metadata pool to be created (for RBD use-cases). If not defined a metadata pool name will be generated based on the name of the data pool used by the application. The metadata pool is always replicated (not erasure coded). + * - ec-profile-k + - int + - 1 + - Number of data chunks that will be used for EC data pool. K+M factors should never be greater than the number of available AZs for balancing. + * - ec-profile-m + - int + - 2 + - Number of coding chunks that will be used for EC data pool. K+M factors should never be greater than number of available AZs for balancing. + * - ec-profile-locality + - int + - + - (lrc plugin - l) Group the coding and data chunks into sets of size l. For instance, for k=4 and m=2, when l=3 two groups of three are created. Each set can be recovered without reading chunks from another set. Note that using the lrc plugin does incur more raw storage usage than isa or jerasure in order to reduce the cost of recovery operations. + * - ec-profile-crush-locality + - string + - + - (lrc plugin) The type of the crush bucket in which each set of chunks defined by l will be stored. For instance, if it is set to rack, each group of l chunks will be placed in a different rack. It is used to create a CRUSH rule step such as 'step choose rack'. If it is not set, no such grouping is done. + * - ec-profile-durability-estimator + - int + - + - (shec plugin - c) The number of parity chunks each of which includes each data chunk in its calculation range. The number is used as a durability estimator. For instance, if c=2, 2 OSDs can be down without losing data. + * - ec-profile-helper-chunks + - int + - + - (clay plugin - d) Number of OSDs requested to send data during recovery of a single chunk. d needs to be chosen such that k+1 <= d <= k+m-1. The larger the d, the better the savings. + * - ec-profile-scalar-mds + - string + - + - (clay plugin) Specifies the plugin that is used as a building block in the layered construction. It can be one of: jerasure, isa or shec. + * - ec-profile-plugin + - string + - jerasure + - EC plugin to use for this applications pool. These plugins are available: jerasure, lrc, isa, shec, clay. + * - ec-profile-technique + - string + - reed_sol_van + - EC profile technique used for this applications pool - will be validated based on the plugin configured via ec-profile-plugin. Supported techniques are 'reed_sol_van', 'reed_sol_r6_op', 'cauchy_orig', 'cauchy_good', 'liber8tion' for jerasure, 'reed_sol_van', 'cauchy' for isa and 'single', 'multiple' for shec. + * - ec-profile-device-class + - string + - + - Device class from CRUSH map to use for placement groups for erasure profile - valid values: ssd, hdd or nvme (or leave unset to not use a device class). + + +Ceph automatic device classing +++++++++++++++++++++++++++++++ + +Newer versions of Ceph do automatic classing of OSD devices. Each OSD +will be placed into ‘nvme’, ‘ssd’ or ‘hdd’ device classes. These can +be used when creating erasure profiles or new CRUSH rules (see following +sections). + +The classes can be inspected using: + +.. code:: + + sudo ceph osd crush tree + + ID CLASS WEIGHT TYPE NAME + -1 8.18729 root default + -5 2.72910 host node-laveran + 2 nvme 0.90970 osd.2 + 5 ssd 0.90970 osd.5 + 7 ssd 0.90970 osd.7 + -7 2.72910 host node-mees + 1 nvme 0.90970 osd.1 + 6 ssd 0.90970 osd.6 + 8 ssd 0.90970 osd.8 + -3 2.72910 host node-pytheas + 0 nvme 0.90970 osd.0 + 3 ssd 0.90970 osd.3 + 4 ssd 0.90970 osd.4 + +The device class for an Erasure Coded pool can be configured in the +consuming charm using the 'ec-device-class' configuration option. diff --git a/deploy-guide/source/_extra/.htaccess b/deploy-guide/source/_extra/.htaccess deleted file mode 100644 index 8fb4d67..0000000 --- a/deploy-guide/source/_extra/.htaccess +++ /dev/null @@ -1,3 +0,0 @@ -RewriteEngine on - -Redirect 301 /config-openstack.html /configure-openstack.html diff --git a/deploy-guide/source/app-masakari.rst b/deploy-guide/source/app-masakari.rst index eeb4be7..244e202 100644 --- a/deploy-guide/source/app-masakari.rst +++ b/deploy-guide/source/app-masakari.rst @@ -502,4 +502,4 @@ Masakari. .. _Masakari charm: http://jaas.ai/masakari .. _openstack-base: https://jaas.ai/openstack-base .. _OpenStack high availability: app-ha.html#ha-applications -.. _Configure OpenStack: configure-openstack.html +.. _Configure OpenStack: config-openstack.html diff --git a/deploy-guide/source/app.rst b/deploy-guide/source/app.rst new file mode 100644 index 0000000..ece40bb --- /dev/null +++ b/deploy-guide/source/app.rst @@ -0,0 +1,31 @@ +========== +Appendices +========== + +.. toctree:: + :maxdepth: 2 + + app-ceph-migration.rst + app-upgrade-openstack.rst + app-vault.rst + app-encryption-at-rest.rst + app-certificate-management.rst + app-series-upgrade.rst + app-series-upgrade-openstack.rst + app-nova-cells.rst + app-octavia.rst + app-pci-passthrough-gpu.rst + app-rgw-multisite.rst + app-ceph-rbd-mirror.rst + app-masakari.rst + app-erasure-coding.rst + app-policy-overrides.rst + app-ovn.rst + app-managing-power-events.rst + app-manila-ganesha.rst + app-swift.rst + app-hardware-offload.rst + app-ha.rst + app-trilio-vault.rst + app-bridge-interface-configuration.rst + app-ceph-iscsi.rst diff --git a/deploy-guide/source/conf.py b/deploy-guide/source/conf.py index 1512941..fa2f319 100644 --- a/deploy-guide/source/conf.py +++ b/deploy-guide/source/conf.py @@ -145,7 +145,6 @@ html_theme = 'openstackdocs' # .htaccess) here, relative to this directory. These files are copied # directly to the root of the documentation. # html_extra_path = [] -html_extra_path = ['_extra'] # If not '', a 'Last updated on:' timestamp is inserted at every page bottom, # using the given strftime format. diff --git a/deploy-guide/source/configure-openstack.rst b/deploy-guide/source/config-openstack.rst similarity index 99% rename from deploy-guide/source/configure-openstack.rst rename to deploy-guide/source/config-openstack.rst index 4a270f1..633c2d9 100644 --- a/deploy-guide/source/configure-openstack.rst +++ b/deploy-guide/source/config-openstack.rst @@ -2,6 +2,9 @@ Configure OpenStack =================== +Overview +-------- + In the :doc:`previous section `, we installed OpenStack. We are now going to configure OpenStack with the intent of making it consumable by regular users. Configuration will be performed by both the admin user and the diff --git a/deploy-guide/source/index.rst b/deploy-guide/source/index.rst index cabad95..6548c13 100644 --- a/deploy-guide/source/index.rst +++ b/deploy-guide/source/index.rst @@ -1,64 +1,74 @@ +.. OpenStack documentation master file, created by + sphinx-quickstart on Fri Jun 30 11:14:11 2017. + You can adapt this file completely to your liking, but it should at least + contain the root `toctree` directive. + ================================= OpenStack Charms Deployment Guide ================================= -The OpenStack Charms Deployment Guide is the main source of information for -OpenStack Charms usage. A search facility is available as a separate -:ref:`search`. +Overview +-------- -Also included is a wealth of information in the form of appendices. These -cover a wide variety of subjects, such as an elaboration of a specific charm -feature or instructions for upgrading an OpenStack cloud. +The main purpose of the OpenStack Charms Deployment Guide is to demonstrate how +to build a multi-node OpenStack cloud with `MAAS`_, `Juju`_, and `OpenStack +Charms`_. For easy adoption the cloud will be minimal. Nevertheless, it will be +capable of both performing some real work and scaling to fit more ambitious +projects. High availability will not be implemented beyond natively HA +applications (Ceph, MySQL8, OVN, Swift, and RabbitMQ). + +.. note:: + + For OpenStack Charms project information, development guidelines, release + notes, and release schedules, please refer to the `OpenStack Charm Guide`_. + +Requirements +------------ + +The software versions used in this guide are as follows: + +* **Ubuntu 20.04 LTS (Focal)** for the MAAS server, Juju client, Juju + controller, and all cloud nodes (including containers) +* **MAAS 2.8.2** +* **Juju 2.8.1** +* **OpenStack Ussuri** + +Hardware requirements are listed on the :doc:`Install MAAS ` +page. + +Appendices +---------- + +The guide also includes a wealth of information in the form of appendices. +These cover a wide variety of subjects, such as an elaboration of a specific +charm feature, how to upgrade an OpenStack cloud, or how to manage power events +in a cloud. + +Help improve this guide +----------------------- To help improve this guide you may `file an issue`_ or `submit a contribution`_. -.. note:: - - For project information, development guidelines, release notes, and release - schedules, please refer to the `OpenStack Charm Guide`_. +Table of contents +----------------- .. toctree:: - :caption: Installation - :maxdepth: 1 + :maxdepth: 2 - install-overview - install-maas - install-juju - install-openstack - install-openstack-bundle - configure-openstack + install-maas.rst + install-juju.rst + install-openstack.rst + install-openstack-bundle.rst + config-openstack.rst + app.rst -.. toctree:: - :caption: Appendices - :maxdepth: 1 - - OpenStack upgrades - Series upgrade - Series upgrade OpenStack - Vault - Certificate lifecycle management - Encryption at Rest - Additional Nova cells - Octavia LBaaS - PCI passthrough - Ceph erasure coding - Ceph RADOS Gateway multisite replication - Ceph RBD mirroring - Ceph iSCSI - Ceph charm deprecation - Masakari - Policy overrides - OVN - Managing power events - Manila Ganesha - Swift usage - NIC hardware offload - High availability - TrilioVault Data Protection - Bridge interface configuration +* :ref:`search` .. LINKS +.. _MAAS: https://maas.io +.. _Juju: https://jaas.ai +.. _OpenStack Charms: https://docs.openstack.org/charm-guide +.. _OpenStack Charm Guide: https://docs.openstack.org/charm-guide .. _file an issue: https://bugs.launchpad.net/charm-deployment-guide/+filebug .. _submit a contribution: https://opendev.org/openstack/charm-deployment-guide -.. _OpenStack Charm Guide: https://docs.openstack.org/charm-guide diff --git a/deploy-guide/source/install-juju.rst b/deploy-guide/source/install-juju.rst index e37550e..c4471d3 100644 --- a/deploy-guide/source/install-juju.rst +++ b/deploy-guide/source/install-juju.rst @@ -2,6 +2,9 @@ Install Juju ============ +Overview +-------- + In the :doc:`previous section `, we set up the base environment in the form of a `MAAS`_ cluster. We are now going to implement `Juju`_ as a management solution for that environment. The main goal will be the creation of diff --git a/deploy-guide/source/install-maas.rst b/deploy-guide/source/install-maas.rst index 1483222..512314d 100644 --- a/deploy-guide/source/install-maas.rst +++ b/deploy-guide/source/install-maas.rst @@ -2,9 +2,11 @@ Install MAAS ============ -In the :doc:`previous section `, we gave a summary of the -OpenStack cloud we'll be building and described the approach we'll take for -doing that. +Overview +-------- + +In the :doc:`previous section `, we gave a summary of the OpenStack +cloud we'll be building and described the approach we'll take for doing that. This page will cover the installation of `MAAS`_ as well as point out what is required out of MAAS in terms of post-installation tasks. The goal is to diff --git a/deploy-guide/source/install-openstack-bundle.rst b/deploy-guide/source/install-openstack-bundle.rst index 9a83a3b..8da6ae9 100644 --- a/deploy-guide/source/install-openstack-bundle.rst +++ b/deploy-guide/source/install-openstack-bundle.rst @@ -37,7 +37,7 @@ Administrator Guides`_ for long-term guidance. .. LINKS .. _Install OpenStack: install-openstack -.. _Configure OpenStack: configure-openstack.html +.. _Configure OpenStack: config-openstack .. _Charm bundles: https://jaas.ai/docs/charm-bundles .. _MAAS: https://maas.io .. _openstack-base: https://jaas.ai/openstack-base diff --git a/deploy-guide/source/install-openstack.rst b/deploy-guide/source/install-openstack.rst index 35c8904..b133950 100644 --- a/deploy-guide/source/install-openstack.rst +++ b/deploy-guide/source/install-openstack.rst @@ -795,12 +795,12 @@ Next steps You have successfully deployed OpenStack using both Juju and MAAS. The next step is to render the cloud functional for users. This will involve setting up networks, images, and a user environment. Go to :doc:`Configure OpenStack -` now. +` now. .. LINKS .. _OpenStack Charms: https://docs.openstack.org/charm-guide/latest/openstack-charms.html -.. _Charm upgrades: app-upgrade-openstack.html#charm-upgrades -.. _Series upgrade: app-series-upgrade.html +.. _Charm upgrades: app-upgrade-openstack#charm-upgrades +.. _Series upgrade: app-series-upgrade .. _Charm store: https://jaas.ai/store .. _Post-commission configuration: https://maas.io/docs/commission-nodes#heading--post-commission-configuration .. _Deploying applications: https://jaas.ai/docs/deploying-applications diff --git a/deploy-guide/source/install-overview.rst b/deploy-guide/source/install-overview.rst deleted file mode 100644 index da5a0be..0000000 --- a/deploy-guide/source/install-overview.rst +++ /dev/null @@ -1,26 +0,0 @@ -======== -Overview -======== - -The purpose of the Installation section is to demonstrate how to build a -multi-node OpenStack cloud with `MAAS`_, `Juju`_, and `OpenStack Charms`_. For -easy adoption the cloud will be minimal. Nevertheless, it will be capable of -both performing some real work and scaling to fit more ambitious projects. High -availability will not be implemented beyond natively HA applications (Ceph, -MySQL8, OVN, Swift, and RabbitMQ). - -The software versions used in this guide are as follows: - -* **Ubuntu 20.04 LTS (Focal)** for the MAAS server, Juju client, Juju - controller, and all cloud nodes (including containers) -* **MAAS 2.8.2** -* **Juju 2.8.1** -* **OpenStack Ussuri** - -Proceed to the :doc:`Install MAAS ` page to begin your -installation journey. Hardware requirements are also listed there. - -.. LINKS -.. _MAAS: https://maas.io -.. _Juju: https://juju.is -.. _OpenStack Charms: https://docs.openstack.org/charm-guide