Uploaded image for project: 'OpenShift Top Level Product Strategy'
  1. OpenShift Top Level Product Strategy
  2. OCPPLAN-9743

Onboarding New Providers/Platforms (Phase 1)

    XMLWordPrintable

Details

    • False
    • False
    • ?
    • No
    • ?
    • ?
    • OCPSTRAT-10Install and update OpenShift on Infrastructure Providers
    • ?
    • 100
    • 100% 100%

    Description

      OCP/Telco Definition of Done
      Feature Template descriptions and documentation.
      <--- Cut-n-Paste the entire contents of this description into your new Feature --->
      <--- Remove the descriptive text as appropriate --->

      Feature Overview

      • As RH OpenShift Product Owners, we want to enable new providers/platforms/service with varying levels of capabilities and integration with minimal reliance on OpenShift Engineering.
      • As a new provider/platform partner, I want to enable my solution (hardware and/or software) with OpenShift with minimal effort.

       

      Problem

      • It is currently challenging for us to enable new platforms / providers without taking the heavy burden on doing the platform specific development ourselves.

      Goals

      • We want to enable the long-tail new platforms/providers to expand our reach into new markets and/or support new use cases.
      • We want to remove strict dependencies we have on Engineering teams to review, support and test new providers.
      • We want to lower the effort required for onboarding new platforms/providers.
      • We want to enable new platform/providers to self-certify.
      • We want to define tiered model for provider/platform integration that delineates ownership and responsibilities throughout new provider/platform development lifecycle and support model.
      • We want to reduce time to onboard new provider/platform – ideally to a single release.
      • We want to maintain consistent customer experience across all providers/platforms.

      Requirements

      • Step-by-step guide on how to add a new platform/provider for each tier
      • Certification tool for partner to self-certify
      • Certification tool results for (at least) each Y/minor release submitted by partner to Red Hat for acknowledgement
      • DCI program to enable partners to run CI with OpenShift on their platform
      • Well documented, accessible, and up-to-date test suites for providing the test coverage of the partner
      • CI includes upgrade testing of OpenShift with partner's components
      • Partner component upgrade failure should not block OpenShift upgrade
      • Partner code is available in repositories in the openshift org on github with an open source license compatible with OpenShift

       

      Requirement Notes isMvp?
      CI - MUST be running successfully with test automation This is a requirement for ALL features. YES
      Release Technical Enablement Provide necessary release enablement details and documents. YES

      (Optional) Use Cases

      This Section:

      • Main success scenarios - high-level user stories
      • Alternate flow/scenarios - high-level user stories
      • ...

      Questions to answer…

      • ...

      Out of Scope

      • …

      Background, and strategic fit

      This Section: What does the person writing code, testing, documenting need to know? What context can be provided to frame this feature.

      Assumptions

      • ...

      Customer Considerations

      • ...

      Documentation Considerations

      Questions to be addressed:

      • What educational or reference material (docs) is required to support this product feature? For users/admins? Other functions (security officers, etc)?
      • Does this feature have doc impact?
      • New Content, Updates to existing content, Release Note, or No Doc Impact
      • If unsure and no Technical Writer is available, please contact Content Strategy.
      • What concepts do customers need to understand to be successful in [action]?
      • How do we expect customers will use the feature? For what purpose(s)?
      • What reference material might a customer want/need to complete [action]?
      • Is there source material that can be used as reference for the Technical Writer in writing the content? If yes, please link if available.
      • What is the doc impact (New Content, Updates to existing content, or Release Note)?

       

      References

      Attachments

        Issue Links

          is related to

          Task - Represents a small unit of work that is not end-user facing. SPLAT-429 Create Provider Enablement Document

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OCPSTRAT-542 [Phase Next] Add a new platform type ("external") to identify clusters with non-integrated partner components enabled

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • New

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OCPSTRAT-339 [Phase 2] Add a new platform type ("external") to identify clusters with non-integrated partner components enabled

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Spike - Represents a research-related task. SPLAT-484 [Spike] Analyze OpenShift components for opportunities to increase pluggability

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OCPSTRAT-516 [Phase 1] Add a new platform type ("external") to identify clusters with non-integrated partner components enabled

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          relates to

          Task - Represents a small unit of work that is not end-user facing. SPLAT-438 Cloud onboarding: Information Gather document

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          split to

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OCPSTRAT-1136 Onboarding New Providers/Platforms (Phase 4)

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • New

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OCPSTRAT-343 Onboarding New Providers/Platforms (Phase 2)

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OCPSTRAT-140 [Docs] Onboarding New Providers/Platforms (Phase 3)

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          links to

          GitHub openshift/enhancements#1234: New "External" PlatformType addition proposal

          Activity

            People

              julim Ju Lim
              julim Ju Lim
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: