Open Stack

On Thu, Nov 01, 2018 at 03:08:09PM +0000, Jeremy Stanley wrote:
> On 2018-11-01 09:27:03 -0400 (-0400), Doug Hellmann wrote:
> > Jeremy Stanley <fungi at yuggoth.org> writes:
> > 
> > > On 2018-11-01 08:52:05 -0400 (-0400), Doug Hellmann wrote:
> > > [...]
> > >> Did I miss any options or issues with this approach?
> > >
> > > https://review.openstack.org/578557
> > 
> > How high of a priority is rolling that feature out? It does seem to
> > eliminate this particular issue (even the edge cases described in the
> > commit message shouldn't affect us based on our typical practices), but
> > until we have one of the two changes in place we're going to have this
> > issue with every release we tag.
> 
> It was written as a potential solution to this problem back when we
> first discussed it in June, but at the time we thought it might be
> solvable via job configuration with minimal inconvenience so that
> feature was put on hold as a fallback option in case we ended up
> needing it. I expect since it's already seen some review and is
> passing tests it could probably be picked back up fairly quickly now
> that alternative solutions have proven more complex than originally
> envisioned.
> -- 
> Jeremy Stanley

Doug's option 3 made sense to me as a way to address this for now. I could see
doing that for the time being, but if this is coming in the near future, we can
wait and go with it as option 4.

Sean