cloud October 2016

cloud@lists.fedoraproject.org

21 participants
110 discussions

[cloud] #70: cloud-init output not going to the openstack log
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#70: cloud-init output not going to the openstack log ---------------------+------------------------------ Reporter: mattdm | Owner: Type: task | Status: new Priority: blocker | Milestone: Fedora 21 (Beta) Component: --- | Keywords: ---------------------+------------------------------ Some combination of "got something wrong in the kernel parameters or where cloud-init is sending its output". -- Ticket URL: <https://fedorahosted.org/cloud/ticket/70> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 1

[cloud] #43: procedures and process for getting updated images onto mirrors
by Fedora Cloud Trac Tickets 13 Oct '16

13 Oct '16

#43: procedures and process for getting updated images onto mirrors ------------------------------+------------------------------ Reporter: mattdm | Owner: Type: task | Status: new Priority: blocker | Milestone: Fedora 21 (Beta) Component: Software Updates | Keywords: ------------------------------+------------------------------ Right now, cloud images only get mirrored at GA release time. We need to figure out how to ship updates. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/43> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 6

[cloud] #165: Reimbursement for the Cloud FAD
by Fedora Cloud Trac Tickets 12 Oct '16

12 Oct '16

#165: Reimbursement for the Cloud FAD --------------------+-------------------- Reporter: kushal | Owner: jzb@… Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: --------------------+-------------------- Attaching the flight ticket + cab receipts. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/165> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

2 6

[Base] adopting the Docker base image into Atomic WG
by Colin Walters 10 Oct '16

10 Oct '16

Now that Cloud -> Atomic and will be focusing on Project Atomic, can we move the Docker base image into this group from the "Fedora Base" group? It never really made sense to me in Base; in: $ git log --format='%ae' fedora-docker-base.ks | sort -u admiller(a)redhat.com dennis(a)ausil.us jpazdziora(a)redhat.com kevin(a)fedoraproject.org kushaldas(a)gmail.com mattdm(a)mattdm.org maxamillion(a)fedoraproject.org pbrobinson(a)gmail.com vpavlin(a)redhat.com walters(a)verbum.org Most of the recent committers are outside of the Base group. And it makes sense to me to have synchronized landing pages/information for Atomic Host and the Docker base image.

3 2

[Fedocal] Reminder meeting : Fedora Cloud Workgroup
by Dusty Mabe 10 Oct '16

10 Oct '16

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

1 0

Updated Invitation: Fedora Release Tools Demo @ Tue Oct 11, 2016 12pm - 1pm (EDT) (acarter@redhat.com)
by Amanda Carter 10 Oct '16

10 Oct '16

This event has been changed. Title: Fedora Release Tools Demo (changed) Note: Hangouts on Air has been deprecated. While we look for another solution we'll hold this demo in bluejeans without a live broadcast or publicly available recording. Apologies for the inconvenience. -- Purpose: The purpose of a demo is to show our stakeholders what we completed this iteration, get feedback from them about the changes & set some context and expectation with them about our direction. Demo agenda & previous demos can be viewed here: http://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tool… Highlights today: Signing updates When: Tue Oct 11, 2016 12pm – 1pm Eastern Time Where: https://redhat.bluejeans.com/5889988581/ Calendar: acarter(a)redhat.com Who: (Guest list is too large to display) Event details: https://www.google.com/calendar/event?action=VIEW&eid=bzE5MWs3OWtzNWc0NjFkY… Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account cloud(a)lists.fedoraproject.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding

1 0

Re: Cloud and Server Q&A
by Adam Williamson 09 Oct '16

09 Oct '16

