cloud April 2014

cloud@lists.fedoraproject.org

31 participants
76 discussions

[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] #50: Deliverables and release engineering changes for Fedora.Next
by Fedora Cloud Trac Tickets 01 Aug '14

01 Aug '14

#50: Deliverables and release engineering changes for Fedora.Next ----------------------+--------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: major | Milestone: Future Component: Planning | Keywords: meeting ----------------------+--------------------- https://lists.fedoraproject.org/pipermail/cloud/2014-April/003759.html See https://fedorahosted.org/rel-eng/ticket/5891 I'm only making a ticket here to get it in the meeting :) -- Ticket URL: <https://fedorahosted.org/cloud/ticket/50> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 2

[cloud] #16: rename cloud spin kickstart to distinguish the cloud base image
by Nobody 02 Jun '14

02 Jun '14

#16: rename cloud spin kickstart to distinguish the cloud base image --------------------+-------------------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: minor | Milestone: Fedora 21 (Branch) Component: --- | Keywords: meeting --------------------+-------------------------------- I have been calling the new general purpose cloud image "Fedora Cloud Base" to distinguish it from the Docker image, the Big Data image, and a potential OpenShift image (if that turns out to not be the Docker one.) I propose we officially call the general-purpose cloud image (currently, the only one) "Fedora Cloud Base". And I'm tagging this with the meeting keyword for ratification. One behind-the-scenes complication is that the spins process involves assembling kickstart fragments, one of which is suffixed with "-base.ks" already, so there is a "cloud-image-base.ks", which would presumably became "cloud-base-base.ks", which is... awesome? silly? One of those. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/16> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

2 3

[cloud] #46: Project Atomic and Fedora Docker C
by Fedora Cloud Trac Tickets 15 May '14

15 May '14

#46: Project Atomic and Fedora Docker C -------------------------------+-------------------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Branch) Component: Docker Host Image | Keywords: meeting -------------------------------+-------------------------------- This is a meeting discussion item. Red Hat has launched http://www.projectatomic.io/ with a lot of bits and pieces that we are already familiar with, plus a few new parts (e.g., geard) that have just landed in Fedora. We have https://fedoraproject.org/wiki/Changes/Docker_Cloud_Image in progress, with a very strong alignment. So, the basic questions are: * Do we want to make the Fedora Docker Host be "Fedora Atomic Host"? * If so, how do we make that happen? * If not, how are we positioning the alternative options? * In either case, what things need to be done? * Who will do those things? -- Ticket URL: <https://fedorahosted.org/cloud/ticket/46> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 6

[cloud] #45: need three packages added to the fedora21 cloud iamge
by Fedora Cloud Trac Tickets 08 May '14

08 May '14

#45: need three packages added to the fedora21 cloud iamge ------------------------------+-------------------------------- Reporter: sdake | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Branch) Component: Cloud Base Image | Keywords: OpenStack ------------------------------+-------------------------------- We need os-collect-config, os-apply-config, and os-refresh-config added to the Fedora cloud images for both OpenStack Heat and OpenStack TripleO. These agents are used for new features or basic functionality in the case of TripleO. These are based on Python3 and import the Python3 runtime when installed. First package: 29 MB (most of the 29MB is the python3 runtime) Second package: 21 MB Third package: 22KB -- Ticket URL: <https://fedorahosted.org/cloud/ticket/45> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 7

Fedora Cloud Working Group Six Month Check-in
by Joe Brockmeier 08 May '14

