This does indeed sound interesting.
Anaconda is one of the more complex bits of software I've worked with. It does a lot various things with a fair bit of flexibility.
My thoughts after 20 seconds of reflection (aka, not thought through at all):
I wonder if it might make sense to converge on something driven by a more modern workflow and tooling? From one perspective Anaconda/Ignition are system setup tools. Might it make sense to begin leveraging some of the automation tools to do some of this setup? Or to put another way: Could anaconda/ignition begin to transition into a well defined Ansible workflow where the UI sets parameters? For as much as I love kickstart, a YAML formatted document might lend itself to templates and easier transition to/from cloud providers....
Pat
On 9/6/19 3:46 PM, Colin Walters wrote:
Hi, I wanted to link this here:
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_coreos_coreo... Most importantly starting from https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_coreos_coreo... and the most recent ones.
Would love to do some brainstorming about how we can share more code/ideas in general; I had some specific comments towards the end.
One thing not explicitly noted there is how key Ignition is to FCOS (and derivatives like RHCOS) - having a common language that works in both bare metal as well as e.g. AWS and Azure is a big deal - and today the OpenShift 4 installer and the [machine-config-operator](https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openshift_ma... ) are built heavily upon it.
Anaconda-devel-list mailing list Anaconda-devel-list@redhat.com https://urldefense.proofpoint.com/v2/url?u=https-3A__www.redhat.com_mailman_...