Cloud SIG meeting minutes 2014-11-05
by Kushal Das
=========================
#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...
.
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-S...
(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
9 years, 5 months
Both atomic and base F21 beta AMIs available
by David Gay
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
9 years, 5 months
32 bit AMI registration boot problem: explaination and possible solutions
by David Gay
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
9 years, 5 months
[cloud] #82: Requesting access to AWS community cloud account
by Fedora Cloud Trac Tickets
#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
9 years, 5 months
