<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=euc-kr">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Angus,</div>
<div><br>
</div>
<div>I think the appropriate place would be the openstack list, possibly with the [container] flag or [kolla] flag.</div>
<div><br>
</div>
<div>Regards</div>
<div>-steve</div>
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Angus Lees <<a href="mailto:gus@inodes.org">gus@inodes.org</a>><br>
<span style="font-weight:bold">Reply-To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Thursday, February 5, 2015 at 4:02 PM<br>
<span style="font-weight:bold">To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [openstack-dev] [kolla][tripleo] Update on Kolla<br>
</div>
<div><br>
</div>
<div>
<div>Without taking anything away from this fine and sensible direction, where _would_ be a good place to discuss more radical container-based deployments?<br>
<div>(I'm fine if the answer is "use ad-hoc communication channels for now")</div>
<br>
<div class="gmail_quote">On Fri Feb 06 2015 at 7:24:12 AM Steven Dake (stdake) <<a href="mailto:stdake@cisco.com">stdake@cisco.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
On 2/5/15, 10:41 AM, "Paul Bourke" <<a href="mailto:paul.bourke@oracle.com" target="_blank">paul.bourke@oracle.com</a>> wrote:<br>
<br>
>Hi Steve,<br>
><br>
>Thanks for the update. For those interested in Kolla development and<br>
>discussion, where is the best place to go?<br>
><br>
>Regards,<br>
>-Paul<br>
<br>
Paul,<br>
<br>
We hang out in the irc channel #tripleo on freenode.<br>
<br>
We use launchpad at <a href="http://launchpad.net/kolla" target="_blank">http://launchpad.net/kolla</a><br>
<br>
We use the openstack-dev mailing list with the tag [kolla]<br>
<br>
Regards,<br>
-steve<br>
<br>
<br>
<br>
><br>
>On 05/02/15 17:25, Steven Dake (stdake) wrote:<br>
>> Hey folks,<br>
>><br>
>> I wanted to provide a brief update on where we are headed with Kolla.<br>
>> Initially Kolla began as a POC to show that containers could be used<br>
>> to deploy OpenStack with the long term plan of integrating that<br>
>> functionality into TripleO. That goal has not changed.<br>
>><br>
>> The tripleo community wants baby steps not outright replacement of the<br>
>> infrastructure as was proposed by using Kubernetes in Kolla as a<br>
>> dependency in this review [1]. Our first step in this process will be<br>
>> to create three new container types. We will create a controller node,<br>
>> a storage node, and a compute node. We have proven that compute can be<br>
>> used.[2] Further, one of our community members is working on a DIB<br>
>> elements->container tool here [3] and we plan to use this along with our<br>
>> other R&D in the area to integrate container tech into tripleo.<br>
>><br>
>> I©öm not quite sure how it will all come together, but after numerous<br>
>> discussions with folks from the tripleo and heat teams, I believe we can<br>
>> find a path forward.<br>
>><br>
>> Regards<br>
>> -steve<br>
>><br>
>><br>
>> [1] <a href="https://review.openstack.org/#/c/144199/" target="_blank">https://review.openstack.org/#<u></u>/c/144199/</a><br>
>> [2]<br>
>><br>
>><a href="http://sdake.io/2015/01/28/an-atomic-upgrade-process-for-openstack-comput" target="_blank">http://sdake.io/2015/01/28/<u></u>an-atomic-upgrade-process-for-<u></u>openstack-comput</a><br>
>>e-nodes/<br>
>> _[3] _<a href="https://review.openstack.org/#/c/152017/" target="_blank">https://review.openstack.org/<u></u>#/c/152017/</a><br>
>><br>
>><br>
>><br>
>>____________________________<u></u>______________________________<u></u>_______________<br>
>>_<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe:<br>
>><a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.<u></u>openstack.org?subject:<u></u>unsubscribe</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">
http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
>><br>
><br>
>_____________________________<u></u>______________________________<u></u>_______________<br>
>OpenStack Development Mailing List (not for usage questions)<br>
>Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">
OpenStack-dev-request@lists.<u></u>openstack.org?subject:<u></u>unsubscribe</a><br>
><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
<br>
<br>
______________________________<u></u>______________________________<u></u>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">
OpenStack-dev-request@lists.<u></u>openstack.org?subject:<u></u>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</blockquote>
</div>
</div>
</div>
</span>
</body>
</html>