Closed fititnt closed 4 years ago
As MVP, this is the actual folder on v0.8.6-alpha
:
# fititnt at bravo in /alligo/code/fititnt/ap-application-load-balancer/tasks/bootstrap on git:master x [3:20:32]
$ ls -l
total 52
drwxrwxr-x 2 fititnt fititnt 4096 Dez 8 12:14 alb-minimal
drwxrwxr-x 2 fititnt fititnt 4096 Dez 15 10:08 alb-standard
drwxrwxr-x 2 fititnt fititnt 4096 Dez 8 07:01 ansible-control-node
drwxrwxr-x 2 fititnt fititnt 4096 Dez 8 02:11 basic-tools
drwxrwxr-x 2 fititnt fititnt 4096 Dez 8 01:54 extra-tools
drwxrwxr-x 2 fititnt fititnt 4096 Dez 14 09:52 lua
-rw-rw-r-- 1 fititnt fititnt 3668 Dez 13 17:48 main.yml
drwxrwxr-x 2 fititnt fititnt 4096 Dez 7 02:22 really-minimal-dependencies
drwxrwxr-x 2 fititnt fititnt 4096 Dez 9 08:44 repositories-3rd-party
drwxrwxr-x 2 fititnt fititnt 4096 Dez 8 03:21 repositories-common-sense
drwxrwxr-x 2 fititnt fititnt 4096 Dez 8 03:10 repositories-from-sources
drwxrwxr-x 2 fititnt fititnt 4096 Dez 10 08:37 updated-system
drwxrwxr-x 2 fititnt fititnt 4096 Dez 7 06:12 very-early-abort-checks
The AP-ALB v0.8.x adaptations to support RHEL/CentOS 8 family and design changes to allow flexibility even for non-tested OSs #34 was the big reason for this group of tasks get on this way.
Related:
11 (old)
15 (maybe near same strategy)
Instead of the optional
common
, since with more OSs things can get complicated, a new, this time strongly recommended, group of tasks could be responsible for tasks that are really, really need on very start of a node, and may not be required to run so often.One example would be a user, with
gather_facts: no
, be able to install at least the python on remote host, or get basic info of that could go wrong.After this, maybe the idea would be make sure that, for the packages one node is interested in setup, all repositories that would need to be prepared already exist.
And then, maybe, the tasks related to create directories, that today are on non-subfolders like the
tasks/alb-init.yml
, could be moved to this group.