diff options
| -rw-r--r-- | docs/rethinkeverything/README.md | 2 | ||||
| -rw-r--r-- | docs/rethinkeverything/ansible/README.md | 22 |
2 files changed, 23 insertions, 1 deletions
diff --git a/docs/rethinkeverything/README.md b/docs/rethinkeverything/README.md index c2813eb..85ef757 100644 --- a/docs/rethinkeverything/README.md +++ b/docs/rethinkeverything/README.md @@ -1,6 +1,6 @@ # Things that need to be rethought - [canonical](https://www.digithink.com/rethinkeverything/no-canonical/) -- ansible +- [ansible](https://www.digithink.com/rethinkeverything/ansible/) - git mirroring - remote backups - vpn/tailscale diff --git a/docs/rethinkeverything/ansible/README.md b/docs/rethinkeverything/ansible/README.md new file mode 100644 index 0000000..37d624c --- /dev/null +++ b/docs/rethinkeverything/ansible/README.md @@ -0,0 +1,22 @@ +# Anisible vs Puppet vs pylxd vs incus. +*THIS IS VERY MUCH A WORK IN PROGRESS* + +Moving to incus pretty much broke the cloud.init+ansible pattern I developed when I started working with lxd. On the otherhand these patterns are pretty disfunctional *(unusable by others, tempermental, usw)* + +## The point. +Looking at this provides the opportunity to do two things. + +1. 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. +## Getting to it. +### Ansible and lxd. +### Use Cases. +### Initialization +### Ad Hoc Updates (ssh-keys root passwds usw) |