[DOCS-110] Add docs about ODL upgrade strategies Created: 03/Oct/18  Updated: 03/Oct/18

Status: Open
Project: docs
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Medium
Reporter: Daniel Farrell Assignee: Daniel Farrell
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

ODL has a somewhat complex upgrades story. We should create some specific docs dedicated to known/recommended upgrade strategies and their limitations. trade-offs and mitigations.

For example, topics to cover:

  • Data store upgrades being difficult at the moment, how to do yang schema migrations
  • Possible to work-around in some deployments by doing replay of events (say from OpenStack Neutron) to ODL. Can do OVS table updates in atomic batch, no dataplane downtime.
  • Additional suggestion is to deploy ODL in a container so can do update by swapping for newer-version container.
  • Configuration management tooling like ansible-opendaylight and puppet-opendaylight handle upgrades because they assume no yang model schema upgrades. This is normally okay, and almost certainly okay between SR releases.
  • RPM upgrade tests are WIP, link to patch.

Generated at Wed Feb 07 19:58:42 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.