On Mon, 8 Apr 2019, Matt Riedemann wrote:
osc-placement has sort of missed this because of an out of sight / out of mind kind of situation. With StoryBoard tracking placement features we could definitely track something like the server side work in placement itself as a task and the osc-placement related change as another task, so the overall story isn't complete until both parts are done (or the CLI task is invalidated for whatever reason - not all microversions require CLI changes).
Yeah, I think we can probably help this situation if we follow the process I've started describing in https://docs.openstack.org/placement/latest/contributor/contributing.html#ne... where it says "Work items that are described in a spec should be reflected as tasks created on the originating story. Update the story with additional tasks as they are discovered." We should make sure that any osc-placement obligations are one of those tasks (and that should probably be a bullet in those docs).
* It's functional tests require a working devstack, which is a bit meh
I'm not familiar with vcrpy but a simple improvement if we're worried about the time it takes to spin up devstack for these functional jobs is simply trim down the list of enabled services in the devstack run. By default devstack is running with most everything [1] - for these tests we should be able to just enable keystone and placement.
Yes, that's probably a good idea to speed up the gate side of things, but what I'm hoping we could figure out is a way to make it so on the dev side of things we don't need a running devstack for the test -> fix iterative cycle. The majority of the actually useful tests in osc-placement are integration tests (but labeled functional) and thus rather costly to run for the sake of development. vcrpy or requests-mock could potentially help us create real functional tests. -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent