Re: [openstack-dev] [heat][rally] What should we do with legacy-rally-dsvm-fakevirt-heat

2018-02-08 Thread Andrey Kurilin
Hi Rico 2018-02-08 11:38 GMT+02:00 Rico Lin : > Thx Andrey, looking forward to new rally job > > At meanwhile, seems current job is broken [1] > Based on the error, the fix requires +2;-2 change to https://github.com/openstack/heat/blob/master/rally-scenarios/plugins/stack_output.py . I can pro

Re: [openstack-dev] [heat][rally] What should we do with legacy-rally-dsvm-fakevirt-heat

2018-02-08 Thread Rico Lin
Thx Andrey, looking forward to new rally job At meanwhile, seems current job is broken [1] and we're expecting for a new job to replace. We will remove the old legacy one (see patch [2]) for now if that won't break rally (in any way). I'm changing only config for heat (under zuul.d/projects.yaml)

Re: [openstack-dev] [heat][rally] What should we do with legacy-rally-dsvm-fakevirt-heat

2018-02-07 Thread Andrey Kurilin
Hi Rico and stackers, Thanks for raising this topic. Short answer: please leave it as is for now. Rally team will work on ZuulV3 jobs soon. Detailed: We are planning to make some big changes in our architecture which includes splitting the main repo into a separate repository for a framework and

[openstack-dev] [heat][rally] What should we do with legacy-rally-dsvm-fakevirt-heat

2018-02-07 Thread Rico Lin
Hi heat and rally team Right now, in heat's zuul jobs. We still got one legacy job to change `legacy-rally-dsvm-fakevirt-heat` [1] which I already put a patch out here [2], but after discussion with infra team, it seems best if we can define this in rally, and reference it in heat. So my question