<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br></div><div><br>On Dec 13, 2013, at 4:25 PM, Georgy Okrokvertskhov <<a href="mailto:gokrokvertskhov@mirantis.com">gokrokvertskhov@mirantis.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">Hi,<div><br></div><div>I will change format to YAML. It should be pretty straightforward.</div><div><br></div><div>I also like an idea of versioning for LP. I personally don't like name "Stream" but we can figure out naming later.</div></div></div></blockquote><div><br></div><div>Version is almost always too specific - remember that some operators may wish to support a single stream of java that may change for users over time. Someone using a java language pack may only want to support one java runtime at a time, but that version # might change. It might be major version, it might be minor version, or the minor version might end up having major incompatible changes and thus a new stream has to be forked.</div><div><br></div><div>The operator needs a way to define a label for users to select a stream ("1.6") that may change over time ("1.6.5.X"), but with a unique id that links apps created against "1.6" to those created later. The operator may also need to supply metadata for these streams, like "obsolete", "will be end of lifed soon". An individual version of a lp in a stream will inherit / reference metadata at some point in time (created at x, has exactly version 1.6.5 build).</div><div><br></div><div>The user definitely needs to be able to choose a version - but that version is a choice that exists for a limited period of time.</div><br><blockquote type="cite"><div><div dir="ltr">
<div><br></div><div>Thanks</div><div>Georgy</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Dec 13, 2013 at 12:40 PM, Clayton Coleman <span dir="ltr"><<a href="mailto:ccoleman@redhat.com" target="_blank">ccoleman@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div>I added some comments to the bottom specifically about lessons learned from operating things like language pack - I discuss the concept of version streams and how an operator spoon feeds base images for the language pack out to applications. </div>
<div><div class="h5"><div><br>On Dec 9, 2013, at 4:05 PM, Georgy Okrokvertskhov <<a href="mailto:gokrokvertskhov@mirantis.com" target="_blank">gokrokvertskhov@mirantis.com</a>> wrote:<br><br></div><blockquote type="cite">
<div><div dir="ltr">Hi,<div><br></div><div>As a part of Language pack workgroup session we created an etherpad for language pack attributes definition. Please find a first draft of language pack attributes here: <a href="https://etherpad.openstack.org/p/Solum-Language-pack-json-format" target="_blank">https://etherpad.openstack.org/p/Solum-Language-pack-json-format</a></div>
<div><br></div><div>We have identified a minimal list of attributes which should be supported by language pack API.</div><div><br></div><div>Please, provide your feedback and\or ideas in this etherpad. Once it is reviewed we can use this as a basis for language packs in PoC.
</div><div><br></div><div>Thanks</div><div>Georgy</div></div>
</div></blockquote></div></div><blockquote type="cite"><div><span>_______________________________________________</span><div class="im"><br><span>OpenStack-dev mailing list</span><br><span><a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a></span><br>
<span><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></span><br></div></div></blockquote></div><br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Georgy Okrokvertskhov<br>
Technical Program Manager,<br>Cloud and Infrastructure Services,<br>
Mirantis<br>
<a href="http://www.mirantis.com/" target="_blank">http://www.mirantis.com</a><br>
Tel. +1 650 963 9828<br>
Mob. +1 650 996 3284<br>
</div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>OpenStack-dev mailing list</span><br><span><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a></span><br><span><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></span><br></div></blockquote></body></html>