So I've come up with a patch that seems to allow this to work. It modifies only a script in the system VM, along with disabling the check that locks down VPCs to only one load balanced network offering. It looked initially to be a bit hairy, and maybe that's why it was left off, but if there's another technical reason such as security please let me know.
I don't see a functional spec mentioning it, just the internal load balancing and load balancing on shared networks. I wouldn't want to step on any work done there if they modify the way VPC load balancing works though, so I'll try to get feedback on whether they are changing the function of the existing haproxy. On Thu, May 2, 2013 at 10: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? >