On Thu, 2016-09-29 at 16:51 -0600, Chris Murphy wrote: > But I don't > think QA clearly understands what cloud image(s) are release blocking, > as previously they were just the non-atomic images. I don't know what's going on with all this crap, but so far as I'm concerned I understand perfectly well what the release blocking images are. It's the ones listed on the release blocking images page which specifically exists for this purpose: https://fedoraproject.org/wiki/Fedora_Program_Management/ReleaseBlocking/Fe… (we still need to make the canonical version of this a JSON file somewhere and generate the human-readable version from the JSON, but meh, I haven't got around to it yet). if it doesn't say 'yes' there, it ain't release blocking. Maintaining that thing is the program manager's problem (i.e. jkurik's), not mine, but it does somewhat concern me the number of 'TBD's on there. I don't think the question of what images are 'release blocking' for F25 should be *remotely* live at this point: it should have been decided weeks ago, at least by Alpha release. And so far as I remember it, that's what the protocol was supposed to be, we weren't still supposed to be kicking around 'is it blocking?' discussions at Beta freeze. I'd personally be very unhappy with any attempt to significantly change what that page says right now. Which images are prominent on the download pages and how much of a relationship there is between that and 'release blocking' status is *also* not my problem, but I'd agree with you (Chris) that it'd be rather strange for the most prominently advertised deliverable for a given product not to be a release-blocking one. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

12 25

No Two Week Atomic Release
by Adam Miller 06 Oct '16

06 Oct '16

Hello all, I just wanted to post a quick update that there has not been a compose that passed all AutoCloud testing criteria for release in the past two weeks. It appears that the Vagrant libvirt images are failing. We will try again for a release next Two Week window. Thank you, -AdamM

4 5

Cloud Meeting Minutes 05-10-2016
by Sayan Chowdhury 05 Oct '16

05 Oct '16

================================== #fedora-meeting-1: fedora_cloud_wg ================================== Meeting started by sayan at 17:01:16 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2016-10-05/fedora_cloud_… . Meeting summary --------------- * Roll Call (sayan, 17:01:23) * Action items from last meeting (sayan, 17:03:53) * LINK: https://stg.pagure.io/atomic-wg/issues (kushal, 17:07:29) * LINK: https://github.com/rtnpro/motdgen (kushal, 17:08:12) * ACTION: kushal will clean up the wiki next week. (kushal, 17:13:52) * vagrant boxes fixups https://fedorahosted.org/cloud/ticket/136 (sayan, 17:14:11) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1290659#c42 (kushal, 17:18:36) * design, deploy and document Fedora OpenShift Playground (FOSP) https://fedorahosted.org/cloud/ticket/153 (sayan, 17:20:30) * make Fedora Atomic download page clearer https://fedorahosted.org/cloud/ticket/154 (sayan, 17:22:41) * Decide on post-GA update cadence for various deliverables https://fedorahosted.org/cloud/ticket/155 (sayan, 17:23:50) * Need complete Kickstart docs for Atomic Host https://fedorahosted.org/cloud/ticket/156 (sayan, 17:25:29) * Ship fedora-motd in F24 atomic image https://fedorahosted.org/cloud/ticket/160 (sayan, 17:27:26) * Finish new Fedora Cloud PRD https://fedorahosted.org/cloud/ticket/170 (sayan, 17:29:46) * Open Floor (sayan, 17:38:40) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1290659 (jbrooks, 17:49:05) Meeting ended at 18:00:28 UTC. Action Items ------------ * kushal will clean up the wiki next week. Action Items, by person ----------------------- * kushal * kushal will clean up the wiki next week. * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * kushal (73) * sayan (59) * jberkus (52) * jbrooks (34) * zodbot (18) * scollier (11) * rtnpro (10) * maxamillion (9) * gholms (8) * dustymabe (7) * walters (6) * vvaldez (2) * trishnag (2) * tflink (1) * imcleod (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- Sayan Chowdhury <https://sayanchowdhury.dgplug.org/> Senior Software Engineer, Fedora Engineering - Emerging Platform GPG Fingerprint : 0F16 E841 E517 225C 7D13 AB3C B023 9931 9CD0 5C8B Proud to work at The Open Organization!

1 0

[cloud] #160: Ship fedora-motd in F24 atomic image
by Fedora Cloud Trac Tickets 05 Oct '16

05 Oct '16

#160: Ship fedora-motd in F24 atomic image --------------------+--------------------- Reporter: rtnpro | Owner: rtnpro Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: meeting --------------------+--------------------- fedora-motd-0.1.3-1 has been tested and moved to stable F24 repo. We need to come up with a plan to ship it an upcoming Fedora 24 atomic cloud images. https://bodhi.fedoraproject.org/updates/FEDORA-2016-c8948356b9 -- Ticket URL: <https://fedorahosted.org/cloud/ticket/160> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 2

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud October 2016