Feature Overview

The AI-in-a-Box platform requires robust observability that supports multi-tenant usage for AI cluster application end users, tenants, and service providers.  Because tenants and end users may belong to different organizations, the observability solution must also enforce fine-grained access control to keep each tenant’s observable cluster information accessible only to the service provider and the tenant owners and end users associated with each individual cluster.  

While ACM currently provides cluster-wide metrics, it does not offer fine-grained access control for metrics from different clusters or different projects (namespaces) within clusters

Goals

This requires three types of observability functions.

• Cluster-level observability (service provider visibility across clusters)
• Single-cluster observability (restricted visibility for a specific cluster owner/administrators)
• Project-level end user observability (observability for project information within a specific namespace of a specific cluster)

Requirements [TBD]

This Section: A list of specific needs or objectives that a Feature must
deliver to satisfy the Feature.. Some requirements will be flagged as MVP.
If an MVP gets shifted, the feature shifts. If a non MVP requirement slips,
it does not shift the feature.

(Optional) Use Cases [TBD]

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 a 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)?

CC bweidenb@redhat.com mhrivnak@redhat.com christophertate tzumainn@redhat.com