This PR will also be used to generate a 2023.2 version of the
Deploy Guide.
Change-Id: I25f24ffe61e0d6293fd6b1efe3287ef7e48da489
Signed-off-by: Peter Matulis <peter.matulis@canonical.com>
* Update channels for a Jammy Bobcat cloud (using 1.8 track for vault at
this time; may change to 1.10)
* Update any command output accordingly
* Add an image related to MAAS health check
* Move the dashboard section from the install page to the configure page
- users may try an operation and it will not work until configuration
is complete
* Reword the section on software sources to be leaner and clearer
* Improve some links - in particular, use charm links to default
channels in the Charmhub in order to get useful documentation
Change-Id: I86e1b2ce1d4b5bc517fe84b9149c0776660d9bcf
Signed-off-by: Peter Matulis <peter.matulis@canonical.com>
Lower the cloud node disk requirements from 3 to 2. This
is also in agreement with the Charm Guide golden path.
Change-Id: I65d63ee8dce90901a739ec8d8bd3f0c7b993deee
Signed-off-by: Peter Matulis <peter.matulis@canonical.com>
Add variables to non-admin user cloud rc file.
Change-Id: I6e714360b2bd0102b5381c8a2dbe05988f8f8118
Signed-off-by: Peter Matulis <peter.matulis@canonical.com>
Like the Charm Guide Getting Started tutorial, use a local
openrc file as opposed to downloading it from the openstack-bundes
repository.
Make this openrc file support Juju 3. It's the same file
recently reviwed in a similar Charm Guide PR.
Related-To: I74315e5a64902d7e96e3557cb99d89493e62ad4c
Change-Id: I3d9b1badda3c79ea2149f5d780c7e25084fd06e2
Signed-off-by: Peter Matulis <peter.matulis@canonical.com>
Subsitute commands and add a pointer for Juju 2.9 users to the central
explanatory page in the Charm Guide.
The Juju version stated as being used in this guide is still of the 2.9
series. This will change when the guide is soon updated for 2023.2.
Change-Id: I807e2824ccae7f87ddb21503d35c417e89562b6e
Signed-off-by: Peter Matulis <peter.matulis@canonical.com>
The whole guide assumes Juju 2.9 as the top page states:
> The software versions used in this guide are as follows:
> * Ubuntu 22.04 LTS (Jammy) for the Juju client, Juju controller, and
> all cloud nodes (including containers)
> * MAAS 3.3.3
> * Juju 2.9.43
> * OpenStack 2023.1 (Antelope)
Now that the default channel of Juju snap is 3.1, we should pin to 2.9
in the short term. Otherwise the first user experience is not going to
be smooth due to backward-incompatible commands such as `juju
add-relation` or `juju run`.
Closes-Bug: #2029323
Change-Id: Ia5eb711de1ef60443311413477460620de17f77d
This PR will be used to generate a 2023.1 version of
this guide by a follow-up backport of it to the
newly-created 2023.1 stable branch.
Change-Id: I1ddc87821febcdf9bbce0d26b38c1cac37b302e9
Update Juju and MAAS versions.
Make some minor text improvements, including links to
charms.
Use channel-specific Charmhub links for charms
Change-Id: I04ab75a56f4311ffb7ec49f4627b75e5d24ef4c6
Slightly reword the text describing how to determine the
value of the osd-devices option (ceph-osd charm).
Closes-Bug: #2008219
Change-Id: I7512d62574f60db3f415ae39757b2a158d559527
Remove some deprecation build warnings from this
guide.
This PR will also be used to generate an OpenStack Zed
version of the guide.
Change-Id: Ie776798f96b0de8d17a08e45e7a4d1e42b84359b
I was forced to use an environment different from what I
normally use, hence the changes to infrastructure values.
Also closes a bug.
Closes-Bug: #2006729
Change-Id: I5d05c7d532b3433c8c53061f8a1727ab6c81e6e9
On Jammy hosts the docs will not build due to an
incompatibility between Sphinx and Python 3.10.
Increase Sphinx version in requirements.txt to at
least 4.2.
Change-Id: I34d9c1a6baa042535ea74758c9a4b51f97e6965a
For internal links to the deploy-guide or, via intersphinx, to
the charm-guide use direct Sphinx links (instead of manual or
manual+redirected URLs).
Change-Id: I509966b2e58c7cd4e7943fbabb530d7178a93118
Make it clearer how software versions are selected for
charms and for cloud services.
Closes-Bug: #1974481
Change-Id: Idcb64aa12ff7e9069d8b0cf20a008ca55ff7ac78
A Juju bug citation (and its workaround) was removed.
LP #1966664 is gnarly and is not completely resolved, but it no
longer affects this guide.
During the testing of the above updated software was used so
update the versions stated in the guide. In particular, a Jammy
Juju controller was used.
Related-Bug: #1966664
Related-Bug: #1971616
Change-Id: I0276861e672b24e0c886a64b5a04bb8e30caf45d
The migration of non-deployment content to the charm-guide
is now complete. This PR is a consequence of that change. It
introduces some rewording and restructuring. In particular,
the installation-overview page is folded into the main
landing page. This PR closes a bug in the process.
Closes-Bug: #1976369
Change-Id: I5e31bd0e340662b52607bc72a089bd7c08190741
Remove the upgrade pages as they are being migrated to
the charm-guide.
Add HTML redirects (and tests) for the more important
pages.
Depends-On: I31ecf2b885d808802fc83a0a8414032764b20e1d
Change-Id: I446a5849cee97351e21ce2435cede2a742d3a9e0
Remove the issues and procedures pages as they are
being migrated to the charm-guide.
Some links need to be changed as a consequence.
Add HTML redirects (and tests) for the more important
pages. A previous redirect was only modified as it was
put into place only very recently.
Depends-On: Iba9231ba501253692acba9f059a913b54226cb5e
Change-Id: Ifd70efb85eba841dd74e8d0b453d8f63f81c16e0
Centralise all noteworthy issues and procedures into a
single page. This will make it much simpler for users to
find important information and will reduce the necessity
to include multiple links in many pages.
Move the placement charm procedure to its own special charm
procedure page and link to it from the stein:train upgrade
path page.
The new page is currently in the Upgrades section but this
is temporary. It will soon be migrated to the charm-guide
where it will be placed under the Project section.
Include an HTML redirect (and test) for the former
upgrade-special page.
Change-Id: I3a8abe0d6b82447ca6d2883065cb1a2ce6d906b9
Fix an HTML redirect that was recently put in place
for a migration of the Networking pages.
Fix a broken link for the project to build.
Change-Id: I99b0287fcb758e1ec8fac7a8f6cf31d76f500107
The practice of orphaning pages should be an exception.
Doing so removes build checks (e.g. link checking).
Change-Id: I12b892ca0f558ad461435d3bb6c16e52c1d1c6e2
Remove the Security pages as they are being migrated
to the charm-guide.
Some links need to be changed as a consequence.
Add HTML redirects (and tests).
The security overview page was completely removed
(not migrated) as its contents did not warrant a page
of its own. The little it had will be incorporated at
a later date.
Change-Id: If1bcbb39b4186fac7073f77bc0dacdac4294d3ff
Remove the Networking pages as they are being migrated
to the charm-guide.
Some links need to be changed as a consequence.
Add HTML redirects (and tests).
Depends-On: I39304470b71742a6cf01aa04cd80e2c2de1cdf9f
Change-Id: Ibc9db2ac43c24f9568d0a2446907ba517856a2df
The OVN documentation requires refactoring.
The first step is to feature the ML2+OVS to ML2+OVN
migration as a special charm procedure.
The change is a strict move (not a review) with the
exception of some link and header management and an
introductory paragraph for the new page.
Change-Id: I3ba6111364bc7703b50cb21f1c0e25e2cafaa8e3
The current master branch has a couple of spelling mistakes.
This commit includes the correction to the following doc:
charm-deployment-guide/deploy-guide/source/app-certificate-management.rst
'Notably' was misspelled as 'Notebly'.
'Existing' was misspelled as 'Exisitng.
Change-Id: I9f46b1d498815bf557c050c24ffee846ae39f706
It is common for users to not have the same
network interface name available across all MAAS
nodes for ovn-chassis units. This PR outlines the
use of hardware addresses.
Change-Id: I84cc572441f55c5e38f4bb99613be2514bddd86a
Add the steps for swtiching between self-signed CA certificate
and third-party intermediate CA certificate after Vault charm
deployment. A note asking user to check the level of authorization
of the intermediate CA certificate is also added.
Closes-Bug: #1913289
Change-Id: I9e8ca51759650d211f491457cb0d0fc0040358e8
Add the intersphinx Sphinx extension to enable seamless
linking from the charm-guide.
This is already enabled for the charm-guide - for seamless
linking from this guide (deploy-guide).
Change-Id: I36442bfc8ff9267786cce87b32dfff2348c30f57
Improve and streamline upgrade overview text.
In particular, move the topology information to the
upgrade-overview page.
Related-Bug: #1929091
Change-Id: If8bb494966915c34f50a23937f3b500ed99c7049
Add dedicated OpenStack upgrade migration path pages to
make it clearer for upgraders. Doing so also removes
non-relevant text from the general upgrade-issues page.
Add a redirect to account for the deleted placement
charm special procedure page.
Closes-Bug: #1970272
Change-Id: Ibd09e9e0d66a6f9e152f37c6ac675eed35c97bde
Remove the storage pages as they are being migrated
to the charm-guide.
Add HTML redirects (and tests) as a consequence.
Depends-On: I933916e1a77e108ec255289e562149240ba09470
Change-Id: I20ffd8b97cfdac37ce83dc9fab35be236999e1e5
Remove the Compute pages as they are being migrated
to the charm-guide.
Add HTML redirects (and tests) as a consequence.
Change-Id: Idf777582fcb902dcd1f603d04c8f872c579460ff