provision.yaml expansion #393
Comments
|
I like the idea in principle. The problem I see is that there is no good connection from the Using existing mechanisms in litmus, setting the desired puppet collection in the
It would be great to use more of bolt's target addressing features and map provision list entries to groups and allow users to set more useful aliases. |
|
@DavidS do you have a working example of how As far as the tear_down or other tasks sometimes the |
|
@DavidS also is |
|
https://puppetlabs.github.io/litmus/Litmus-core-commands.html#provisioning-via-yaml ---
default:
provisioner: docker
images: ['litmusimage/centos:7']
centos7:
provisioner: docker
images: ['litmusimage/centos:7']
params:
param_a: someone
param_b: something
vars:
var1=value1
var2=value2
but the resulting inventory shows: ---
version: 2
groups:
- name: docker_nodes
targets: []
- name: ssh_nodes
targets:
- uri: localhost:2227
config:
transport: ssh
ssh:
user: root
password: root
port: 2227
host-key-check: false
facts:
provisioner: docker
container_name: litmusimage_centos_7-2227
platform: litmusimage/centos:7
os-release:
NAME: CentOS Linux
VERSION: 7 (Core)
ID: centos
ID_LIKE: rhel fedora
VERSION_ID: '7'
PRETTY_NAME: CentOS Linux 7 (Core)
ANSI_COLOR: 0;31
CPE_NAME: cpe:/o:centos:centos:7
HOME_URL: https://www.centos.org/
BUG_REPORT_URL: https://bugs.centos.org/
CENTOS_MANTISBT_PROJECT: CentOS-7
CENTOS_MANTISBT_PROJECT_VERSION: '7'
REDHAT_SUPPORT_PRODUCT: centos
REDHAT_SUPPORT_PRODUCT_VERSION: '7'
vars: var1=value1 var2=value2
- name: winrm_nodes
targets: []so based on that the docs need to be updated as params do not work? |
|
Currently you can specify a provision.yaml in order to provision multiple images.
What would be useful is to add a collection key to the inventory of hosts so if you just run
rake "litmus:install_agent"it would reference this provision file for a possible collection in order to provide different agent's across the inventory?Current:
Proposal:
Currently in order to accomplish this you must run:
litmus:provision_list[centos7-puppet6]followed bylitmus:agent_install[puppet6,localhost:2222]and then
litmus:provision_list[centos7-puppet6]followed bylitmus:agent_install[puppet7,localhost:2223]obviously with the target port changing this is difficult from an automation perspective
The proposal would be that by default if no key is specified for
litmus:provision_listto loop through them all as well as the same loop when it comes tolitmus:install_agent... currently both of these without keys error:provision_list:
install_agent: (From the error looks like it should be attempting to install the latest agent but fails as it can't find it)
Think it would also be useful for the
targetkey instead of having to belocalhost:222Xit could be thelist_nameso you could dopdk bundle exec rake "litmus:tear_down[centos7-puppet6]"vspdk bundle exec rake "litmus:tear_down[localhost:2222]"The text was updated successfully, but these errors were encountered: