summaryrefslogtreecommitdiff
path: root/doc/source/user
Commit message (Collapse)AuthorAgeFilesLines
* docs: Update docs to reflect deprecation statusStephen Finucane2022-04-061-0/+6
| | | | | Change-Id: I56b862305b31916cef143494050e5e08b1ac70b1 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* PDF documentation buildAkihiro Motoki2019-10-113-9/+106
| | | | | | | | | Also reorganizes the document structure to match both HTML and PDF docs. Story: 2006100 Task: 35143 Change-Id: Ie3f38e2ecf52e6a6cbd52bb36196e6f589f1ca0f
* Microversion 2.63 - Add trusted_image_certificatesJackie Truong2018-06-151-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | This change adds a `--trusted-image-certificate-id` option to the `nova boot` and `nova rebuild` commands. This option takes in a a single trusted certificate ID. The option may be used multiple times to specify multiple trusted certificate IDs, which will be used to validate certificates in the image signature verification process. If ID values are not specified using this option, the value of the newly added OS_TRUSTED_IMAGE_CERTIFICATE_IDS environment variable will be used instead. This value will be converted into a list before being passed on. The ``nova rebuild`` command also gets a new ``--trusted-image-certificates-unset`` option to unset/reset the trusted image certificates in a server during rebuild. This is similar to unsetting key_name and user_data during rebuild. Corresponding `trusted_image_certificates` kwarg has been added to the server create and rebuild Python API bindings. Co-Authored-By: Brianna Poulos <Brianna.Poulos@jhuapl.edu> Co-Authored-By: Matt Riedemann <mriedem.os@gmail.com> Change-Id: I235541a689732826950c7b2a510d5835211120c3 Implements: blueprint nova-validate-certificates
* Update "The nova Shell Utility" in the user guideTakashi NATSUME2017-10-161-14/+35
| | | | | Change-Id: I02025f364a11b7f41935fe835407852fc37b4d87 Closes-Bug: #1723895
* doc: Create directory structure for docs migrationStephen Finucane2017-07-122-0/+75
The spec [1] recommends the following sections: - install - contributor - configuration - cli - admin - user - reference Only a few of these are useful here: - contributor - cli - user - reference Add these and populate them. [1] specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration Change-Id: I8a9ddcc915f25ebfaa1e994dba6c15883bd2715d