#23 File F22 change: Re-factor cloud-init
Closed None Opened 5 years ago by mattdm.

'''Summary:''' Cloud Init was initially designed for a different distribution and is only loosely tailored for our needs. As it stands, it pulls in a rather large set of packages not used for other things. It is also written in Python, itself a large subsystem which it would eventually be nice to leave out of the base. Effort is moderate, with some low-hanging fruit which may be addressed easily.

'''Importance:''' vital long term, but just moderate for F21 (We really need this, but if we don't get work it now, it's in acceptable shape for this release.)

'''Timeframe:''' F21 alpha, or F22 / if we don't make alpha with changes, this can go in next release.

'''Scope:''' Self-contained

'''Cloud SIG owner:''' TBD

https://fedoraproject.org/wiki/Changes/Refactor-Cloud-Init


Adding the meeting keyword to this one in specific because we really need someone to sign up for the actual work here if we want to do it for F21.

As discussed elsewhere, the likely scope for this change for F21 "reducing dependencies of existing cloud-init, particularly cheetah". That is, https://bugzilla.redhat.com/show_bug.cgi?id=974327

If that's all we want to tackle this time around, I suggest we do do that, but defer this feature to F22, because while useful to us (particularly, reduced need to respin the images due to security updates, but also, reduced size), it's not really interesting as a feature in itself.

If we get to the point where we feel an alternate metadata service better serves our needs, then we need a feature.

Therefore, I'm moving this to F22. And I'm calling for lazy consensus on this -- unless someone wants to commit to tackling the bigger work for F21 by Tuesday's feature deadline, we'll leave it moved.

I'll be investigating if we could make min-metadata-service a suitable replacement for cloud-init within F22 timeframe. I doubt that cloud-init is a good option for the long run.

as per current meeting, remove meeting keyword :)

We will be investigating min-cloud-agent (new name for min-metadata-service) for the Fedora Atomic image ''only'' for F21. May look at it for other images for F22.

Some news, min-metadata-service development has been stopped.

I'll be mentoring a GSoC student to work on a cloud contextualization tool (probably in Go), I intend to work closely with student to ensure that the project will be maintained in the long-term. So I moved milestone to Future until I get better insight on this project as a cloud-init alternative.

Replying to [comment:9 hguemar]:

I'll be mentoring a GSoC student to work on a cloud contextualization tool (probably in Go), I intend to work closely with student to ensure that the project will be maintained in the long-term. So I moved milestone to Future until I get better insight on this project as a cloud-init alternative.

Thanks for the update. Will min-metadata-service be a compatible replacement for cloud-init, or will it be a different metadata/contextualization standard?

I think the plan is for it to be compatible with a subset of functionality.

Especially if the plan is for the work to continue in Go, I think the most sensible approach would be to collaborate with CoreOS on their implementation https://github.com/coreos/coreos-cloudinit (possibly as a fork if we need specific features they don't and won't accept, but I don't think that's likely).

Closing this ticket as part of trac clean up process. If you want to reopen, please reopen it after we move to pagure.io as atomic-wg.

Login to comment on this ticket.

Metadata