----- Original Message ----- > From: "Matthew Miller" <mattdm@xxxxxxxxxxxxxxxxx> > To: "Fedora Cloud SIG" <cloud@xxxxxxxxxxxxxxxxxxxxxxx> > Sent: Wednesday, June 26, 2013 11:20:55 AM > Subject: Fedora 20 cloud plans? > > With F19 almost out the door, it's time to shift attention to the next > thing! > > Here's what I'm thinking about right now; would love to hear your opinions > and advice here, and also about other things in the cloud arena which we > should be working on. > > Cloud Image Generation > ====================== > - finally getting this automated weekly in koji, to a download > site and to EC2. See notes for this at > https://fedoraproject.org/wiki/Features/FirstClassCloudImages/KojiPlan > - move to Oz (or other fully anaconda-based image generation) > > Improving the Cloud Image > ========================= > - cloud-util improvement > - subpackaging growpart means we don't need to pull in huge deps (bz > #975497) > - cloud-init improvements > - can we remove the cheetah dependency? (bz #974327) > - other dependency softening (eg bz #974329, bz #786488) > - disable direct writes to the console, which will address several > problems (bz #977952) > - others? > - disable the gettys by default? > - look at the logging configuration (rsyslog/journald double-logging issue; > look at memory and on-disk journald consumption) > - more reductionism as reasonable -- maybe we can look at tackling the docs, > translations, and kernel-modules size issues? burn sendmail with fire? > get systemd-journal-gatewayd out of the image so it stops pulling in the > libmicrohttpd web server and crypto libs which wouldn't be there otherwise > (bz #908081) > > Vagrant > ======= > - We're blocked from having "real" vagrant base boxes by a lack of Chef, > which is blocked by bz #823351; hope to have that resolved and Chef as > an F20 feature I talked to Sam Kottler about this a bit over the weekend when I saw him and I didn't exactly get the warm fuzzies about upstream movement here; maybe he can elaborate? :\ (But chef & real vagrant boxes would be awesome) > - Also, Vagrant is very Virtualbox-centric, and we don't have that in Fedora > (out of tree kernel modules); work on a KVM provider for Vagrant should > make that a non-issue -- https://github.com/adrahon/vagrant-kvm To be clear: This is so that we can use vagrant boxes (of any OS flavor?) on a Fedora desktop, yes? Not an issue with "have a Fedora vagrant box to open on other Linux distros or mac" ? > > > Cloud Infrastructure Software > ============================= > - OpenNebula? Sure. I know Shawn Starr was working on this last year, and Jaime Melis had mailed the list a few times about it; the packaging got somewhere, though had some issues - https://bugzilla.redhat.com/show_bug.cgi?id=815001 I was also going to mention OwnCloud - which had been targeted for F18, was dropped, and now I see a F19 feature page for it, and it says it's 100% done, but isn't in the feature list (???) - http://fedoraproject.org/wiki/Features/OwnCloud - I'm guessing it didn't make the feature list since it doesn't seem to have been moved into the feature wrangler queue (still tagged as FeaturePageIncomplete) ... which is kind of a bummer since it would have been nice to feature. But is probably worthwhile adding at least to the cloud sig wiki that it's there. -r > > > > -- > Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm@xxxxxxxxxxxxxxxxx> > _______________________________________________ > cloud mailing list > cloud@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/cloud > _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud
