instack-undercloud is no longer in use by the TripleO project. Removing
the code to avoid confusion. Stable branches will continue to be
maintained for their life however no new features should be added.
Change-Id: I63a813c7c1ffd30ca30017133d31a497b77a9a4d
Blueprint: remove-instack-undercloud
-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
Now that Puppet is driving a large portion of the Undercloud installation, we
can clean up some previously used elements from the json-files.
We do have to provide some additional bits via the undercloud-install element,
such as simple dib-init-system script. This is much simpler than continuing to
use large elements from tripleo-image-elements that have other unintended
side-effects that we want to avoid.
Change-Id: I0c3626e3b4a2de3d7f1e1bc3274be4150b552a26
Alex Schultz