<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">
<p>An alternate schema, and the one in current use, places the os
and openstack-release under the tag section. <br>
</p>
<p>This has the advantage of lower administrative overhead. It
takes 'admin' powers to create a new <image>, whereas
anyone with write permissions can create a new <tag>.<br>
</p>
<p>Lets call this version 2.</p>
<p><b><br>
</b></p>
<p><b>Image naming schema</b></p>
<pre><image-name>=<org>/<image>:<tag></pre>
<pre><org>=starlingx</pre>
<pre><image>=stx-<component>
<tag>=<git-tag-or-branch>-<os>-<openstack-release>[-<qualifier>]
<os>=centos | ubuntu | clear-linux
<openstack-release>=pike | queens | rocky ...
</pre>
<pre><component>=aodh | ceilometer| cinder | glance | gnocchi | heat | horizon | ironic | keystone | libvirt | magnum | murano | neutron | nova-api-proxy | nova | panko ...
<qualifier>=<timestamp> | latest | stable
<git-tag-or-branch>=dev | r2018.10 | r2018.10.0 | ...
</pre>
Note: 'dev' replaces 'master'<br>
<br>
<br>
On 18-12-04 01:29 PM, Scott Little wrote:<br>
</div>
<blockquote type="cite"
cite="mid:38d5e899-8741-18f9-88a7-47153c34f982@windriver.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<p>Here is my proposal for the StarlingX docker repository.</p>
<p><b><b>Docker repository location</b></b></p>
<p>- hub.docker.com, as a public set of repositories under the
organization 'starlingx'<b><b><br>
</b></b></p>
<p><b>Build frequency</b></p>
<p>- On demand for release/milestone branches</p>
<p>- Will probably start with daily for master branch. Perhaps
when things stabilize we'll reduce build frequency, or even use
commit driven builds.</p>
<p><b>Retention policy<br>
</b></p>
<p>- Perhaps two weeks for master branch builds? but always one
'stable' build (see below)<br>
</p>
<p>- Will start with daily for master branch. Perhaps when things
stabilize we'll reduce build frequency, or even use commit
driven builds.</p>
<p><b>Image naming schema</b></p>
<pre><image-name>=<org>/<image>:<tag></pre>
<pre><org>=starlingx</pre>
<pre><image>=stx-<os>-<openstack-release>-<component>
<tag>=<git-tag> | <git-branch>[-<qualifier>]
<os>=centos | ubuntu | clear-linux
<openstack-release>=pike | queens | rocky ...
</pre>
<pre><component>=aodh | ceilometer| cinder | glance | gnocchi | heat | horizon | ironic | keystone | libvirt | magnum | murano | neutron | nova-api-proxy | nova | panko ...
<qualifier>=<timestamp> | latest | stable
<git-tag-or-branch>=master | r2018.10 | r2018.10.0 | ...
</pre>
Note: we can't have the '/' or ':' character in a branch name. So
r/2018.10 would have to be shortened to 'r2018.10'. <br>
However i think it's better to use the tag to allow for rebuilds
of a release '2018.10.0'. My only concern here is that our current
git tagging convention doesn't distinguish release from
milestone. I would prefer a 'r' or 'm' prefix on our git tags.<br>
<p>Note: the 'latest' or 'stable' qualifiers would be aliases to
the timestamped image. 'Stable' might be over selling it on
master branch... perhaps some other term... 'tested', 'usable'?</p>
<p><br>
</p>
<p>e.g.</p>
<pre>starlingx/stx-centos-pike-nova:master-20181201
starlingx/stx-centos-pike-nova:master-20181202
starlingx/stx-centos-pike-nova:master-20181203
starlingx/stx-centos-pike-nova:master-latest -> master-20181203
starlingx/stx-centos-pike-nova:master-stable -> master-20181201
starlingx/stx-centos-pike-nova:r2018.10.0
starlingx/stx-centos-pike-nova:r2018.10.1
starlingx/stx-centos-pike-nova:r2018.10-latest -> r2018.10.1</pre>
<br>
Comments?<br>
<br>
Scott<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Starlingx-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Starlingx-discuss@lists.starlingx.io">Starlingx-discuss@lists.starlingx.io</a>
<a class="moz-txt-link-freetext" href="http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss">http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>