cloud October 2014

cloud@lists.stg.fedoraproject.org

29 participants
99 discussions

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

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud October 2014