October 2014 - cloud - Fedora mailing-lists

2014-10-15 @ 16:00 UTC ** F21 Blocker Review Meeting
by Mike Ruckman 13 Oct '14

13 Oct '14

# F21 Blocker Review meeting # Date: 2014-10-15 # Time: 16:00 UTC (12:00 EDT, 09:00 PDT) # Location: #fedora-blocker-review on irc.freenode.net As testing of Beta TC3 continues, it's time for another blocker review meeting. Currently we have 3 proposed blockers and 2 proposed FEs. We have 10 accepted blockers to review. Should be a shorter meeting :) If you want to take a look at the accepted blockers, the full list can be found here: https://qa.fedoraproject.org/blockerbugs/milestone/21/beta/buglist We'll be evaluating these bugs to see if they violate the Beta Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F21 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting See you Wednesday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- // Mike -- Fedora QA freenode: roshi http://roshi.fedorapeople.org

1 0

Fedora 21 Beta Test Compose 3 (TC3) Available Now!
by Adam Williamson 10 Oct '14

10 Oct '14

As per the Fedora 21 schedule [1], Fedora 21 Beta Test Compose 3 (TC3) is now available for testing. Content information, including changes, can be found at https://fedorahosted.org/rel-eng/ticket/6010#comment:4 . Please see the following pages for download links (including delta ISOs) and testing instructions. Normally dl.fedoraproject.org should provide the fastest download, but download-ib01.fedoraproject.org is available as a mirror (with an approximately 1 hour lag) in case of trouble. To use it, just replace "dl" with "download-ib01" in the download URL. Installation: https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test Base: https://fedoraproject.org/wiki/Test_Results:Current_Base_Test Workstation and Desktop: https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test Server: https://fedoraproject.org/wiki/Test_Results:Current_Server_Test Cloud: https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test The Summary page: https://fedoraproject.org/wiki/Test_Results:Current_Summary combines the result tables from all the pages, without the instructions. Ideally, all Alpha and Beta priority test cases for each of these test pages [2] should pass in order to meet the Beta Release Criteria [3]. Help is available on #fedora-qa on irc.freenode.net [4], or on the test list [5]. Create Fedora 21 Beta test compose (TC) and release candidate (RC) https://fedorahosted.org/rel-eng/ticket/6010 Current Blocker and Freeze Exception bugs: http://qa.fedoraproject.org/blockerbugs/current [1] http://fedorapeople.org/groups/schedule/f-21/f-21-quality-tasks.html [2] https://fedoraproject.org/wiki/QA:Release_validation_test_plan [3] https://fedoraproject.org/wiki/Fedora_21_Beta_Release_Criteria [4] irc://irc.freenode.net/fedora-qa [5] https://admin.fedoraproject.org/mailman/listinfo/test -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

[DRAFT] Changes to Working Group structure
by Joe Brockmeier 10 Oct '14

10 Oct '14

Hi all, As discussed last week, we need to make some changes to the language about choosing members of the CWG. Current: Membership ---------- The Fedora Cloud Working Group has nine voting members, one selected by the Fedora Engineering Steering Committee as the liaison to FESCo, and the others initially selected by the FESCo liaison. Because continuity is important, Working Group members serve as long as they are able and willing. Each voting member of the working group will confirm their continued membership every six months. When a position in the group becomes available, that position will be filled by unanimous consent of the existing members. Suggested Change: ----------------- The Fedora Cloud Working Group will have a minimum of five voting members, one selected by the Fedora Engineering Steering Committee (FESCo) as the liaison to FESCo, and the others to be approved by a lazy majority of the existing Working Group members. Because continuity is important, Working Group members serve as long as they are able, willing, and active. There is no upper cap on Working Group Members, but members may be removed from active status after sustained inactivity or on majority vote of the rest of the Working Group. Current: Making Decisions ---------------- Because Fedora is a global project, members of the working group may be distributed across multiple timezones. It may be possible to have a real-time IRC meetings, but in general we will conduct business on the Fedora Cloud mailing list. Many of our decisions can be made through "lazy consensus". Under this model, an intended action is announced on the mailing list, discussed, and if there is no controversy or dissenting views with a few days, simply done. For bigger issues, where there may be disagreement, or where there is long-term impact, or where an action may not easily be undone, we will use a ticketing system for voting https://fedorahosted.org/cloud/. Working group members can vote +1 to approve, -1 to disagree, or 0 to abstain; five +1 votes are necessary for a measure to pass. Non-members may comment on the ticket and (of course) discuss on the mailing list, but are asked to refrain from putting votes in the ticket. Suggested Change: Making Decisions ---------------- Because Fedora is a global project, members of the working group are distributed across multiple timezones. While the Working Group does have real-time IRC meetings, these are used as working sessions and policy or major technical decisions will be conducted on the Fedora Cloud (cloud(a)lists.fedoraproject.org) mailing list. When possible, we will try to take decisions through "lazy consensus." Under this model, an intended action is announced on the mailing list, discussed, and if there is no controversy or dissenting views with a few days, simply done. In some cases a vote may be required if: - Consensus cannot be reached through discussion. - There's a long-term impact. - An action cannot easily be undone. When a vote is required, we will use the Trac ticketing system for voting at https://fedorahosted.org/cloud/. Working group members can vote +1 to approve, -1 to disagree, or 0 to abstain; a majority of +1 votes are necessary for a measure to pass. Non-members may comment on the ticket and (of course) discuss on the mailing list, but are asked to refrain from putting votes in the ticket. # # # Thoughts, comments, flames? Best, jzb -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

5 6

Friday meeting agenda [Draft]
by Joe Brockmeier 09 Oct '14

09 Oct '14

Hi all, Will be out tomorrow, but promised to send a draft agenda to help run the meeting. Here's the action items and tickets for tomorrow: * jzb to draft changes to Fedora Cloud Working Group Governance Structure and sent to list [DONE] * mattdm to take changes in Fedora Cloud Working Group Governance Structure to FESCo once accepted. * roshi to update fedocal once a date is set * jzb continue planning Atomic image test days. Wait for new date. [IN PROGRESS] * jzb Continue to work on a runbook for having Atomic and other cloud images updated out of band. [IN PROGRESS] * roshi wait until next week for feedback on ticket 77 then move forward. * kushal and roshi to work on Ticket 38 on Automatic Smoketests on Image Build w/an eye towards completion for Fedora 22. * roshi remind Cloud SIG about blocker review meetings. * number80 set a poll to change WG meeting date Tickets tagged with meeting: https://fedorahosted.org/cloud/report/9 Note on Ticket 74 - also see my AI above. In progress, but nothing to report this week. Note on Ticket 75 - still in progress, waiting for beta. Nothing to report this week. Best, jzb -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

