-
Epic
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
None
-
maestro_milestone_1
-
False
-
None
-
False
-
-
Not Selected
-
To Do
-
0% To Do, 0% In Progress, 100% Done
Value Statement
- Share component with OCM & SD for scale and cost cheap requirements
- Address the hyperscale requirements in Telco / Edge area.
Definition of Done for Engineering Story Owner (Checklist)
- Support event driver for work-agent as a prototype (Consumer)
- Take ManifestworkReplicsSet as an example to produce events (Producer)
- Event API Spec Design document
- MQTT lifecycle management, need to consider Authu + Authz / maintenance/ upgrade
- DB + non-kube rest API for user
================== (M2)
1. how to do e2e tests
resource <--cloudevent--> maestro <--cloudevents--> work-agent
2. failure cases
Development Complete
- The code is complete.
- Functionality is working.
- Any required downstream Docker file changes are made.
Tests Automated
- [ ] Unit/function tests have been automated and incorporated into the
build. - [ ] 100% automated unit/function test coverage for new or changed APIs.
Secure Design
- [ ] Security has been assessed and incorporated into your threat model.
Multidisciplinary Teams Readiness
- [ ] Create an informative documentation issue using the [Customer
Portal_doc_issue template](
https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
and ensure doc acceptance criteria is met. Link the development issue to
the doc issue. - [ ] Provide input to the QE team, and ensure QE acceptance criteria
(established between story owner and QE focal) are met.
Support Readiness
- [ ] The must-gather script has been updated.