Re: Fedora Cloud Workgroup Meeting Minutes 01 May 2014
-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 ro...@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 j...@redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/ -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTajUSAAoJEKbW5zOgIHzUkc0H/j4FbzBPYXohtPrWOUQ1iJ6k cM/rwqQkk0qQ4zHjGkDblQ7GWNfzalLIaJ96bye20+JuEHZvmFIVzTXNJ0MILCiD ONSl0eEKN8/vSiIxK9UaUgyOOkxaqCqlpC579zAQVP9tSK7y2LNY9EZxgUh1PcDl P4M42GgY0R9ED15gyltqCDQRo4mAqZqO2M2rNHkVYQZsSPE9B4XCMAVmjLBsEI0Y fm+ztw6nvgUTkcXg80d3/v9/QM6lOAmtrSZAcJJd7GrwNKW+EIi3n0kzepfAQ6Tm s9Dj/z+D3CvvUfAaHBoSVnba9EUpAwVHLQBLEdLebkrz8pyMZnXTQtJCz+RKXPY= =OLOg -END PGP SIGNATURE- ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Fedora Cloud Workgroup Meeting Minutes 01 May 2014
On Wed, May 7, 2014 at 9:28 AM, Joe Brockmeier j...@redhat.com wrote: 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. I'll be on IRC, but unfortunately I have a time conflict on that slot (as I imagine many people do as it's a prime time that's reachable by PST, EST, and GMT). And don't hesitate to send email at other times of course! ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [cloud] #53: anaconda doesn't allow installation of current fedora-cloud-base.ks
#53: anaconda doesn't allow installation of current fedora-cloud-base.ks -+- Reporter: walters | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Resolution: Keywords: | -+- Comment (by walters): walters dgilmore, did you see the conclusion of yesterday's thread? is setting a root pw in kickstart then locking good enough? dgilmore walters: its really not walters dgilmore, ok, we need to figure this out; i'm interested as I need to be producing cloud images via anaconda as well walters should take this to a bug or something dlehman pardon me for being behind, but what's the problem? dlehman you want root locked but anaconda doesn't allow that? dgilmore dlehman: anaconda doesnt allow it without creatinga user walters dlehman, i think the typing to catch you up is best done in a bug dlehman fair enough dgilmore dlehman: need to be able to say the root account can be locked if a package that will configure the system on first boot is installed dlehman dgilmore: and the rationale is that we can't know for sure if there will be compulsory user-account creation, so we can't lock root, right? dgilmore walters: but yeah a bug is probably best walters https://fedorahosted.org/cloud/ ? dgilmore dlehman: well we can deal with it all in %post, but that is easy to get wrong walters i can wordsmith this dlehman the only way anaconda could let this slide, I think, is if those initial-setup packages provide something that says I take full responsibility for compulsory user account configuration dlehman then we can just reassign the bugs to those packages when they inevitably come dgilmore dlehman: right dlehman so I think those various packages should have Provides: user- account-setup walters https://fedorahosted.org/cloud/ticket/53 dgilmore dlehman: i am okay with that dgilmore initial-setup cloud-init etc can all provide that dlehman and that means if they get installed it's their responsibility to see to it that the accounts are created dlehman it doesn't matter what else is installed, doesn't matter what the user does, c c davidshea we'd need a way to ensure that the service or whatever is actually enabled on boot. that's all over the place right now walters are you saying anaconda would come with code to check the rpm transaction for something with the requisite provides? dlehman it certainly sounds better than maintaining a list of packages that may or may not handle it dlehman I'm not volunteering, but if you want something better than what we have now this seems like the way to go. dlehman we can log prominently WARNING: not enforcing user account creation because package foo will handle it on the reboot walters though come to think of it, this isn't going to work for me walters at least not easily walters since min-metadata-service will likely be in the default tree, just not enabled walters as davidshea says walters maybe in the future i'd have a variant tree for cloud, also with stuff like the physical kernel drivers stripped out * walters keeps coming back to the idea of a kickstart verb for this -- Ticket URL: https://fedorahosted.org/cloud/ticket/53#comment:1 cloud https://fedorahosted.org/cloud Fedora Cloud Working Group Ticketing System ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
More information on Cloud spins
Hi everyone, This is my first email on this list. I work for Red Hat, but I am writing here as the maintainer of the Fedora Scientific Spin [1], a KDE based Fedora spin aiming to cater to the needs of Linux users whose work and play involves number crunching, and all related work. I have some docs here, which are (yet!) to be completed [2]. I happened to come across a ticket that aims to create cloud images for spins. I haven't followed any discussion at all on that. Where can I learn more about this? Basically, I am interested to see if a stripped down version of Fedora Scientific can be offered as a cloud image as well. Thank you. Best, Amit. [1] http://spins.fedoraproject.org/scientific-kde/ [2] http://fedora-scientific.readthedocs.org/en/latest/ ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
