<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
It turns out we already have one: <a href="https://launchpad.net/magnum-ui" class="">https://launchpad.net/magnum-ui</a>
<div class=""><br class="">
</div>
<div class="">The Driver is already set to "Magnum Drivers”.</div>
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Jun 12, 2015, at 12:26 PM, Adrian Otto <<a href="mailto:adrian.otto@rackspace.com" class="">adrian.otto@rackspace.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<meta content="text/html; charset=Windows-1252" class="">
<div style="word-wrap: break-word; font-size: 14px; font-family: Calibri, sans-serif;" class="">
<div class="">Okay, I will think on that a bit.</div>
<div class=""><br class="">
</div>
<div class="">Adrian</div>
<br class="">
<br class="">
-------- Original message --------<br class="">
From: "Steven Dake (stdake)" <<a href="mailto:stdake@cisco.com" class="">stdake@cisco.com</a>>
<br class="">
Date: 06/12/2015 8:04 AM (GMT-08:00) <br class="">
To: "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" class="">openstack-dev@lists.openstack.org</a>>
<br class="">
Subject: Re: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum - need a vote from the core team
<br class="">
<br class="">
<div class="">
<div class="">Adiran,</div>
<div class=""><br class="">
</div>
<div class="">Disagree.</div>
<div class=""><br class="">
</div>
<div class="">The python-magnumclient and heat-coe-templates have separate launchpad trackers. I suspect we will want a separate tracker for python-k8sclient when we are ready for that.</div>
<div class=""><br class="">
</div>
<div class="">IMO each repo should have a separate launchpad tracker to make the lives of the folks maintaining the software easier :) This is a common best practice in OpenStack.</div>
<div class=""><br class="">
</div>
<div class="">Regards</div>
<div class="">-steve</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<span id="OLK_SRC_BODY_SECTION" class="">
<div style="font-family: Calibri; font-size: 11pt; text-align: left; border-width: 1pt medium medium; border-style: solid none none; padding: 3pt 0in 0in; border-top-color: rgb(181, 196, 223);" class="">
<span style="font-weight:bold" class="">From: </span>Adrian Otto <<a href="mailto:adrian.otto@rackspace.com" class="">adrian.otto@rackspace.com</a>><br class="">
<span style="font-weight:bold" class="">Reply-To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" class="">openstack-dev@lists.openstack.org</a>><br class="">
<span style="font-weight:bold" class="">Date: </span>Friday, June 12, 2015 at 7:47 AM<br class="">
<span style="font-weight:bold" class="">To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" class="">openstack-dev@lists.openstack.org</a>><br class="">
<span style="font-weight:bold" class="">Subject: </span>Re: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum - need a vote from the core team<br class="">
</div>
<div class=""><br class="">
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="border-left:#b5c4df 5 solid; padding:0 0 0 5; margin:0 0 0 5" class="">
<div class="">
<meta content="text/html; charset=Windows-1252" class="">
<div style="word-wrap: break-word; font-size: 14px; font-family: Calibri, sans-serif;" class="">
<div class="">Steve,</div>
<div class=""><br class="">
</div>
<div class="">There is no need for a second LP project at all.</div>
<div class=""><br class="">
</div>
<div class="">Adrian</div>
<br class="">
<br class="">
-------- Original message --------<br class="">
From: "Steven Dake (stdake)" <<a href="mailto:stdake@cisco.com" class="">stdake@cisco.com</a>>
<br class="">
Date: 06/12/2015 7:41 AM (GMT-08:00) <br class="">
To: "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" class="">openstack-dev@lists.openstack.org</a>>
<br class="">
Subject: Re: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum - need a vote from the core team
<br class="">
<br class="">
<div class="">
<div class="">Adrian,</div>
<div class=""><br class="">
</div>
<div class="">Great thanks for that. I would recommend one change and that is for one magnum-drivers team across launchpad trackers. The magnum-drivers team as you know (this is for the benefit of others) is responsible for maintaining the states of the launchpad
trackers.</div>
<div class=""><br class="">
</div>
<div class="">Regards,</div>
<div class="">-steve</div>
<div class=""><br class="">
</div>
<span id="OLK_SRC_BODY_SECTION" class="">
<div style="font-family: Calibri; font-size: 11pt; text-align: left; border-width: 1pt medium medium; border-style: solid none none; padding: 3pt 0in 0in; border-top-color: rgb(181, 196, 223);" class="">
<span style="font-weight:bold" class="">From: </span>Adrian Otto <<a href="mailto:adrian.otto@rackspace.com" class="">adrian.otto@rackspace.com</a>><br class="">
<span style="font-weight:bold" class="">Reply-To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" class="">openstack-dev@lists.openstack.org</a>><br class="">
<span style="font-weight:bold" class="">Date: </span>Thursday, June 11, 2015 at 7:21 PM<br class="">
<span style="font-weight:bold" class="">To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" class="">openstack-dev@lists.openstack.org</a>><br class="">
<span style="font-weight:bold" class="">Subject: </span>Re: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum - need a vote from the core team<br class="">
</div>
<div class=""><br class="">
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="border-left:#b5c4df 5 solid; padding:0 0 0 5; margin:0 0 0 5" class="">
<div class="">
<div class="" style="word-wrap:break-word">Team,<br class="">
<br class="">
We are fortunate enough to have a thriving community of developers who want to make OpenStack great, and several of us have pledged support for this work in Magnum. Due to the amount of interest expressed in this pursuit, and the small amount of overlap between
the developers in magnum-core, I’m authorizing the creation of a new gerrit ACL group named magnum-ui-core. Please install me as the pilot member of the group. I will seed the group with those who have pledged support for the effort from the “essential” subscribers
to the following blueprint. If our contributors to the magnum-ui repo feel that review velocity is too low, I will add magnum-core as a member so we can help. On regular intervals, I will review the activity level of our new group, and make adjustments as
needed to add/subtract from it in accordance with input from the active contributors. We will use the Magnum project on Launchpad for blueprints and bugs.
<div class=""><br class="">
</div>
<div class=""><a href="https://blueprints.launchpad.net/magnum/+spec/magnum-horizon-plugin" class="">https://blueprints.launchpad.net/magnum/+spec/magnum-horizon-plugin</a></div>
<div class=""><br class="">
</div>
<div class="">There are 8 contributors identified, who will comprise our initial magnum-ui-core group.<br class="">
<div class=""><br class="">
</div>
<div class="">I ask that the ACLs be configured as follows:</div>
<div class=""><br class="">
</div>
<blockquote class="" style="margin:0 0 0 40px; border:none; padding:0px">
<div class=""><font face="Courier" class="">[access "refs/heads/*"]</font></div>
<div class=""><font face="Courier" class="">abandon = group magnum-ui-core</font></div>
<div class=""><font face="Courier" class="">create = group magnum-milestone</font></div>
<div class=""><font face="Courier" class="">label-Code-Review = -2..+2 group magnum-ui-core</font></div>
<div class=""><font face="Courier" class="">label-Workflow = -1..+1 group magnum-ui-core</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">[access "refs/tags/*"]</font></div>
<div class=""><font face="Courier" class="">pushSignedTag = group magnum-milestone</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">[receive]</font></div>
<div class=""><font face="Courier" class="">requireChangeId = true</font></div>
<div class=""><font face="Courier" class="">requireContributorAgreement = true</font></div>
<div class=""><font face="Courier" class=""><br class="">
</font></div>
<div class=""><font face="Courier" class="">[submit]</font></div>
<div class=""><font face="Courier" class="">mergeContent = true</font></div>
</blockquote>
<div class="">
<div class=""><br class="">
</div>
<div class="">Thanks everyone for your enthusiasm about this new pursuit. I look forward to working together with you to make this into something we are all proud of.</div>
<div class=""><br class="">
</div>
<div class="">Adrian</div>
<div class=""><br class="">
</div>
<div class="">PS: Special thanks to sdake for initiating this conversation, and helping us to arrive at a well reasoned decision about how to approach this.</div>
<div class="">
<div class="">
<div class="">
<div class=""><br class="">
<blockquote type="cite" class="">On Jun 4, 2015, at 10:58 AM, Steven Dake (stdake) <<a href="mailto:stdake@cisco.com" class="">stdake@cisco.com</a>> wrote:<br class="">
<br class="">
Hey folks,<br class="">
<br class="">
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.<br class="">
<br class="">
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.<br class="">
<br class="">
As far as “how to get patches approved”, there are two models we can go with.<br class="">
<br class="">
Option #1:<br class="">
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.<br class="">
<br class="">
Option #2:<br class="">
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.<br class="">
<br class="">
Cores, please vote on Option #1, or Option #2, and Adrian can make a decision based upon the results.<br class="">
<br class="">
Regards<br class="">
-steve<br class="">
<br class="">
__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">
OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
</blockquote>
<br class="">
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</span></div>
</div>
</div>
</blockquote>
</span></div>
</div>
__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">
OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>