diff options
| author | D Delmar Davis <don@suspectdevices.com> | 2025-02-14 23:29:51 -0800 |
|---|---|---|
| committer | D Delmar Davis <don@suspectdevices.com> | 2025-02-14 23:29:51 -0800 |
| commit | 493bd61df9c3ff71547f8aca9c16952790cd5d93 (patch) | |
| tree | e61b8eea7e8ef123b75fdc76f9807ec324fc27d8 | |
| parent | 4e0b9c8319bd54985d6bb9f1eae0719b385031fb (diff) | |
This is the way.
| -rw-r--r-- | docs/rethinkeverything/ansible/README.md | 20 |
1 files changed, 12 insertions, 8 deletions
diff --git a/docs/rethinkeverything/ansible/README.md b/docs/rethinkeverything/ansible/README.md index 37d624c..75e5428 100644 --- a/docs/rethinkeverything/ansible/README.md +++ b/docs/rethinkeverything/ansible/README.md @@ -6,15 +6,19 @@ Moving to incus pretty much broke the cloud.init+ansible pattern I developed whe ## The point. Looking at this provides the opportunity to do two things. -1. Fix the pattern. +## Fix the pattern. - 1. Look at alternative toolsets - 2. Define what we are trying to achieve. - 1. Update containers in our environment centrally. - 2. Maintain the best security model. - 3. Initialize containers with the tools/configurations we want universally (python3, nano, ssh, usw/ssh-keys,admin user, usw) - 3. Impliment the desired outcomes using each of the tools based on the goals above. - 4. Select the best toolset and patterns. +- Define what we are trying to achieve. + - Update containers in our environment centrally. + - Maintain the best security model. + - for the colo + - for the house lan + - Look at alternative toolsets + - test each of tool sets + - Initialize and update containers with the tools/configurations we want universaly (python3, nano, ssh, usw/ssh-keys,admin user, usw) + - Update the containers +- Impliment the desired outcomes using each of the tools based on the goals above. +- Select the best toolset and patterns and start using them. ## Getting to it. ### Ansible and lxd. ### Use Cases. |