Dell - Internal Use - Confidential
Dell Ironic Ci is failing on this patch because of that. With holidays and many 
on vacation, would appreciate some additional time to make the switch.
Thanks
Rajini

From: Ruby Loo [mailto:opensr...@gmail.com]
Sent: Tuesday, December 19, 2017 8:48 AM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [Ironic] Removal of tempest plugin code from 
openstack/ironic & openstack/ironic-inspector



On Mon, Dec 18, 2017 at 11:29 PM, 
<arkady.kanev...@dell.com<mailto:arkady.kanev...@dell.com>> wrote:
Thanks for response.
My recommendation is:
1. only allow patches into openstack/ironic-tempest-plugin
2. Give Ironic CI owners time period (3 weeks?) to switch their setup to only 
use openstack/ironic-tempest-plugin and not master and report back to Ironic CI 
team if it works for them. If yes, go ahead and switch if not, report back.
3. At the end of that time, if majority of Ironic CI site complete their  
transition to ironic-tempest-plugin we switch.

Thanks,
Arkady

I think this is reasonable. I cringe at knowingly doing something that will 
most likely break the third party CI when people are away and cannot address 
it. Also, apart from the danger that the third party CIs are running old 
versions of the tempest plugins (I doubt that we'll be doing major overhaul of 
that in the next 2+ weeks), the reason we have 3rd party CI is to make sure 
patches work against those HW. Having most or all of them being unavailable due 
to this breakage means that there won't be any feedback that someone's code 
would have broken 3rd party CI outside of the tempest changes.

John, don't you have a patch that removes the tempest plugin from master? Do 
most/all of the 3rd party CIs fail due to that? (Or is it not as simple as 
that?) Ah, yes, https://review.openstack.org/#/c/527733/ shows that all the 3rd 
party CI fail (although I don't know if it is due to that patch or if they were 
already failing prior to that).

--ruby
__________________________________________________________________________
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

Reply via email to