1 0

[Fedocal] Reminder meeting : Fedora Cloud Workgroup
by Haïkel 08 Oct '14

08 Oct '14

Dear all, You are kindly invited to the meeting: Fedora Cloud Workgroup on 2014-10-10 from 17:00:00 to 18:00:00 UTC At fedora-meeting(a)irc.freenode.net The meeting will be about: Standing meeting for the Fedora Cloud Workgroup. Source: https://apps.fedoraproject.org/calendar//meeting/482/

2 1

Atomic Updates - do we follow traditional model or a new one?
by Joe Brockmeier 08 Oct '14

08 Oct '14

Hey all, One of the things that came out of the weekly meeting with infra/releng and folks working on Atomic is what I think may be a mis-match in expectations on upgrades/release process for the Atomic host. As called out in the host definition[1] Atomic is planned as a rolling stream of updates - and users are expected to move to the next release in the stream rather than staying on a specific version or having to carry an overlapping stream. That is: If you're on Fedora 21 Atomic, when Fedora 22 Atomic is released then that would be what you switch to - not a Fedora 21 tree. I know for CentOS Atomic we won't be maintaining a set of overlapping releases, and I don't think RHEL will either. That sort of defeats the model, really. (Also, there's not exactly an upgrade for Atomic something like F21->F22 if there are multiple trees, eventually you would have to manually switch trees if we were producing overlapping sets.) In discussing this in today's meeting[2], Dennis suggested we'd need to go to FESCo to get agreement that we can pursue the non-overlapping model. Before I do that, I wanted to make sure we were all in agreement that is the way to go. Thoughts, comments, flames? [1] https://gist.github.com/jzb/0f336c6f23a0ba145b0a [2] http://meetbot.fedoraproject.org/atomic/2014-10-07/atomic.2014-10-07-18.09.… -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

5 9

Cloud Test Overview
by Mike Ruckman 08 Oct '14

08 Oct '14

Hey fellow fedorans! I've made some slight edits to the existing "Test Overview" [0] on the wiki and would like some feedback. It's meant as a high-level overview of all the things we think we need to test for the Fedora 21 cloud product. It's not intended to be an exhaustive list, just a basic statement of intent. So if you have a couple minutes to look it over (it's short) and look for anything I might have missed, it would be greatly appreciated. Thanks! [0] https://fedoraproject.org/wiki/User:Roshi/QA/Cloud_Docs/Test_Overview -- // Mike -- Fedora QA freenode: roshi http://roshi.fedorapeople.org

5 12

Regrets for Friday's meeting
by Joe Brockmeier 07 Oct '14

07 Oct '14

Hey all, A little early, but I'm going to be out of office Friday and won't be able to make the meeting. If someone can chair, I'll try to make sure the agenda is updated and will send along my notes/report before then. Thanks, jzb -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

2 2

Fedora / Infrastructure meeting minutes 7 October 2014
by Joe Brockmeier 07 Oct '14

07 Oct '14

========================================= #atomic: Fedora Atomic and Infrastructure ========================================= Meeting started by jzb at 18:09:05 UTC. The full logs are available at http://meetbot.fedoraproject.org/atomic/2014-10-07/atomic.2014-10-07-18.09.… . Meeting summary --------------- * LINK: http://meetbot.fedoraproject.org/atomic/2014-09-30/atomic.2014-09-30-18.14.… (jzb, 18:10:25) * Atomic Runbook (jzb, 18:10:44) * ACTION: oddshocks Compile questions and get with dgilmore to figure out mirrormanager / releng / build systems info. (jzb, 18:19:37) * ACTION: oddshocks start compiling documentation based on information about mirrormanager / build systems. (jzb, 18:19:57) * ACTION: jzb send new meeting time for 16:30 CDT (jzb, 18:36:11) * ACTION: jzb update calendar (jzb, 18:37:08) * new business (jzb, 18:41:12) * LINK: https://dl.fedoraproject.org/pub/alt/fedora-atomic/ is fetched over HTTPS (walters, 18:47:57) * ACTION: jzb Take Atomic update model to FESCo (jzb, 19:26:57) Meeting ended at 19:54:20 UTC. Action Items ------------ * oddshocks Compile questions and get with dgilmore to figure out mirrormanager / releng / build systems info. * oddshocks start compiling documentation based on information about mirrormanager / build systems. * jzb send new meeting time for 16:30 CDT * jzb update calendar * jzb Take Atomic update model to FESCo Action Items, by person ----------------------- * dgilmore * oddshocks Compile questions and get with dgilmore to figure out mirrormanager / releng / build systems info. * jzb * jzb send new meeting time for 16:30 CDT * jzb update calendar * jzb Take Atomic update model to FESCo * oddshocks * oddshocks Compile questions and get with dgilmore to figure out mirrormanager / releng / build systems info. * oddshocks start compiling documentation based on information about mirrormanager / build systems. * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * jzb (120) * dgilmore (96) * walters (76) * dustymabe (38) * oddshocks (38) * stickster (36) * jbrooks (4) * centbot (2) * quaid (2) * zodbot (2) * roshi (1) * gregdek (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

1 0

Proposed Cloud release criteria for F21
by Mike Ruckman 07 Oct '14

07 Oct '14

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. -- // Mike -- Fedora QA freenode: roshi http://roshi.fedorapeople.org

5 5

Your account has been limited until we hear from you PP-503-472-206
by zghyk 04 Oct '14

04 Oct '14

4 6

Fedora Cloud SIG Meeting Minutes 2014-10-03-17
by Joe Brockmeier 03 Oct '14

03 Oct '14

