Re: [openstack-dev] [magnum-ui] Proposed Core addition, and removal notice

[Bradley Jones (bradjone)]

+1 

Shu has done some great work in magnum-ui and will be a welcome addition to the 
core team.

Thanks,
Brad

> On 5 Mar 2016, at 00:29, Adrian Otto  wrote:
> 
> Magnum UI Cores,
> 
> I propose the following changes to the magnum-ui core group [1]:
> 
> + Shu Muto
> - Dims (Davanum Srinivas), by request - justified by reduced activity level.
> 
> Please respond with your +1 votes to approve this change or -1 votes to 
> oppose.
> 
> Thanks,
> 
> Adrian
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [magnum-ui][magnum] Suggestions for Features/Improvements

[Bradley Jones (bradjone)]

We have started to compile a list of possible features/improvements for 
Magnum-UI. If you have any suggestions about what you would like to see in the 
plugin please leave them in the etherpad so we can prioritise what we are going 
to work on.

https://etherpad.openstack.org/p/magnum-ui-feature-list

Thanks,
Brad Jones
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum - need a vote from the core team

[Bradley Jones (bradjone)]

The review for the creation of the new project is here 
https://review.openstack.org/190998

To confirm Adrian, do you intend to use the Magnum launchpad for UI related bps 
and bugs or the Magnum UI launchpad indicated in the spec 
(https://launchpad.net/magnum-ui)? If it’s the former I shall update the spec 
to indicate so.

Thanks,
Brad

On 12 Jun 2015, at 03:21, Adrian Otto 
mailto:adrian.o...@rackspace.com>> wrote:

Team,

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.

https://blueprints.launchpad.net/magnum/+spec/magnum-horizon-plugin

There are 8 contributors identified, who will comprise our initial 
magnum-ui-core group.

I ask that the ACLs be configured as follows:

[access "refs/heads/*"]
abandon = group magnum-ui-core
create = group magnum-milestone
label-Code-Review = -2..+2 group magnum-ui-core
label-Workflow = -1..+1 group magnum-ui-core

[access "refs/tags/*"]
pushSignedTag = group magnum-milestone

[receive]
requireChangeId = true
requireContributorAgreement = true

[submit]
mergeContent = true

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.

Adrian

PS: Special thanks to sdake for initiating this conversation, and helping us to 
arrive at a well reasoned decision about how to approach this.

On Jun 4, 2015, at 10:58 AM, Steven Dake (stdake) 
mailto:std...@cisco.com>> wrote:

Hey folks,

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.

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.

As far as “how to get patches approved”, there are two models we can go with.

Option #1:
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.

Option #2:
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.

Cores, please vote on Option #1, or Option #2, and Adrian can make a decision 
based upon the results.

Regards
-steve

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum - need a vote from the core team

[Bradley Jones (bradjone)]

Sure, I’ve got the patch ready just waiting on a final decision re: governance.

Brad

On 9 Jun 2015, at 14:46, Steven Dake (stdake) 
mailto:std...@cisco.com>> wrote:

Adrian,

I think you are on the road but perhaps you have access to email.

Can you pull the trigger on your preferred governance approach?  Brad will do 
the rest (creation of stackforge project, etc)  From my perspective, the UI 
spec is ready to hit the repo and we shouldn’t block these folks good work 
because we can’t make a decision :).

Given the broad interest from a lot of interested parties and no defined best 
practice in OpenStack for handling UI governance, I think a separate 
magnum-ui-core may make the most sense so the Magnum core team responsible for 
the infrastructure doesn’t balloon with a bunch of folks that don’t know much 
about Magnum in detail.  If the ui dev team has slow reviews, which I doubt, we 
can add magnum-core to the magnum-ui-core team as a subteam in gerrit.

I know this is a change in my previous stance, but I didn’t expect such broad 
interest.

Brad,

Once we get a decision from Adrian, can you submit a stackforge repo creation 
and link the review on this thread so interested parties can review 
appropriately?

Regards,
-steve

From: Adrian Otto mailto:adrian.o...@rackspace.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Date: Thursday, June 4, 2015 at 2:30 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum - 
need a vote from the core team

Team,

I have published a top level blueprint for a magnum-horizon-plugin:

https://blueprints.launchpad.net/magnum/+spec/magnum-horizon-plugin

My suggestion is that any contributor interested in contributing to this 
feature should subscribe to that blueprint, and record their intent to 
contribute in the Whiteboard of the BP. Furthermore, I suggest that any 
contributors who are a good fit for core reviewer duties for this effort 
subscribe to the blueprint and mark themselves as “Participation Essential” so 
I can get a clear picture of how to deal with grouping the related core 
reviewer team (or adding them to the current core group).

I think that this effort would benefit from a spec submitted as a review using 
the following template:

http://git.openstack.org/cgit/openstack/nova-specs/tree/specs/liberty-template.rst

