Upgrade the test confs

Registered by Michael Basnight on 2012-12-05

The test conf are currently json files. There is duplication between the test confs and the regular confs since there is no access to the regular confs. The "limitation" of the old confs was the lack of nested values, so the json was used. The new oslo cfg can use nested values in the form of

[rabbit]
host = blah

So you can do things like CONF.rabbit.host and CONF.rabbit is not None, which is enough to make the new oslo cfg features work with the test.confs json features.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Approved
Assignee:
None
Definition:
Drafting
Series goal:
Accepted for future
Implementation:
Unknown
Milestone target:
milestone icon ongoing

Related branches

Sprints

Whiteboard

Description:
-----------------
There is a test case that checks for volume size limits that will behave differently based on multiple flags.

Note: This test should pass by default as Volume Support is enabled by all flags.

reddwarf/reddwarf/tests/api/instances.py => test_instance_size_too_big

This test hinges on the following property "reddwarf_can_have_volume" that comes from test.conf (rdi: test_begin.conf)

There is a known issue where if you want to run this test with Volume Support = False you will need to toggle flags in three property files.

reddwarf:
    - reddwarf.conf
    - reddwarf-taskmanager.conf

reddwarf-integration:
    - test.conf

https://review.openstack.org/#/c/18444/
https://bugs.launchpad.net/reddwarf-integration/+bug/1092315

Suggested Work
---------------------
Try to refactor properties to only use one flag if possible, or refactor tests to not rely on properties for the two cases. Meaning you just have one test that will create an instance with a volume and one without.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.