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

Red Hat Insights Integration via insights-operator for OpenStack services on OpenShift

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • None
    • None
    • None
    • Not Selected
    • False
    • False
    • Hide

      None

      Show
      None
    • 0
    • 0
    • 0% To Do, 100% In Progress, 0% Done

      Feature Overview 

      Red Hat OpenStack Services on OpenShift (RHOSO) integration with Red Hat Insights Operator will provide automated, secure collection of OpenStack cluster usage data from customer environments. This Feature enables proactive problem identification and enhanced feature usage insights, significantly aiding in customer support and product planning. Customers benefit from optimized operations through personalized recommendations and proactive insights on their OpenStack configurations.

      Goals

      • Enable automated and anonymized data collection from customer RHOSO environments.
      • Provide insights into feature adoption and usage trends within RHOSO.
      • Support proactive identification of configuration issues and recommendations for optimization.

      Who benefits from this Feature, and how?

      • Customers benefit from proactive issue detection, improved system health, and tailored recommendations.
      • Product and support teams gain valuable insights into customer environments, improving the quality of support and strategic product decisions.

      Requirements

      Requirements Notes isMvp?
      Integrate RHOSO CRs with Insights Operator Collect data from OpenstackControlPlane, OpenstackDataPlaneDeployment, and OpenstackDataPlaneNodeSet CRs. Yes
      Anonymize sensitive data IP addresses and other sensitive information must be anonymized before transmission. Yes
      Unique OpenStack cluster identification Generate unique IDs for each OpenStack cluster separate from OpenShift clusterID. Yes
      Support multiple OpenStack clusters per OCP Allow data collection from multiple OpenStack clusters on a single OpenShift deployment. Yes
      Data aggregation and transmission Data collected must be aggregated, anonymized, and transmitted securely and separately per OpenStack cluster. Yes
           

       

      Done - Acceptance Criteria:

      • RHOSO Insights integration is operational, with data from specified CRs collected, anonymized, and securely transmitted.
      • A unique, consistent ID scheme for OpenStack clusters is in place and operational.
      • Successfully validated multiple OpenStack clusters data handling within a single OpenShift environment.
      • No personally identifiable or sensitive information is transmitted.

      Use Cases:

      • Administrator doesn't opt out for Insights integration for RHOSO in connected environments.
      • Operator collects anonymized data daily from RHOSO CRs.
      • Insights Engine processes data and provides visibility on usage, recommendations, and proactive alerts to the customer portal.

      Out of Scope:

      • Real-time monitoring or continuous streaming of data.
      • Integration with third-party analytics platforms.

      Documentation Considerations __(Initial completion while in Refinement status):

      Instructions for reviewing insights and recommendations through the customer portal.

      Questions to Answer __(Initial completion while in Refinement status):
      Include a list of refinement / architectural questions that may need to be answered before coding can begin.
      <your text here>

      Background and Strategic Fit:

      This Feature aligns with Red Hat’s strategic initiative to leverage data-driven insights for product improvement and proactive customer support. It extends the current Insights capabilities of OpenShift to specifically address OpenStack environments running on OpenShift.

      Customer Considerations __(Initial completion while in Refinement status):

      • Transparency on data collected, emphasizing anonymity and security.
      • Minimal performance impact during data collection.
      • Opt-out feature, clearly communicated.

      Team Sign Off (Completion while in Planning status)

      • All required Epics (known at the time) are linked to the this Feature
      • All required Stories, Tasks (known at the time) for the most immediate Epics have been created and estimated
      • Add - Reviewers name, Team Name
      • Acceptance == Feature as “Ready” - well understood and scope is clear - Acceptance Criteria (scope) is elaborated, well defined, and understood
      • Note: Only set FixVersion/s: on a Feature if the delivery team agrees they have the capacity and have committed that capability for that milestone
      Reviewed By Team Name Accepted Notes
             
             
             
             

       

              skaplons@redhat.com Slawomir Kaplonski
              pnavarro@redhat.com Pedro Navarro Perez
              Haresh Khandelwal
              rhos-dfg-networking-squad-neutron
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: