<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style>body{font-family:Helvetica,Arial;font-size:13px}</style>
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">
<br>
</div>
<br>
<div id="bloop_sign_1522530876311808000" class="bloop_sign"></div>
<br>
<p class="airmail_on">On March 31, 2018 at 12:35:31 PM, Jeremy Stanley (<a href="mailto:fungi@yuggoth.org">fungi@yuggoth.org</a>) wrote:</p>
<blockquote type="cite" class="clean_bq"><span>
<div>
<div></div>
<div>On 2018-03-31 18:06:07 +0000 (+0000), Steven Dake (stdake) wrote: <br>
> I appreciate your personal interest in attempting to clarify the <br>
> Kolla mission statement. <br>
> <br>
> The change in the Kolla mission statement you propose is <br>
> unnecessary. <br>
[...] <br>
<br>
I should probably have been more clear. The Kolla mission statement <br>
right now says that the Kolla team produces two things: containers <br>
and deployment tools. This may make it challenging for the team to <br>
avoid tightly coupling their deployment tooling and images, creating <br>
a stratification of first-class (those created by the Kolla team) <br>
and second-class (those created by anyone else) support for <br>
deployment tools using those images. <br>
<br>
</div>
</div>
</span></blockquote>
<div><br>
</div>
<div>The problems raised in this thread (tension - tight coupling - second class citizens - stratification) was predicted early on - prior to Kolla 1.0. That prediction led to the creation of a technical solution - the Kolla API. This API permits anyone
to reuse the containers as they see fit if they conform their implementation to the API. The API is not specifically tied to the Ansible deployment technology. Instead the API is tied to the varying requirements that various deployment teams have had in
the past around generalized requirements for making container lifecycle management a reality while running OpenStack services and their dependencies inside containers.</div>
<div><br>
</div>
<div>
<blockquote type="cite" class="clean_bq" style="font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;">
<span>
<div>
<div>Is the intent to provide "a container-oriented deployment solution<span class="Apple-converted-space"> </span><br>
and the container images it uses" (kolla-ansible as first-class<span class="Apple-converted-space"> </span><br>
supported deployment engine for these images) or "container images<span class="Apple-converted-space"> </span><br>
for use by arbitrary deployment solutions, along with an example<span class="Apple-converted-space"> </span><br>
deployment solution for use with them" (kolla-ansible on equal<span class="Apple-converted-space"> </span><br>
footing with competing systems that make use of the same images)?</div>
</div>
</span></blockquote>
</div>
<p>My viewpoint is as all deployments projects are already on an equal footing when using Kolla containers.</p>
<p>I would invite the TripleO team who did integration with the Kolla API to provide their thoughts.</p>
<p>I haven't kept up with OSH development, but perhaps that team could provide their viewpoint as well.</p>
<p><br>
</p>
<p>Cheers</p>
<p>-steve</p>
<div>
<blockquote type="cite" class="clean_bq" style="font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;">
<span>
<div>
<div><span class="Apple-converted-space"> </span><br>
--<span class="Apple-converted-space"> </span><br>
Jeremy Stanley<span class="Apple-converted-space"> </span><br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br>
</div>
</div>
</span></blockquote>
</div>
</body>
</html>