This commit adds the code to manage a ansible callback_plugins directory
and sets in the ansible.cfg. This will be used for adding our own
callback plugins.
Change-Id: I697a74a5dbd63e9a87913c96a3e9be93ee7860da
The version is hardcoded within the class code, preventing to
specify a specific version of Ansible for nodes using this class.
In the infracloud baremetal node I need Ansible 2.1.1.0, I will
propose a subsequent patch on system-config/site.pp after this
merges.
Change-Id: Ie4120c8744eed78022ebcc3ea696142d1a1375aa
There are two observed failures with 2.1:
* Our group hiera files are not being copied over.
* ansible_module_puppet_post_puppetdb.py causes a "MODULE FAILURE".
Change-Id: I79fd382180dfe3b024fdcdab8a5a984800fad336
Pulling inventory from puppetmaster was a neat hack, but it was also
a hack. Let's stop providing it.
Depends-On: Ic6809ed0b7014d7aebd414bf3a342e3a37eb10b6
Change-Id: I6bb66cecca8c3ddd6d2cef2a05324faa67ca98c2
In anticipation of puppet 4, start trying to deal with puppet 4 things
that can be helpfully predicted by puppet lint plugins.
This patch also fixes lint errors caught by the
puppet-lint-absolute_classname-check gem. It removes a duplicate
inclusion of the logrotate class rather than fixing its namespace
issue.
Change-Id: I263b8a80a18bc2607d547caac7e8587e2e4dd5ea
Once we have standalone ansible roles, we don't need to embed the
ansible code in the puppet module. We also don't need to delete the
existing roles path, as the follow on standalone role should go in
place, but we want the existing role to exist in the mean time.
Change-Id: I76d5cab55942beaff44ea5f289f93ff6ce772c5f
Puppet won't remove directories without force => true being set. Set it
to actually get rid of the dir.
Change-Id: I3d3486c50d291a14eb5262998234159f1b4668c1
Roles can contain embedded library code, which is how roles work when
you distribute them on ansible galaxy. Put the library there and remove
the old location to prepare for standalone modules.
Change-Id: Iaa7906f71bb0a3bc255695e72b6ae061407fa2b8
With split puppet master infrastructure ansible needs to be told which
puppetmaster to talk to. Do this by making puppetmaster a required
argument to the puppet ansible playbook.
Since we can't rely on the cert listing while this is happening also add
puppet master specific host list files which can be used to specify
which hosts talk to which puppetmaster via the new ansible playbook
feature.
Change-Id: I412c2bd6cb390d00d1b9d0e4630e75776edabbb9
If the logic is just in a role, it's hard to re-use it in a one-off
manner on the command line. By putting it into a module, we can
run:
ansible git0* -m puppet
To run puppet on the git farm, for instance.
Also, the file is completely not openstack specific, so do it in
such a way that we can submit it as a module upstream.
Change-Id: I35b2850e02ec5da2b41ad14eec9fd6d5a356bc93
Instead of a shell script looping over ssh calls, use a simple
ansible playbook. The benefit this gets is that we can then also
script ad-hoc admin tasks either via playbooks or on the command
line. We can also then get rid of the almost entirely unused
salt infrastructure.
Change-Id: I53112bd1f61d94c0521a32016c8a47c8cf9e50f7
Andreas Jaeger