Re: [Netstack] Quantum API resource status proposal

Great write-up Salvatore, comments inline. dan On Tue, Aug 2, 2011 at 4:34 PM, Salvatore Orlando < salvatore.orla...@eu.citrix.com> wrote: > Following the discussion on synchronous vs asynchronous behaviour in the > last Netstack meeting, we agreed to send around a proposal for introducing > the

Re: [Netstack] [Merge]lp:~raxnetworking/quantum/api_extensions into lp:quantum

Hi Dan and Salvatore, Thanks for your inputs. I agree that the community should reach the agreement on data extension before the merge. Actually, there are two things we need to discuss within the community. 1. Do we allow the data extension to the core resource? 2. If we all

Re: [Netstack] [Merge]lp:~raxnetworking/quantum/api_extensions into lp:quantum

And here my comments (also posted previously): I don't have anything in principle against extending core API entities. My only concern is "portability" of client apps. If I write my application using the core API, and I get extended attributes in responses (or I'm supposed to specify extended a

Re: [Netstack] [Merge]lp:~raxnetworking/quantum/api_extensions into lp:quantum

I'm in favor of making a decision on whether we allow data extensions or not before approving this. If the code goes in allowing data extensions, it would be hard to reverse. I personally am in favor of allowing data extensions, but want to make sure there is general agreement. Below are the com

Re: [Netstack] [Merge]lp:~raxnetworking/quantum/api_extensions into lp:quantum

Hi Ying, Santosh fixed a couple of minor issues I found in the code. In Tuesday's meeting we did not really discuss about whether API extensions should allow to extend core resources as well. However, I do not want to hold up this branch for too long. I just want to be sure that it allows to i

Re: [Netstack] [Merge]lp:~raxnetworking/quantum/api_extensions into lp:quantum

Hi Santhosh and Salvatore, I saw api_extensions merge request is still pending. Are there any fixes going on? Best, Ying > -Original Message- > From: Tyler Smith -X (tylesmit) > Sent: Thursday, August 04, 2011 12:00 PM > To: Ying Liu (yinliu2) > Cc: netstack@lists.launchpad.net > Subjec

Re: [Netstack] [Merge]lp:~raxnetworking/quantum/api_extensions into lp:quantum

Hi Ying, You (and Salvatore) were right. I checked out the branch, but now I get a 500 error: RoutesException: URL or environ must be provided I'm looking into fixing it now. Regardless, https://code.launchpad.net/~tylesmit/quantum/api-client-add-list-extensions

Re: [Netstack] [Merge]lp:~raxnetworking/quantum/api_extensions into lp:quantum

Hi Tyler, /v0.1/extensions works for me. You can check your quantum.conf file to see whether the extension is configured or not. BTW, this extension framework is not merged with quantum yet. You need to directly check out Santosh's branch to use /v0.1/extensions Best, Ying > -Original Messa

Re: [Netstack] [Merge]lp:~raxnetworking/quantum/api_extensions into lp:quantum

Hi Tyler, I just tried on my dev environment from Santhosh's branch, and the URI /v0.1/extensions works. I get an empty extension list as a response, as I haven't loaded any. The 404 error might indicate that the extension middleware is not specified in the quantum pipeline in etc/quantum.co

Re: [Netstack] [Merge]lp:~raxnetworking/quantum/api_extensions into lp:quantum

Hi Santhosh, I'm trying to write a wrapper for this call in the api client, but I get a 404 when I request /v0.1/extensions. Am I missing something? Thanks, -Tyler On 8/4/2011 12:31 AM, Santhosh Kumar M wrote: Hi Arvind, In quantum, we can find all supported extensions and its basic detail