Uploaded image for project: 'OpenStack Strategy'
  1. OpenStack Strategy
  2. RHOSSTRAT-901

Allow distribution of Flamingo version of Manila in RHOSO-18

XMLWordPrintable

    • Icon: Initiative Initiative
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • None
    • None
    • Not Selected
    • False
    • False
    • Hide

      None

      Show
      None
    • 0
    • 0
    • 33% To Do, 67% In Progress, 0% Done

      Initiative Overview (mandatory - Complete while in New status)
      Due to customer desire to adopt features that are only available in recent versions of OpenStack, we want to explore available options and the feasibility of shipping misaligned versions of OpenStack components during the lifespan of single product major

       

      For example

      • deploy Manila from the Flamingo release branch in RHOSO18 (where other components are at the Antelope release)
      • bump Manila from Antelope to Flamingo in RHOSO18
      • rebase RHOSO19 components from Epoxy to Gazpacho to shorten the features time to market

       

      Goals (mandatory - Complete while in New status)
      Allow use of recent OpenStack features in stable RHOSO major versions

       

      Done - Acceptance Criteria (mandatory - Complete while in Refinement status):

      We have the ability to distribute a fully working OpenStack environment where the various components are not all at the same release level

       

      Out of Scope  (Initial completion while in Refinement status):

      We do not intend to support nor distribute multiple versions of the same OpenStack component in a single product release

              gfidente-rh Giulio Fidente
              gfidente-rh Giulio Fidente
              rhos-storage-manila
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: