Uploaded image for project: 'Container / Cluster Management (XCM) Strategy'
  1. Container / Cluster Management (XCM) Strategy
  2. XCMSTRAT-294

OSD documentation clarity on cloud agnostic and cloud specific features

XMLWordPrintable

    • True
    • Hide

      Blocked in QE review.

      Show
      Blocked in QE review.
    • False
    • Red
    • 66
    • 66% 66%
    • Hide

      30-April

      • Blocked by QE review and still have some outstanding questions that have not been answered yet.

      19-March

      • Other projects got me sidetracked from getting as far on this and I'd like to be by this point. Project will probably not be complete until end of April, rather than beginning of April.

      14-Feb

      • Identified AWS-specific documentation in OSD. Created a Google Doc of all the locations that need to be modified to be either cloud-agnostic or add information about GCP.
      Show
      30-April Blocked by QE review and still have some outstanding questions that have not been answered yet. 19-March Other projects got me sidetracked from getting as far on this and I'd like to be by this point. Project will probably not be complete until end of April, rather than beginning of April. 14-Feb Identified AWS-specific documentation in OSD. Created a Google Doc of all the locations that need to be modified to be either cloud-agnostic or add information about GCP.
    • 8
    • CY24Q1
    • 0

      Feature Overview (aka. Goal Summary)  

      Due to the lack of focus on OSD, and GCP specifically, our OSD documentation has many instances where we list out AWS-specific examples for configuring various platform features. As we focus on OSD on GCP and make it available for customers to purchase through the GCP marketplace, we need to review our documentation to ensure that we are providing our customers with the correct and relevant information to deploy and manage our platform.

      We need to have clarity in our OSD documentation around which features are cloud provider agnostic and which features are cloud provider specific. In cases where the feature is not cloud provider agnostic, we should list examples of consuming a feature in AWS as well as GCP.

      Goals (aka. expected user outcomes)

      The goal is to provide customers with confirmation of the features that are applicable to OSD on the cloud provider of their choice.

      Requirements (aka. Acceptance Criteria):

      • Highlight features that are cloud provider specific and those are cloud provider agnostic
      • Provide examples AWS as well as GCP examples to configure a feature if it is cloud provider specific
      • Highlight OSD features that only apply to a particular cloud provider
         

            rhn-engineering-abhgupta Abhishek Gupta
            rhn-engineering-abhgupta Abhishek Gupta
            Akash Kanni, Shreyans Mulkutkar, Valeriia Shapoval, Yu Wang
            Elizabeth Hartman Elizabeth Hartman
            Yi Sun Yi Sun
            Elizabeth Hartman Elizabeth Hartman
            Not Needed Not Needed (Inactive)
            Needs Assignee Needs Assignee (Inactive)
            Abhishek Gupta Abhishek Gupta
            Not Needed Not Needed (Inactive)
            Taylor Fahlman Taylor Fahlman
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: