Hi,
I am working on $subject.
* We use puppet to download and extract carbon server into the instnace
* WKA configuration is done by cartridge agent by plugins. We can not do
WKA configuration by puppet since wka members are dynamic
*
Define an application which has wka-carbon cartridge and non-wka-carbon
cartridge. non-wka cartridge has a startup dependency so wka cluster
startups first.
In order to identify weather it is a wka or non wka, we can define
properties in the cartridge definition. So the properties will be visible
in cartridge agent.
CLUSTERING_TYPE=wka
SERVER_TYPE=worker|manager
*Logic in cartridge agent plugins*
A wka member when started, it will
publish its IP to metadata as wka members
Fetch other members of its cluster and all non wka members by reading
topology and adds them to a restart queue. This is done since other members
should be reconfigured when a wka members is added
A non wka member just fetches the wka members from metadata service and
updates its configuration (axis2.xml)
Every members listen to MemberActivates event, when the event is triggered
it check weather this members is a wka member. If so then check if I am in
the restart queue, if so start reconfiguring by fetching updated wka
members from the metadata service.
I will post the application definition and more diagrams as I progress on.
--
Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
