avoid requirement on tarball for unit tests
Bug #1285388 reported by
gordon chung
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceilometer |
Fix Released
|
High
|
Chris Dent |
Bug Description
we have a test-requirement on swift to test the middleware. it'd be better if we didn't have this to avoid random breakage.
we should look at a way where it's not necessary whether by enabling the test in tempest, rejigging tests to avoid dependency, or if necessary finding an alternative way to gather data rather than through middleware
Changed in ceilometer: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in ceilometer: | |
milestone: | none → juno-3 |
assignee: | nobody → Chris Dent (chdent) |
Changed in ceilometer: | |
status: | Fix Committed → Fix Released |
Changed in ceilometer: | |
milestone: | juno-3 → 2014.2 |
To post a comment you must log in.
a) gathering the data via middleware is pretty inefficient, especially as currently written: https:/ /bugs.launchpad .net/ceilometer /+bug/1337761 but my understanding was that there was some resistance from somewhere to drop notifications of this data out of swift itself.
b) If the middleware is going to carry on being the way it is, there's no particular reason to use the webob from swift itself. It's there to provide a fake request environment, which is easy enough to do other ways.
Presumably with _this_ test want to test the middleware itself not swift.
Tempests tests could be created which properly test the use of the middleware against real swift data, if that's desirable. The current tests would not be able to do that.
I'll have this bug if nobody else is chafing to have it.