Open Stack

Hi Vinay,

I left a few comments on the specification document.
While I understand this is functional for the VPC use case, there might be
applications also outside of the VPC.
My only concern is that, at least in the examples in the document, this
appear to be violating a bit the tenet of neutron being
"technology-agnostic".
I am however confident that it should be doable to find a way to work
around it, or have a discussion identifying the cases where instead it's
advisable to expose the underlying technology.

>From a general perspective, I have not been following closely the
discussion on VPC; I hope to find time to catch up.
However, I recall seeing a blueprint for using nova-api as endpoint for
network operations as well; is that still the current direction>

Salvatore


On 21 March 2014 07:01, Vinay Bannai <vbannai at gmail.com> wrote:

> Hello Folks,
>
> Please see a blueprint that we (eBay Inc) would like to propose for the
> Juno summit. This blueprint addresses the feature of network tagging
> allowing one to tag network resources with key value pairs as explained in
> the specification URL. We at eBay have a version of this feature
> implemented and deployed in our production network. This blueprint
> formalizes the feature definition with enhancements to address more generic
> use cases. I have enabled comments and would like to hear opinions and
> feedback.
>
> The document will be updated with REST URL and resource modeling over the
> weekend for those interested in the details.
>
>
> https://docs.google.com/document/d/1ZqW7qeyHTm9AQt28GUdfv46ui9mz09UQNvjXiewOAys/edit#
>
>
> Regards
>
> --
> Vinay Bannai
> eBay Inc
>
> _______________________________________________
> OpenStack-dev mailing list
> 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/20140321/de1bfe6e/attachment.html>