Move howto contents to admin directory
This is needed because it was discovered that the
"admin guide" link from upstream (docs.openstack.org)
cannot be a redirect (to our current howto dir). I
like the new organisation better anyway.
Conflicts:
doc/test/redirect-tests.txt - fix tests up since admin cannot
be redirected to howto and this change makes it such that howto
redirects to admin
(cherry picked from commit 8bf87e2c8a
)
Change-Id: Ia62536914f00e4721cb72a394920fa47bda306dd
This commit is contained in:
parent
2177cc6d84
commit
c98fe888ea
|
@ -54,4 +54,4 @@ RedirectMatch 301 ^/charm-guide/([^/]+)/reference/2010.html$ /charm-guide/$1/rel
|
|||
RedirectMatch 301 ^/charm-guide/([^/]+)/reference/2101.html$ /charm-guide/$1/release-notes/2101.html
|
||||
RedirectMatch 301 ^/charm-guide/([^/]+)/reference/2110.html$ /charm-guide/$1/release-notes/2110.html
|
||||
|
||||
RedirectMatch 301 ^/charm-guide/([^/]+)/admin/index.html$ /charm-guide/$1/howto/index.html
|
||||
RedirectMatch 301 ^/charm-guide/([^/]+)/howto/([^/]+).html$ /charm-guide/$1/admin/$2.html
|
||||
|
|
|
@ -2,31 +2,28 @@
|
|||
How-to guides
|
||||
=============
|
||||
|
||||
Administrators
|
||||
--------------
|
||||
|
||||
Operations
|
||||
~~~~~~~~~~
|
||||
----------
|
||||
|
||||
General cloud operations:
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
../admin/ops-change-keystone-password
|
||||
../admin/ops-scale-in-nova-compute
|
||||
../admin/ops-unseal-vault
|
||||
../admin/ops-config-tls-vault-api
|
||||
../admin/ops-live-migrate-vms
|
||||
../admin/ops-scale-back-with-hacluster
|
||||
../admin/ops-scale-out-nova-compute
|
||||
../admin/ops-start-innodb-from-outage
|
||||
../admin/ops-auto-glance-image-updates
|
||||
../admin/ops-implement-ha-with-vip
|
||||
../admin/ops-cloud-admin-access
|
||||
../admin/ops-reissue-tls-certs
|
||||
../admin/ops-replace-rabbitmq-node
|
||||
../admin/ops-repair-rabbitmq-node
|
||||
ops-change-keystone-password
|
||||
ops-scale-in-nova-compute
|
||||
ops-unseal-vault
|
||||
ops-config-tls-vault-api
|
||||
ops-live-migrate-vms
|
||||
ops-scale-back-with-hacluster
|
||||
ops-scale-out-nova-compute
|
||||
ops-start-innodb-from-outage
|
||||
ops-auto-glance-image-updates
|
||||
ops-implement-ha-with-vip
|
||||
ops-cloud-admin-access
|
||||
ops-reissue-tls-certs
|
||||
ops-replace-rabbitmq-node
|
||||
ops-repair-rabbitmq-node
|
||||
|
||||
Ceph storage operations (published in the Charmed Ceph documentation):
|
||||
|
||||
|
@ -40,7 +37,7 @@ Ceph storage operations (published in the Charmed Ceph documentation):
|
|||
Software upgrades <https://ubuntu.com/ceph/docs/software-upgrades>
|
||||
|
||||
Management
|
||||
~~~~~~~~~~
|
||||
----------
|
||||
|
||||
Cloud management how-to guides:
|
||||
|
|
@ -41,8 +41,8 @@ Below is a comparison of the repair and replacement methods.
|
|||
|
||||
\* especially if a new machine must be provisioned
|
||||
|
||||
\** can be mitigated with the :doc:`Deferred service events
|
||||
<../howto/deferred-events>` feature
|
||||
\** can be mitigated with the :doc:`Deferred service events <deferred-events>`
|
||||
feature
|
||||
|
||||
Initial state of the cluster
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
|
|
@ -21,7 +21,7 @@ to replace one of its nodes.
|
|||
have adverse effects on the cloud's ability to service its current workload.
|
||||
|
||||
The above issue can be mitigated through the use of :doc:`Deferred service
|
||||
events <../howto/deferred-events>`. If restarts are deferred, a client will
|
||||
events <deferred-events>`. If restarts are deferred, a client will
|
||||
nonetheless experience a slight delay (due to timeouts) if it tries to
|
||||
contact a non-existent node.
|
||||
|
||||
|
|
|
@ -56,5 +56,5 @@ healthy state:
|
|||
mysql-innodb-cluster/2* active idle 2/lxd/2 10.0.0.218 Unit is ready: Mode: R/W, Cluster is ONLINE and can tolerate up to ONE failure.
|
||||
|
||||
See the :ref:`mysql-innodb-cluster section <mysql_innodb_cluster_startup>` on
|
||||
the :doc:`Managing power events <../howto/managing-power-events>` page for full
|
||||
the :doc:`Managing power events <managing-power-events>` page for full
|
||||
coverage.
|
||||
|
|
|
@ -38,7 +38,7 @@ Operators, including key tasks for successful deployment and operations.
|
|||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
howto/index
|
||||
admin/index
|
||||
|
||||
Concepts
|
||||
--------
|
||||
|
|
|
@ -64,4 +64,6 @@
|
|||
/charm-guide/latest/reference/2101.html 301 /charm-guide/latest/release-notes/2101.html
|
||||
/charm-guide/latest/reference/2110.html 301 /charm-guide/latest/release-notes/2110.html
|
||||
|
||||
/charm-guide/xena/admin/index.html 301 /charm-guide/xena/howto/index.html
|
||||
/charm-guide/latest/howto/managing-power-events.html 301 /charm-guide/latest/admin/managing-power-events.html
|
||||
/charm-guide/latest/howto/deferred-events.html 301 /charm-guide/latest/admin/deferred-events.html
|
||||
|
||||
|
|
Loading…
Reference in New Issue