The external doc section wasn't indented properly, which caused it to
be included in the internal docs, causing confusion.
Change-Id: If731a14c0d28d016ef033319fc322b3f5dafcdce
Following basic deployment it isn't explicit that you must pass the
overcloud endpoint to the postconfig
Change-Id: I50c656f5269fc0493d66b4b77b16b0038ea2bc2d
The 'gate' tag used to appear on almost every test. It was removed some
time ago and 'smoke' was reclaimed to mean a basic test for all services.
Change-Id: If51bcb585833ec5d86b08247ed3e888ccceb8477
Currently there's not much detail in the introduction page, this adds
a little more overview information about the undercloud/overcloud concept
and role categories.
Change-Id: I28be6c373713ba5ffde480bfa18d1f44c22d0368
Diving into heat resources is of no use, when Ironic deployment has failed.
Starting with Ironic node-list can give important clues to whether
the deployment failed before baremetal provisioning, during it or after.
Change-Id: Idd329e71a724cd2a900cf9631f241884cdd6a2eb
This changes the documentation to reflect the seperation of
matching and introspection.
We no longer use the /etc/edeploy config in the basic flow, so we
can remove those from the ironic-discoverd element. These will
instead be included in the ahc-tools packaging.
Change-Id: If88fc8cf69aa00f81098398e7ac643ff31d57959
The mirrors.einstein.yu.edu epel mirror is not responding. We should be using
dl.fedoraproject.org instead.
Change-Id: I6b798566b46787090a9e6df53654370c7af876ad
The directions say to install the unified CLI, but the only package in
the command is python-rdomanager-oscplugin. The client is a dependency
so it will get installed, but it's potentially confusing to say one
thing and then do something different. Update the step description to
better match what's happening.
Change-Id: If74c8f3d01a4d35051cf54340a269ec95ba286c0
-Very incomplete testing right now
-Puts the password and stackrc files in the current user's home
directory during the install. Given that they now have secure
permissions and we recommend doing that anyway, I think it's fine,
but it is a non-trivial change in behavior.
This was done because it's awkward to read a root-owned file from
a Python process running as a regular user.
-Uses oslo.config instead of the bash-style answers file. A sample
conf file created by the oslo.config generator is included (for
now, although we may want to generate that dynamically at some
point). Backwards compatibility with existing answers files is
maintained for now, but is deprecated.
-Hard-codes the image path in instack-test-overcloud to . It's
difficult to extract the value from the conf file in bash (unless
they overrode the default, there's nothing for ConfigParser to read),
and since it's just a simple sanity test script I think that's okay,
at least for now.
Change-Id: I09270997dea7fdad2b40dfb303967ff425b55a9b
...and run it optionally from instack-deploy-overcloud.
Co-Authored-By: Imre Farkas <ifarkas@redhat.com>
Change-Id: I5975345d6aa3f3e9fc92f62cd1cc908f2d21679b
