cloud October 2014

cloud@lists.stg.fedoraproject.org

29 participants
99 discussions

ec2 elastic network interfaces for fedora
by Ethan Tuttle 22 Oct '14

22 Oct '14

Hi fedora-cloud people. I just posted some code on github that I thought would be of interest here. It's a port of amazon's ec2-net-utils RPM to fedora 20. This adds proper support for elastic network interfaces to F20 instances on ec2. https://github.com/etuttle/ec2-utils There's a README there with some gory details as well as a link to a copr repository for builds. This work may not be appropriate for Fedora's base ami (which is cross-cloud I think)? But in the future, it would be nice if the official AMI could support ENI's out-of-the-box. I find ENI's very useful for migrating services between instances with minimal downtime. Thanks, Ethan

1 0

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

22 Oct '14

Dear all, You are kindly invited to the meeting: Fedora Cloud Workgroup on 2014-10-24 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

reconsider cloud environment in anaconda ui for f21
by Matthew Miller 22 Oct '14

22 Oct '14

Right now, Cloud is the default environment in the Anaconda UI. This is clearly not right, and there's an urgent ticket to do Something Else. (https://fedorahosted.org/fesco/ticket/1358) I know there was general agreement that we want it there, but I wonder if it would be better to defer to F22. That's because a) I still think it might be confusing to people who don't realize that it's for a guest image, but _mostly_ because there are enough kickstart hacks (including the one which should make growpart not break rebooting) that the comps environment doesn't really provide a good starting point for someone making a cloud image. Getting those hacks out of kickstart seems like a good goal for f22, but I'd like to drop it for now if you agree. What do you think? -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

4 5

2014-10-22 @ 1600 UTC ** Fedora 21 Blocker Review Meeting
by Mike Ruckman 22 Oct '14

22 Oct '14

# F21 Blocker Review meeting # Date: 2014-10-22 # Time: 16:00 UTC (12:00 EDT, 09:00 PDT) # Location: #fedora-blocker-review on irc.freenode.net We've already had one blocker review meeting this week (which is likely why I forgot to send this email until now), but it's time for another! With Go/No-Go being decided tomorrow we have plenty to do in order to be ready. So far we've got 9 proposed blockers and and 4 proposed freeze exceptions to look through for this 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 in a couple hours! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- // Mike -- Fedora QA freenode: roshi http://roshi.fedorapeople.org

1 0

okay so.... tc4 is unbootable
by Matthew Miller 20 Oct '14

20 Oct '14

I thought the most likely culprit might be my hack for the growpart/sfdisk/mbr problem, but it seems like the kickstart file is actually truncated -- see http://koji.fedoraproject.org/koji/taskinfo?taskID=7900887 (and click on https://kojipkgs.fedoraproject.org//work/tasks/887/7900887/fedora-cloud-bas… Something is not right.... -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

1 0

New in beta to highlight?
by Joe Brockmeier 20 Oct '14

20 Oct '14

Hi all, Any big new features/changes in the beta we should be highlighting in the beta announcement? Please let me know ASAP and I'll incorporate them. Or - edit boldly! https://fedoraproject.org/wiki/F21_Beta_release_announcement Best, jzb -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

3 2

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

20 Oct '14

1 0

2014-10-17 @ 1700 ** Cloud WG Meeting Minutes
by Mike Ruckman 17 Oct '14

17 Oct '14