Adapt it for magnum (I have not contributed a spec template of our own yet. 
TODO.)

Contribute it here:

http://git.openstack.org/cgit/openstack/magnum/tree/specs

Thanks,

Adrian

On Jun 4, 2015, at 12:58 PM, Steven Dake (stdake) 
mailto:std...@cisco.com>> wrote:

Hey folks,

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.

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.

As far as “how to get patches approved”, there are two models we can go with.

Option #1:
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.

Option #2:
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.

Cores, please vote on Option #1, or Option #2, and Adrian can make a decision 
based upon the results.

Regards
-steve

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum - need a vote from the core team

[Bradley Jones (bradjone)]

Initial draft of spec is out for review here 
https://review.openstack.org/188958 feedback welcome :)

Thanks,
Brad Jones

On 4 Jun 2015, at 22:30, Adrian Otto 
mailto:adrian.o...@rackspace.com>> wrote:

Team,

I have published a top level blueprint for a magnum-horizon-plugin:

https://blueprints.launchpad.net/magnum/+spec/magnum-horizon-plugin

My suggestion is that any contributor interested in contributing to this 
feature should subscribe to that blueprint, and record their intent to 
contribute in the Whiteboard of the BP. Furthermore, I suggest that any 
contributors who are a good fit for core reviewer duties for this effort 
subscribe to the blueprint and mark themselves as “Participation Essential” so 
I can get a clear picture of how to deal with grouping the related core 
reviewer team (or adding them to the current core group).

I think that this effort would benefit from a spec submitted as a review using 
the following template:

http://git.openstack.org/cgit/openstack/nova-specs/tree/specs/liberty-template.rst

Adapt it for magnum (I have not contributed a spec template of our own yet. 
TODO.)

Contribute it here:

http://git.openstack.org/cgit/openstack/magnum/tree/specs

Thanks,

Adrian

On Jun 4, 2015, at 12:58 PM, Steven Dake (stdake) 
mailto:std...@cisco.com>> wrote:

Hey folks,

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.

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.

As far as “how to get patches approved”, there are two models we can go with.

Option #1:
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.

Option #2:
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.

Cores, please vote on Option #1, or Option #2, and Adrian can make a decision 
based upon the results.

Regards
-steve

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum - need a vote from the core team

[Bradley Jones (bradjone)]

I will get a spec out for review by end of day tomorrow.

Thanks,
Brad Jones

On 4 Jun 2015, at 22:30, Adrian Otto 
mailto:adrian.o...@rackspace.com>> wrote:

Team,

I have published a top level blueprint for a magnum-horizon-plugin:

https://blueprints.launchpad.net/magnum/+spec/magnum-horizon-plugin

My suggestion is that any contributor interested in contributing to this 
feature should subscribe to that blueprint, and record their intent to 
contribute in the Whiteboard of the BP. Furthermore, I suggest that any 
contributors who are a good fit for core reviewer duties for this effort 
subscribe to the blueprint and mark themselves as “Participation Essential” so 
I can get a clear picture of how to deal with grouping the related core 
reviewer team (or adding them to the current core group).

I think that this effort would benefit from a spec submitted as a review using 
the following template:

http://git.openstack.org/cgit/openstack/nova-specs/tree/specs/liberty-template.rst

Adapt it for magnum (I have not contributed a spec template of our own yet. 
TODO.)

Contribute it here:

http://git.openstack.org/cgit/openstack/magnum/tree/specs

Thanks,

Adrian

On Jun 4, 2015, at 12:58 PM, Steven Dake (stdake) 
mailto:std...@cisco.com>> wrote:

Hey folks,

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.

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.

As far as “how to get patches approved”, there are two models we can go with.

Option #1:
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.

Option #2:
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.

Cores, please vote on Option #1, or Option #2, and Adrian can make a decision 
based upon the results.

Regards
-steve

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum - need a vote from the core team

[Bradley Jones (bradjone)]

>From a quick look around there doesn’t seem to be a consensus on how to deal 
>with UI teams, some projects seem to use just the main projects core team 
>(group based policy ui), others use a mix of the project core team and the 
>Horizon core team (monasca-ui) and in the case of tuskar-ui they use just the 
>Horizon core team. I can’t find a case of another project having a dedicated 
>ui-core team but as I say it was a quick look through the project config acls 
>so I may have missed some.

My two cents are that it is important that the people working on this effort 
have some level of control over the code base in order for things to progress 
quickly and to that end either approach #1, #2 or Hongbin’s suggestions 
achieves that goal. So either of the options work for me from that point of 
view and the decision really has to come down to what will work best in getting 
current Magnum folks participating in all aspects of the ui design, 
implementation and particularly reviewing.

It is also important to have Horizon cores participate in reviews to ensure 
that we don’t diverge too much from upstream changes in Horizon, it sounds like 
we already have that commitment for reviews from David and Thai so thanks guys 
:)

