Hi All,

Following is the implementation workflow we are planing with the LVS load
balancer extension for Stratos.

1. We are passing the virtual IPs with service names when starting the LVS
extension.LVS extension will check if this service exists in the
topology.If this service exists in the topology, extension will write the
configuration related to the "keepalived"[1][2].Otherwise it will give the
warning message to the user.Please note that this LVS extension can execute
as a standalone service.(As similar with our current haproxy and nginx
extensions)

2. If any service need to use the LVS as a load balancer it needs to pass
its related LVS virtual IP with cartridge "subscribableInfo".Those
subscriber info will pass to the payload of that cartridge.

3. We will write the plugin at python agent to get this LVS virtual IP from
the payload and create a dummy interface in the real server.[See Real
Server Setup section in ref 2]

Please share your thoughts on this.

[1] http://www.keepalived.org/pdf/UserGuide.pdf
[2]
https://docs.google.com/document/d/1uGWZu4WRQY8IP9ysS8MjlTfvNISXguPY6KoFkXFfXW0/edit

Thanks,
Gayan

-- 

Gayan Gunarathne
Technical Lead
WSO2 Inc. (http://wso2.com)
email  : gay...@wso2.com  | mobile : +94 766819985

Reply via email to