Venkatachalam [mailto:vijay.venkatacha...@citrix.com]
Sent: 15 October 2014 05:38
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS][Octavia] Floating IP management
Thanks for the doc.
The floating IP could be hosted directly by the lb backend/lb
driver.
Thanks,
Vjay
From: Vijay Venkatachalam [mailto:vijay.venkatacha...@citrix.com]
Sent: 15 October 2014 05:38
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS][Octavia] Floating IP management
Thanks for the doc.
The floating IP
: [openstack-dev] [Neutron][LBaaS][Octavia] Floating IP management
I felt guilty after reading Vijay B. 's reply :).
My apologies to have replied in brief, here are my thoughts in detail.
Currently LB configuration exposed via floating IP is a 2 step operation.
User has to first create a VIP
@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Neutron][LBaaS][Octavia] Floating IP management
I'm unsure the meaning of hosting FLIP directly on the LB.
There can be LB appliances (usually physical appliance) that sit at the edge
and is connected to receive
Nice diagrams. :-) Thanks. Susanne
On Mon, Oct 13, 2014 at 4:18 PM, Phillip Toohill
phillip.tooh...@rackspace.com wrote:
Diagrams in jpeg format..
On 10/12/14 10:06 PM, Phillip Toohill phillip.tooh...@rackspace.com
wrote:
Hello all,
Heres some additional diagrams and docs. Not
Hi Phillip,
Adding my thoughts below. I’ll first answer the questions you raised with
what I think should be done, and then give my explanations to reason
through with those views.
1. Do we want to add logic in the plugin to call the FLIP association API?
We should implement the logic in
: [openstack-dev] [Neutron][LBaaS][Octavia] Floating IP management
Nice diagrams. :-) Thanks. Susanne
On Mon, Oct 13, 2014 at 4:18 PM, Phillip Toohill
phillip.tooh...@rackspace.commailto:phillip.tooh...@rackspace.com wrote:
Diagrams in jpeg format..
On 10/12/14 10:06 PM, Phillip Toohill
Hello all,
Heres some additional diagrams and docs. Not incredibly detailed, but
should get the point across.
Feel free to edit if needed.
Once we come to some kind of agreement and understanding I can rewrite
these more to be thorough and get them in a more official place. Also, I
understand
I'll add some more info to this as well:
Neutron LBaaS creates the neutron port for the VIP in the plugin layer
before drivers ever have any control. In the case of an async driver,
it will then call the driver's create method, and then return to the
user the vip info. This means the user will
Hello All,
I wanted to start a discussion on floating IP management and ultimately
decide how the LBaaS group wants to handle the association.
There is a need to utilize floating IPs(FLIP) and its API calls to
associate a FLIP to the neutron port that we currently spin up.
See DOCS here:
10 matches
Mail list logo
