GitHub user gauravaradhye opened a pull request:
https://github.com/apache/cloudstack/pull/128
CLOUDSTACK-8251: Adding automation test cases for dedicated public IP ranges
Test cases for dedicated public IP ranges feature.
Tested on KVM setup.
Although this test cases won't break any other test cases, it's possible
that these test might fail when run in parallel with other test cases due to
shared resources in the setup. Hence adding the test suite to maint folder so
that it is run separately and serially.
Log:
Dedicate public IP range to an account in root domain ... === TestName:
test_01_dedicate_public_ip_range_root_domain |
Status : SUCCESS ===
ok
Dedicate public IP range to an account in user domain ... === TestName:
test_02_dedicate_public_ip_range_user_domain |
Status : SUCCESS ===
ok
Dedicate public IP range to an account during its creation only ... ===
TestName:
test_03_dedicate_during_creation_root_domain | Status : SUCCESS ===
ok
Dedicate public IP range to an account in user domain during its creation
only ... === TestName:
test_04_dedicate_during_creation_user_domain | Status : SUCCESS ===
ok
Create guest network in account with dedicated public ip range and acquire
IPs in network ... === TestName:
test_05_acquire_ip_single_guest_network | Status : SUCCESS ===
ok
Create multiple guest networks and acquire IPs from dedicated range ... ===
TestName:
test_06_acquire_ip_multiple_guest_network | Status : SUCCESS ===
ok
Acquire public IP from dedicated range in network tier of VPC ... ===
TestName: test_08_acquire_ip_in_vpc | Status :
SUCCESS ===
ok
Dedicate invalid public IP range to an account ... === TestName:
test_10_dedicate_invalid_ip_range | Status : SUCCESS ===
ok
Dedicate public IP range to invalid account ... === TestName:
test_11_dedicate_to_wrong_account | Status : SUCCESS ===
ok
Dedicate already dedicated public IP range ... === TestName:
test_12_dedicate_already_dedicated_range | Status : SUCCESS
===
ok
Dedicate public IP range to an account having lesser public ip limit than
range ... === TestName: test_13_public_ips_limit
| Status : SUCCESS ===
ok
Disassociate a public IP from dedicated public IP range ... === TestName:
test_14_release_ip_from_dedicated_range |
Status : SUCCESS ===
ok
Release dedicated public ip range with no IPs acquired ... === TestName:
test_15_release_dedicated_range | Status :
SUCCESS ===
ok
Delete dedicated public IP range with no network rules on IP addresses ...
=== TestName:
test_16_delete_ip_range_no_network_rules | Status : SUCCESS ===
ok
Delete Dedicated public IP range with network rules on IP addresses ... ===
TestName:
test_17_delete_ip_range_network_rules | Status : SUCCESS ===
ok
Delete network with public IP from dedicated range acquired in it ... ===
TestName: test_18_delete_network | Status :
SUCCESS ===
ok
Create guest network in account with dedicated public ip range ... ===
TestName: test_19_delete_account | Status : SUCCESS
===
ok
Create guest network in account with dedicated public ip range ... ===
TestName: test_20_release_range_not_dedicated |
Status : SUCCESS ===
ok
Dedicate a public IP range, acquire some IPs and relese the range ... ===
TestName:
test_21_release_dedicated_range_ip_address_in_use | Status : SUCCESS ===
ok
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gauravaradhye/cloudstack 8251
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/128.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 #128
----
commit 42da7c2a6170d620222dba958ebb971f7f0811f5
Author: Gaurav Aradhye <gaurav.arad...@clogeny.com>
Date: 2015-03-24T10:46:50Z
CLOUDSTACK-8251: Adding automation test cases for dedicated public IP ranges
----
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
