<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Greetings to the community <span id="🙂">🙂<br>
</span></div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<span id="🙂" class="ContentPasted5">I would like to bring to this mailing list a discussion we are having about splitting the stx-openstack application repositories from the main starlingx manifest into a new one.
<div><br class="ContentPasted5">
</div>
<div class="ContentPasted5">In order to decouple the OpenStack Clients currently shared between platform and application we are suggesting to decouple the platform and application builds in separate manifests (e.g. starlingx/manifest/default.xml and starlingx/manifest/stx-openstack.xml).</div>
<div class="ContentPasted5">I understand that the new manifest needs to be created and build jobs configured properly and tested, I can also create the Stories for mapping this work later.</div>
<div><br class="ContentPasted5">
</div>
<div class="ContentPasted5">BENEFITS: we achieve the freedom of building different versions of the same packages (i.e. openstack clients) that are shared between the platform and the application.</div>
<div class="ContentPasted5">The end goal would be something like:</div>
<div><br class="ContentPasted5">
</div>
<div class="ContentPasted5">Remain as is (default manifest aligns to upstream Debian version => Victoria)</div>
<div class="ContentPasted5">============</div>
<div class="ContentPasted5">stx/upstream openstack/barbican</div>
<div class="ContentPasted5">stx/upstream openstack/keystone</div>
<div class="ContentPasted5">stx/upstream openstack/python-barbicanclient</div>
<div class="ContentPasted5">stx/upstream openstack/python-keystoneclient</div>
<div class="ContentPasted5">stx/upstream openstack/python-horizon</div>
<div class="ContentPasted5">stx/upstream openstack/python-openstackclient</div>
<div class="ContentPasted5">Only keep the services needed by the platform. Some existing patches might have been brought forward to support stx-openstack, so we should re-evaluate as part of this.</div>
<div class="ContentPasted5">Those would still be built as part of STX Platform builds, i.e. starlingx/manifest/default.xml</div>
<div class="ContentPasted5">Manifest should not include stx/openstack-armada-app repo anymore.</div>
<div><br class="ContentPasted5">
</div>
<div class="ContentPasted5">Relocate (stx-openstack app independently aligns to version of choice: Victoria [current] => Antelope [future])</div>
<div class="ContentPasted5">====================</div>
<div class="ContentPasted5">stx/upstream openstack/barbican copy-to stx/openstack-armada-app/upstream/openstack/barbican</div>
<div class="ContentPasted5">stx/upstream openstack/keystone copy-to stx/openstack-armada-app/upstream/openstack/keystone</div>
<div class="ContentPasted5">stx/upstream openstack/python-barbicanclient copy-to stx/openstack-armada-app/upstream/openstack/python-barbicanclient</div>
<div class="ContentPasted5">stx/upstream openstack/python-keystoneclient copy-to stx/openstack-armada-app/upstream/openstack/python-keystoneclient</div>
<div class="ContentPasted5">stx/upstream openstack/python-horizon copy-to stx/openstack-armada-app/upstream/openstack/python-horizon</div>
<div class="ContentPasted5">stx/upstream openstack/python-openstackclient copy-to stx/openstack-armada-app/upstream/openstack/python-openstackclient</div>
<div class="ContentPasted5">stx/upstream openstack/openstack-pkg-tools move-to stx/openstack-armada-app/upstream/openstack/openstack-pkg-tools</div>
<div class="ContentPasted5">stx/upstream openstack/openstack-ras move-to stx/openstack-armada-app/upstream/openstack/openstack-ras</div>
<div class="ContentPasted5">stx/upstream openstack/python-aodhclient move-to stx/openstack-armada-app/upstream/openstack/python-aodhclient</div>
<div class="ContentPasted5">stx/upstream openstack/python-cinderclient move-to stx/openstack-armada-app/upstream/openstack/python-cinderclient</div>
<div class="ContentPasted5">stx/upstream openstack/python-glanceclient move-to stx/openstack-armada-app/upstream/openstack/python-glanceclient</div>
<div class="ContentPasted5">stx/upstream openstack/python-gnocchiclient move-to stx/openstack-armada-app/upstream/openstack/python-gnocchiclient</div>
<div class="ContentPasted5">stx/upstream openstack/python-heatclient move-to stx/openstack-armada-app/upstream/openstack/python-heatclient</div>
<div class="ContentPasted5">stx/upstream openstack/python-ironicclient move-to stx/openstack-armada-app/upstream/openstack/python-ironicclient</div>
<div class="ContentPasted5">stx/upstream openstack/python-keystoneclient move-to stx/openstack-armada-app/upstream/openstack/python-keystoneclient</div>
<div class="ContentPasted5">stx/upstream openstack/python-neutronclient move-to stx/openstack-armada-app/upstream/openstack/python-neutronclient</div>
<div class="ContentPasted5">stx/upstream openstack/python-novaclient move-to stx/openstack-armada-app/upstream/openstack/python-novaclient</div>
<div class="ContentPasted5">stx/upstream openstack/python-openstacksdk move-to stx/openstack-armada-app/upstream/openstack/python-openstacksdk</div>
<div class="ContentPasted5">stx/upstream openstack/python-osc-lib move-to stx/openstack-armada-app/upstream/openstack/python-osc-lib</div>
<div class="ContentPasted5">stx/upstream openstack/python-oslo-messaging move-to stx/openstack-armada-app/upstream/openstack/python-oslo-messaging</div>
<div class="ContentPasted5">stx/upstream openstack/python-pankoclient move-to stx/openstack-armada-app/upstream/openstack/python-pankoclient</div>
<div class="ContentPasted5">stx/upstream openstack/python-wsme move-to stx/openstack-armada-app/upstream/openstack/python-wsme</div>
<div class="ContentPasted5">stx/upstream openstack/rabbitmq-server move-to stx/openstack-armada-app/upstream/openstack/rabbitmq-server</div>
<div><br class="ContentPasted5">
</div>
<div class="ContentPasted5">The OpenStack Distro Team will create a new directory under stx/openstack-armada-app to store all application needed packages.</div>
<div class="ContentPasted5">This will include clients and the stx-openstack Docker images we build only for the application. This way, on stx-openstack build we can build the same packages (name) but using different versions/source code. Manifest does not include
upstream repo.</div>
<br>
------<span class="ContentPasted5 ContentPasted6">------</span><span class="ContentPasted5 ContentPasted7">------</span><span class="ContentPasted5 ContentPasted8">------</span><br>
<br>
</span></div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof ContentPasted0 ContentPasted1 ContentPasted2 ContentPasted4">
<span></span>
<div class="ContentPasted3">We have discussed it between a small group of people so I would like to bring it to the attention of everyone and let the community speak in case there are any concerns against it and/or to support this change proposal. This work
will be done in a couple of phases, progressively moving towards achieving the end goal explained here.<br>
<br>
Looking forward for hearing back from you <span id="🙂">🙂</span><br>
</div>
<div class="ContentPasted3"><br>
</div>
<br>
<br>
</div>
</body>
</html>