================================= #fedora-meeting: Fedora Cloud SIG ================================= Meeting started by jzb at 17:01:55 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2014-10-03/fedora-meeting.2… . Meeting summary --------------- * Cloud WG Composition (jzb, 17:04:57) * LINK: https://fedoraproject.org/wiki/Cloud/Governance (jzb, 17:09:35) * ACTION: jzb to draft changes to Fedora Cloud Working Group Governance Structure and sent to list (jzb, 17:18:32) * ACTION: mattdm to take changes in Fedora Cloud Working Group Governance Structure to FESCo once accepted. (jzb, 17:18:50) * Action Item: roshi to update fedocal (jzb, 17:19:21) * jzb to email lists and update Project Atomic (jzb, 17:20:26) * LINK: http://koji.fedoraproject.org/koji/tasks?owner=ausil&state=all&view=flat&me… (roshi, 17:26:03) * ACTION: roshi to update fedocal once a date is set (roshi, 17:28:44) * ACTION: jzb continue planning Atomic image test days. Wait for new date. (jzb, 17:29:46) * Coordinate with releng on updates to set procedure for updates. (jzb, 17:30:44) * ACTION: jzb Continue to work on a runbook for having Atomic and other cloud images updated out of band. (jzb, 17:31:40) * roshi to shore up overview specifics (jzb, 17:32:10) * Meeting Tickets in Trac (jzb, 17:35:58) * LINK: https://fedorahosted.org/cloud/report/9 (jzb, 17:36:08) * Release Criteria Discussion (jzb, 17:36:45) * LINK: https://fedorahosted.org/cloud/ticket/77 (jzb, 17:36:54) * ACTION: roshi wait until next week for feedback on ticket 77 then move forward. (jzb, 17:45:30) * relates to ticket #51 start communication/collaboration on cloud image updates (jzb, 17:47:31) * LINK: https://fedorahosted.org/cloud/ticket/51 (jzb, 17:47:38) * meeting agenda item/tracker for Project Atomic (jzb, 17:47:58) * LINK: https://fedorahosted.org/cloud/ticket/64 (jzb, 17:48:06) * Automatic Smoketests on Image Build (jzb, 17:51:28) * LINK: https://fedorahosted.org/cloud/ticket/38 (jzb, 17:51:39) * ACTION: kushal and roshi to work on Ticket 38 on Automatic Smoketests on Image Build w/an eye towards completion for Fedora 22. (jzb, 17:57:16) * Open Floor (jzb, 17:57:29) * LINK: https://fedoraproject.org/wiki/Cloud/Atomic_Runbooks (jzb, 18:01:46) * oddshocks starting Atomic Runbooks and SOPs (jzb, 18:01:55) * Cloud SIG congratulates kushal on joining the Fedora team to work on Fedora Cloud (jzb, 18:02:40) * draft of Atomic test day post (jzb, 18:03:39) * LINK: http://fpaste.org/138963/12356769/ (jzb, 18:03:47) * Atomic Definition Discussion Draft (jzb, 18:04:45) * LINK: http://lists.centos.org/pipermail/centos-announce/2014-October/020660.html is the announcement. (kushal, 18:05:26) * CentOS Cloud SIG announcement (jzb, 18:06:04) * HELP: please look over atomic definition draft and provide feedback (mattdm, 18:06:08) * LINK: http://lists.centos.org/pipermail/centos-announce/2014-October/020660.html is the announcement. (jzb, 18:06:17) * Fedora AWS community account (agrimm, 18:07:26) * HELP: More cloud SIG folks to blocker review meetings. (jzb, 18:13:20) * ACTION: roshi remind Cloud SIG about blocker review meetings. (jzb, 18:14:21) * ACTION: number80 set a poll to change WG meeting date (number80, 18:17:09) Meeting ended at 18:17:37 UTC. Action Items ------------ * jzb to draft changes to Fedora Cloud Working Group Governance Structure and sent to list * mattdm to take changes in Fedora Cloud Working Group Governance Structure to FESCo once accepted. * roshi to update fedocal once a date is set * jzb continue planning Atomic image test days. Wait for new date. * jzb Continue to work on a runbook for having Atomic and other cloud images updated out of band. * roshi wait until next week for feedback on ticket 77 then move forward. * kushal and roshi to work on Ticket 38 on Automatic Smoketests on Image Build w/an eye towards completion for Fedora 22. * roshi remind Cloud SIG about blocker review meetings. * number80 set a poll to change WG meeting date Action Items, by person ----------------------- * jzb * jzb to draft changes to Fedora Cloud Working Group Governance Structure and sent to list * jzb continue planning Atomic image test days. Wait for new date. * jzb Continue to work on a runbook for having Atomic and other cloud images updated out of band. * kushal * kushal and roshi to work on Ticket 38 on Automatic Smoketests on Image Build w/an eye towards completion for Fedora 22. * mattdm * mattdm to take changes in Fedora Cloud Working Group Governance Structure to FESCo once accepted. * number80 * number80 set a poll to change WG meeting date * roshi * roshi to update fedocal once a date is set * roshi wait until next week for feedback on ticket 77 then move forward. * kushal and roshi to work on Ticket 38 on Automatic Smoketests on Image Build w/an eye towards completion for Fedora 22. * roshi remind Cloud SIG about blocker review meetings. * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * jzb (151) * roshi (91) * number80 (42) * dustymabe (31) * mattdm (31) * kushal (30) * agrimm (20) * oddshocks (15) * zodbot (10) * walters (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

1 0

[cloud] #64: meeting agenda item/tracker for Project Atomic
by Fedora Cloud Trac Tickets 03 Oct '14

03 Oct '14

#64: meeting agenda item/tracker for Project Atomic --------------------+--------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: meeting --------------------+--------------------- Weekly report on status/blockers/todos for Project Atomic in Fedora -- starting with image generation and ostree repos and building up from there. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/64> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 7

[cloud] #41: Write Initial QA Documents
by Fedora Cloud Trac Tickets 02 Oct '14

02 Oct '14

#41: Write Initial QA Documents --------------------------+-------------------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 21 (Branch) Component: Testing & QA | Keywords: --------------------------+-------------------------------- * '''What:''' Work out and write down structured test plans and test cases and, if additional are necessary, release criteria / requirements. * '''Where:''' Fedora Wiki * '''Why:''' So testers know how to test, and QA overlords and rel-eng know when the images are actually ready for release. Or maybe rather, when they're not. * '''When:''' Before the very first alpha release candidate (RC) of Fedora 21 is due. * '''Who:''' Someone in cloud working group in collaboration with QA. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/41> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 6

Agenda for Tomorrow's meeting
by Joe Brockmeier 02 Oct '14

02 Oct '14

Hey all, For tomorrow's meeting we have the following: Action Items ------------ * mattdm to follow up on list or tickets for WG Composition * roshi to update fedocal * roshi to write brief writeup about atomic testday * jzb to email lists and update Project Atomic * jzb coordinate with releng to see what they'd need and document it on the wiki? * roshi to shore up overview specifics * everyone else to read his new version when he mails the list with it Also, open Trac tickets for the meeting: https://fedorahosted.org/cloud/report/9 Any new items we have this week? Best, jzb -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

1 0

