[openstack-dev] [Neutron][TripleO] Neutron DB migrations best practice
Robert Collins
robertc at robertcollins.net
Wed Feb 26 00:42:31 UTC 2014
So we had this bug earlier in the week;
https://bugs.launchpad.net/tripleo/+bug/1283921
Table 'ovs_neutron.ml2_vlan_allocations' doesn't exist" in neutron-server.log
We fixed this by running neutron-db-migrate upgrade head... which we
figured out by googling and asking weird questions in
#openstack-neutron.
But what are we meant to do? Nova etc are dead easy: nova-manage db
sync every time the code changes, done.
Neutron seems to do something special and different here, and it's not
documented from an ops perspective AFAICT - so - please help, cluebats
needed!
-Rob
--
Robert Collins <rbtcollins at hp.com>
Distinguished Technologist
HP Converged Cloud
More information about the OpenStack-dev
mailing list