I saw that it was pushing individual tier rules as a whole config. When I first disabled the check, I could create two LB networks, but they'd erase each other's haproxy configs.
Instead of modifying the java to pass different things, I modified the ssvm script to take the new config and merge it/edit the existing one, so no changes were needed in the management server or individual hypervisor resources. On Fri, May 3, 2013 at 10:25 AM, Alena Prokharchyk < [email protected]> wrote: > Marcus, the limitation exists only on the VPC Virtual Router side. All LB > rules are stored in the single haProxy config, and haproxy restarts on any > of the single rule change. If we support public LB on multiple tiers, the > changes to the tier1 rule would affect rules of the tier2 as well (rules > will become unavailable for some time while ha proxy restart is happening). > > Anthony Xu wrote the backend for the feature, he might share more details > on the topic. Anthony? > > There is also a Jira ticket - implement LB on multiple tiers inside the > VPC by providing graceful HA proxy restart. Its targeted post 4.2 > > -Alena. > > On 5/2/13 9:30 PM, "Marcus Sorensen" <[email protected]> wrote: > > >Maybe this has been asked before... Is there a technical reason why VPC > >can > >only support one loadbalanced tier? What kind of issues would one run > >into > >if you simply let the network offering be used multiple times in a VPC? > > > > >
