Playbook should be split into some atomic tasks #12

Open
opened 2019-06-30 00:51:48 +00:00 by ubergeek · 3 comments

Some of the tasks in the playbook don't need to run every time. ie, user provisioning.

So, we should keep site.yml as being the play of all play, but break down the users into an atomic play, break down the webserver stuff atomically, and probably packages.

Some of the tasks in the playbook don't need to run every time. ie, user provisioning. So, we should keep site.yml as being the play of all play, but break down the users into an atomic play, break down the webserver stuff atomically, and probably packages.
ubergeek added the
enhancement
label 2019-06-30 00:55:50 +00:00
deepend self-assigned this 2023-07-26 21:31:53 +00:00
Naglfar was assigned by deepend 2023-07-26 21:31:53 +00:00
Owner

What is the best approach to doing just this. User creation for sure should be separate.. But not sure how much else should be separated out.

What is the best approach to doing just this. User creation for sure should be separate.. But not sure how much else should be separated out.
Author

I think by web server configs (web/gopher/etc, in one go), user management, and maybe shell-server required things. ie, I can update web front end, or new/removed users, or fix up the environment for people to log in.

Past that is an exercise, if you want, to break everything into atomic tasks, that eventually roll into one master playbook, to rebuild the entire server (Should the need arise)

I think by web server configs (web/gopher/etc, in one go), user management, and maybe shell-server required things. ie, I can update web front end, or new/removed users, or fix up the environment for people to log in. Past that is an exercise, if you want, to break everything into atomic tasks, that eventually roll into one master playbook, to rebuild the entire server (Should the need arise)
Owner

How does that work with ansible. I seem to be somewhat grasping what is currently setup. But not sure the best way things could be split up. Should it just be more files like the site.yml that only runs portions of the ansible script instead of all of it. Or is it done in some other way. Sorry very green when it comes to ansible.

How does that work with ansible. I seem to be somewhat grasping what is currently setup. But not sure the best way things could be split up. Should it just be more files like the site.yml that only runs portions of the ansible script instead of all of it. Or is it done in some other way. Sorry very green when it comes to ansible.
This repo is archived. You cannot comment on issues.
No description provided.