Koper, Dies <diesk@...>
Thanks for your reply.
I’m not sure what API we’re currently using and if not LBaaS, why not.
Either way, it sounds like the collocated job is the easiest solution for now.
From: ronak banka [mailto:ronakbanka.cse(a)gmail.com]
Sent: Tuesday, September 15, 2015 4:02 PM
To: Discussions about the Cloud Foundry BOSH project.
Subject: [cf-bosh] Re: Re: automatically registering gorouters with OpenStack LB
I Agree that it will be helpful for Openstack deployments but having something like this in CPI will only be helpful when native Openstack LBaaS api are used .
For custom ELB deployments it will be good to create separate Bosh release and make a elb-register job collocated along with router job which will add or remove router from ELB using api or else way.
On Tue, Sep 15, 2015 at 3:37 PM, Voelz, Marco <marco.voelz(a)sap.com<mailto:marco.voelz(a)sap.com>> wrote:
I agree that the registration at an external ELB would be very helpful to have – just like it is done for AWS. We currently use the HAProxy, so I guess this is a challenge which will hit us at a later point in time…
I’d love to see a PR for this! :)
On 15/09/15 01:54, "Koper, Dies" <diesk(a)fast.au.fujitsu.com<mailto:diesk(a)fast.au.fujitsu.com>> wrote:
I’m aware of bosh aws cpi’s elbs option to list ELBs with gorouters.
I’m looking for a similar option for OpenStack.
How do people ensure that when gorouters are e.g. rolled during an upgrade, the new VMs are automatically registered with the load balancer?
We use a LB we developed ourselves, which is hooked in to OpenStack using its pluggable LB infrastructure.