ecember 16, 2014 7:10 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Neutron] [RFC] Floating IP idea solicitation and
collaboration
Hi Keshava,
2014-12-15 11:52, A, Keshava :
> I have been thinking of "Starting MPLS right from CN" for L2VPN/EVPN
> scen
Hi Ryan,
Mathieu Rohon :
We have been working on similar Use cases to announce /32 with the
Bagpipe BGPSpeaker that supports EVPN.
Btw, the code for the BGP E-VPN implementation is at
https://github.com/Orange-OpenSource/bagpipe-bgp
It reuses parts of ExaBGP (to which we contributed encodings
h
Not sure how the above answers your questions; please keep asking if it
does not ! ;)
-Thomas
-Original Message-
From: Mathieu Rohon [mailto:mathieu.ro...@gmail.com]
Sent: Monday, December 15, 2014 3:46 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [ope
n [mailto:mathieu.ro...@gmail.com]
Sent: Monday, December 15, 2014 3:46 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron] [RFC] Floating IP idea solicitation and
collaboration
Hi Ryan,
We have been working on similar Use cases to announce
Hi Ryan,
We have been working on similar Use cases to announce /32 with the
Bagpipe BGPSpeaker that supports EVPN.
Please have a look at use case B in [1][2].
Note also that the L2population Mechanism driver for ML2, that is
compatible with OVS, Linuxbridge and ryu ofagent, is inspired by EVPN,
an
On Mon, Dec 8, 2014 at 7:57 PM, Carl Baldwin wrote:
> I'll be traveling around the time of the L3 meeting this week. My
> flight leaves 40 minutes after the meeting and I might have trouble
> attending. It might be best to put it off a week or to plan another
> time -- maybe Friday -- when we co
baluk...@bluebox.net]
> *Sent:* Tuesday, December 09, 2014 7:18 AM
> *To:* OpenStack Development Mailing List (not for usage questions)
>
> *Subject:* Re: [openstack-dev] [Neutron] [RFC] Floating IP idea
> solicitation and collaboration
>
>
>
> For what it's worth
:18 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron] [RFC] Floating IP idea solicitation and
collaboration
For what it's worth, I know that the Octavia project will need something which
can do more advanced layer-3 networking in ord
678.548.7261
> > e: ryan.cleven...@rackspace.com
> >
> > ____________________
> > From: Carl Baldwin [c...@ecbaldwin.net]
> > Sent: Sunday, December 07, 2014 4:04 PM
> > To: OpenStack Development Mailing List
> > Subject: Re: [openstack-dev] [Ne
4 4:04 PM
> To: OpenStack Development Mailing List
> Subject: Re: [openstack-dev] [Neutron] [RFC] Floating IP idea solicitation
> and collaboration
>
> Ryan,
>
> I have been working with the L3 sub team in this direction. Progress has
> been slow because of other priorities b
ck-dev] [Neutron] [RFC] Floating IP idea solicitation and
collaboration
Ryan,
I have been working with the L3 sub team in this direction. Progress has been
slow because of other priorities but we have made some. I have written a
blueprint detailing some changes needed to the code to enab
Ryan,
I have been working with the L3 sub team in this direction. Progress has
been slow because of other priorities but we have made some. I have
written a blueprint detailing some changes needed to the code to enable the
flexibility to one day run glaring ups on an l3 routed network [1]. Jaim
Hi,
At Rackspace, we have a need to create a higher level networking service
primarily for the purpose of creating a Floating IP solution in our
environment. The current solutions for Floating IPs, being tied to plugin
implementations, does not meet our needs at scale for the following reasons:
13 matches
Mail list logo
