<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 1, 2016 at 8:36 AM, Jiri Tomasek <span dir="ltr"><<a href="mailto:jtomasek@redhat.com" target="_blank">jtomasek@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div class=""><div class="h5"><br>
<br>
On 27.7.2016 15:18, Steven Hardy wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
On Wed, Jul 27, 2016 at 08:41:32AM -0300, Honza Pokorny wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
Hello folks,<br>
<br>
As the tripleo-ui project is quickly maturing, it might be time to start<br>
versioning our code.  As of now, the version is set to 0.0.1 and that<br>
hardly reflects the state of the project.<br>
<br>
What do you think?<br>
</blockquote>
I would like to see it released as part of the coordinated tripleo release,<br>
e.g tagged each milestone along with all other projects where we assert the<br>
release:cycle-with-intermediary tag:<br>
<br>
<a href="https://github.com/openstack/governance/blob/master/reference/projects.yaml#L4448" rel="noreferrer" target="_blank">https://github.com/openstack/governance/blob/master/reference/projects.yaml#L4448</a><br>
<br>
Because tripleo-ui isn't yet fully integrated with TripleO (e.g packaging,<br>
undercloud installation and CI testing), we've not tagged it in the last<br>
two milestone releases, but perhaps we can for the n-3 release?<br>
<br>
<a href="https://review.openstack.org/#/c/324489/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/324489/</a><br>
<br>
<a href="https://review.openstack.org/#/c/340350/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/340350/</a><br>
<br>
When we do that, the versioning will align with all other TripleO<br>
deliverables, solving the problem of the 0.0.1 version?<br>
<br>
The steps to achieve this are:<br>
<br>
1. Get per-commit builds of tripleo-ui working via delorean-current:<br>
<br>
<a href="https://trunk.rdoproject.org/centos7-master/current/" rel="noreferrer" target="_blank">https://trunk.rdoproject.org/centos7-master/current/</a><br>
<br>
2. Get the tripleo-ui package installed and configured as part of the<br>
undercloud install (via puppet) - we might want to add a conditional to the<br>
undercloud.conf so it's configurable (enabled by default?)<br>
<br>
<a href="https://github.com/openstack/instack-undercloud/blob/master/elements/puppet-stack-config/puppet-stack-config.pp" rel="noreferrer" target="_blank">https://github.com/openstack/instack-undercloud/blob/master/elements/puppet-stack-config/puppet-stack-config.pp</a><br>
<br>
3. Get the remaining Mistral API pieces landed so it's fully functional<br>
<br>
4. Implement some basic CI smoke tests to ensure the UI is at least<br>
accessible.<br>
<br>
Does that sequence make sense, or have I missed something?<br>
</blockquote></div></div>
Makes perfect sense. Here is the launchpad link that tracks undercloud integration of GUI <a href="https://blueprints.launchpad.net/tripleo-ui/+spec/instack-undercloud-ui-config" rel="noreferrer" target="_blank">https://blueprints.launchpad.net/tripleo-ui/+spec/instack-undercloud-ui-config</a></blockquote><div><br></div><div>It would be great to work this into the informational menu where the Service Status lives. I put together some quick mockups on what this could look like:</div><div><a href="https://invis.io/247VLM4SB#/178151973_2016-8-1_TripleO_UI51">https://invis.io/247VLM4SB#/178151973_2016-8-1_TripleO_UI51</a><br></div><div><br></div><div>What do you all think?</div><div><br></div><div>Thanks,</div><div>Liz</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><br>
<br>
Jirka<div class=""><div class="h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<br>
Steve<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div></div>