[cloud] #36: Coordinate F21 / fedora next website
by Fedora Cloud Trac Tickets 02 Oct '14

02 Oct '14

#36: Coordinate F21 / fedora next website ----------------------------+------------------------------- Reporter: mattdm | Owner: jzb Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Final) Component: Website & Wiki | Keywords: ----------------------------+------------------------------- '''Summary:''' Since we are now one of the three top level artifacts Fedora produces, we want to emphasize our unique niche. Updated website with new flashier branding, plus tools for selecting different images for different use cases '''Importance:''' vital (it's basically part of the whole exercise) '''Timeframe:''' F21 release / arguably, having the web site up ''is'' the release. And it'd be nice to have earlier, like at the alpha and beta '''Fedora Sub-Project/SIG:''' Websites '''Cloud SIG owner:''' Joe Brockmeier https://fedorahosted.org/fedora-websites/ticket/248 -- Ticket URL: <https://fedorahosted.org/cloud/ticket/36> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 7

[cloud] #61: meeting agenda item: next steps on test plan
by Fedora Cloud Trac Tickets 02 Oct '14

02 Oct '14

#61: meeting agenda item: next steps on test plan --------------------+--------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: meeting --------------------+--------------------- See Mike's draft cloud test plan https://fedoraproject.org/wiki/User:Roshi/QA/Cloud_Docs/Test_Plan and Adam's general F21 plan https://fedoraproject.org/wiki/User:Adamwill/Draft_Fedora_21_test_plan We should discuss next steps at our next meeting. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/61> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 5

Atomic/Fedora Infra Meeting Minutes (2014-09-30)
by Joe Brockmeier 02 Oct '14

02 Oct '14

============================== #atomic: Atomic/Infrastructure ============================== Meeting started by stickster at 18:14:43 UTC. The full logs are available at http://meetbot.fedoraproject.org/atomic/2014-09-30/atomic.2014-09-30-18.14.… . Meeting summary --------------- * Roll call! (stickster, 18:15:00) * ostree/update status (stickster, 18:15:53) * http://ur1.ca/i9r40 (jzb, 18:24:36) * LINK: https://git.fedorahosted.org/cgit/mirrormanager/tree/server/mirrormanager/r… (dgilmore, 18:29:46) * ACTION: oddshocks add some info to https://fedoraproject.org/wiki/Cloud/Atomic_Runbooks (oddshocks, 18:31:50) * walters has been working on centralizing compose scripts in https://github.com/projectatomic/rpm-ostree-toolbox (jzb, 18:41:15) * LINK: http://wiki.centos.org/HowTos/CommunityBuildSystem (jzb, 18:42:49) * LINK: https://fedorahosted.org/rel-eng/ticket/6004 (jzb, 18:57:03) * ACTION: dgilmore to bring lmacken into discussion about Atomic/Bodhi/updates. (jzb, 19:02:22) Meeting ended at 19:09:30 UTC. Action Items ------------ * oddshocks add some info to https://fedoraproject.org/wiki/Cloud/Atomic_Runbooks * dgilmore to bring lmacken into discussion about Atomic/Bodhi/updates. Action Items, by person ----------------------- * dgilmore * dgilmore to bring lmacken into discussion about Atomic/Bodhi/updates. * oddshocks * oddshocks add some info to https://fedoraproject.org/wiki/Cloud/Atomic_Runbooks * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * dgilmore (49) * jzb (47) * oddshocks (25) * walters (21) * stickster (19) * imcleod (8) * zodbot (8) * centbot (7) * jbrooks (7) * nirik (5) * dustymabe (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

1 0

Atomic Host Definition [Discussion Draft]
by Joe Brockmeier 02 Oct '14

02 Oct '14

