system-config/playbooks/set-hostnames.yaml

- hosts: "!disabled"
  gather_facts: false
  roles:
    - set-hostname
Rearrange set-hostnames and cloud-init removal In launch-node, we run two playbooks that aren't part of base. One sets the system's hostname and removes cloud-init, the other runs unattended update. We need to run the hostname setting in our functional tests so that the hosts behave as expected, but running the cloud-init removal is a little weird, since our test nodes already don't have it. Make it so that set-hostname actually just sets the hostname, and then run it in run-base. For running puppet, we need the host to have the correct hostname. Move cloud-init removal to the base-server role. Also move the autoremove into base-server, since it's probably a nice way to get rid of excess things. Change-Id: I53cb8c515444a7d73b839e799c5794b067429daa 2020-04-19 17:20:10 -05:00			`- hosts: "!disabled"`
Don't gather facts in set-hostnames It's a waste of energy Change-Id: I8e456b10eec08fad4741ed51554a8c8c67fc7cbf 2019-05-08 14:20:49 +00:00			`gather_facts: false`
Add base playbooks and roles to bootstrap a new server We want to launch a new bastion host to run ansible on. Because we're working on the transition to ansible, it seems like being able to do that without needing puppet would be nice. This gets user management, base repo setup and whatnot installed. It doesn't remove them from the existing puppet, nor does it change the way we're calling anything that currently exists. Add bridge.openstack.org to the disabled group so that we don't try to run puppet on it. Change-Id: I3165423753009c639d9d2e2ed7d9adbe70360932 2018-07-31 11:53:35 -05:00			`roles:`
			`- set-hostname`