When running ansible we need to pass a specific version of
project-config through to puppet from ansible. Do this via the
project_config_ref fact that the puppet role in ansible understands.
Depends-On: Id99c3c2c20764ed4ba4259bd53f8067289374403
Change-Id: I88995c81c13080d913bac239a7635619cdc34441
The current set of runs make the fleet depend on all git changes
working. The only thing we actually care about is that gerrit doesn't
get updated if git fails.
Change-Id: Id488e14c7dbaddfbffece7b1d8ef65f06b3688d8
Now that the migration to puppetmaster.openstack.org is complete,
remove duplicate references to ci-puppetmaster.openstack.org and
also take out the temporary Puppet v2 vs v3 compatibility code used
to choose between them.
Change-Id: I32d48e844ab1872391f9f2a4e233804b7a29feb5
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
Sometimes we need to clean the workspaces. While we have a command
documented, go ahead and make a playbook for it.
Change-Id: I1887dec24563811a71157c000b2d8ae9b7850d6a
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