08 May '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, According to our governance charter[1] the working group's nine voting members are supposed to "confirm their continued membership every six months." If I'm not mistaken, the current membership was established mid-October last year - which puts us due about now. Here's the current membership: James Antill Robyn Bergeron Joe Brockmeier Haïkel Guémar Sam Kottler Sandro Mathys Matthew Miller (FESCo Liaison) Frankie Onuonga Mattias Runge If you're interested in continuing membership, could you please confirm by the next IRC meeting on Thursday next week? Alternatively, if anyone would like to step down this is a good time to do so. This is members with a binding vote on any decisions that need to be voted on - anyone, of course, is welcome and encouraged to participate in cloud WG activities, meetings, etc. Best, jzb [1] https://fedoraproject.org/wiki/Cloud/Governance - -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTWUBWAAoJEKbW5zOgIHzUwtwH/01Jhqa1WvMws6AosR5m8DO/ zlhA+zG1qzSw1q30B41e2qAvsihJMYAB88S7QRL2qJBsRdFz2d0BSnptryY7vIma 6MEViPOkDVyslarAzsGpU8aZk5mldg8TGpum59JrwannXp5AoxqRxfX1Ik29mgyS cLWL3p+3l+VA5SgkvzPNtvhah90RPhUHTGa/r3TU+vC4vJkxT8MXyF0i+xXR/7pV uljMYs1RlH7n2jdW9Q7X44mznm5+ooSyu2kP/XW+2sjO8TH3jKrWL+zvMUw77cfw 4fH+xiC9Qlg9NTABZ8UEB4B3jzvZTZPQbZDxTVFHImwGVqqF014as1rfKNYRpvs= =/hvZ -----END PGP SIGNATURE-----

5 5

Initial Draft of QA Docs
by Mike Ruckman 05 May '14

05 May '14

As per the meeting today [0] here's an email detailing what I've put together so far for QA/Testing documentation for ticket #41 [1]. It's not a ton, but it somewhere to start from. I'm keeping my working copies in my personal wiki space [2] for now. I cut out the things I didn't think were relevant to Cloud from the Release Criteria and created a draft of a test plan [3]. Some of the areas are sparse on information because I wasn't sure what to put down. On my list of things to do I still need to start on validation matrices for each of the milestones - but I wanted to get some feedback before putting all that together (Didn't want to spend too much time going in the wrong direction if this isn't what you all had in mind). Any feedback and edits would be great. Thanks! // Mike [0] http://meetbot.fedoraproject.org/fedora-meeting/2014-04-24/fedora-meeting.2… [1] https://fedorahosted.org/cloud/ticket/41 [2] https://fedoraproject.org/wiki/User:Roshi/QA/Cloud_Docs [3] https://fedoraproject.org/wiki/User:Roshi/QA/Cloud_Docs/Test_Plan

2 1

[cloud] #49: Spins Process for Cloud Images
by Fedora Cloud Trac Tickets 01 May '14

01 May '14

#49: Spins Process for Cloud Images ---------------------+-------------------------------- Reporter: red | Owner: Type: task | Status: new Priority: blocker | Milestone: Fedora 21 (Branch) Component: --- | Keywords: meeting ---------------------+-------------------------------- So, according to ausil, we're supposed to follow the standard Spin Process to create additional cloud products. Are we okay with that or do we want to cause some ruckus? :) It seems the process is also used by e.g. the (kinda special) ARM images, etc. For reference: http://fedoraproject.org/wiki/Spins_Process -- Ticket URL: <https://fedorahosted.org/cloud/ticket/49> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 3

[cloud] #47: Crucial basic Docket Host Image decisions
by Fedora Cloud Trac Tickets 01 May '14

01 May '14

#47: Crucial basic Docket Host Image decisions -------------------------------+-------------------------------- Reporter: red | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Branch) Component: Docker Host Image | Keywords: meeting -------------------------------+-------------------------------- Originally brought up in ticket #19, there's a few basic but crucial decisions to be made regarding the Fedora Docket Host Image. Therefore, I'm proposing the following set of decisions for the next meeting: - Whether to use (rpm-)ostree (aka Fedora Atomic Initiative) - Whether to remove yum/dnf (if going with ostree) - Whether to replace cloud-init by coreos' cloud-init or min-metadata- service - Whether to kick out python (if we decided against yum/dnf and cloud- init) Some of these decisions also benefit or contradict decisions to be made in ticket #46. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/47> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 1

Fwd: Re: Fedora Cloud Working Group Six Month Check-in
by Haïkel 30 Apr '14

30 Apr '14

Sorry, I didn't check that the android mail client did a reply all or not. Best regards, H. ---------- Message transféré ---------- De : "H. Guémar" <hguemar(a)fedoraproject.org> Date : 24 avr. 2014 18:51 Objet : Re: Fedora Cloud Working Group Six Month Check-in À : <jzb(a)redhat.com> Cc : Hi, I hereby confirm my membership. See you, next week ! H.

5 6

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud April 2014