There's no .md file in here, so change links. Looking at the used links,
these are all external links and thus sphinx cannot test whether they
work. Use internal links so that all links work - and work even after
renames.
This shows up as e.g.:
WARNING: unknown document: install-maas.html
Update tox.ini so that these are hard errors.
Remove dead requirement oslosphinx, it's not needed anymore here since
openstackdocstheme is used.
Change-Id: Ieae398aecb48c2e26de5c50261e700f8790e64ce
Now etcd and vault have two relations. Also, it's nice to have explicit
relations for others for the future.
Change-Id: Ic2652ba7d317e5adb93a5cf93a813d37f29efd87
Close-Bug: #1835165
Add new appendix detailing how to configure the Ceph RADOS
Gateway to make use of Erasure Coding and automatic storage
device classing.
Change-Id: I85ff5deae37e2471434a499fd4d97d9b577386ce
Ensure its clear that the authorize-charm action should be run
on the lead vault unit in a HA deployment by using the /leader
syntax to auto-identify the lead unit.
Add '--wait' parameter to example to ensure users see any action
failures.
Change-Id: I7dff6c3188d1877529e879adea4af9ffb8dee7c8
Closes-Bug: 1818660
Add a new appendix to detail how to use the multisite replication
features of the ceph-radosgw charm.
Change-Id: I3ac1a5ecab1449b700b2b41948ffcb5deb9d8fc1
Add instructions for migrating to using the cinder-ceph charm.
Depends-On: I93eb801ca4a166f862d5d86711d9476c61851344
Change-Id: Ibf98e98f938c186b8b7701fc763e7d1acb0521fb
Add pre-upgrade step to discover and purge and old compute service
entries; in later openstack releases, the DB model will throw
exceptions for service entries with versions less than the minimum
requirement, causing API requests to error post upgrade.
Change-Id: Id739f0f23aaadf08dff216bb9f17552deee1b0a4
Closes-Bug: 1809260
This change adds a new section to the upgrade appendix to list known
issues at the time that might not be resolvable via charm changes; i.e.
that need operator manual intervention.
Change-Id: I0250ac7dbb289e7e63703818a475f1854bf0f8a4
openstack-dev was decomissioned this night in https://review.openstack.org/621258
Update openstack-dev to openstack-discuss
Change-Id: I233cc3eb926c5bd0c0f6787e65c2bb5b74dc80f4
Closes-Bug: #1808310
Add new appendix for deployment, configuration and usage of
Octavia as part of an OpenStack Rocky deployment.
Change-Id: Id488b250055c1ec4e07821dda9d652e72e68e9ca
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.
Change-Id: I87413d8be9424db1208bbf234d8ac32bfd17f724
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
We have only a single job and that basically only runs when directory
deploy-guide gets updated. To be able to merge changes to other files,
overwrite the filelist of the job.
Change-Id: I6a1564422b72d1c116a828f3a4b17f3b0839edb7
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Introduce a minor change to the guide's build configuration file in
order to trigger the jobs and allow the patch to be tested.
Change-Id: Ib01525732af596518c57fd37a1e6b2a8ef064f66
Story: #2002586
Task: #24317
Also simplify names used and reference the latest LTS
version of Ubuntu for image creation example.
Change-Id: I8fe3fb9ac811a47558054fe368dd9b4435b82eb0
The documentation for vault suggests creating a token from the
root token specifically for the vault authorisation action.
To lock the token down the number of times the token can be used is
set. The charm action uses the token multiple times so the action
fails. Since the token is created with a relatively short ttl it
seems reasonable to remove the usage limit entirely.
Feedback from users has shown that when following the documentation
the need to unseal each vault unit individually was missed so this
instruction is now next to the unseal explanation as well as being
reiterated in the HA section.
When deploying an HA configuration etcd must support etcd3, this
requirement was lacking in the instructions so it has been added.
Change-Id: I07c233ccadd52ec7fe2fff6276e56cd88c48acf1
Closes-Bug: #1779875
Add Certificate Lifecycle Management Appendix. Since setting up
Vault is common between Encryption at Rest and Certificate
Lifecycle management, it has been moved to its own appendix
which can be referenced by EaR and CLM.
Change-Id: I867f938fc9e836334469d4fc2eb102fd32bb69e6
Provide details on how to encrypt data at rest to mitigate the
risk of data compromise in the event that a disk, server or
multiple servers are lost from a data center deployment.
Change-Id: I804e306583135a5cc770250f6eab664a737b7f56
This is so that people can contribute bugs/feature requests, or be
able to submit changes to the documentation.
Also, due to strangeness in the zuul guide merging process, added
a guid in enable-merge to get it to merge the commit.
Change-Id: Id94f89779cc8ec672ef351f84efa04e98155663e
The previous step adds a cloud named 'mymaas' which is the name
that should be used on the bootstrap command.
Change-Id: If0134032dcf8fc699257ea019f222261dd804eed
Andreas Jaeger