Commit Graph

12 Commits

Author SHA1 Message Date
Ghanshyam Mann 8325044e7a Retire Tripleo: remove repo content
TripleO project is retiring
- https://review.opendev.org/c/openstack/governance/+/905145

this commit remove the content of this project repo

Change-Id: Ib988f3b567e31c2b9402f41e5dd222b7fc006756
2024-02-24 11:41:49 -08:00
Ben Nemec cd32029388 Stop using setup.py [test|testr|build_sphinx]
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
2019-01-16 13:21:28 -06:00
Ben Nemec 93d2f4f56c Support deploying with multiple Heat environments
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.
2017-08-09 10:03:38 -05:00
Ben Nemec 280854393c Add a few more .gitignores
A few other files that are in my local environment but shouldn't
go into git.
2017-03-07 16:05:49 -06:00
Ben Nemec d0a5bdfe65 Ignore all env*.yaml files
Deploying with --id creates more of these and we don't want to
track them in git.
2017-03-07 16:05:49 -06:00
Ben Nemec 713e5984a1 Ignore doc/build directory 2017-02-16 16:24:19 -06:00
Ben Nemec 9fe31995c5 Reorganize into package and add tox for testing
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.
2016-07-14 12:23:41 -05:00
Steve Baker 7c44c7fc6a Add net-iso-gen.py generated network templates 2016-04-07 13:06:03 +12:00
Ben Nemec 5217e54102 Ignore bmc_bm_pairs file 2015-11-18 10:34:02 -06:00
Ben Nemec a329325fa4 Remove controller config from templates
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.
2015-11-17 16:36:36 -06:00
Ben Nemec af16ed882a Actually add quintupleo files
Forgot to actually include the new templates in the previous commit.
This adds them and updates all of the templates to use a single
env file.
2015-09-30 23:47:20 -05:00
Ben Nemec 425a9a3830 Initial import 2015-07-24 14:18:51 -05:00