Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-1815

support for upgrading schemas without complete reload of data (DB migrations) - PoC + devops guide

    XMLWordPrintable

    Details

    • Template:
    • Back End Estimate:
      XXL < 30 days
    • Estimation Notes and Assumptions:
      XXL is the largest available. This item is likely larger.
    • Development Team:
      Core: Platform
    • Calculated Total Rank:
      65
    • PO Rank:
      9
    • Rank: Chicago (MVP Sum 2020):
      R1
    • Rank: Duke (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R1
    • Rank: GBV (MVP Sum 2020):
      R1
    • Rank: Lehigh (MVP Summer 2020):
      R1
    • Rank: Leipzig (ERM Aut 2019):
      R2
    • Rank: TAMU (MVP Jan 2021):
      R1
    • Rank: U of AL (MVP Oct 2020):
      R2

      Description

      (Note: Q3 work include a PoC and initial devops migration guide, rollout and additional Platform functionality is postponed to Q4)

      Currently in FOLIO, if there is a change to the schema used by a storage module, there is no upgrade path for the data already in the module. As we now have test deployments and are trying to move towards production deployments, this will be critical for ongoing testing and operations.

      This lack has been identified as Technical Debt by the Technical Council.

      Some solution for schema upgrades and migrating data will be needed for all storage modules. The solution could include multiple components. For example, maybe one part of the solution is to include data updates the the Definition of Done for each development team, and maybe there's something that could be added to the core to make it easier to create these migrations. That's just for illustration. The important thing is that FOLIO needs a way to address address schema updates and corresponding data changes that can be consistent across modules.

      SysOps identified these sub-issues:

      • Ability to roll back an upgrade
      • Consider the wider scope of how upgrades will occur in FOLIO systems
      • Downtime considerations, can we limit or have no downtime for an application?
      • May need additional work in modules/Okapi/RMB
      • Would want schema upgrade included in Definition of Done

      FOLIO June meeting TC tech debt slides:
      https://docs.google.com/presentation/d/1Cz5-xhvMdCdm7SXYLhIQE8KV9YIsQW1faNUIWmMANx8

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                Taras_Spashchenko Taras Spashchenko
                Reporter:
                tod Tod Olson
                Back End Estimator:
                Jakub Skoczen Jakub Skoczen
                Votes:
                0 Vote for this issue
                Watchers:
                12 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases