[
https://issues.apache.org/jira/browse/CLOUDSTACK-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13651259#comment-13651259
]
ASF subversion and git services commented on CLOUDSTACK-2367:
-------------------------------------------------------------
Commit 269e87591eee7b54762a1ea68a6d096b5d32d686 in branch
refs/heads/vpc-multi-tier-public-lb from Marcus Sorensen
<[email protected]>
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=269e875 ]
Summary: Initial commit for vpc multi-network public loadbalancer
Detail: Adjust vpc_loadbalance.sh to adjust firewall rules for multi-tier LB,
call /root/reconfigLB_vpc rather than /root/reconfigLB.sh (single isolatednet
script). Disable check that only allows one loadbalanced network offering
per VPC.
BUG-ID: CLOUDSTACK-2367
Signed-off-by: Marcus Sorensen <[email protected]> 1367957466 -0600
> VPC - allow loadbalanced network offering on multiple tiers
> -----------------------------------------------------------
>
> Key: CLOUDSTACK-2367
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2367
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
> Affects Versions: 4.2.0
> Reporter: Marcus Sorensen
> Assignee: Marcus Sorensen
> Fix For: 4.2.0
>
>
> Currently, VPC only allows one network tier to use network offering with load
> balancing. This feature requests that multiple tiers can have load balancing.
> It will build off of the current haproxy functionality, just allowing the
> configurations to work for several networks.
> I am creating a branch called "vpc-multi-tier-public-lb" to work on this.
> I will need help with adjusting the UI to allow it (in the area where a new
> tier is created), as well as adjusting any marvin test. The changes are
> minor, and unless testing actual functionality, there is nothing to test
> other than "are we allowed to use the lb network offering more than once?".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
