Re: [openstack-dev] [heat][rally] What should we do with legacy-rally-dsvm-fakevirt-heat
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 propose a patch with a fix and we can leave legacy-rally job at experimental queue. Or we can return to this after sometime. I'm ok about both cases. > 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), won't > touch `legacy-rally-dsvm-fakevirt-heat` itself (I guess that is up to > rally team to remove it later) > > [1] http://logs.openstack.org/29/531929/3/experimental/ > legacy-rally-dsvm-fakevirt-heat/cd797f4/job-output.txt. > gz#_2018-02-08_05_02_37_258609 > [2] https://review.openstack.org/542111 > > 2018-02-08 3:39 GMT+08:00 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 a separate repository for all OpenStack plugins. >> To minimize work across all projects which have Rally job, we decided to >> pause working on ZuulV3 until the split will be finished. >> As for estimates, I'm planning to make the final release before splitting >> today or tomorrow. As soon as new release will be ready, we will start >> working on splitting and CI as well. >> >> Thanks for the patient and for using Rally! >> >> 2018-02-07 10:13 GMT+02:00 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 to rally team for all these will be, do we still need >>> this job? and how you guys think about if we put that into rally? >>> >>> [1] https://github.com/openstack-infra/project-config/blob/m >>> aster/zuul.d/projects.yaml#L6979 >>> [2] https://review.openstack.org/#/c/509141 >>> -- >>> May The Force of OpenStack Be With You, >>> >>> *Rico Lin*irc: ricolin >>> >>> >>> >>> __ >>> OpenStack Development Mailing List (not for usage questions) >>> Unsubscribe: openstack-dev-requ...@lists.op >>> enstack.org?subject:unsubscribe >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >>> >> >> >> -- >> Best regards, >> Andrey Kurilin. >> >> >> __ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib >> e >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > > -- > May The Force of OpenStack Be With You, > > *Rico Lin*irc: ricolin > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Best regards, Andrey Kurilin. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [heat][rally] What should we do with legacy-rally-dsvm-fakevirt-heat
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), won't touch `legacy-rally-dsvm-fakevirt-heat` itself (I guess that is up to rally team to remove it later) [1] http://logs.openstack.org/29/531929/3/experimental/legacy-rally-dsvm-fakevirt-heat/cd797f4/job-output.txt.gz#_2018-02-08_05_02_37_258609 [2] https://review.openstack.org/542111 2018-02-08 3:39 GMT+08:00 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 a separate repository for all OpenStack plugins. > To minimize work across all projects which have Rally job, we decided to > pause working on ZuulV3 until the split will be finished. > As for estimates, I'm planning to make the final release before splitting > today or tomorrow. As soon as new release will be ready, we will start > working on splitting and CI as well. > > Thanks for the patient and for using Rally! > > 2018-02-07 10:13 GMT+02:00 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 to rally team for all these will be, do we still need this >> job? and how you guys think about if we put that into rally? >> >> [1] https://github.com/openstack-infra/project-config/blob/ >> master/zuul.d/projects.yaml#L6979 >> [2] https://review.openstack.org/#/c/509141 >> -- >> May The Force of OpenStack Be With You, >> >> *Rico Lin*irc: ricolin >> >> >> >> __ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib >> e >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > > -- > Best regards, > Andrey Kurilin. > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [heat][rally] What should we do with legacy-rally-dsvm-fakevirt-heat
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 a separate repository for all OpenStack plugins. To minimize work across all projects which have Rally job, we decided to pause working on ZuulV3 until the split will be finished. As for estimates, I'm planning to make the final release before splitting today or tomorrow. As soon as new release will be ready, we will start working on splitting and CI as well. Thanks for the patient and for using Rally! 2018-02-07 10:13 GMT+02:00 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 to rally team for all these will be, do we still need this > job? and how you guys think about if we put that into rally? > > [1] https://github.com/openstack-infra/project-config/blob/master/zuul.d/ > projects.yaml#L6979 > [2] https://review.openstack.org/#/c/509141 > -- > May The Force of OpenStack Be With You, > > *Rico Lin*irc: ricolin > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Best regards, Andrey Kurilin. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [heat][rally] What should we do with legacy-rally-dsvm-fakevirt-heat
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 to rally team for all these will be, do we still need this job? and how you guys think about if we put that into rally? [1] https://github.com/openstack-infra/project-config/blob/master/zuul.d/projects.yaml#L6979 [2] https://review.openstack.org/#/c/509141 -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
