There are at least 3 types of solutions I'm aware of:
1) Using VLANs and physical or virtual-machine appliances that route packets
between VLANs.
Tutorial:
http://developer.rackspace.com/blog/neutron-networking-vlan-provider-networks.html
2) Using an L2 overlay and virtual machines that route pac
On Nov 16, 2013, at 9:43 AM, Dean Troyer wrote:
> On Sat, Nov 16, 2013 at 11:15 AM, Harshad Nakil
> wrote:
> Sean,
> We have diff in three repositories.
> Nova, Neutron and devstack. Each review is requiring other to happen first.
> Do you have recommendation how do we deal with these dependen
) as agenda organizers; please drop us a note if you intend to attend
and wether you would like to present something to the group.
Pedro.
On Nov 7, 2013, at 11:27 AM, Rochelle.Grober wrote:
>
>
> From: Pedro Roque Marques [mailto:pedro.r.marq...@gmail.com]
> Colin,
> "
Radomir,
An extra issue that i don't believe you've covered so far is about comment
ownership. I've just read an email on the list that follows a pattern that i've
heard many complaints about:
-1 with a reasonable comment, submitter addresses the comment, reviewer
never comes back.
Revi
Colin,
"The nice thing about standards is that there are so many of them to choose
from."
For instance, if you take this Internet Draft:
http://tools.ietf.org/html/draft-ietf-l3vpn-end-system-02 which is based on
RFC4364.
It has already been implemented as a Neutron plugin via OpenContrail
(ht
