cloud November 2014

cloud@lists.fedoraproject.org

25 participants
90 discussions

Debugging the failed Atomic compose
by Colin Walters 07 Nov '14

07 Nov '14

Koji task: http://koji.fedoraproject.org/koji/taskinfo?taskID=7978937 OZ log: https://kojipkgs.fedoraproject.org//work/tasks/8937/7978937/oz-x86_64.log It looks to me like we hung in the rpm -qa listing. Hard to guess why without being able to get in there with a debugger or something =/ Any ideas? We can try submitting kickstart files with debugging bits.

1 0

Fwd: #6032: Atomic image is missing from the mirrors
by Joe Brockmeier 07 Nov '14

07 Nov '14

----- Forwarded Message ----- From: "Fedora Release Engineering" <rel-eng(a)fedoraproject.org> Sent: Thursday, November 6, 2014 6:14:27 PM Subject: Re: #6032: Atomic image is missing from the mirrors #6032: Atomic image is missing from the mirrors -----------------------------+----------------------- Reporter: jzb | Owner: rel-eng@… Type: defect | Status: closed Milestone: Fedora 21 Beta | Component: koji Resolution: wontfix | Keywords: Blocked By: | Blocking: -----------------------------+----------------------- Changes (by ausil): * status: new => closed * resolution: => wontfix Comment: you will need to file a websites bug to get the links to atomic removed. http://koji.fedoraproject.org/koji/taskinfo?taskID=7978937 is the failed task, I am not really sure why it failed to compose. but as it failed and is not a release blocking thing it missed the boat. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6032#comment:1> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project _______________________________________________ rel-eng mailing list rel-eng(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/rel-eng -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

1 0

Cloud SIG meeting minutes 2014-11-05
by Kushal Das 06 Nov '14

06 Nov '14

========================= #fedora-meeting: Cloud WG ========================= Meeting started by kushal at 19:02:50 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2014-11-05/fedora-meeting.2… . Meeting summary --------------- * Roll Call (kushal, 19:03:04) * Previous Meeting Follow-up (kushal, 19:06:55) * LINK: https://fedorahosted.org/cloud/report/9 (roshi, 19:09:27) * LINK: http://fedoraproject.org/get-prerelease#cloud (jzb, 19:13:41) * ACTION: kushal will keep an eye to verify actual release images on the mirrors (kushal, 19:19:05) * ACTION: jzb to file rel-eng ticket for missing images (kushal, 19:28:57) * Plan test days for Atomic image (#74) (kushal, 19:29:56) * LINK: https://fedorahosted.org/rel-eng/ticket/6032 (kushal, 19:30:14) * ACTION: jzb follow up on tc for Atomic test days image (jzb, 19:32:53) * LINK: https://fedorahosted.org/cloud/ticket/74 (jzb, 19:33:05) * Article for Fedora Magazine on "state of cloud SIG/product" for beta release (75) (kushal, 19:46:09) * LINK: https://fedorahosted.org/cloud/la/75 (kushal, 19:46:23) * Public Uploaded Images Criteria (#80) (kushal, 19:51:10) * LINK: https://fedorahosted.org/cloud/ticket/80 (kushal, 19:51:18) * participation in OpenShift Commons (#83) (kushal, 19:59:21) * LINK: https://fedorahosted.org/cloud/ticket/83 (kushal, 19:59:29) * LINK: https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2014-Sep… (dustymabe, 20:04:29) * LINK: http://origin.openshift.com/commons (kushal, 20:15:29) * Open Floor (kushal, 20:15:51) Meeting ended at 20:28:33 UTC. Action Items ------------ * kushal will keep an eye to verify actual release images on the mirrors * jzb to file rel-eng ticket for missing images * jzb follow up on tc for Atomic test days image Action Items, by person ----------------------- * jzb * jzb to file rel-eng ticket for missing images * jzb follow up on tc for Atomic test days image * kushal * kushal will keep an eye to verify actual release images on the mirrors * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * kushal (107) * jzb (69) * dustymabe (54) * mattdm (37) * roshi (23) * zodbot (13) * oddshocks (10) * lalatenduM (5) * scollier (1) * jsmith (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot Kushal -- Fedora Cloud Engineer CPython Core Developer Director Python Software Foundation http://kushaldas.in

2 1

fedora atomic beta feedback (in short: many things broken)
by Matthew Miller 06 Nov '14

06 Nov '14

https://bugzilla.redhat.com/show_bug.cgi?id=1160833 -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

3 2

help wanted -- test/karma docker-storage-setup
by Matthew Miller 05 Nov '14

05 Nov '14

