GitHub user pritisarap12 opened a pull request: https://github.com/apache/cloudstack/pull/285
Disable enable zone pod cluster and host Test cases for testing the behavior of resources running on zone, cluster, pod, host and admin/non-admin user after disabling the zone, cluster, pod, host respectively You can merge this pull request into a Git repository by running: $ git pull https://github.com/pritisarap12/cloudstack Disable-Enable-Zone-Pod-Cluster-1 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/285.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 #285 ---- commit aa2a15444547baf04fb7de247fd8efa41b0c0995 Author: pritisarap12 <priti.sa...@clogeny.com> Date: 2015-05-11T17:06:14Z CS-41038 Disabling Zone, Pod, Cluster: --Test cases for testing the behaviour of resources running on zone and admin/non-admin user after disabling the Zone commit 102668f6add704eaa845487fdaf6a5dcd1381f4e Author: pritisarap12 <priti.sa...@clogeny.com> Date: 2015-05-14T06:40:50Z CS-41038 Disabling Zone, Pod, Cluster: --Test cases for testing the behaviour of resources running on zone and admin/non-admin user after disabling the Zone --Integrating review Changes --pep8 issues --create private template than public template --Delete zone part to be added in separate testcase commit 01d927bb2f32d9de3cad801ab5b5e85b3b414846 Author: pritisarap12 <priti.sa...@clogeny.com> Date: 2015-05-18T06:18:22Z CS-41038 Disable-Enable-Zone-Pod-Cluster-1: --Moved the file testpath_disable_zone.py in component/maint folder so that it runs serially and not in parallel with other test suites. commit 38f67aeac985a26f0c4c2d0ca67420ee536928f9 Author: pritisarap12 <priti.sa...@clogeny.com> Date: 2015-05-22T11:28:17Z Disable-Enable-Zone-Pod-Cluster-1: ----Test cases for testing the behaviour of resources running on zone, cluster, pod, host and admin/non-admin user after disabling the zone, cluster, pod, host respectively ---- --- 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. ---