Open Stack

One issue is that development is going to move forward on
openstack/ironic-tempest-plugin. No new code will go into the tempest
plugin code in either openstack/ironic or openstack/ironic-inspector.

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 opposed to delaying, but somewhat opposed.

Thoughts?
John

On Mon, Dec 18, 2017 at 11:19 AM, <Arkady.Kanevsky at dell.com> wrote:

> John,
>
> Should we give all Ironic CI maintainers to do the migration before
> pulling the code from master?
>
> Especially that close to holiday season when a lot of folks are out.
>
> We want to avoid Ironic CI not being functional for several weeks.
>
> Thanks,
>
> Arkady
>
>
>
> *From:* John Villalovos [mailto:openstack.org at sodarock.com]
> *Sent:* Monday, December 18, 2017 10:59 AM
> *To:* openstack-dev <openstack-dev at 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 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 branches. Previously all branches (master
> and stable) were pulling from the master branch of openstack/ironic and/or
> openstack/ironic-inspector to get the tempest-plugin code. Now they all
> pull from the master branch of openstack/ironic-tempest-plugin. Note:
> openstack/ironic-tempest-plugin will NOT have any stable branches, only
> master.
>
> We will be removing all the tempest-plugin code from the master branch of
> openstack/ironic and openstack/ironic-inspector on Tuesday 19-Dec-2017. We
> will NOT be removing the tempest-plugin code from any stable branches. We
> (Ironic) didn't/don't use that code but since downstream consumers may we
> will leave it in place.
>
> Any 3rd Party CI that are testing using the tempest-plugin code pulled
> from master will need to update their CI to now use
> openstack/ironic-tempest-plugin
>
> Again we will be removing all the tempest-plugin code from the master
> branch of openstack/ironic and openstack/ironic-inspector on Tuesday
> 19-Dec-2017. If your CI depends on that code, please update to use the new
> openstack/ironic-tempest-plugin repository.
>
>
>
>
>
> On Mon, Dec 18, 2017 at 8:33 AM, John Villalovos <
> openstack.org at sodarock.com> wrote:
>
>
>
>
>
> On Fri, Dec 15, 2017 at 7:27 AM, John Villalovos <
> openstack.org at sodarock.com> 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
> openstack/ironic-inspector-plugin repository. We have been busily (
> https://review.openstack.org/#/q/topic:ironic-tempest-plugin ) migrating
> all of the projects to use this new repository.
>
> If you have a 3rd Party CI or something else that is depending on the
> tempest plugin code please migrate it to use openstack/ironic-tempest-
> plugin.
>
> We plan to remove the tempest plugin code on Tuesday 19-Dec-2017 from
> openstack/ironic and openstack/ironic-tempest-plugin. And then after that
> doing backports of those changes to the stable branches.
>
>
>
> After discussion on IRC in regards to back-porting to the stable branches.
> We will NOT backport the removal of the tempest plugin code as it could
> break distros and other consumers.
>
>
>
>
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20171218/bb44421d/attachment.html>