Hi all, $subject?
Currently, if we have 2 as the minimum of a deployment policy, then we use it at a subscription(say PHP), it will spawn 2 instances since the same deployment policy is used for LB cluster as well. So the LB cluster, which is common to all the subscriptions that are in one network partition, and use "default load balencer" option become dependent on first subscription. I think we can improve here. We can have a default deployment policy for LB cartridges, which will be used when running minimum rule for that subscription, and it will not depend on first subscription... WDYT? Thanks. -- -- Lahiru Sandaruwan Software Engineer, Platform Technologies, WSO2 Inc., http://wso2.com lean.enterprise.middleware email: [email protected] cell: (+94) 773 325 954 blog: http://lahiruwrites.blogspot.com/ twitter: http://twitter.com/lahirus linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
