Age | Commit message (Collapse) | Author | Files | Lines |
|
JIRA: FUNCTEST-224
Change-Id: Ib10dc312a761b06fe36174c5c19a0165f746593e
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
JIRA: FUNCTEST-213
Change-Id: I66c02dd6ff12ffb9798ebe44a4cfe7bfc73e76c3
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
JIRA: FUNCTEST-186
All the openstack related functions are in openstack_utils.py and
the remaining functions in functest_utils.py
All the scripts are adapted to this structure.
Change-Id: I7f3805779741f0b085985d0d053feb429250b1ea
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
Change-Id: I3ffc864768a7c474ee1063eecee1e2085de807b5
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
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>
|
|
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>
|