Hi Ram,
Inline. Thanks,
Dan
On Wed, Jul 27, 2011 at 12:13 PM, Ram Durairaj (radurair) <
radur...@cisco.com> wrote:
> Hi Dan:
>
>
> Responses embedded.
>
> ** **
>
> *From:* Dan Wendlandt [mailto:d...@nicira.com]
> *Sent:* Wednesday, July 27, 2011 10:04 AM
> *To:* Ram Durairaj (radurair
Hi Dan:
Responses embedded.
From: Dan Wendlandt [mailto:d...@nicira.com]
Sent: Wednesday, July 27, 2011 10:04 AM
To: Ram Durairaj (radurair)
Cc: Troy Toman; Salvatore Orlando; netstack@lists.launchpad.net
Subject: Re: [Netstack] Quantum API question - port creation
On Wed, Jul 27, 201
On Wed, Jul 27, 2011 at 10:23 AM, Troy Toman wrote:
>
> On Jul 27, 2011, at 12:17 PM, Dan Wendlandt wrote:
>
> To clarify, I think the question is whether the API layer should enforce
> that the implementation is asynchronous, or leave it up to the plugin. In
> general my preference is to leave
On Jul 27, 2011, at 12:17 PM, Dan Wendlandt wrote:
To clarify, I think the question is whether the API layer should enforce that
the implementation is asynchronous, or leave it up to the plugin. In general
my preference is to leave things up to the plugin, but this has the possible
downside t
To clarify, I think the question is whether the API layer should enforce
that the implementation is asynchronous, or leave it up to the plugin. In
general my preference is to leave things up to the plugin, but this has the
possible downside that people might write clients that assume synchronous
b
On Wed, Jul 27, 2011 at 9:48 AM, Ram Durairaj (radurair) wrote:
> I like the model 2 as well.
>
> I'm not an API expert, but for any "Cloud API" following asynchronous
> model is a basic design tenet and IMHO must be supported.
>
> On the persistence or DB side, on 802.1qbh plugin, we saw the nee
It sounds like the nova API that troy referenced does not REQUIRE the call
to be asynchronous, rather it ALLOWS the call to be asynchronous by saying
that only a subset of the attributes must be returned in the POST:
"Note that when creating a server only the server ID, its links, and the
admin pa
I like the model 2 as well.
I'm not an API expert, but for any "Cloud API" following asynchronous
model is a basic design tenet and IMHO must be supported.
On the persistence or DB side, on 802.1qbh plugin, we saw the need for a
persistence store. We are adding that function with ORM/mysql. Rohi
On Jul 27, 2011, at 10:00 AM, Salvatore Orlando wrote:
> Hi Troy,
>
> This is a very good point in light of the work I'm doing for making sure the
> API specification is consistent with its implementation.
>
> Consistency with Openstack API is one of the reasons for which the
> specification
Hi Troy,
This is a very good point in light of the work I'm doing for making sure the
API specification is consistent with its implementation.
Consistency with Openstack API is one of the reasons for which the
specification states that port creation should happen asynchronously (as well
as ot
10 matches
Mail list logo
