On Wed, Dec 21, 2016 at 5:06 PM, Ben Pfaff <b...@ovn.org> wrote: > On Wed, Dec 07, 2016 at 02:28:13PM -0500, Russell Bryant wrote: > > Signed-off-by: Russell Bryant <russ...@ovn.org> > > This procedure isn't what I expected. It recommends: > > 1. Upgrade SB/NB databases and northd. > 2. Upgrade ovn-controller. > 3. Upgrade integration. > > I think that this is likely to cause problems in the common case, > because the new northd is likely to try to start using features that are > not yet available on the hypervisors, such as new logical match fields > and actions. > > I expected: > > 1. Upgrade ovn-controller. > 2. Upgrade SB/NB databases and northd. > 3. Upgrade integration. > > (I don't think that it matters when the databases are upgraded, though, > as long as they're upgraded before northd.) >
Thanks for the feedback! There's a possible problem in this case, too. ovn-controller could try to start using new fields in the southbound database that aren't there yet. Maybe it should be: 1. Upgrade SB/NB databases. 2. Upgrade ovn-controller. 3. Upgrade ovn-northd. 4. Upgrade integration. -- Russell Bryant _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev