You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by sureshanaparti <gi...@git.apache.org> on 2015/09/21 16:43:04 UTC
[GitHub] cloudstack pull request: CLOUDSTACK-7151: Support multiple physica...
GitHub user sureshanaparti opened a pull request:
https://github.com/apache/cloudstack/pull/862
CLOUDSTACK-7151: Support multiple physical networks at cluster level for guest traffic over VMware deployments.
CLOUDSTACK-7151: Support multiple physical networks at cluster level for guest traffic over VMware deployments.
1. API Changes - addcluster and updatecluster
2. VMware resource changes
3. Database and Upgrade changes
Currently, in cloudstack, the support for cluster level override settings (introduced in 4.2.0 with VMware DVS Integration) for guest and public traffic types blocks support for multiple physical networks defined in the zone for these traffic types over VMware deployments. It is required to support multiple physical networks defined in the zone for these traffic types at zone and cluster level(when defined) without impacting existing cluster level override settings. This would also fix the issue CLOUDSTACK-7151 - vmware: Type of vSwitch was not detected correctly while preparing public/guest virtual networks.
Also, renaming of vSwitch name for guest and public traffic type overridden at cluster in current cloudstack deployment has become troublesome, requiring manual update to database. This need to be addressed such that admin would be able to seamlessly re-name vSwitch name at cluster in Cloudstack whenever required, even in production cloud.
Design change for existing cluster level traffic override settings. FS/Design details: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Support+multiple+physical+networks+at+cluster+level+for+guest+traffic+over+VMware+deployments
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sureshanaparti/cloudstack CLOUDSTACK-7151_VMwareMultiplePhyNetworksSupportAtCluster
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/862.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #862
----
commit 8ce5ef939c0590eabb9c9ea97ad650c2a4f4402a
Author: Suresh Kumar Anaparti <su...@citrix.com>
Date: 2015-09-21T14:27:03Z
CLOUDSTACK-7151: Support multiple physical networks at cluster level for guest traffic over VMware deployments.
1. API Changes - addcluster and updatecluster
2. VMware resource changes
3. Database and Upgrade changes
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] cloudstack pull request: CLOUDSTACK-7151: Support multiple physica...
Posted by sureshanaparti <gi...@git.apache.org>.
Github user sureshanaparti commented on the pull request:
https://github.com/apache/cloudstack/pull/862#issuecomment-142004394
Tested database upgrade and updated API cmds addcluster and updatecluster to support multiple physical networks at cluster level.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] cloudstack pull request: CLOUDSTACK-7151: Support multiple physica...
Posted by rhtyd <gi...@git.apache.org>.
Github user rhtyd commented on the pull request:
https://github.com/apache/cloudstack/pull/862#issuecomment-216192713
@sureshanaparti please rebase against latest master, squash your commits into one and push -f, update on status of your PR
tag:vmware-pickup
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---