Brad Jones

On 4 Jun 2015, at 21:35, Steven Dake (stdake) 
mailto:std...@cisco.com>> wrote:

Hongbin,

I hadn’t thought of that, even though it seems obvious ;)  We can absolutely do 
that.  I almost like this option better then #1 but I don’t want the ui folks 
to feel like second class citizens.  This goes back to the trust the ui 
developers to not review things they know not about :)

Bradley,

How are other OpenStack projects handling the UI teams which clearly have a 
totally different specialty than the typical core team for a project with the 
Horizon big tent changes?

Regards
-steve


From: Hongbin Lu mailto:hongbin...@huawei.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Date: Thursday, June 4, 2015 at 1:30 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum - 
need a vote from the core team

Could we have a new group magnum-ui-core and include magnum-core as a subgroup, 
like the heat-coe-tempalte-core group.

Thanks,
Hongbin

From: Steven Dake (stdake) [mailto:std...@cisco.com]
Sent: June-04-15 1:58 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum - need 
a vote from the core team

Hey folks,

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.

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.

As far as “how to get patches approved”, there are two models we can go with.

Option #1:
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.

Option #2:
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.

Cores, please vote on Option #1, or Option #2, and Adrian can make a decision 
based upon the results.

Regards
-steve

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum - need a vote from the core team

[Bradley Jones (bradjone)]

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.

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.

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.

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).

That is a brief overview of my vision for this effort and I believe that 
version 1 should comfortably be achievable this release cycle.

Thanks,
Brad Jones

On 4 Jun 2015, at 19:49, Brad Topol 
mailto:bto...@us.ibm.com>> wrote:

How big a work item is this?


Brad Topol, Ph.D.
IBM Distinguished Engineer
OpenStack
(919) 543-0646
Internet:  bto...@us.ibm.com
Assistant: Kendra Witherspoon (919) 254-0680



From:Thai Q Tran/Silicon Valley/IBM@IBMUS
To:"OpenStack Development Mailing List \(not for usage questions\)" 
mailto:openstack-dev@lists.openstack.org>>
Date:06/04/2015 02:20 PM
Subject:Re: [openstack-dev] [magnum][horizon] Making a dashboard for 
Magnum - need a vote from the core team




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.

-"Steven Dake (stdake)" mailto:std...@cisco.com>> wrote: 
-
To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
From: "Steven Dake (stdake)" mailto:std...@cisco.com>>
Date: 06/04/2015 11:03AM
Subject: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum - need 
a vote from the core team

Hey folks,

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.

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.

As far as “how to get patches approved”, there are two models we can go with.

Option #1:
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.

Option #2:
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.

Cores, please vote on Option #1, or Option #2, and Adrian can make a decision 
based upon the results.

Regards
-steve

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum - need a vote from the core team

[Bradley Jones (bradjone)]

I’m really keen to take on this effort, to echo what Steve said I think adding 
a dashboard component to Magnum is critical in adoption and delivering good 
usability to all.

Thanks,
Brad Jones


On 4 Jun 2015, at 18:58, Steven Dake (stdake) 
mailto:std...@cisco.com>> wrote:

Hey folks,

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.

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.

As far as “how to get patches approved”, there are two models we can go with.

Option #1:
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.

Option #2:
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.

Cores, please vote on Option #1, or Option #2, and Adrian can make a decision 
based upon the results.

Regards
-steve

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Horizon] [UX] Curvature interactive virtual network design

[Bradley Jones (bradjone)]

Neutron DVR is not something that has been tested but as long as DVR exposes a 
similar API to the current Neutron Router implementation there should be no 
problems. Curvature is agnostic to the underlying implementation of logical 
components.

Additional network services like LBaaS are on our roadmap to include.

Thanks,
Brad

From: Stefano Santini mailto:ssantin...@gmail.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Date: Sunday, 9 November 2014 21:30
To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Horizon] [UX] Curvature interactive virtual 
network design

Another +1 for me and 2 preliminary questions

Router visualisation will work also with Neutron DVR ?
Any change to handle also network services  ? (i.e. LBaaS)

Thanks & regards
Stefano

On Sun, Nov 9, 2014 at 5:39 PM, Stuart Fox 
mailto:stu...@demonware.net>> wrote:
+1 from me

Also, can you get Cisco to opensource Avos? It was demo'd at Atlanta

On Sun, Nov 9, 2014 at 6:45 AM, Chris Dent 
mailto:chd...@redhat.com>> wrote:
On Fri, 7 Nov 2014, John Davidge (jodavidg) wrote:

We’d like to gauge interest from the community on whether this is something 
people want.

When I go to the existing network topology maps in horizon I
frequently find myself wanting to drag stuff around.

So +1 from me.

--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




--
BR,
Stuart

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev