-
Feature
-
Resolution: Done
-
Critical
-
None
-
False
-
None
-
False
-
Not Selected
-
0% To Do, 0% In Progress, 100% Done
Feature Overview
Maestro is resources orchestrator for Kubernetes. We want to leverage it to solve the ACM potential performance issue. The Maestro includes
- Maestro server: provide restful and gRPC services.
- Middleware: MQTT and Postgres. MQTT is a transport layer to transfer cloudevents between server and agent. Postgres is used to persist data.
- Maestro Agent: wire to the MQTT and receive the cloudevents message.
In ACM, we want to deploy the Maestro as a MCE addon. Once maestro addon enables, you can choose to use maestro way to transfer the data between hub and managed clusters.
Goals
This Section: Provide high-level goal statement, providing user context
and expected user outcome(s) for this feature
- Deploy maestro as a MCE addon on OpenShift (bweidenb@redhat.com jpacker@redhat.com are you OK to limit to OpenShift?)
-
- Deploy maestro server and middleware into the hub cluster and deploy maestro agent into the managed clusters.
- Middleware includes Postgres and AMQ Streams for production
Introduce a field in MCE calls `workloadDrive`. the values can be kafka and kube. default value is kube.- Make the manifestreplicaset controller works fine with kafka as workloadDrive.
Requirements
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.
| 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 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)?