Re: [atomic] OpenStack Magnum concerns about Project Atomic

[Dusty Mabe <dusty dustymabe com>]

On 02/24/2016 10:13 AM, Steve Gordon wrote:
> Hi all,
> 
> Not sure if this is the right place as the Magnum folks are primarily using the Fedora Atomic images as their base but I was recently pointed to this IRC discussion where the Magnum folks outlined some of their concerns resulting from interacting with the Atomic images which are causing them to look elsewhere:
> 
>     http://eavesdrop.openstack.org/irclogs/%23openstack-containers/%23openstack-containers.2016-02-15.log.html
> 
> This is in some ways a continuation of this earlier thread:
> 
>     http://lists.openstack.org/pipermail/openstack-dev/2016-February/thread.html#85699
> 
> Trying to boil down the comments into a summary:
> 
> * Depending on timing age of components in Fedora Atomic leads to a need for Magnum folks to rebuild image, at least until such time as more of the pieces are containerized (k8s/etcd/flanel) [1].
> * Rebuild image documentation lacks troubleshooting information (I encountered this myself, there are plenty of places for things to go off the rails in the compose and create-vm-disk steps and the tooling provides very limited error output in some cases). 
> * Lack of clarity around if or when originally proposed build cadences will be hit for Fedora Atomic - I think this was originally proposed as 2-weekly but it's hard to tell if that has actually been hit to an outsider. To me it looks like yes [2] but do we record anywhere when a new build was pushed out to the mirrors as the current stable?
> * Doesn't really feel like an active global community versus e.g. CoreOS. I know this is a challenging thing to "solve" but I list it as it is part of their concern, I myself have asked a question in the #atomic IRC and it was eventually answered but only when US East coast folks were up and awake again.
> 
> I know this is very high level feedback in many cases and difficult to action but wanted to highlight it . Scott has already answered my query on the Fedora cloud list w.r.t. containerization plans for the services mentioned which I think would help Magnum folks a lot [1], and I see we are apparently now doing two-weekly updates to the Fedora cloud image [2] though as I mentioned it would be great if we can illustrate the history of this in terms of regular builds produced/pushed.

Hey Steve,

So we have been working out the process a bit for doing these releases. The process right
now isn't the best and sometimes leads to delays in release, but there are plans to resolve
these problems (I believe for the F24 time frame). That being said, here are the following 
release emails accompanied by the release date:

12/01 http://lists.fedoraproject.org/archives/list/cloud lists fedoraproject org/message/EOMKYV6Z3H4N4TVBVNYV47VXFNAF2XZM/
12/15 http://lists.fedoraproject.org/archives/list/cloud lists fedoraproject org/message/T6PVY62LR43LJE7JM2SHHNTKATQZZD76/
01/12 http://lists.fedoraproject.org/archives/list/cloud lists fedoraproject org/message/HYMEDBCGFU7VYNZQLXMAINGIH7M65TAT/
01/27 http://lists.fedoraproject.org/archives/list/cloud lists fedoraproject org/message/TG2GOTOYNRM6HZINT4A52XLDQKYICFSI/
02/12 http://lists.fedoraproject.org/archives/list/cloud lists fedoraproject org/message/TG2GOTOYNRM6HZINT4A52XLDQKYICFSI/
02/23 http://lists.fedoraproject.org/archives/list/cloud lists fedoraproject org/message/CW5BQS3ODAVYJGAJGAZ6UA3XQMKEISVJ/

I hope this helps answers one of the questions you had. 

Dusty