Note: I am proposing in the next Ironic meeting (
https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting )
that we move forward on removing the tempest plugin code from
openstack/ironic and openstack/ironic-inspector. It will have been over
three weeks since the initial email in
mailto: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
ome 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
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<mai
On Mon, Dec 18, 2017 at 11:29 PM, 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
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 01:37:13PM -0700, Julia Kr
On Mon, Dec 18, 2017 at 01:37:13PM -0700, Julia Kreger wrote:
> > And actually I almost think the holiday time is the best time since the
> > fewest number of people are going to care. But maybe I'm wrong. I do wonder
> > if nobody is around to watch a 3rd Party CI for two weeks, how likely is it
> And actually I almost think the holiday time is the best time since the
> fewest number of people are going to care. But maybe I'm wrong. I do wonder
> if nobody is around to watch a 3rd Party CI for two weeks, how likely is it
> to still be working when they get back?
>
> I'm not vehemently
weeks.
>
> Thanks,
>
> Arkady
>
>
>
> *From:* John Villalovos [mailto:openstack@sodarock.com]
> *Sent:* Monday, December 18, 2017 10:59 AM
> *To:* openstack-dev <openstack-dev@lists.openstack.org>
> *Subject:* Re: [openstack-dev] [Ironic] Removal of tem
@sodarock.com]
Sent: Monday, December 18, 2017 10:59 AM
To: openstack-dev <openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [Ironic] Removal of tempest plugin code from
openstack/ironic & openstack/ironic-inspector
To hopefully make things more clear.
All of the iron
To hopefully make things more clear.
All of the ironic related projects that were using the tempest-plugin code
from either openstack/ironic or openstack/ironic-inspector have been
migrated to use the tempest-plugin code in openstack/ironic-tempest-plugin.
This includes master and stable
On Fri, Dec 15, 2017 at 7:27 AM, John Villalovos wrote:
> I wanted to send out a note to any 3rd Party CI or other users of the
> tempest plugin code inside either openstack/ironic or
> openstack/ironic-inspector. That code has been migrated to the
>
I wanted to send out a note to any 3rd Party CI or other users of the
tempest plugin code inside either openstack/ironic or
openstack/ironic-inspector. That code has been migrated to the
openstack/ironic-inspector-plugin repository. We have been busily (
13 matches
Mail list logo