<div dir="ltr">In previous conversations, my understanding was the UI implementation had to be very scheduler dependent to be very effective. Is my understanding accurate? If so, the complexity grows with the number supported.<div><br></div><div>David</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jun 4, 2015 at 1:59 PM, Bradley Jones (bradjone) <span dir="ltr"><<a href="mailto:bradjone@cisco.com" target="_blank">bradjone@cisco.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">
<div>
<div>It’s difficult to put a quantifiable figure on how big a work item this is but I can try to give an overview of the steps required.</div>
<div><br>
</div>
<div>The first step will be to extend the Horizon API to include CRUD operations that we need to perform with Magnum. Assuming that there are no issues here and API changes/additions are not required at this point, we can begin to flesh out how we
would like the UI to look. We will aim to reduce the amount of Magnum specific UI code that will need to be maintained by reusing components from Horizon. This will also speed up the development significantly.</div>
<div><br>
</div>
<div>In version 1 of Magnum UI a user should be able to perform all normal interactions with Magnum through the UI with no need for interaction with the python client.</div>
<div><br>
</div>
<div>Future versions of Magnum UI would include admin specific views and any additional Magnum specific UI components we may want to add (maybe some visualisations).</div>
<div><br>
</div>
<div>That is a brief overview of my vision for this effort and I believe that version 1 should comfortably be achievable this release cycle.</div>
<div><br>
</div>
Thanks,
<div>Brad Jones</div>
</div><div><div class="h5">
<div><br>
</div>
<div>
<div>
<blockquote type="cite">
<div>On 4 Jun 2015, at 19:49, Brad Topol <<a href="mailto:btopol@us.ibm.com" target="_blank">btopol@us.ibm.com</a>> wrote:</div>
<br>
<div><font size="2" face="sans-serif">How big a work item is this?</font>
<br>
<font size="2" face="sans-serif"><br>
<br>
Brad Topol, Ph.D.<br>
IBM Distinguished Engineer<br>
OpenStack<br>
<a href="tel:%28919%29%20543-0646" value="+19195430646" target="_blank">(919) 543-0646</a><br>
Internet: <a href="mailto:btopol@us.ibm.com" target="_blank">btopol@us.ibm.com</a><br>
Assistant: Kendra Witherspoon <a href="tel:%28919%29%20254-0680" value="+19192540680" target="_blank">(919) 254-0680</a></font> <br>
<br>
<br>
<br>
<font size="1" color="#5f5f5f" face="sans-serif">From: </font><font size="1" face="sans-serif">Thai Q Tran/Silicon Valley/IBM@IBMUS</font>
<br>
<font size="1" color="#5f5f5f" face="sans-serif">To: </font><font size="1" face="sans-serif">"OpenStack Development Mailing List \(not for usage questions\)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>></font>
<br>
<font size="1" color="#5f5f5f" face="sans-serif">Date: </font><font size="1" face="sans-serif">06/04/2015 02:20 PM</font>
<br>
<font size="1" color="#5f5f5f" face="sans-serif">Subject: </font><font size="1" face="sans-serif">Re: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum - need a vote from the core team</font>
<br>
<hr noshade>
<br>
<br>
<br>
<font size="2" face="sans-serif">I am interested but not sure how much time I have this release cycle. I can take on a more hands-off approach and help review to make sure that magnum-ui is align with future horizon directions.<br>
</font><font size="2" color="#a1009f" face="sans-serif"><br>
-----"Steven Dake (stdake)" <<a href="mailto:stdake@cisco.com" target="_blank">stdake@cisco.com</a>> wrote: -----</font>
<br>
<font size="2" face="sans-serif">To: "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
From: "Steven Dake (stdake)" <<a href="mailto:stdake@cisco.com" target="_blank">stdake@cisco.com</a>><br>
Date: 06/04/2015 11:03AM<br>
Subject: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum - need a vote from the core team<br>
</font><br>
<font size="2" face="sans-serif">Hey folks,</font> <br>
<br>
<font size="2" face="sans-serif">I think it is critical for self-service needs that we have a Horizon dashboard to represent Magnum. I know the entire Magnum team has no experience in UI development, but I have found atleast one volunteer Bradley
Jones to tackle the work.</font> <br>
<br>
<font size="2" face="sans-serif">I am looking for more volunteers to tackle this high impact effort to bring Containers to OpenStack either in the existing Magnum core team or as new contributors. If your interested, please chime in on this thread.</font>
<br>
<br>
<font size="2" face="sans-serif">As far as “how to get patches approved”, there are two models we can go with.</font>
<br>
<br>
<font size="2" face="sans-serif">Option #1:</font> <br>
<font size="2" face="sans-serif">We add these UI folks to the magnum-core team and trust them not to +2/+A Magnum infrastructure code. This also preserves us as one team with one mission.</font>
<br>
<br>
<font size="2" face="sans-serif">Option #2:</font> <br>
<font size="2" face="sans-serif">We make a new core team magnum-ui-core. This presents special problems if the UI contributor team isn’t large enough to get reviews in. I suspect Option #2 will be difficult to execute.</font>
<br>
<br>
<font size="2" face="sans-serif">Cores, please vote on Option #1, or Option #2, and Adrian can make a decision based upon the results.</font>
<br>
<br>
<font size="2" face="sans-serif">Regards</font> <br>
<font size="2" face="sans-serif">-steve</font> <br>
<br>
<font size="3" face="Courier New">__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank">
OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe</font><font size="3" color="blue" face="Courier New"><u><br>
</u></font><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><font size="3" color="blue" face="Courier New"><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></a><tt><font size="2">__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank">
OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br>
</font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><tt><font size="2">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></tt></a><tt><font size="2"><br>
</font></tt><br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank">
OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<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>
</div>
</blockquote>
</div>
<br>
</div>
</div></div></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</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></div>