Open Stack

Hi Mark,

Do you suggest us to pause on this BP. Let us know if someone is already working on this.

Regards,
Balaji.P

From: Mark McClain [mailto:mark.mcclain at dreamhost.com]
Sent: Friday, August 30, 2013 5:41 AM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [Neutron] Resource URL support for more than two levels

Stay tuned.  There are folks working on a proposed set of API framework changes.  This will be something that we'll discuss as part of deciding the features in the Icehouse release.

mark

On Aug 29, 2013, at 10:08 AM, Justin Hammond <justin.hammond at rackspace.com<mailto:justin.hammond at rackspace.com>> wrote:


I find that kind of flexibility quite valuable for plugin developers. +1 to this. I'd like to be involved if possible with helping you with it.

From: balaji patnala <patnala003 at gmail.com<mailto:patnala003 at gmail.com>>
Reply-To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Thu, 29 Aug 2013 11:02:33 +0530
To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Cc: "openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>" <openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>>
Subject: Re: [openstack-dev] [Neutron] Resource URL support for more than two levels

Hi,

When compared to Nova URL implementations, It is observed that the Neutron URL support cannot be used for more than TWO levels.

Applications which want to add as PLUG-IN may be restricted with this.

We want to add support for changes required for supporting more than TWO Levels of URL by adding the support changes required in Core Neutron Files.

Any comments/interest in this.?

Regards,
Balaji.P




On Tue, Aug 27, 2013 at 5:04 PM, B Veera-B37207 <B37207 at freescale.com<mailto:B37207 at freescale.com>> wrote:
Hi,

The current infrastructure provided in Quantum [Grizzly], while building Quantum API resource URL using the base function 'base.create_resource()' and RESOURCE_ATTRIBUTE_MAP/SUB_RESOURCE_ATTRIBUTE_MAP, supports only two level URI.
Example:
GET  /lb/pools/<pool_id>/members/<member_id>

Some applications may need more than two levels of URL support. Example: GET  /lb/pools/<pool_id>/members/<member_id>/xyz/<xyz_id>

If anybody is interested in this, we want to contribute for this as BP and make it upstream.

Regards,
Veera.

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

_______________________________________________ OpenStack-dev mailing list OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130902/1cd9573a/attachment.html>