This website requires JavaScript.
Explore
Get Started
opendev
/
system-config
Code
Issues
Proposed changes
5e8d704278
Branches
Tags
View all branches
system-config
/
playbooks
/
roles
/
base
/
users
/
defaults
/
main.yaml
5 lines
81 B
YAML
Raw
Normal View
History
Unescape
Escape
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
all_users
:
{}
Disable distro cloud image users more forcefully This updates our user management system to use the userdel --force flag when disabling and removing distro cloud image users like 'ubuntu', 'centos' and 'admin'. The reason for this is when we switch from using the distro user to boot strap launchnode over to root the distro user may still have running processes that prevent userdel from succeeding. This should address that problem and delete the user anyway. The last step in the launch node process is to reboot which should clear out any stale processes. We don't do this for normal users as they aren't removed at node launch time and this may be too forceful for them. It would be better for us to error in that case and clean up any stale processes. Change-Id: I79caf2a996566ecaec4cb4a70941bb3f03a5fb73
2022-10-03 09:21:42 -07:00
disabled_distro_cloud_users
:
[
]
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
disabled_users
:
[
]
extra_users
:
[
]
Copy Permalink