On Tue, 2014-09-30 at 22:38 -0600, Mike Ruckman wrote: > Hello fellow Fedorans! I told cloud@ that I would work on some criteria to go > over, and here's what I have so far. These are pretty rough, but I think > they're servicable enough for the time being. There are only two I've thought > of for Beta, but I'm probably forgetting something. Patches welcome :) Here > they are: > > === Growroot === > > Release blocking cloud images must be able to automatically utilize all > available space on a supported volume. > [Supported Volume?] > -> PVM, HVM volumes, basically, growroot should work without breaking on both > types of volumes. > > === Cloud-init === > > The cloud-init package must be functional for release blocking cloud images. > [Functional?] > -> the provided cloud-init package needs to work, but we won't block > on issues that EC2 or Openstack have with their service providing > said meta-data. ACK > Looking through the existing criteria we either need to update the existing > pages, create a cloud criteria page or be willing to handwave away criteria > that don't apply (for instance, GUI updates don't apply to cloud images). I'm > fine with the handwavy answer - I don't know that codifying every detail in the > wiki actually adds any value. We kind of already have this, really, in that we don't *explicitly* say that all the requirements about desktop stuff don't apply to non-desktop installs, but everyone just understands it. We could add some fairly short boilerplate somewhere that covers the most obvious cases, easily enough. I think these are short enough that we could reasonably add a 'Cloud Product requirements' section to the existing criteria, along the line of the 'Server Product requirements' section that's already there. > That being said, there were some general edits I would make to the current beta > criteria: > > ----- Clarifications ----- > > * Define "supported configurations" in the "Release-blocking images must boot" > criteria to include all of the products. We already did this. Remember that the criteria are *additive*. The Beta 'Release-blocking images must boot' criterion is only a small addition to the Alpha one, which exhaustively lists the supported environments and so forth. There is a definition of 'release-blocking images' in the preamble shared between all the pages: "The term 'release-blocking images' means all the images in which bugs are currently considered capable of blocking a Fedora release. The current set of release-blocking images includes the images defined by the three primary Products - Server, Workstation and Cloud - in their product requirement documents and/or technical specifications, and the KDE live image." > * Note that cloud installations don't need to be able to upgraded from release > to release (this might be wrong though) This is kind of an interesting one I'd think we'd want the Cloud WG to consider. > * I would alter the "Shutdown, reboot, logout" criteria say "system" instead of > "desktop" since I'm sure all products want to be able to do all those things. It already states: "must work using standard console commands" we could possibly look at re-wording it to cover Cockpit for Server and cloud management consoles (clouds have those, right? right?) for Cloud. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
