[All][Neutron] Migrate old DB migration versions to init ops

Ruby Loo opensrloo at gmail.com
Thu Jul 2 13:37:00 UTC 2020


Hi,

On Tue, Jun 30, 2020 at 10:53 PM Akihiro Motoki <amotoki at gmail.com> wrote:

> On Tue, Jun 30, 2020 at 9:01 PM Lajos Katona <katonalala at gmail.com> wrote:
> >
> > Hi,
> > Simplification sounds good (I do not take into considerations like "no
> code fanatic movements" or similar).
> > How this could affect upgrade, I am sure there are deployments older
> than pike, and those at a point will
> > got for some newer version (I hope we can give them good answers for
> their problems as Openstack)
> >
> > What do you think about stadium projects? As those have much less
> activity (as mostly solve one rather specific problem),
> > and much less migration scripts shall we just "merge" those to init ops?
> > I checked quickly a few stadium project and only bgpvpn has newer
> migration scripts than pike.
>
> In my understanding, squashing migrations can be done repository by
> repository.
> A revision hash of each migration is not changed and head revisions
> are stored in the database per repository, so it should work.
> For initial deployments, neutron-db-manage runs all db migrations from
> the initial revision to a specified revision (release), so it has no
> problem.
> For upgrade scenarios, this change just means that we just dropped
> support upgrade from releases included in squashed migrations.
> For example, if we squash migrations up to rocky (and create
> rocky_initial migration) in the neutron repo, we no longer support db
> migration from releases before rocky. This would be the only
> difference I see.
>
<snip>

I wonder if this is acceptable (that an OpenStack service will not support
db migrations prior to rocky). What is (or is there?) OpenStack's stance
wrt support for upgrades?  We are using ocata and plan on upgrading but we
don't know when that might happen :-(

--ruby
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20200702/c0aa0630/attachment.html>


More information about the openstack-discuss mailing list