Open Stack

Hi Sergey

Thanks for your information, it's really help.
Actually I am from Magnum team and we are using heat to do orchestration 
on docker swarm bay.

Swarm master only support A-P mode (active-passive), I wonder if there 
any workaround to
implement my requirement :
----------------
/VIP : 192.168.0.10//
////
//master-1 192.168.0.100 (A)//
//master-2 192.168.0.101 (P)//
////
//if I want to make VIP to alway connect with master-1(since it is A 
mode),//
//only switch to master-2 when master-1 down. what should I do?/
---------------

Below link is the heat template of k8s(k8s supports A-A mode, so it can 
use ROUND_ROBIN).
https://github.com/openstack/magnum/blob/master/magnum/templates/kubernetes/kubecluster.yaml#L343

P.S Copy to Magnum team.

thanks
Eli.


On 2015年11月16日 15:15, Sergey Kraynev wrote:
> On 16 November 2015 at 09:46, Qiao,Liyong <liyong.qiao at intel.com 
> <mailto:liyong.qiao at intel.com>> wrote:
>
>     hi, I have some questions about neutorn LBaas.
>
>     seen from the wiki, the load balancer only support:
>
>     *Table 4.6. Load Balancing Algorithms*
>
>     *Name*
>     LEAST_CONNECTIONS
>     ROUND_ROBIN
>
>
>     https://wiki.openstack.org/wiki/Neutron/LBaaS/API
>
>     think about if I have a A-P mode HA
>
>     VIP : 192.168.0.10
>
>     master-1 192.168.0.100 (A)
>     master-2 192.168.0.101 (P)
>
>     if I want to use VIP to alway connect with master-1(since it is A
>     mode),
>     only switch to master-2 when master-1 down. what should I do?
>     any plan to support more algorithms for neutron lbaas?
>
>     BTW, the usage is from heat:
>
>       etcd_pool:
>         type: OS::Neutron::Pool
>         properties:
>           protocol: HTTP
>           monitors: [{get_resource: etcd_monitor}]
>           subnet: {get_resource: fixed_subnet}
>     *      lb_method: ROUND_ROBIN*
>           vip:
>             protocol_port: 2379
>
>
>
>     thanks,
>     Eli.
>
>     -- 
>     BR, Eli(Li Yong)Qiao
>
>
>     __________________________________________________________________________
>     OpenStack Development Mailing List (not for usage questions)
>     Unsubscribe:
>     OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>     <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> Hi, Qiao,Liyong
>
> I can not say about LBaaS team plans for supporting some additional 
> algorithms :)
> AFAIK, they do not plan add it to v1 API.
> As I understand it may be discussed as part of v2 API [1]
>
> In the Heat we have related BP [2], with several patches on review. So 
> if it will be implemented on Neutron side, we may add such 
> functionality too.
>
> [1] 
> http://developer.openstack.org/api-ref-networking-v2-ext.html#lbaas-v2.0
> [2] https://blueprints.launchpad.net/heat/+spec/lbaasv2-suport
>
> -- 
> Regards,
> Sergey.
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-- 
BR, Eli(Li Yong)Qiao

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151116/0209f92e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: liyong_qiao.vcf
Type: text/x-vcard
Size: 123 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151116/0209f92e/attachment.vcf>