We added heatclient and metalsmith requirements as part of our modules
so we need to make sure to properly capture them.
Change-Id: Ia5859ecf0822f19b9f04dda79d5b8b5eaf5220be
Paunch was removed in Victoria cycle, therefore this module isn't useful
anymore and can't work. So we need to remove it.
Change-Id: Ie1bd288ec524e025fb6e56f7bdb740ce35d6a104
We've started using tripleo-common and other client libraries in custom
ansible modules. Should be there in requirements.
Change-Id: Ib47f5a597f613f1a7638a9c16e8eb4eb7d7de369
Now, it only supports "apply" which is called by THT but later we could
add other actions that are supported by the CLI.
Example of usage:
- name: Start containers for step 1
paunch:
config: /var/lib/tripleo-config/hashed-container-startup-config-step_1.json
config_id: tripleo_step1
Co-Authored-By: Sagi Shnaidman <sshnaidm@redhat.com>
Change-Id: Iaf988eaf3136c93703aac972a0e853c98a888e65
In order to have tripleo-ansible added to global requirements
the "ansible" requirement must be removed[0]. This change
transitions the requirement from an upstream maintained file
to our tox config, which we maintained outside of requirements
and is only ever used in local testing. With this package
removed we'll be able to have tripleo-ansible part of the
global requirements sync.
[0] - https://review.opendev.org/#/c/667413/1/projects.txt
Change-Id: Icf1e636bd1fbb73fd6d06a8e43fe55bcbe482122
Signed-off-by: Kevin Carter <kecarter@redhat.com>
Alex Schultz