-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 05/05/2014 10:23 AM, Colin Walters wrote:
On Thu, May 1, 2014 at 2:37 PM, Mike Ruckman roshi@fedoraproject.org wrote:
- Crucial basic Docket Host Image decisions (jzb, 08:07:23) *
https://fedorahosted.org/cloud/ticket/47 (jzb, 08:07:36) * AGREED: fedora atomic docker-specific image will not include yum/dnf (mattdm, 08:15:47)
OK, but with rpm-ostree I'd like to highlight that it does already link to libhawkey and rpm, which are the same C libraries underlying dnf. This is important preparatory work for package layering.
That said, has anyone built a list of blockers/issues they see? I have made a good amount of progress on Anaconda, and I'm pretty confident of delivery by next month.
Any chance you can make it to tomorrow's meeting? We might have more questions that you are uniquely qualified to help us sort out.
- AGREED: try min-metadata-service for fedora atomic image for
alpha, fall back to cloud-init for beta if it doesn't work out (mattdm, 08:29:56)
I'm interested in this as well, although I don't see it as so critical. Investing in thinning down cloud-init is also likely viable.
- AGREED: aim for getting python out of the fedora atomic image
too, if all of the previous things line up. (mattdm, 08:34:36)
One issue I see here is that there are a lot of valid reasons to want Python on the host for configuration management type tasks, and the answer to this is to still support local package layering on top of a base tree.
I'm relatively confident I can have basic package layering by Alpha.
Great!
Best,
jzb
- -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb@redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/