yahoo-eng-team team mailing list archive

[Matt Thompson <1488021@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

In my AIO test instance, I have just upgraded neutron from
7.0.0.0b3.dev200 to 7.0.0.0b3.dev356.  If I run 'neutron-db-manage
current', I see:

root@aio_neutron_server_container-47ef3931:~# neutron-db-manage current 2>/dev/null
  Running current for neutron ...
2a16083502f3 (head)
1b4c6e320f79
  OK
root@aio_neutron_server_container-47ef3931:~#

Based on this, I can see that one branch is not on head, and that
migrations will need to be applied to that specific branch.

In our deployment tooling, what we currently do after neutron has
upgraded is run 'neutron-db-manage upgrade liberty_expand@head' while
neutron-server is up and running.  We then proceed to shut down all
neutron-server instances and run 'neutron-db-manage upgrade
liberty_contract@head'.  Once that has completed, we start up neutron-
server again.

What would be ideal is if the 'neutron-db-manage current' output also
indicated which alembic branch the migration ID was referring  to.  That
way, we could determine if we're on head for a given branch, and if not
proceed with applying the migrations for that specific branch.  For the
liberty_expand@head branch, this is a non-issue since these migrations
can run with neutron-server up and responding.  However, if we can avoid
having to shut down neutron-server unnecessarily when there are no
pending  liberty_contract@head migrations, this would give us a much
smoother deployment experience.

Please give me a shout if I can provide any further information.

Thanks,
Matt

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1488021

Title:
  Display alembic branch in neutron-db-manage current

Status in neutron:
  New

Bug description:
  In my AIO test instance, I have just upgraded neutron from
  7.0.0.0b3.dev200 to 7.0.0.0b3.dev356.  If I run 'neutron-db-manage
  current', I see:

  root@aio_neutron_server_container-47ef3931:~# neutron-db-manage current 2>/dev/null
    Running current for neutron ...
  2a16083502f3 (head)
  1b4c6e320f79
    OK
  root@aio_neutron_server_container-47ef3931:~#

  Based on this, I can see that one branch is not on head, and that
  migrations will need to be applied to that specific branch.

  In our deployment tooling, what we currently do after neutron has
  upgraded is run 'neutron-db-manage upgrade liberty_expand@head' while
  neutron-server is up and running.  We then proceed to shut down all
  neutron-server instances and run 'neutron-db-manage upgrade
  liberty_contract@head'.  Once that has completed, we start up neutron-
  server again.

  What would be ideal is if the 'neutron-db-manage current' output also
  indicated which alembic branch the migration ID was referring  to.
  That way, we could determine if we're on head for a given branch, and
  if not proceed with applying the migrations for that specific branch.
  For the liberty_expand@head branch, this is a non-issue since these
  migrations can run with neutron-server up and responding.  However, if
  we can avoid having to shut down neutron-server unnecessarily when
  there are no pending  liberty_contract@head migrations, this would
  give us a much smoother deployment experience.

  Please give me a shout if I can provide any further information.

  Thanks,
  Matt

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1488021/+subscriptions