Warn about openstack-origin in appendices
Change-Id: I7435bf7df2ec4ce148c647fc4c98e37bfe7ab3e1 Closes-Bug: #1895662
This commit is contained in:
parent
732ecf2e51
commit
d061ef3e1a
@ -19,6 +19,11 @@ controlled NFS mounts to OpenStack instances.
|
||||
Deployment
|
||||
----------
|
||||
|
||||
.. warning::
|
||||
|
||||
Throughout this guide make sure ``openstack-origin`` matches the value you
|
||||
used when `deploying OpenStack`_.
|
||||
|
||||
One way to add Manila Ganesha is to do so during the bundle deployment of a new
|
||||
OpenStack cloud. This is done by means of a bundle overlay, such as
|
||||
`manila-ganesha-overlay.yaml`:
|
||||
@ -165,5 +170,6 @@ used to secure access to Ganesha even if the network is not a Neutron managed
|
||||
network.
|
||||
|
||||
.. LINKS
|
||||
.. _deploying OpenStack: install-openstack
|
||||
.. _create the share: https://docs.openstack.org/manila/latest/admin/cephfs_driver.html#create-cephfs-nfs-share
|
||||
.. _grant access: https://docs.openstack.org/manila/latest/admin/cephfs_driver.html#allow-access-to-cephfs-nfs-share
|
||||
|
@ -85,6 +85,11 @@ Usage
|
||||
Configuration
|
||||
~~~~~~~~~~~~~
|
||||
|
||||
.. warning::
|
||||
|
||||
Throughout this guide make sure ``openstack-origin`` matches the value you
|
||||
used when `deploying OpenStack`_.
|
||||
|
||||
The below overlay bundle can be used to deploy Masakari when using a bundle to
|
||||
deploy OpenStack.
|
||||
|
||||
@ -503,3 +508,4 @@ Masakari.
|
||||
.. _openstack-base: https://jaas.ai/openstack-base
|
||||
.. _OpenStack high availability: app-ha.html#ha-applications
|
||||
.. _Configure OpenStack: configure-openstack.html
|
||||
.. _deploying OpenStack: install-openstack.html
|
||||
|
@ -33,6 +33,11 @@ placed haproxy instances on neutron-gateway units.
|
||||
Deployment
|
||||
----------
|
||||
|
||||
.. warning::
|
||||
|
||||
Throughout this guide make sure ``openstack-origin`` matches the value you
|
||||
used when `deploying OpenStack`_.
|
||||
|
||||
Octavia makes use of OpenStack Barbican for storage of certificates for
|
||||
TLS termination on load balancers; Barbican makes use of Vault for secure
|
||||
storage of this data. Follow the instructions for deployment and
|
||||
@ -282,6 +287,7 @@ Octavia please refer to the `Octavia cookbook`_.
|
||||
.. LINKS
|
||||
.. _Vault: app-vault
|
||||
.. _Certificate Lifecycle Management: app-certificate-management
|
||||
.. _deploying OpenStack: install-openstack
|
||||
.. _Octavia Policies: https://docs.openstack.org/octavia/latest/configuration/policy.html
|
||||
.. _Octavia cookbook: https://docs.openstack.org/octavia/latest/user/guides/basic-cookbook.html
|
||||
.. _operators maintenance: https://docs.openstack.org/octavia/latest/admin/guides/operator-maintenance.html#rotating-the-amphora-images
|
||||
|
@ -286,6 +286,11 @@ For more details on these options see the upstream `Global clusters`_ document.
|
||||
Deployment
|
||||
^^^^^^^^^^
|
||||
|
||||
.. warning::
|
||||
|
||||
Throughout this guide make sure ``openstack-origin`` matches the value you
|
||||
used when `deploying OpenStack`_.
|
||||
|
||||
This example assumes there are two data centres, one in San Francisco (SF) and
|
||||
one in New York (NY). These contain Juju models 'swift-sf' and 'swift-ny'
|
||||
respectively. Model 'swift-ny' contains OpenStack region 'RegionOne' and
|
||||
@ -500,6 +505,7 @@ contains the Juju "offers" that ``swift-sf.yaml`` will consume:
|
||||
juju deploy -m swift-sf ./swift-sf.yaml --overlay ./swift-sf-consumer.yaml
|
||||
|
||||
.. LINKS
|
||||
.. _deploying OpenStack: install-openstack
|
||||
.. _Global clusters: https://docs.openstack.org/swift/latest/overview_global_cluster.html
|
||||
.. _Cross model relations: https://jaas.ai/docs/cross-model-relations
|
||||
.. _swift-proxy: https://jaas.ai/swift-proxy
|
||||
|
@ -36,6 +36,11 @@ Prerequisites
|
||||
Deployment
|
||||
----------
|
||||
|
||||
.. warning::
|
||||
|
||||
Throughout this guide make sure ``openstack-origin`` matches the value you
|
||||
used when `deploying OpenStack`_.
|
||||
|
||||
The TrilioVault solution consists of three core services:
|
||||
|
||||
- TrilioVault Workload Manager: this service provides the main API
|
||||
@ -146,4 +151,5 @@ The trilio-wlm and trilio-data-mover applications should be in the 'active'
|
||||
state and ready for use.
|
||||
|
||||
.. LINKS
|
||||
.. _deploying OpenStack: install-openstack
|
||||
.. _trilio.io: https://www.trilio.io/triliovault/openstack/
|
||||
|
Loading…
x
Reference in New Issue
Block a user