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.
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.
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.
* Note that cloud installations don't need to be able to upgraded from release to release (this might be wrong though)
* 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.
Currently, that's all the input I have for the current release criteria. Each of the new criteria would require new Testcases to be written. If anyone has any feedback on any of these, it would be appreciated. Like Adam said in his Server proposal, it would be good to get these taken care of ASAP as we have a TC landing sometime tonight (I know, I know, it's a little late - but I think these criteria fit the *intent* everyone has had so far).
Any feedback would be great! Thanks!
PS - Feel free to ping me on IRC if you have any questions.
On 09/30/2014 11:38 PM, 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.
+1
=== 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.
+1
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.
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.
Note that cloud installations don't need to be able to upgraded from release to release (this might be wrong though)
So, basically, we're taking a stand here and saying "don't treat your cattle like pets"? I'm OK with this, totally, just want to be clear.
- 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.
+1
Currently, that's all the input I have for the current release criteria. Each of the new criteria would require new Testcases to be written. If anyone has any feedback on any of these, it would be appreciated. Like Adam said in his Server proposal, it would be good to get these taken care of ASAP as we have a TC landing sometime tonight (I know, I know, it's a little late - but I think these criteria fit the *intent* everyone has had so far).
Any feedback would be great! Thanks!
This all looks good to me. I do have the feeling that there's probably more we should have here, but it's not leaping to mind what.
Best,
jzb
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.
On Wed, Oct 01, 2014 at 05:54:42PM -0700, Adam Williamson wrote:
<snip>
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.
That works for me. I don't even think the boilerplate is required - it's worked so far. I was just making a note of it in case.
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.
I'll go ahead and add these two in then.
<snip>
- 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.
This is still going to be up for discussion with the Cloud WG. I can see it either way, depending on if your cloud is mostly pets or mostly cattle. I'll add that to the meeting agenda for this friday (Cloud WG meeting).
- 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.
If it seems like it's worth it. I just read the "desktop" as the qualifier for the criteria - but like above, everyone just understands it as is. At best, I was nitpicking I think :)
-- // Mike -- Fedora QA freenode: roshi http://roshi.fedorapeople.org
On Tue, Sep 30, 2014 at 10:38:26PM -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.
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.
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.
Note that cloud installations don't need to be able to upgraded from release to release (this might be wrong though)
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.
Currently, that's all the input I have for the current release criteria. Each of the new criteria would require new Testcases to be written. If anyone has any feedback on any of these, it would be appreciated. Like Adam said in his Server proposal, it would be good to get these taken care of ASAP as we have a TC landing sometime tonight (I know, I know, it's a little late - but I think these criteria fit the *intent* everyone has had so far).
Any feedback would be great! Thanks!
PS - Feel free to ping me on IRC if you have any questions.
Looks good to me. +1
Dusty