[14:48] <holmanb> Ramseslll: It's possible, but not a well-tested use-case for cloud-init directly. I suggest looking into subiquity's autoinstall config options (which uses cloud-init indirectly).
[18:59] <blackboxsw> holmanb: I'm looking over your ansible PR. Some interesting thoughts here, I think it's worth us carving up a small spec on ansible use-cases w/ cloud-init so we can brainstorm about how we want ansible config to play in the control node/management node deployments as well. (which would inform our documentation too) Maybe it's worth us pushing a PR against ansible as well for cloud-init fact support upstream built-in.
[19:00] <blackboxsw> But we can chat about that future work separate from the PR i guess  https://github.com/canonical/cloud-init/pull/1579
[19:00] <ubottu> Pull 1579 in canonical/cloud-init "Add Ansible Config Module" [Open]
[19:12] <holmanb> blackboxsw: Big thanks for the feedback and review
[19:15] <holmanb> blackboxsw: This approach was taken following previous discussions about this work because it fits cleanly into cloud-init's scope (configure an instance on bringup), unlike the the agentless "common use case" that ansible recommends (configure N nodes simultaneously). Happy to work on a spec for discussions regarding preconfiguring an ansible manager node and/or expanding the cloud-init scope. That definitely requires outside 
[19:15] <holmanb> input, agreed +1
[21:23] <phunyguy> holmanb: hey, not sure if you replied... had some znc issues over here so I don't have the backscroll.  Hope you had a fun weekend and made it back with all your fingers and toes.