As Joe noted the other day, Fedora Atomic is intended to come with this service, which will create storage space for Docker images. As mentioned in the IRC meeting, at this point, the plan is to get this to stable after the beta (before the feature freeze, as soon as possible), to update the Atomic tree definition, and then to request a test candidate including it. But the first step is getting it to stable. So, testers wanted -- https://admin.fedoraproject.org/updates/docker-storage-setup-0.0.3-1.fc21 second priority after http://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test of course :) -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

5 17

Meeting On Wednesday at 19:00 UTC
by Dusty Mabe 05 Nov '14

05 Nov '14

I have updated fedlocal [1] to reflect the new meeting time. One slight problem I just realized is that Daylight Savings ends on November 2nd so this may change some member's availability. I guess we will cross that bridge when we get there. Dusty [1] - https://apps.fedoraproject.org/calendar/cloud/2014/10/27/

4 4

Both atomic and base F21 beta AMIs available
by David Gay 05 Nov '14

05 Nov '14

Good news, everyone! Both base and atomic AMIs seem to be working properly (x86_64). As per our previous discussion, the 32 bit cloud base image needs to be rebuilt due to a PAE kernel problem, so that won't be available for now. robyduck has said that he'll be able to add the AMI IDs to the official page in a couple hours, but for now, you can find them on my FedoraPeople page: https://oddshocks.fedorapeople.org/ They're public and good to go, so you should be able to boot them and SSH in with the username 'fedora'. Let me know if there are any problems! -- oddshocks

2 1

32 bit AMI registration boot problem: explaination and possible solutions
by David Gay 04 Nov '14

04 Nov '14

Hi -- these beta AMIs need to be done today. 64 bit base AMIs have been successfully uploaded, but I *still* haven't nailed the problem with the 32 bit registration method. Or rather, I've isolated the problem, but haven't found a solution. Searching the net has not been going well with this particular issue, as most people don't seem to deal with 32 bit images much anymore, and barely any EC2 instance types even support the architecture anymore. I've written up a little problem statement with few solutions. If anyone has experience with this stuff or ideas/input, it's greatly welcomed. Problem ------- 64 bit base image works 100% fine, 32 bit image fails to boot with a probable kernel issue. System Log ---------- The below log likely indicates the attempted use of an invalid kernel. However, I _do_ properly specify the AKI of the proper architecture and region. http://ur1.ca/ioklt Givens ------ 1. I register AMIs based on an EBS volume snapshot. 2. You cannot have an instance that is both 32 bit architecture and EBS-optimized. 3. I use a 64 bit "utility instance" (so that I can use EBS backing) to write the 32-bit raw image file to a secondary volume. 3a. That volume is necessarily EBS, as previously mentioned. 4. The registered 32 bit AMI is tested by spinning up a 32 bit instance (non-EBS) based on the AMI I register from the snapshotted EBS volume. (I assume this is where the problem stems from, AKA, maybe you can't register a 32 bit AMI based on an EBS-backed volume?) 5. 64 bit cloud base AMI registers perfectly fine with this same setup (of course, I use all 64 bit instances and kernel IDs for this process). Hopeful Solution ---------------- There _is_ some sort of way to get a 32 bit AMI registered and bootable with this EBS method. Less-nice Solution ------------------ Do an instance store backed registration manually with a manifest file for the 32 bit images only. *I don't have experience with instance store registration, so help would be welcome, though I can probably figure it out*. Last-ditch Solution ------------------- I've been lead to believe that other folks like kushal may have been able to register the 32 bit AMIs succesfully just by straight up using the ec2 command line tools. If you have a good method for this, send it my way, and I'll run it locally to ensure that we have 32 bit beta AMIs today, since this is sort of the hard deadline. Thanks for reading this longer email! -- oddshocks

7 16

[Fedocal] Reminder meeting : Fedora Cloud Workgroup
by Dusty Mabe 03 Nov '14

03 Nov '14

Dear all, You are kindly invited to the meeting: Fedora Cloud Workgroup on 2014-11-05 from 19:00:00 to 20: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

[cloud] #82: Requesting access to AWS community cloud account
by Fedora Cloud Trac Tickets 03 Nov '14

03 Nov '14

#82: Requesting access to AWS community cloud account -------------------------------------------------+------------------------- Reporter: oddshocks | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 21 Component: Infrastructure & Release | (Beta) Engineering | Keywords: aws, | permissions -------------------------------------------------+------------------------- Hi, I'd like to have the password for the AWS community cloud account, as well as an access/secret key set. I need this information to continue developing Fedimg and work with the cloud folks on providing Fedora cloud/atomic/etc images as AMIs on EC2. Thanks! Oh, and yeah, my PGP key is updated on my FAS account. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/82> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 3

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud November 2014