diff --git a/doc/source/advanced_deployment/profile_matching.rst b/doc/source/advanced_deployment/profile_matching.rst index b5644d47d..9626940d6 100644 --- a/doc/source/advanced_deployment/profile_matching.rst +++ b/doc/source/advanced_deployment/profile_matching.rst @@ -40,7 +40,7 @@ Accessing additional introspection data --------------------------------------- Every introspection run (as described in -:doc:`../basic_deployment/basic_deployment`) collects a lot of additional +:doc:`../basic_deployment/basic_deployment_cli`) collects a lot of additional facts about the hardware and puts them as JSON in Swift. Swift container name is ``ironic-inspector`` and can be modified in **/etc/ironic-discoverd/discoverd.conf**. Swift object name is stored under diff --git a/doc/source/post_deployment/migration.rst b/doc/source/post_deployment/migration.rst index 0309ae40a..42c9e40ac 100644 --- a/doc/source/post_deployment/migration.rst +++ b/doc/source/post_deployment/migration.rst @@ -48,6 +48,6 @@ Manager. First, register and introspect the additional hardware with Ironic just as you would have done when :doc:`initially deploying -<../basic_deployment/basic_deployment>` the cloud with RDO Manager. Then +<../basic_deployment/basic_deployment_cli>` the cloud with RDO Manager. Then :doc:`scale out ` the 'Compute' role in the new overcloud to start making use of the additional capacity.