These are all deprecated. For unit testing stestr should be used
directly, and for doc builds sphinx-build should be used directly.
A couple of minor doc changes were needed to eliminate warnings.
Change-Id: Ic2e1b9d692c9b5866f888fb4c8c08bf95742764e
Big changes here. This will make it easier to deploy some of the
more advanced OVB options like network-isolation. Instead of users
having to figure out which lines in the sample env.yaml to uncomment
when deploying advanced options, they will simply be able to include
one environment file that contains all the appropriate parameters
to turn on the option.
This _should_ be backwards compatible with existing monolithic
env.yaml configurations. If it is not, that is a bug.
To create the option environments, a slightly modified copy of the
sample environment generator from tripleo-heat-templates has been
copied into the project. The sample environments should _not_ be
edited directly. Instead, the definition in the sample-env-generator
directory should be altered and the tool re-run to update the
environment.
Moves the functional code into an openstack_virtual_baremetal env
and adds a tox configuration for testing. Existing unit tests for
deploy.py are moved into the tests subpackage. Further unit tests
for the other modules will be added in followup commits.
Symlinks from the bin directory are left so the previous workflow
should continue to work as before.
Upon further reflection, I think it's more flexible and maintainable
to simply do this using a separate stack. If the prefixes are
chosen appropriately (say baremetal and baremetal_controller), the
build-nodes-json script will include all of the nodes in the json
file, so we end up with essentially the same thing, but you can
reasonably do this for an arbitrary number of different nodes types.
This also doesn't play nicely with the single BMC changes, so that's
another motivation for making the change. We could fix the single
BMC case, but as noted above I prefer the multi-stack method
anyway.
For convenience, I added a deploy-controller script that takes its
environment configuration from a controller.yaml file instead of
env.yaml.