summaryrefslogtreecommitdiffstats
path: root/testcases/VIM/OpenStack/CI/libraries/generate_defaults.py
AgeCommit message (Collapse)AuthorFilesLines
2016-02-03Consider volumes and floatingips as defaults in clean_openstackjose.lausuch1-1/+24
Change-Id: I3ffc864768a7c474ee1063eecee1e2085de807b5 Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com> (cherry picked from commit 16038f444c1e80006e13b72cb0597976a0b2f92e)
2016-02-02Use generate_defaults instead of os_defaults fixed parametersjose.lausuch1-3/+6
JIRA: FUNCTEST-131 Running generate_defaults.py in prepare_env.sh (before running any test) will create a file with the CURRENT OpenStack objects in the deployment. After each test, the cleanup script will take into consideration those parameters instead of the specified in os_defaults.yaml Keep os_defaults.yaml for the moment Change-Id: I5f38fef47f0a6d79407d1d582b1e7d3713503e07 Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com> (cherry picked from commit 47635924e6def36be3c44a047d91018e47a439eb)
2016-02-01Add script to generate the OpenStack defaultsjose.lausuch1-0/+176
JIRA: FUNCTEST-131 It checks the existing Openstack objects in the current deployment (i.e. when the script is executed) and it will create a yaml file to be used afterwards by clean_openstack. This way, a user can generate the defaults when needed if there are things that are not meant to be deleted without fear of using clean_openstack. Change-Id: Iacf204bdd14f591df21b3f243d27199ead2404b0 Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com> (cherry picked from commit 954907ac2995cfc158d5e363829af7c776be5f90)