Hi all, Several folks have asked for a definition of what's supposed to be in an Atomic Host -- which is sort of loosely defined currently, but a more explicit definition is in order. Including a discussion draft based on working documents for RHEL Atomic here. Apologies for sending it to such a wide audience (CentOS, Fedora, and Atomic-devel) but I know we have participants who are only on one of the lists. The text is below in Markdown and I've also created a Gist [1] should anyone wish to send patches that way. Note there's a full list of packages at the end, from the RHEL work. This is not to say "Atomic must include these packages" but "here's what we're currently working with." [1] https://gist.github.com/jzb/0f336c6f23a0ba145b0a#file-atomic-host-definition Thoughts, comments, flames? Best, jzb # # # # Atomic Host Definition [Discussion Draft] This document is meant to serve as a baseline definition for Project Atomic hosts, to be implemented from CentOS, Fedora, and Red Hat Enterprise Linux (RHEL). The purpose of the document is not to restrict the packages or services offered with an Atomic host, but to ensure a baseline of functionality and working standard that each product team can implement **before** adding additional functionality. The initial working draft is being taken from work going into RHEL Atomic, but it is expected that the CentOS Atomic SIG and Fedora Cloud Workgroup will provide input and direction to Project Atomic going forward. This is simply the first cut at a shared understanding that gives each team a basis for cooperation. ## Atomic Host Definition The next section provides some guidance on how an Atomic host differs from other products that are provided by the distributions, and the expectations that projects should convey to users. ### What is an Atomic Host? The Atomic Host is a minimal set of packages and services essential to running and orchestrating containers: * Minimal Footprint: An Atomic Host should have a minimal footprint with only essential technologies needed to run containers. Services that can or should be run in a container should *not* be part of the Atomic Host. * Container Host Optimized: The Atomic Host **must** be able to build, deploy, and run containers "out of the box." The Atomic host is a single-purpose OS, customized to run containers and that's all. Additional services and applications should be deployed in containers, not added to the host. * Support for Docker Container Format: Fairly self-explanatory, the Atomic host should include all applications and services required to run Docker containers. * Atomic Update and Rollback Capability: Using rpm-ostree/OStree, Atomic hosts will support atomic updates and rollbacks to the previous release state. * Provided as a tree defined by the project team (not RPMs), with updated trees for errata and minor releases. - DIY Atomic Trees: It's up to the project whether they wish to provide tools and guidance (documentation) around building their own Atomic trees. * Rolling Stream of Updates: The expectation is that Atomic hosts will not have an "overlapping stream" of supported releases. Instead, users will be expected to move to an updated release rather than stay on a specific release version. - Example: Fedora 20 Atomic Host will receive monthly updates while Fedora 21 is in development. When Fedora 21 Atomic Host is released, the next update for users on Fedora 20 Atomic Host will carry them to Fedora 21, and so forth. **At this time we won't plan to carry overlapping versions of the operating system for Atomic Host users.** * Multi-host orchestration capabilities for Atomic Host infrastructure. * Multi-host infrastructure for application containers. * x86_64 Only: Current plans are for the Atomic Host to be x86_64 only. * Target platforms: KVM (qcow2), Baremetal, AWS AMI, and GCE. ### Compatibility With Parent Distribution The Atomic Host is composed of packages from the parent distribution and is expected to be compatible with CentOS, Fedora, or RHEL (respectively) and its behavior should not differ from the parent distribution where similar functionality exists. * ABI/KABI Compatibility: Atomic Host is generally compatible with underlying ABI and KABI for common packages. * Exceptions to ABI compatibility: Docker and Kubernetes *may* break ABI compatibility. * Unique Packages: May be composed from sources outside the standard distribution (e.g., EPEL, Copr trees). * Release Versioning: Numbering will follow parent distribution. * Asynchronous Updates: The Atomic host functionality may move ahead of parent distribution where necessary. * For example, an update in Anaconda may be needed that isn't yet available in CentOS 7. The Atomic version of Anaconda may move ahead of CentOS 7 if necessary and sync up at a later date. * Long-term divergence is *not* planned. Any instances where packages diverge from the parent distribution needs to be tracked, and a plan in place to ensure the packages sync up in time. ## Goals for Atomic Hosts The goal for the Atomic Host is *not* to be a full, general purpose, operating system. It's a single-purpose host designed to run Docker containers and provide orchestration tools to manage containers at scale. * Independent release cadence from parent distribution to respond to rapidly changing ecosystem. * Deliver images for bare metal and important cloud/virtualization platforms (AWS, GCE, KVM, OpenStack). * Minimal footprint. ## Package Definition: ### Newer than / different from RHEL/CentOS 7 * tuned * glib2 * glib-networking * libsoup * docker * hawkey * libsolv * authconfig * python-blivet * anaconda * pykickstart * lorax * systemd ### New Packages * nss-altfiles * libgsystem * ostree * rpm-ostree-client ### Compose Tooling * rpm-ostree * rpm-ostree-toolbox ### Appendix A: Full Package List (RHEL 7 Atomic) ModemManager-glib-1.1.0-6.git20130913.el7.x86_64 NetworkManager-0.9.9.1-26.git20140326.4dba720.el7_0.x86_64 NetworkManager-glib-0.9.9.1-26.git20140326.4dba720.el7_0.x86_64 PyYAML-3.10-11.el7.x86_64 acl-2.2.51-12.el7.x86_64 audit-2.3.3-4.el7.x86_64 audit-libs-2.3.3-4.el7.x86_64 audit-libs-python-2.3.3-4.el7.x86_64 avahi-0.6.31-13.el7.x86_64 avahi-autoipd-0.6.31-13.el7.x86_64 avahi-libs-0.6.31-13.el7.x86_64 basesystem-10.0-7.el7.noarch bash-4.2.45-5.el7.x86_64 bash-completion-2.1-6.el7.noarch bind-libs-9.9.4-14.el7.x86_64 bind-libs-lite-9.9.4-14.el7.x86_64 bind-license-9.9.4-14.el7.noarch bind-utils-9.9.4-14.el7.x86_64 binutils-2.23.52.0.1-16.el7.x86_64 bridge-utils-1.5-9.el7.x86_64 btrfs-progs-3.12-4.el7.x86_64 bzip2-libs-1.0.6-12.el7.x86_64 c-ares-1.10.0-3.el7.x86_64 ca-certificates-2013.1.95-71.el7.noarch cadvisor-0.4.0-0.0.git5a6d06c0.el7.centos.x86_64 checkpolicy-2.1.12-6.el7.x86_64 chkconfig-1.3.61-4.el7.x86_64 cloud-init-0.7.5-1.el7_0.x86_64 coreutils-8.22-11.el7.x86_64 cpio-2.11-22.el7.x86_64 cracklib-2.9.0-11.el7.x86_64 cracklib-dicts-2.9.0-11.el7.x86_64 cronie-1.4.11-11.el7.x86_64 cronie-anacron-1.4.11-11.el7.x86_64 crontabs-1.11-6.20121102git.el7.noarch cryptsetup-libs-1.6.3-2.el7.x86_64 cups-libs-1.6.3-14.el7.x86_64 curl-7.29.0-19.el7.x86_64 cyrus-sasl-gssapi-2.1.26-17.el7.x86_64 cyrus-sasl-lib-2.1.26-17.el7.x86_64 dbus-1.6.12-8.el7.x86_64 dbus-glib-0.100-7.el7.x86_64 dbus-libs-1.6.12-8.el7.x86_64 dbus-python-1.1.1-9.el7.x86_64 device-mapper-1.02.84-14.el7.x86_64 device-mapper-event-1.02.84-14.el7.x86_64 device-mapper-event-libs-1.02.84-14.el7.x86_64 device-mapper-libs-1.02.84-14.el7.x86_64 device-mapper-persistent-data-0.3.2-1.el7.x86_64 dhclient-4.2.5-27.el7_0.1.x86_64 dhcp-common-4.2.5-27.el7_0.1.x86_64 dhcp-libs-4.2.5-27.el7_0.1.x86_64 diffutils-3.3-4.el7.x86_64 dmidecode-2.12-5.el7.x86_64 dnsmasq-2.66-12.el7.x86_64 docker-1.2.0-17.el7.x86_64 dracut-033-161.el7.x86_64 e2fsprogs-1.42.9-4.el7.x86_64 e2fsprogs-libs-1.42.9-4.el7.x86_64 elfutils-libelf-0.158-3.el7.x86_64 etcd-0.4.6-3.el7.centos.x86_64 ethtool-3.8-3.el7.x86_64 expat-2.1.0-8.el7.x86_64 file-libs-5.11-21.el7.x86_64 filesystem-3.2-18.el7.x86_64 findutils-4.5.11-3.el7.x86_64 fipscheck-1.4.1-5.el7.x86_64 fipscheck-lib-1.4.1-5.el7.x86_64 freetype-2.4.11-9.el7.x86_64 gawk-4.0.2-4.el7.x86_64 gdbm-1.10-8.el7.x86_64 geard-0-0.7.3.atomic.git78f7ef1.el7.x86_64 git-1.8.3.1-4.el7.x86_64 glib-networking-2.40.1-1.atomic.el7.x86_64 glib2-2.40.0-1.atomic.el7.x86_64 glibc-2.17-55.el7_0.1.x86_64 glibc-common-2.17-55.el7_0.1.x86_64 gmp-5.1.1-5.el7.x86_64 gnupg2-2.0.22-3.el7.x86_64 gnutls-3.1.18-9.el7_0.x86_64 gobject-introspection-1.36.0-4.el7.x86_64 gpgme-1.3.2-5.el7.x86_64 grep-2.16-1.el7.x86_64 groff-base-1.22.2-8.el7.x86_64 grubby-8.28-8.el7.x86_64 gsettings-desktop-schemas-3.8.2-3.el7.x86_64 gzip-1.5-7.el7.x86_64 hardlink-1.0-19.el7.x86_64 hawkey-0.4.12-3.atomic.1.el7.x86_64 hostname-3.13-3.el7.x86_64 info-5.1-4.el7.x86_64 initscripts-9.49.17-1.el7_0.1.x86_64 iproute-3.10.0-13.el7.x86_64 iptables-1.4.21-13.el7.x86_64 iputils-20121221-6.el7.x86_64 irqbalance-1.0.6-5.el7.x86_64 jansson-2.4-6.el7.x86_64 jbigkit-libs-2.0-11.el7.x86_64 json-c-0.11-4.el7_0.x86_64 json-glib-0.16.0-3.el7.x86_64 kernel-3.10.0-123.8.1.el7.x86_64 keyutils-libs-1.5.8-3.el7.x86_64 kmod-14-9.el7.x86_64 kmod-libs-14-9.el7.x86_64 kpartx-0.4.9-66.el7.x86_64 krb5-libs-1.11.3-49.el7.x86_64 kubernetes-0.2-0.9.gitf7a5ec3.el7.centos.x86_64 less-458-8.el7.x86_64 libacl-2.2.51-12.el7.x86_64 libarchive-3.1.2-7.el7.x86_64 libassuan-2.1.0-3.el7.x86_64 libattr-2.4.46-12.el7.x86_64 libbasicobjects-0.1.0-22.el7.x86_64 libblkid-2.23.2-16.el7.x86_64 libcap-2.22-8.el7.x86_64 libcap-ng-0.7.3-5.el7.x86_64 libcgroup-0.41-6.el7.x86_64 libcollection-0.6.2-22.el7.x86_64 libcom_err-1.42.9-4.el7.x86_64 libcurl-7.29.0-19.el7.x86_64 libdaemon-0.14-7.el7.x86_64 libdb-5.3.21-17.el7_0.1.x86_64 libdb-utils-5.3.21-17.el7_0.1.x86_64 libdhash-0.4.3-22.el7.x86_64 libedit-3.0-12.20121213cvs.el7.x86_64 libestr-0.1.9-2.el7.x86_64 libevent-2.0.21-4.el7.x86_64 libffi-3.0.13-11.el7.x86_64 libgcc-4.8.2-16.2.el7_0.x86_64 libgcrypt-1.5.3-4.el7.x86_64 libgnome-keyring-3.8.0-3.el7.x86_64 libgpg-error-1.12-3.el7.x86_64 libgsystem-2014.2-2.atomic.el7.x86_64 libgudev1-208-12.atomic.4.el7.centos.x86_64 libidn-1.28-3.el7.x86_64 libini_config-1.0.0.1-22.el7.x86_64 libipa_hbac-1.11.2-68.el7_0.5.x86_64 libjpeg-turbo-1.2.90-5.el7.x86_64 libldb-1.1.16-4.el7.x86_64 libmnl-1.0.3-7.el7.x86_64 libmodman-2.0.1-8.el7.x86_64 libmount-2.23.2-16.el7.x86_64 libndp-1.2-4.el7.x86_64 libnetfilter_conntrack-1.0.4-2.el7.x86_64 libnfnetlink-1.0.1-4.el7.x86_64 libnl-1.1.4-3.el7.x86_64 libnl3-3.2.21-6.el7.x86_64 libnl3-cli-3.2.21-6.el7.x86_64 libpath_utils-0.2.1-22.el7.x86_64 libpcap-1.5.3-3.el7.x86_64 libpipeline-1.2.3-3.el7.x86_64 libproxy-0.4.11-6.el7.x86_64 libpwquality-1.2.3-4.el7.x86_64 libref_array-0.1.3-22.el7.x86_64 libselinux-2.2.2-6.el7.x86_64 libselinux-python-2.2.2-6.el7.x86_64 libselinux-utils-2.2.2-6.el7.x86_64 libsemanage-2.1.10-16.el7.x86_64 libsemanage-python-2.1.10-16.el7.x86_64 libsepol-2.1.9-3.el7.x86_64 libsolv-0.6.4-2.el7.x86_64 libsoup-2.45.90-2.atomic.git20140601.2.el7.x86_64 libss-1.42.9-4.el7.x86_64 libssh2-1.4.3-8.el7.x86_64 libsss_idmap-1.11.2-68.el7_0.5.x86_64 libstdc++-4.8.2-16.2.el7_0.x86_64 libtalloc-2.0.8-4.el7.x86_64 libtasn1-3.3-5.el7_0.x86_64 libtdb-1.2.12-3.el7.x86_64 libteam-1.9-15.el7.x86_64 libtevent-0.9.18-6.el7.x86_64 libtiff-4.0.3-14.el7.x86_64 libuser-0.60-5.el7.x86_64 libutempter-1.1.6-4.el7.x86_64 libuuid-2.23.2-16.el7.x86_64 libverto-0.2.5-4.el7.x86_64 libwbclient-4.1.1-37.el7_0.x86_64 libwebp-0.3.0-3.el7.x86_64 libxml2-2.9.1-5.el7.x86_64 libxml2-python-2.9.1-5.el7.x86_64 libyaml-0.1.4-10.el7.x86_64 linux-firmware-20140804-0.1.git6bce2b0.el7_0.noarch lm_sensors-libs-3.3.4-10.el7.x86_64 logrotate-3.8.6-4.el7.x86_64 lua-5.1.4-14.el7.x86_64 lvm2-2.02.105-14.el7.x86_64 lvm2-libs-2.02.105-14.el7.x86_64 lzo-2.06-6.el7_0.2.x86_64 m2crypto-0.21.1-15.el7.x86_64 man-db-2.6.3-9.el7.x86_64 man-pages-3.53-5.el7.noarch mozjs17-17.0.0-10.el7.x86_64 mtools-4.0.18-5.el7.x86_64 nano-2.3.1-10.el7.x86_64 ncurses-5.9-13.20130511.el7.x86_64 ncurses-base-5.9-13.20130511.el7.noarch ncurses-libs-5.9-13.20130511.el7.x86_64 net-tools-2.0-0.17.20131004git.el7.x86_64 nettle-2.7.1-2.el7.x86_64 nmap-ncat-6.40-4.el7.x86_64 nspr-4.10.6-1.el7_0.x86_64 nss-3.16.2-2.el7_0.x86_64 nss-altfiles-0-1.atomic.git20131217gite2a80593.el7.x86_64 nss-softokn-3.16.2-1.el7_0.x86_64 nss-softokn-freebl-3.16.2-1.el7_0.x86_64 nss-sysinit-3.16.2-2.el7_0.x86_64 nss-tools-3.16.2-2.el7_0.x86_64 nss-util-3.16.2-1.el7_0.x86_64 numactl-libs-2.0.9-2.el7.x86_64 openldap-2.4.39-3.el7.x86_64 openssh-6.4p1-8.el7.x86_64 openssh-clients-6.4p1-8.el7.x86_64 openssh-server-6.4p1-8.el7.x86_64 openssl-libs-1.0.1e-34.el7_0.4.x86_64 ostree-2014.6-2.atomic.el7.x86_64 p11-kit-0.18.7-4.el7.x86_64 p11-kit-trust-0.18.7-4.el7.x86_64 pam-1.1.8-9.el7.x86_64 passwd-0.79-4.el7.x86_64 pcre-8.32-12.el7.x86_64 perl-5.16.3-283.el7.x86_64 perl-Carp-1.26-244.el7.noarch perl-Encode-2.51-7.el7.x86_64 perl-Error-0.17020-2.el7.noarch perl-Exporter-5.68-3.el7.noarch perl-File-Path-2.09-2.el7.noarch perl-File-Temp-0.23.01-3.el7.noarch perl-Filter-1.49-3.el7.x86_64 perl-Getopt-Long-2.40-2.el7.noarch perl-Git-1.8.3.1-4.el7.noarch perl-HTTP-Tiny-0.033-3.el7.noarch perl-PathTools-3.40-5.el7.x86_64 perl-Pod-Escapes-1.04-283.el7.noarch perl-Pod-Perldoc-3.20-4.el7.noarch perl-Pod-Simple-3.28-4.el7.noarch perl-Pod-Usage-1.63-3.el7.noarch perl-Scalar-List-Utils-1.27-248.el7.x86_64 perl-Socket-2.010-3.el7.x86_64 perl-Storable-2.45-3.el7.x86_64 perl-TermReadKey-2.30-20.el7.x86_64 perl-Text-ParseWords-3.29-4.el7.noarch perl-Time-Local-1.2300-2.el7.noarch perl-constant-1.27-2.el7.noarch perl-libs-5.16.3-283.el7.x86_64 perl-macros-5.16.3-283.el7.x86_64 perl-parent-0.225-244.el7.noarch perl-podlators-2.5.1-3.el7.noarch perl-threads-1.87-4.el7.x86_64 perl-threads-shared-1.43-6.el7.x86_64 pinentry-0.8.1-14.el7.x86_64 pkgconfig-0.27.1-4.el7.x86_64 policycoreutils-2.2.5-11.el7.x86_64 policycoreutils-python-2.2.5-11.el7.x86_64 polkit-0.112-5.el7.x86_64 polkit-pkla-compat-0.1-4.el7.x86_64 popt-1.13-16.el7.x86_64 ppp-2.4.5-33.el7.x86_64 procps-ng-3.3.9-6.el7.x86_64 pth-2.0.7-22.el7.x86_64 pygobject2-2.28.6-11.el7.x86_64 pygobject3-base-3.8.2-4.el7.x86_64 pygpgme-0.3-9.el7.x86_64 pyliblzma-0.5.3-11.el7.x86_64 pytalloc-2.0.8-4.el7.x86_64 python-2.7.5-16.el7.x86_64 python-IPy-0.75-6.el7.noarch python-backports-1.0-6.el7.noarch python-backports-ssl_match_hostname-3.4.0.2-4.el7.noarch python-boto-2.25.0-2.el7.noarch python-chardet-2.0.1-7.el7.noarch python-cheetah-2.4.4-5.el7.x86_64 python-configobj-4.7.2-7.el7.noarch python-dateutil-1.5-7.el7.noarch python-decorator-3.4.0-3.el7.noarch python-dmidecode-3.10.13-11.el7.x86_64 python-ethtool-0.8-5.el7.x86_64 python-iniparse-0.4-9.el7.noarch python-jsonpatch-1.2-2.el7.noarch python-jsonpointer-1.0-2.el7.noarch python-libs-2.7.5-16.el7.x86_64 python-markdown-2.1.1-2.el7.noarch python-pillow-2.0.0-17.gitd1c6db8.el7.x86_64 python-prettytable-0.7.2-1.el7.noarch python-pycurl-7.19.0-17.el7.x86_64 python-pygments-1.4-9.el7.noarch python-pyudev-0.15-6.el7.noarch python-requests-1.1.0-8.el7.noarch python-rhsm-1.12.3-1.el7.x86_64 python-setuptools-0.9.8-3.el7.noarch python-six-1.6.1-1.el7.noarch python-sssdconfig-1.11.2-68.el7_0.5.noarch python-urlgrabber-3.10-4.el7.noarch python-urllib3-1.5-8.el7.noarch pyxattr-0.5.1-5.el7.x86_64 qrencode-libs-3.4.1-3.el7.x86_64 readline-6.2-9.el7.x86_64 redhat-release-atomic-host-7.0-20140701.0.atomic.el7.x86_64 rpm-4.11.1-16.el7.x86_64 rpm-build-libs-4.11.1-16.el7.x86_64 rpm-libs-4.11.1-16.el7.x86_64 rpm-ostree-client-2014.106.2.g0f16e2e-1.atomic.el7.x86_64 rpm-python-4.11.1-16.el7.x86_64 rsync-3.0.9-15.el7.x86_64 rsyslog-7.4.7-6.el7.x86_64 samba-libs-4.1.1-37.el7_0.x86_64 sed-4.2.2-5.el7.x86_64 selinux-policy-3.12.1-153.el7_0.10.noarch selinux-policy-targeted-3.12.1-153.el7_0.10.noarch setools-console-3.3.7-46.el7.x86_64 setools-libs-3.3.7-46.el7.x86_64 setup-2.8.71-4.el7.noarch shadow-utils-4.1.5.1-15.atomic.1.el7.x86_64 shared-mime-info-1.1-7.el7.x86_64 sqlite-3.7.17-4.el7.x86_64 sssd-1.11.2-68.el7_0.5.x86_64 sssd-ad-1.11.2-68.el7_0.5.x86_64 sssd-client-1.11.2-68.el7_0.5.x86_64 sssd-common-1.11.2-68.el7_0.5.x86_64 sssd-common-pac-1.11.2-68.el7_0.5.x86_64 sssd-ipa-1.11.2-68.el7_0.5.x86_64 sssd-krb5-1.11.2-68.el7_0.5.x86_64 sssd-krb5-common-1.11.2-68.el7_0.5.x86_64 sssd-ldap-1.11.2-68.el7_0.5.x86_64 sssd-proxy-1.11.2-68.el7_0.5.x86_64 subscription-manager-1.12.5-1.git.9.1a03d02.el7.x86_64 subscription-manager-plugin-ostree-1.12.5-1.git.9.1a03d02.el7.x86_64 sudo-1.8.6p7-11.el7.x86_64 syslinux-4.05-8.el7.x86_64 syslinux-extlinux-4.05-8.el7.x86_64 sysstat-10.1.5-4.el7.x86_64 systemd-208-12.atomic.4.el7.centos.x86_64 systemd-libs-208-12.atomic.4.el7.centos.x86_64 systemd-sysv-208-12.atomic.4.el7.centos.x86_64 sysvinit-tools-2.88-14.dsf.el7.x86_64 tar-1.26-29.el7.x86_64 tcp_wrappers-libs-7.6-77.el7.x86_64 teamd-1.9-15.el7.x86_64 tmux-1.8-4.el7.x86_64 tuned-2.3.0-16.el7.noarch tuned-profiles-atomic-2.3.0-16.el7.noarch tzdata-2014g-1.el7.noarch usermode-1.111-5.el7.x86_64 ustr-1.0.4-16.el7.x86_64 util-linux-2.23.2-16.el7.x86_64 vim-minimal-7.4.160-1.el7.x86_64 virt-what-1.13-5.el7.x86_64 wpa_supplicant-2.0-12.el7.x86_64 xfsprogs-3.2.0-0.10.alpha2.el7.x86_64 xz-5.1.2-8alpha.el7.x86_64 xz-libs-5.1.2-8alpha.el7.x86_64 yum-3.4.3-118.el7.noarch yum-metadata-parser-1.1.4-10.el7.x86_64 zlib-1.2.7-13.el7.x86_64 -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

