These role task inclusions force a linear-like sequence
and result in a lot of unnecessary skipped tasks. This
takes extra time, and causes a lot of log noise which
makes debugging more difficult.
Given that a host can ever only have a single role, it
makes more sense to just include the applicable role
task file if it exists.
Change-Id: Id2cadceaaf563dc94fcf2d8ce0f0cb9054a65d40
Add additional commonly ignored files to .gitignore. The additional
entries were copied from what is already configured in
python-tripleoclient. Add these to .gitignore has the additional benefit
of these files also being ignored by ansible-lint, since ansible-lint
uses git ls-files.
Change-Id: Ibad5463c7e7c744f068609d62ccd4d3b0fd6eab0
Signed-off-by: James Slagle <jslagle@redhat.com>
The environments/deployed-network-environment.j2.yaml template will
generate an environment file based entirely off of the used roles data
and network data files that can be used in place of the generated
environments from the "overcloud network" commands.
For environments without Neutron, the generated file is easier than
having to define all these parameter values manually.
Change-Id: If839245b306370095ad21d753e9f5d4c98f1740c
Signed-off-by: James Slagle <jslagle@redhat.com>
The environment
environments/deployed-server-deployed-neutron-ports.yaml, the
deployed-neutron-port.yaml template, and DeployedServerPortMap parameter
are deprecated in favor of NodePortMap, ControlPlaneVipData, and
VipPortMap, which can be used with the generated
environments/deployed-ports.yaml.
Change-Id: Ib59bb985fe15f612f93a33b1a688427e684654dd
Signed-off-by: James Slagle <jslagle@redhat.com>
- enable run of ansible-lint, with a temporary set of excludes
- fixes two problems reported by ansible-linter
Change-Id: Ibbe23db8fd5ac1008109f50f514df96686b0fa19
Bug: #1921409
- fixed bindep to allow execution under fedora
- fixed flake8 config to use officially recommended use patterns
- assured that git does not report dirty after running tox (both
pep8 and tht environments where breaking this by creating untracked
files). tox-extra plugin addition will prevent future regressions.
Change-Id: I4137056853f8c5f1c2304bfb6ec1188a82b12130
Bug: #1921409
These resources aren't used anymore and are leftovers from previous Heat
resources which don't exist anymore.
Change-Id: I4b33df191c4eb3cd961bbdbaf6ef28844de6d1a9
In line with [1] removing references to developer tools in
.gitignore.
[1] https://review.openstack.org/#/c/592520/
Change-Id: Ie25972a89efb8314d2632c804bca0f37c7f2630b
This is a tool to automate the generation of our sample environment
files. It takes a yaml file as input, and based on the environments
defined in that file generates a number of sample environment files
from the parameters in the Heat templates. A tox genconfig target
is added that mirrors how the other OpenStack services generate
their sample config files.
A description of the available options for the input file is
provided in a README file in the sample-env-generator directory.
In this commit only a single sample config is provided as a basic
example of how the tool works, but subsequent commits will add
more generated sample configs.
Change-Id: I855f33a61bba5337d844555a7c41b633b3327f7a
bp: environment-generator
This patch adds a local version of our template processing
routine so that developers can more quickly view the templates
that are actually getting generated. I've noticed multiple developers
now do a full deployment with 'overcloud deploy' only to download
the swift container with the generated templates. This simple task
avoids that step by allowing developers to generate it locally.
It also aims to preserve the ability to use t-h-t templates directly
with Heat (instead of going through Mistral) should users wish to do that.
The new undercloud heat installer requires the ability to generate
templates without requiring Mistral and Swift to do so.
Ideally the Mistral API workflow would use this same code
so perhaps in the future we might modify that routine to:
-download swift tarball containing the templates
-run this local routine that lives in t-h-t
-re-upload the tarball of templates to the swift container
Change-Id: Ie664c9c5f455b7320a58a26f35bc403355408d9b
Proper VLAN support requires adding the IP address to a new device,
rather than br-ex/br-ctlplane. This is added in the
tripleo-image-elements change https://review.openstack.org/103449
(I3f77f72ac623792e844dbb4d501b6ab269141f8e) and here we just expose
it with appropriate glue to get the IP address from Neutron.
With this we can now describe a VLAN public interface scenario
to the undercloud and overcloud control planes.
Change-Id: I4d2194fc813aebb0708d6fddf4f05bae5f091fd8
There is no need for a tuskar-specific undercloud template. Tuskar is
installed via elements just like any other undercloud service.
This template is not being used in devtest and I'm not sure it ever has
been.
Change-Id: I531d927b1984873b32f440d33a130788670f7cd9
To support the changes to the cinder element to allow the nfs
backend to be utilized, this template has been added to show
the usage of the nfs_shares key in the cinder metadata.
The value is a list of strings containing share addresses.
This change is added to facilitate an example to test
the cinder element change: https://review.openstack.org/#/c/74563/
You may setup the nfs server manually or use the nfs-server
element at https://review.openstack.org/#/c/74712/.
Change-Id: I5b6cb118b34421ea07a81ed1fe68db24b1d4f19d
Now that merge.py is invokable from another script
(Ia6b6416fe10358d23f2b120283eecaf4c1178cfd) and from comments at that
review, it makes sense to offer a nicer way to consume the merge
functionality.
Once you git clone tripleo-heat-templates you can python setup.py
install and get /usr/bin/tripleo_heat_merge as well as a
tripleo_heat_merge package in python2.7/site-packages.
Makefile edits required because we moved merge.py into the
tripleo_heat_merge directory for the packaging.
Change-Id: I587fa7a826f93f89e8e5c266af7f5765438fe738
This will require some changes to our devtest scripts
and TOCI to ensure we build the overcloud-vm template
before attempting to use it.
Change-Id: I14b5e4a0ccf5f18429bfc33e527bdb4760b8d1a3
merge.py is undocumented and untested, which is undesirable, as it does
not seem to be going away any time soon.
Change-Id: I7e4870e58a32c567e5947b9a48893b8210ad4d65