Thanks for following up with me.
On Fri, May 3, 2013 at 10:46 AM, Alena Prokharchyk <
alena.prokharc...@citrix.com> wrote:
> I'm working on internal Lb feature. Internal Lb rules will be managed by
> the dedicated system vms. For more details, see the:
>
> *
> FS:
> https://cwiki.apache.org/conf
I'm working on internal Lb feature. Internal Lb rules will be managed by
the dedicated system vms. For more details, see the:
*
FS:https://cwiki.apache.org/confluence/display/CLOUDSTACK/Internal+Load+Bal
ancing+between+VPC+tiers
* the feature is not merged to master as UI yet to be done; refer to
I will look for that jira ticket and see what the status is... thanks.
On Fri, May 3, 2013 at 10:30 AM, Marcus Sorensen wrote:
> 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 h
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/
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
anot
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
wil
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?
