- Oct 07, 2024
-
-
Pierre Riteau authored
Change-Id: Ic99f2ac8f8052e6e0eaaa75650f465ff079f69cb
-
- Dec 14, 2022
-
-
Mark Goddard authored
Kayobe provides various roles and plugins in the ansible directory. These are accessible to Kayobe playbooks in the same directory. In some cases it can be useful to use these items from Kayobe custom playbooks, however they cannot since they reside in a different directory. Typically we work around this by symlinking to the relevant directory from the directory containing the custom playbook. This is not an elegant workaround, and has assumptions about the relative paths of the Kayobe configuration and virtual environment in which Kayobe is installed. This change adds the Kayobe role, collection, and plugin paths to the relevant Ansible lookup paths using environment variables. This allows custom playbooks to use these items. Also added to the lookup paths are roles, collections and plugins in Kayobe configuration in the etc/kayobe/ansible/ directory. This removes the limitation of playbooks needing to reside in the same directory as those items in order to use them. We import the Ansible configuration settings module directly, since it avoids replicating the configuration logic. Story: 2010280 Task: 46234 Change-Id: I2fb2b4d7ed937e0184a62b0f119659569448f8df
-
- Dec 12, 2022
-
-
as0 authored
Running multiple playbooks do not require a comma to added between them. Amend docs with a minor fix to improve readability/usability. Change-Id: I17e1c50f63bbbd4df73bd7a76769bde942cc024a
-
- Oct 04, 2022
-
-
Alex-Welsh authored
adds the argument --skip-hooks/-sh which will stop the execution of hooked ansible playbooks. Either a pattern can be specified to match against or hook execution can be stopped altogether with "all" Story: 2009241 Task: 43390 Change-Id: I4f2176aa056fec62e31d07140e3d05779480a93d
-
- Sep 08, 2022
-
-
Mark Goddard authored
The group variables originally in ansible/group_vars/ were playbook group variables, due to being adjacent to the playbooks. Typically they provided default values for global variables in the all group, as well as some more specific groups. This has worked fairly well, but results in (at least) a couple of problems. 1. The default variable precedence rules mean that these playbook group variables have a higher precedence than inventory group variables (for a given group). This can make it challenging to override playbook group variables in the inventory in Kayobe configuration. 2. Any playbook run by Kayobe must be in the same directory as the playbook group variables in order to use them. Given that they include variables required for connectivity such as ansible_host and ansible_user, this is quite critical. For Kayobe custom playbooks, we work around this by symlinking to the group_vars directory from the directory containing the custom playbook. This is not an elegant workaround, and has assumptions about the relative paths of the Kayobe configuration and virtual environment in which Kayobe is installed. Story: 2010280 Task: 46233 Change-Id: Ifea5c7e73f6f410f96a7398bfd349d1f631d9fc0
-
- Oct 04, 2021
-
-
Will Szumski authored
This change allows you to define additional VMs to deploy on the seed-hypervisor. Co-authored-by:
Piotr Parczewski <piotr@stackhpc.com> Co-authored-by:
Will Szumski <will@stackhpc.com> Co-authored-by:
Mark Goddard <mark@stackhpc.com> Story: 2008741 Task: 42095 Change-Id: I8055fc5eb0a9edadcb35767303c659922f2d07ca
-
- Sep 27, 2021
-
-
Mark Goddard authored
This change adds support for installing Ansible collections via requirements.yml in Kayobe or Kayobe config. Story: 2008391 Task: 41315 Change-Id: I764ff019a18266b593add7ab80ee095d7d07a869
-
- Mar 25, 2021
-
-
Pierre Riteau authored
Change-Id: If51a715bc9f68fbf750baeecb0e8415178bb5641
-
- Jul 10, 2020
-
-
Pierre Riteau authored
The original instructions used an absolute path for the symbolic link, which would not be valid if the kayobe-config repository was cloned in a different location. Change-Id: Id595a12845f445203993fc6ed567e7f7f393742f
-
- May 26, 2020
-
-
Will Szumski authored
Sometimes there is a need to develop site specific playbooks. Currently, it is necessary to manually invoke these at the right point during the deployment. Adding the ability to automatically run these custom playbooks will reduce the chance of running these playbooks at the wrong point or forgetting to run them at all. Change-Id: I1ae0f1f94665925326c8b1869dd75038f6f1b87d Story: 2001663 Task: 12606
-
- Oct 31, 2019
-
-
Mark Goddard authored
Change-Id: I358585260cc85fb1d364d2e246656557a2398ef9
-
- Jul 11, 2018
-
-
Will Miller authored
Ensure all references to the Ansible control host are worded as such, to ensure consistency and avoid potential confusion with the OpenStack controllers. Change-Id: Id92e537ccbfdd55287b8eae296f649640c70ce17
-
- May 21, 2018
-
-
Mark Goddard authored
Change-Id: Ia00bd15d037ce3f1db66a953f9c327074e509627 Story: 2001663 Task: 12599
-