Go to file
Jean-Philippe Evrard 82f0126248 Use sudo for role testing
There are 2 ways to realize the privilege escalation
needed for the gate jobs.

1) Editing the playbooks (and hope to not forget to
write the sudo/become lines for every role)
2) Editing the inventory and set the variable there.

I'm taking the second approach with the minimum set
of variables (become_method is sudo by default and
become_user is root by default).

Change-Id: I54b8c1489bfc46d4a03c907f4a86f0313c7778ff
2015-11-25 19:15:25 +01:00
2015-11-03 02:57:54 -06:00
2015-11-03 02:57:54 -06:00
2015-11-03 02:57:54 -06:00
2015-11-03 02:57:54 -06:00
2015-11-03 02:57:54 -06:00
2015-11-03 02:57:54 -06:00
2015-11-25 19:15:25 +01:00
2015-11-03 02:57:54 -06:00
2015-11-03 02:57:54 -06:00
2015-11-03 02:57:54 -06:00
2015-11-03 02:57:54 -06:00
2015-11-03 02:57:54 -06:00
2015-11-03 02:57:54 -06:00
2015-11-03 02:57:54 -06:00
2015-11-03 02:57:54 -06:00

OpenStack host setup

tags

openstack, host, cloud, ansible

category

*nix

Role for basic setup and configuration of a host machine for the intended purpose of use within OpenStack.

- name: Basic host setup
  hosts: "hosts"
  user: root
  roles:
    - { role: "openstack_hosts", tags: [ "openstack-hosts-setup" ] }
Description
Role openstack_hosts for OpenStack-Ansible
Readme 6.8 MiB
Languages
Jinja 59.1%
Python 40.9%