integration tests are no longer independent from heat
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Medium
|
Angus Salkeld |
Bug Description
Our OS::Heat:
This kind of defeats the idea of being able to run integration tests "standalone" against (remote) Heat. Currently the whole thing works only because pwd for integtaion tests run is our top repo dir, so "heat" can be imported and used.
I see two options here:
1) stay committed to "standalone integration tests" idea and move the OS::Heat:
2) dump the whole "standalone" idea, require whole heat + requirements for integration tests and clearly advertise that the only supported way of running them is installing on the same box heat is installed and updating heat.conf accordingly.
Given gripes we had with requirements for integration tests not being able to sync with global requirements, I'm leaning towards option 2. Also, latest pip is caching the downloaded packages, so one of the purposes of separate requirements for integration tests (decrease gate setup time) is no longer critical.
Changed in heat: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → liberty-3 |
Changed in heat: | |
importance: | High → Medium |
milestone: | liberty-3 → liberty-rc1 |
Changed in heat: | |
assignee: | Angus Salkeld (asalkeld) → Pavlo Shchelokovskyy (pshchelo) |
Changed in heat: | |
assignee: | Pavlo Shchelokovskyy (pshchelo) → Angus Salkeld (asalkeld) |
Changed in heat: | |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | liberty-rc1 → 5.0.0 |
I would like to see OS::Heat: :TestResource move in to the main tree and I think there will be valid use cases for users to write templates using them such as: :TestResource for debugging (once we have a way of disabling constraints like nova.server)
- operators scale testing their own heat deployment
- users mocking out a real resource with OS::Heat:
If we can't make requirements work by leaving them in heat_integratio ntests/ requrements. txt or moving them to test_requiremen ts.txt then I'd rather consider we create a new repo for integration tests.