Open Stack

On Thu, Aug 30, 2018 at 6:34 PM, Eric Fried <openstack at fried.cc> wrote:

> Greetings.
>
> The captains of placement extraction have declared readiness to begin
> the process of seeding the new repository (once [1] has finished
> merging). As such, we are freezing development in the affected portions
> of the openstack/nova repository until this process is completed. We're
> relying on our active placement reviewers noticing any patches that
> touch these "affected portions" and, if that reviewer is not a nova
> core, bringing them to the attention of one, so we can put a -2 on it.
>
>
Apologies for having missed the large and wide discussions about placement
future in the past weeks. I was off so I just saw the consensus yesterday
evening my time.
Now that disclaimer is done, can I know the reasoning why we call the
freeze as of now and not waiting for either Stein-2 or Stein-3 ?

My main concern is that the reshaper series is still being reviewed for
Nova. Some other changes using Placement (like drivers using nested
Resource Providers and the likes) are also not yet implemented (or even be
uploaded) and I'm a bit afraid of us discovering yet another cross-services
problem (say with having two distinct computes having different versions)
that would make the fix more harder than just fixing directly.



> Once the extraction is complete [2], any such frozen patches should be
> abandoned and reproposed to the openstack/placement repository.
>
> Since there will be an interval during which placement code will exist
> in both repositories, but before $world has cut over to using
> openstack/placement, it is possible that some crucial fix will still
> need to be merged into the openstack/nova side. In this case, the fix
> must be proposed to *both* repositories, and the justification for its
> existence in openstack/nova made clear.
>
>
We surely can do such things for small fixes that don't impact a lot of
files. What I'm a bit afraid of is any large change that would get some
merge conflicts. Sure, we can find ways to fix it too, but again, why
shouldn't we just wait for Stein-2 ?

-Sylvain (yet again apologies for the late opinion).


For more details on the technical aspects of the extraction process,
> refer to this thread [3].
>
> For information on the procedural/governance process we will be
> following, see [4].
>
> Please let us know if you have any questions or concerns, either via
> this thread or in #openstack-placement.
>
> [1] https://review.openstack.org/#/c/597220/
> [2] meaning that we've merged the initial glut of patches necessary to
> repath everything and get tests passing
> [3]
> http://lists.openstack.org/pipermail/openstack-dev/2018-August/133781.html
> [4] https://docs.openstack.org/infra/manual/creators.html
>
> __________________________________________________________________________
> 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/20180831/5d720e72/attachment.html>