GitHub user gauravaradhye opened a pull request:
https://github.com/apache/cloudstack/pull/159
CLOUDSTACK-8380: Adding script to testSetupSuccess.py to check VCenter port
groups are created for storage, management and public traffic as soon as zone
is deployed
This test will be run on vmware zone once the zone is up, if the zone uses
vmware DVS.
Data Center Details must filled up in config dict.
Tested on Vmware and KVM. On KVM it skips.
VMware:
Test correct VCenter ports are created for all traffic types ... ===
TestName: test_VCenterPorts | Status : SUCCESS ===
ok
system VMs need to be ready and Running for each zone in cloudstack ...
SKIP: skip
built-in templates CentOS to be ready ... SKIP: skip
----------------------------------------------------------------------
Ran 3 tests in 25.920s
OK (SKIP=2)
on KVM:
Test correct VCenter ports are created for all traffic types ... SKIP: This
test is intended only for vmware
system VMs need to be ready and Running for each zone in cloudstack ...
SKIP: skip
built-in templates CentOS to be ready ... SKIP: skip
----------------------------------------------------------------------
Ran 3 tests in 0.021s
OK (SKIP=3)
Other Changes:
1. Increases retry count while checking system VM state
2. Fixed import* issues
Travis might fail in case the pull request at
https://github.com/apache/cloudstack/pull/155 is not closed.
Please merge above mentioned pull request first and then try to merge this
one.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gauravaradhye/cloudstack 8380
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/159.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 #159
----
commit 469270ab0c6ee2df4d1ece0aa2b8d68fd281cd9a
Author: Gaurav Aradhye <[email protected]>
Date: 2015-04-13T11:20:38Z
CLOUDSTACK-8380: Adding script to testSetupSuccess.py to check VCenter port
groups are created for storage, management and public traffic as soon as zone
is deployed
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