1 0

2014-10-03 @ 16:00 UTC ** Out of band Blocker Review Meeting
by Mike Ruckman 01 Oct '14

01 Oct '14

# F21 Blocker Review meeting # Date: 2014-10-03 # Time: 16:00 UTC (12:00 EDT, 09:00 PDT) # Location: #fedora-blocker-review on irc.freenode.net Towards the end of today's blocker review meeting, we decided it would be good for us to have a another meeting this week to deal with the unusually large number of blockers left we have to go through. Currently the number we still have is 15. So if you're available to help go through the list this Friday, we'd appreciate the help going through the list. On the other hand, if it works out for more people to do the meeting tomorrow, we can do that as well. I just feared it would be too short of notice to go ahead and schedule for tomorrow. Reply to test(a)lists.fedoraproject.org or ping me on IRC if tomorrow works better for you, we can adjust accordingly if there is enough interest. If you want to take a look at the accepted blockers, the full list can be found here: https://qa.fedoraproject.org/blockerbugs/milestone/21/beta/buglist We'll be evaluating these bugs to see if they violate the Beta Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F21 can be found on the wiki [0]. Product specific plans are still being solidified, but that should be sorted quickly. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting See you Friday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- // Mike -- Fedora QA freenode: roshi http://roshi.fedorapeople.org

