
This docs change will result in switching over to the workflow driven container prepare by doing the following: - Only document calling "openstack tripleo container image prepare" when testing more complex ContainerImagePrepare parameters - Remove reference to containers-default-parameters.yaml, replacing it in overcloud deploy with containers-prepare-parameter.yaml directly - For minor updates, instruct users to check the contents of containers-prepare-parameter.yaml so they know what will happen during the minor update This change does not cover major upgrades to Rocky since the major upgrade docs are still on Queens. The rocky major upgrade instructions should describe running "openstack tripleo container image prepare default" then merging the result with any customized containers-default-parameters.yaml which they had in their previous deployment (in the common case, no merging will be needed). Change-Id: I3eca2beeeacb31994cb870e8d4c5f3ba01051078 Blueprint: container-prepare-workflow
Team and repository tags
TripleO Documentation
This is the documentation source for the TripleO project. You can read the generated documentation at TripleO Docs.
You can find out more about TripleO at the TripleO Wiki.
Getting Started
Documentation for the TripleO project is hosted on the OpenStack
Gerrit site. You can view all open and resolved issues in the
openstack/tripleo-docs
project at TripleO
Reviews.
General information about contributing to the OpenStack documentation available at OpenStack Documentation Contributor Guide
Quick Start
The following is a quick set of instructions to get you up and running by building the TripleO documentation locally. The first step is to get your Python environment configured. Information on configuring is available at Python Project Guide
Next you can generate the documentation using the following command. Be sure to run all the commands from within the recently checked out repository.
tox -edocs
Now you have the documentation generated for the various available
formats from the local source. The resulting documentation will be
available within the doc/build/
directory.