Fedora 21 Alpha RC testing request
by Adam Williamson
Hi, folks!
In case anyone didn't see it elsewhere, we put 21 Alpha RC1 out for
testing today. It still has some kinks, but we really need to make sure
we have a reasonably complete test run on it and catch any remaining
blockers. If folks could help test particularly in their own areas of
interest, that'd be great.
The images can be found at
https://dl.fedoraproject.org/pub/alt/stage/21_Alpha_RC1/ - it's a fairly
big tree and the folder layout is still a bit of a work-in-progress,
sorry if you have to click around until you find something.
The test pages are:
https://fedoraproject.org/wiki/Test_Results:Fedora_21_Alpha_RC1_Install
https://fedoraproject.org/wiki/Test_Results:Fedora_21_Alpha_RC1_Base
https://fedoraproject.org/wiki/Test_Results:Fedora_21_Alpha_RC1_Desktop
https://fedoraproject.org/wiki/Test_Results:Fedora_21_Alpha_RC1_Server
to test, basically, pick a test case from (one of) the table(s), run it,
and edit your result into the appropriate table cell using the
{{result}} macro - short version, {{result|pass|adamwill}} is a pass,
{{result|warn|adamwill|123456}} is a warning (aka the compromise between
'pass' and 'fail' - use it for things that aren't exactly critical fails
but are worth noting), and {{result|fail|adamwill|654321}} is a failure.
The number should be a Bugzilla bug #.
Please file bugs for failures; if the bug's serious, propose it as a
release blocker by setting it to block the bug 'AlphaBlocker' or using
the blocker bug webapp at
https://qa.fedoraproject.org/blockerbugs/propose_bug . Each test case
has a link to the release criteria that it enforces at the top - you can
refer to this in proposing the blocker. But please err on the side of
nominating bugs as blockers, we'd rather have a few to reject than miss
one we should have blocked for. Rejections do not go on your permanent
record :)
The test cases have milestones listed alongside them in the tables. Do
the tests marked 'Alpha' first, then the ones marked 'Beta', then the
ones marked 'Final', and the ones with no milestone come last (these are
optional tests that aren't usually expected to encounter release
blocking issues).
Later composes may follow - please do help test those too. We need to
run all the Alpha tests against at least one of the release composes
(ideally we'd run them all against all the RCs).
Thanks a lot folks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
9 years, 7 months
Cloud SIG Meeting Minutes (2014-09-12)
by Kushal Das
===================================
#fedora-meeting: cloud (2014-09-12)
===================================
Meeting started by mattdm at 17:06:11 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2014-09-12/cloud.2014-09-...
.
Meeting summary
---------------
* roll call! (mattdm, 17:06:57)
* Project Atomic (number80, 17:09:03)
* LINK: https://fedorahosted.org/cloud/ticket/64 (number80,
17:09:22)
* Atomic website updated and removal of 32 bits downloads (ticket #36)
(number80, 17:15:10)
* LINK: https://fedorahosted.org/cloud/report/9 (1JTAAFO1I,
17:18:47)
* LINK: https://fedorahosted.org/cloud/ticket/75 that is (kushal,
17:20:43)
* Article for Fedora Magazine on "state of cloud SIG/product" for alpha
release (dustymabe, 17:21:45)
* LINK: Article for Fedora Magazine on "state of cloud SIG/product"
for alpha release (dustymabe, 17:21:59)
* LINK: https://fedorahosted.org/cloud/ticket/75 (dustymabe,
17:22:10)
* IDEA: number80: we could also start to write something on the wiki
collaboratively (kushal, 17:27:15)
* LINK:
https://fedoraproject.org/wiki/User:Hguemar/marketing/cloud_image_f21_status
(number80, 17:29:13)
* LINK:
https://fedoraproject.org/wiki/User:Hguemar/marketing/cloud_image_f21_status
(kushal, 17:29:25)
* wiki page created for ideas for fedora magazine article for f21
cloud image (dustymabe, 17:30:34)
* Plan test days for Atomic image (kushal, 17:31:07)
* LINK: https://fedorahosted.org/cloud/ticket/74 (kushal, 17:31:16)
* ACTION: roshi will reach out to jzb for corodination of Atomic image
testdays. (kushal, 17:34:35)
* Coordinate F21 / fedora next website (kushal, 17:34:55)
* LINK: https://fedorahosted.org/cloud/ticket/36 (kushal, 17:35:03)
* start communication/collaboration on cloud image updates (kushal,
17:37:03)
* LINK: https://fedorahosted.org/cloud/ticket/51 (kushal, 17:37:17)
* meeting agenda item: next steps on test plan (kushal, 17:39:37)
* https://fedorahosted.org/cloud/ticket/61 (kushal, 17:39:43)
* LINK:
https://fedoraproject.org/wiki/User:Roshi/QA/Cloud_Docs/ticket61
also pointed out in the ticket. (kushal, 17:41:52)
* meeting agenda item/tracker for Project Atomic (kushal, 17:49:17)
* https://fedorahosted.org/cloud/ticket/64 (kushal, 17:49:22)
* Open Floor (kushal, 17:54:19)
* ACTION: hguemar & roshi organize a test day for base image
(discussion on the list) (number80, 18:01:04)
* ACTION: mattdm to discuss wg composition on list (mattdm, 18:01:18)
Meeting ended at 18:07:39 UTC.
Action Items
------------
* roshi will reach out to jzb for corodination of Atomic image testdays.
* hguemar & roshi organize a test day for base image (discussion on the
list)
* mattdm to discuss wg composition on list
Action Items, by person
-----------------------
* mattdm
* mattdm to discuss wg composition on list
* roshi
* roshi will reach out to jzb for corodination of Atomic image
testdays.
* hguemar & roshi organize a test day for base image (discussion on
the list)
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* kushal (61)
* roshi (57)
* mattdm (51)
* number80 (34)
* dustymabe (31)
* zodbot (15)
* oddshocks (9)
* walters (4)
* agrimm (3)
* 1JTAAFO1I (3)
* imcleod (2)
* jsmith (2)
* Southern_Gentlem (1)
* ochento (1)
* amita (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
9 years, 7 months
Weekly report (regrets for today's meeting)
by Joe Brockmeier
Hey all,
Just a quick update for the meeting:
- Have updated ticket #59 as mostly done (sad there's no corresponding
entry for that) and removed the meeting keyword. Some questions to
resolve, but I think just about closed. [1]
- Added ticket #74 to plan test days for the Atomic image. This is still
dependent on having the image. Added meeting keyword, but this probably
won't require further discussion today. (This was my action item from
last week's meeting.) [2]
- Have updated ticket #36. Sent a patch against the staging site that
makes a few language changes and removes the 32-bit downloads. Other
ticket was updated saying it was accepted, so this looks good. [3][4]
- Have updated ticket #64 on latest info from infrastructure / Atomic
meetings. We are now producing Atomic images regularly with the test
composes - oddshocks has volunteered to step in and help with patching
compose scripts as needed to add Atomic to dailies, etc. More info in
the ticket, but things are looking good. [5]
- Added ticket #75 to track "state of" article I agreed to write to
coincide with alpha release.
[1] https://fedorahosted.org/cloud/ticket/59
[2] https://fedorahosted.org/cloud/ticket/74
[3] https://fedorahosted.org/cloud/ticket/36
[4] https://fedorahosted.org/fedora-websites/ticket/267#comment:25
[5] https://fedorahosted.org/cloud/ticket/75
Please let me know if I've missed anything. Matthew is empowered to
accept action items for me if there's something reasonable that I can
help with to keep things rolling.
Thanks,
jzb
--
Joe Brockmeier | Principal Cloud & Storage Analyst
jzb(a)redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpress.net/
9 years, 7 months
Re: [Base] Terminology for docker/atomic images
by Matthew Miller
On Mon, Sep 08, 2014 at 05:48:33PM +0200, Václav Pavlín wrote:
> I agree with Colin - Docker Base Image is what we should use when
> talking about Docker images which are then used in Docker Layered
> Images as a base layer on top of which you can build. Please don't
Yeah, after thinking about it I agree with this. People will just have to
get used to the idea that "image" means a lot of things, if they aren't
already.
> If you are in context of Docker you can safely use Base Image and
> Layered Image. If you talk in general, adding "Docker" will bring
> you to the right "namespace".
Just to throw a wrinkle in things, when we're talking in the wide world of
Docker where it's not all Fedora (weird, right?) it's probably the "Fedora
Base Image" -- or _maybe_ the "Fedora Docker Base Image".
> Do we need a documentation of this somewhere on Fedora Wiki?
Yes!
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
9 years, 7 months