1 0

[Fedocal] Reminder meeting : Fedora Cloud Workgroup
by Haïkel 01 Oct '14

01 Oct '14

Dear all, You are kindly invited to the meeting: Fedora Cloud Workgroup on 2014-10-03 from 17:00:00 to 18:00:00 UTC At fedora-meeting(a)irc.freenode.net The meeting will be about: Standing meeting for the Fedora Cloud Workgroup. Source: https://apps.fedoraproject.org/calendar//meeting/482/

1 0

Fwd: Fedora 21 Accepted Changes 100% Complete Deadline in two weeks
by Joe Brockmeier 01 Oct '14

01 Oct '14

FYI -------- Forwarded Message -------- Subject: Fedora 21 Accepted Changes 100% Complete Deadline in two weeks Date: Wed, 1 Oct 2014 09:18:09 -0400 (EDT) From: Jaroslav Reznik <jreznik(a)redhat.com> Reply-To: devel(a)lists.fedoraproject.org To: devel-announce(a)lists.fedoraproject.org Greetings! This time I'm sending "Accepted Changes 100% Complete" reminder a bit earlier than usually as we still have quite a lot of work to do on Changes and it's going to help other teams to participate in Changes process earlier (aka Docs team etc.). 2014-10-14 Accepted Changes 100% Complete Expected bug state is ON_QA - Change has to be code completed and can be tested in the Beta release (optionally by Fedora QA). Please make sure to update state of yours Change(s) bug(s) on time. In case of any problems, let me know, we will try to find solution. http://fedoraproject.org/wiki/Releases/21/Schedule Expect more nagging in Change bug(s) between now and Beta Freeze ;-). Thanks Jaroslav -- Your friendly Change Wrangler _______________________________________________ devel-announce mailing list devel-announce(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

1 0

severe f21 alpha bug: cloud images can't reboot
by Matthew Miller 01 Oct '14

01 Oct '14

See https://bugzilla.redhat.com/show_bug.cgi?id=1147998 This may be related to the automatic partition resizing, but I'm not sure. PVM-based booting, as in EC2 (uh, except for HVM in EC2, obviously) is unaffected. We should probably add "reboots properly in HMV environment; and reboots properly in PVM environment" to our validation tests and release criteria. -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

6 9

cloud wg official membership refresh?
by Matthew Miller 30 Sep '14

30 Sep '14

Hey all. I can't help but noticing a significant disconnect between the original wg membership (including last time we called for a check-in) and the people who are coming to meetings and doing a lot of the work. This doesn't reflect negatively on the original slate -- things just shape up differently and whatever. Overall, in fact, I think it's a very positive thing, because a) lots of new (and returning) faces (or names, at least, because... online) and b) this hasn't gotten in the way of us doing anything in any way. But I think we should name and ratify a new slate to better reflect the active state of the SIG in the past few months. Anyone opposed? -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

6 11

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud October 2014