========================= #fedora-meeting: Cloud WG ========================= Meeting started by roshi at 17:04:13 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2014-10-17/fedora-meeting.2… . Meeting summary --------------- * Roll Call (roshi, 17:04:34) * Previous Meeting Follow-up (roshi, 17:07:17) * LINK: https://fedoraproject.org/wiki/Fedora_21_Beta_Release_Criteria#Cloud_Produc… (roshi, 17:11:23) * dustymabe to figure out FAS information for a Digital Ocean account (roshi, 17:18:28) * dustymabe working with mattdm and legal to get DO TOS approved (dustymabe, 17:19:21) * Releaseing Updated images (#43) (roshi, 17:20:24) * LINK: https://fedorahosted.org/cloud/ticket/43 (roshi, 17:20:29) * ACTION: dustymabe to updateticket #43 (roshi, 17:30:28) * Smoke Tests (#38) (roshi, 17:30:47) * LINK: https://fedorahosted.org/cloud/ticket/38 (roshi, 17:31:01) * Atomic Testday (#74) (roshi, 17:33:51) * LINK: https://fedorahosted.org/cloud/ticket/74 (roshi, 17:33:56) * still waiting on a date to begin planning for an Atomic Testday (roshi, 17:35:06) * State of SIG article for magazine (#75) (roshi, 17:37:51) * LINK: https://fedorahosted.org/cloud/ticket/75 (roshi, 17:37:55) * ACTION: dustymabe to ask in ticket #51 if it can be closed (roshi, 17:41:16) * Release Criteria (#77) (roshi, 17:41:40) * LINK: https://fedorahosted.org/cloud/ticket/77 (roshi, 17:41:47) * Open Floor (roshi, 17:43:03) * LINK: https://fedoraproject.org/wiki/Changes/Convert_Fedora_Cloud_Image_to_Fedora… this is done (kushal, 17:43:11) * Kushal started working on https://fedorahosted.org/cloud/ticket/62 (kushal, 17:46:01) * LINK: https://fedorahosted.org/cloud/ticket/62 (kushal, 17:46:06) * kushal submitted patch(s) to rel-eng team so that nightly builds from masher script get build properly. (kushal, 17:49:00) * ACTION: agrimm to update credentials on AWS (roshi, 17:54:52) Meeting ended at 17:58:42 UTC. Action Items ------------ * dustymabe to updateticket #43 * dustymabe to ask in ticket #51 if it can be closed * agrimm to update credentials on AWS Action Items, by person ----------------------- * agrimm * agrimm to update credentials on AWS * dustymabe * dustymabe to updateticket #43 * dustymabe to ask in ticket #51 if it can be closed * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * roshi (114) * dustymabe (45) * kushal (32) * oddshocks (13) * zodbot (11) * lalatenduM (6) * agrimm (4) * nirik (2) * number80 (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- // Mike -- Fedora QA freenode: roshi http://roshi.fedorapeople.org

1 0

[cloud] #77: Release Criteria Discussion
by Fedora Cloud Trac Tickets 17 Oct '14

17 Oct '14

#77: Release Criteria Discussion --------------------------+--------------------- Reporter: roshi | Owner: roshi Type: task | Status: new Priority: normal | Milestone: Future Component: Testing & QA | Keywords: meeting --------------------------+--------------------- I proposed a couple criteria to be added for the Beta Cloud release. Namely, discussion about if updates between cloud releases is something we want/need. Relevant threads: - Test@ https://lists.fedoraproject.org/pipermail/test/2014-October/123060.html - Cloud@ https://lists.fedoraproject.org/pipermail/cloud/2014-October/004311.html It also occurs to me that we need a criteria for naming one of your cattle, something along the lines of migrating a cloud image, that started as a Cloud Product, to a Server Product. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/77> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 3

ostree compose script developments
by David Gay 17 Oct '14

17 Oct '14

Hi -- At this point, I thought I'd send out an email with my current understanding of the processes we need to add to the releng scripts for ostree, as well as some questions regarding these compose scripts, specifically: - buildbranched [https://git.fedorahosted.org/cgit/releng/tree/scripts/buildbranched] - buildrawhide [https://git.fedorahosted.org/cgit/releng/tree/scripts/buildrawhide] Disclaimer: I have a limited understanding of releng processes, so feel free to correct me on anything. I'm simply hoping to help move along our ostree work faster. It seems to me that we should add in the bulk of the ostree processes after the compose process completes, but before the rsync. In buildbranched, this is at line 180. In buildrawhide, this is at line 172. This would be where we'd init an ostree repo somewhere like /srv/ostree/repo, use our treefile to run the compose (which captures RPMs to build the tree), and then generate a summary of the repo with `ostree summary -u`. For our purposes, the summary file resulting from this process would serve a comparable purpose as the repomd.xml file we use for our "standard" builds. My thinking is that these scripts could easily accomplish this process, and get the summary file to where it needs to be for use with the MirrorManager metalink business that needs to be tackled next. That's my perception of what needs to be done after poking around. Next, some questions: 1. n00b question: I'm not sure how what needs to go *in* an image is decided. In order to run the ostree compose, we need to generate a treefile that contains -- among other things -- a list of RPMs that need to be installed. What's the best way to get content for that list? 2. The treefile also needs a branch name for the content. Any input on the naming scheme? 3. The treefile can also take a number of optional values. I'm not sure if any are needed for this process, but they are listed here: https://github.com/projectatomic/rpm-ostree/blob/master/doc/treefile.md Perhaps `gpg_key`, `boot_location`, and/or `units`? 4. What's the best way for me to test the changes I make to the scripts? Can I set up some sort of local build environment, or get access to a testing machine? Perhaps I should just send a patch to someone or a list? I think that's it for now. I can pop in with MirrorManager stuff after we get this compose process working to the point that we're getting a good summary file. -- David

3 2

← 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