Open Stack

Angus,

I think the appropriate place would be the openstack list, possibly with the [container] flag or [kolla] flag.

Regards
-steve


From: Angus Lees <gus at inodes.org<mailto:gus at inodes.org>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Thursday, February 5, 2015 at 4:02 PM
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: Re: [openstack-dev] [kolla][tripleo] Update on Kolla

Without taking anything away from this fine and sensible direction, where _would_ be a good place to discuss more radical container-based deployments?
(I'm fine if the answer is "use ad-hoc communication channels for now")

On Fri Feb 06 2015 at 7:24:12 AM Steven Dake (stdake) <stdake at cisco.com<mailto:stdake at cisco.com>> wrote:

On 2/5/15, 10:41 AM, "Paul Bourke" <paul.bourke at oracle.com<mailto:paul.bourke at oracle.com>> wrote:

>Hi Steve,
>
>Thanks for the update.  For those interested in Kolla development and
>discussion, where is the best place to go?
>
>Regards,
>-Paul

Paul,

We hang out in the irc channel #tripleo on freenode.

We use launchpad at http://launchpad.net/kolla

We use the openstack-dev mailing list with the tag [kolla]

Regards,
-steve



>
>On 05/02/15 17:25, Steven Dake (stdake) wrote:
>> Hey folks,
>>
>> I wanted to provide a brief update on where we are headed with Kolla.
>>   Initially Kolla began as a POC to show that containers could be used
>> to deploy OpenStack with the long term plan of integrating that
>> functionality into TripleO.  That goal has not changed.
>>
>> The tripleo community wants baby steps not outright replacement of the
>> infrastructure as was proposed by using Kubernetes in Kolla as a
>> dependency in this review [1].   Our first step in this process will be
>> to create three new container types.  We will create a controller node,
>> a storage node, and a compute node.  We have proven that compute can be
>> used.[2]  Further, one of our community members is working on a DIB
>> elements->container tool here [3] and we plan to use this along with our
>> other R&D in the area to integrate container tech into tripleo.
>>
>> I¹m not quite sure how it will all come together, but after numerous
>> discussions with folks from the tripleo and heat teams, I believe we can
>> find a path forward.
>>
>> Regards
>> -steve
>>
>>
>> [1] https://review.openstack.org/#/c/144199/
>> [2]
>>
>>http://sdake.io/2015/01/28/an-atomic-upgrade-process-for-openstack-comput
>>e-nodes/
>> _[3] _https://review.openstack.org/#/c/152017/
>>
>>
>>
>>_________________________________________________________________________
>>_
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>>OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>__________________________________________________________________________
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150205/233aab8e/attachment.html>