Hi Pedro, > We did have plans to implement a provider for the LBaaS API that would > implement this but this is also related to the next question... Any news/update around that? Did you wrote a blueprint ? Can we follow the work on a review thread?
> Implementation-wise this is fairly incremental… the hardest part is to > define a schema for the health-monitoring probes. The vrouter-agent can > easily periodically run commands: whether a simple http query or an external > script… The status of these would then need to be fed back to the conditional > advertisement of the virtual IP addresses. How you finally decide to health check the backend? Édouard. On Thu, May 28, 2015 at 5:59 PM, Pedro Marques <[email protected]> wrote: > > On May 28, 2015, at 12:30 AM, Stefan Andres <[email protected]> wrote: > > On 26.05.15 18:24, Pedro Marques wrote: > > Equal cost multi path… (assuming that you don’t modify the route > preferences). > > > Hey Pedro, > how do I set that (giving 1 floating IP to two VMs) up exactly for two VMs? > > > Today that has to be performed via the contrail API directly. > We did have plans to implement a provider for the LBaaS API that would > implement this but this is also related to the next question... > > > Is it smart enough not to send any packages when one VM is not reachable? > > > Not at the moment. There are multiple applications that require the vrouter > to be able to perform heath monitoring in a distributed fashion. And make > advertisement of service-chain and VIP routes conditional on the VM > answering the health monitor probes. > > Implementation-wise this is fairly incremental… the hardest part is to > define a schema for the health-monitoring probes. The vrouter-agent can > easily periodically run commands: whether a simple http query or an external > script… The status of these would then need to be fed back to the > conditional advertisement of the virtual IP addresses. > > > Regards, > Stefan > > > Pedro. > > On May 26, 2015, at 9:03 AM, [email protected] > <mailto:[email protected]> wrote: > > A single fip assigned to multiple vmis? What will that do exactly? > > > (Sent from my phone) > > Soren Hansen > AVP, Chief Cloud Architect > Reliance Jio Infocomm, Ltd. > > ------------------------------------------------------------------------ > *From:* Dev <[email protected] > <mailto:[email protected]>> on behalf of Pedro > Marques <[email protected] <mailto:[email protected]>> > *Sent:* 26 May 2015 17:33 > *To:* 王李明 > *Cc:* [email protected] <mailto:[email protected]> > *Subject:* Re: [opencontrail-dev] can contrail use lvs for loadbalance > > LBaaS API is only supported with proxy mode at the moment. > You can however create a floating-ip in any network and assign a > floating-ip to multiple instances via the contrail API. That will > provide you with the equivalent functionality. > > Pedro. > > On May 24, 2015, at 7:33 PM, 王李明 <[email protected] > <mailto:[email protected]>> wrote: > > hi Pedro： > I know the contrail 2.0 is support haproxy > but *the mode of Direct Routing for lvs is not support* > * * > *I want to know whether contrail can support lvs Direct Routing mode ?*** > *发件人:* Pedro Marques [mailto:[email protected]] > *发送时间:* 2015年5月23日 6:28 > *收件人:* 王李明 > *抄送:* [email protected] <mailto:[email protected]> > *主题:* Re: [opencontrail-dev] can contrail use lvs for loadbalance > > Recent code versions (2.0+) support LBaaS. neutron.conf needs to be > updated in order to enable this functionality. > > AFAIK the settings are: > > [DEFAULT] > service_plugins = > neutron_plugin_contrail.plugins.opencontrail.loadbalancer.plugin.LoadBalancerPlugin > > > [service_providers] > service_provider = > LOADBALANCER:Opencontrail:neutron_plugin_contrail.plugins.opencontrail.loadbalancer.driver.OpencontrailLoadbalancerDriver:default > > > > On May 22, 2015, at 5:51 AM, 王李明 <[email protected] > <mailto:[email protected]>> wrote: > > > hi all: > I have test for lvs but I find it is can not work > can contrail use lvs for loadbalance now ? > > any help will be appricate > > Wang Liming > > _______________________________________________ > Dev mailing list > [email protected] <mailto:[email protected]> > http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org > > > > "*Confidentiality Warning*: This message and any attachments are > intended only for the use of the intended recipient(s), are > confidential and may be privileged. If you are not the intended > recipient, you are hereby notified that any review, re-transmission, > conversion to hard copy, copying, circulation or other use of this > message and any attachments is strictly prohibited. If you are not the > intended recipient, please notify the sender immediately by return > email and delete this message and any attachments from your system. > *Virus Warning:* Although the company has taken reasonable precautions > to ensure no viruses are present in this email. The company cannot > accept responsibility for any loss or damage arising from the use of > this email or attachment." > > > > > _______________________________________________ > Dev mailing list > [email protected] > http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org > > > > -- > SysEleven GmbH > Umspannwerk - Aufgang C > Ohlauer Straße 43 > 10999 Berlin > > Tel +49 30 233 2012 0 > Fax +49 30 616 755 50 > > http://www.syseleven.de > http://www.facebook.com/SysEleven > > Firmensitz: Berlin > Registergericht: AG Berlin Charlottenburg, HRB 108571 B > Geschäftsführer: Marc Korthaus, Thomas Lohner, Jens Ihlenfeld > > > > _______________________________________________ > Dev mailing list > [email protected] > http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org > _______________________________________________ Dev mailing list [email protected] http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
