[openstack-dev] [ironic] [qa] Testing config drive creation in our CI
Jim Rollenhagen
jim at jimrollenhagen.com
Mon Sep 26 12:43:37 UTC 2016
On Mon, Sep 26, 2016 at 7:29 AM, Sean Dague <sean at dague.net> wrote:
> On 09/26/2016 07:15 AM, Dmitry Tantsur wrote:
>> On 09/26/2016 01:09 PM, Sean Dague wrote:
>>> This should probably be set at the job level, and not buried inside
>>> devstack to be different based on hypervisor. That's going to be a lot
>>> more confusing to unwind later.
>>
>> Fair. So should we just set DEVSTACK_GATE_CONFIGDRIVE for all our jobs?
>> Do you think it should go somewhere here:
>> https://github.com/openstack-infra/devstack-gate/blob/7ecc7dd4067d99e0fa7525a9fffc8b05e1a7b58f/devstack-vm-gate.sh#L343-L370
>> ?
>
> The devstack-gate change is probably sufficient.
>
> That being said, you can also add "config_drive": True to the server
> create json per request, and it will use a config drive. That may be a
> better option for testing, as it will let you specify at the test level
> what needs config drive testing.
>
> http://developer.openstack.org/api-ref/compute/?expanded=create-server-detail#id7
Well, we use some of the nova tests from tempest's trees, so that
probably isn't an option here. :)
We've been trying a bit to move things out of d-s-g and into project-config,
so I'd rather put it into project-config unless we have a good reason not to
do so.
// jim
More information about the OpenStack-dev
mailing list