Ivar,
With the currently supported set of services I also agree, but as more
services get supported in the future, or we hand out that choice to
tenants' VMs, it starts to justify a generic model that does not
restrict whether EPs should provide service chains.
That said, I do not yet totally und
cram more
>> than
>> >> one abstraction in one single API, as it does violate the above
>> mentioned
>> >> principles. Ultimately I like the L2 GW API proposed by 1 and 2
>> because it's
>> >> in line with those principles. I'd rather
Hello all,
Also, what about Kevin's https://review.openstack.org/#/c/87825/? One of
its use cases is exactly the L2 gateway. These proposals could probably be
inserted in a more generic work for moving existing datacenter L2 resources
to Neutron.
Cheers,
On 14 November 2014 15:28, Mathieu Rohon w
Hello Sumit.
Unfortunately I could not go to the round table meeting, sorry for the
absence.
Did you talk about traffic steering? Is there some place or etherpad with a
summary of what was discussed/outlined?
Cheers,
On 5 November 2014 17:22, Sumit Naiksatam wrote:
> Hi,
>
> We had a productive
I was at Maruti's presentation and it was very interesting. I have
developed a similar PoC so I got even more interested.
The main difference between them, from my understanding during the
presentation, is that my PoC tries to encompass very heteogeneous kinds of
networking equipment. Say, making
>What I really hate is having to throw away my (local, precious for me)
history for all change requests because I need to upload a change to Gerrit.
+1
>3. and now you get the first version that deserves to be seen by
community, so you run 'git review', it asks you for desired commit message,
and
I have developed a new kind of agent (used to remote-configure
heterogeneous legacy switches) and it would definitely benefit from
interacting with, e.g., the ovs agent.
Igor Duarte Cardoso.
http://igordcard.com
Sent from mobile.
On Jul 31, 2014 2:49 AM, "loy wolfe" wrote:
> openstack is designe
ric API definition and
> implementations
> (including ML2). In "external attachment point" blueprint review, API
> and generic topics are mainly discussed so far and the detail
> implementation is not discussed
> so much yet. ML2 implementation detail can be discussed later
Hello Kevin.
There is a similar Neutron blueprint [1], originally meant for Havana but
now aiming for Juno.
I would be happy to join efforts with you regarding our blueprints.
See also: [2].
[1] https://blueprints.launchpad.net/neutron/+spec/ml2-external-port
[2] https://blueprints.launchpad.net/n