2019-07-10 Control Loop Sub Committee Weekly Meeting
Discussion items
Duration | Agenda Item | Requested by | Notes / Links |
---|---|---|---|
START RECORDING | |||
| Discussion on Frankfurt planning steps and review each requirement. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ATTENDEES
Please fill in if i missed you.
NOTES
Frankfurt Planning TODOS:
Gather Requirements | Gather inputs from all the Subcommittees, EUAG, etc + Submit new project proposal | |||||||
| Identify Req. Owners and Define functional requirements, use case and non functional reqs - wiki page | |||||||
| Validate with Architecture Team new project proposal |
|
|
| ||||
| Validate with Architecture Team new requirements |
|
|
| ||||
Refine Requirements | Req. Owner will consolidate company engagement (Dev, test) |
|
| |||||
| Write next level of details and enter inputs in JIRA not PTL but Req. Owner(s) |
| ||||||
| Write next level of details and enter inputs in JIRA not PTL but Req. Owner(s) |
| ||||||
| Initial TSC Prioritization |
|
|
|
|
| ||
Prioritize | Initiate discussions with PTL (including Integration team) by creating Tasks/Sub-Tasks | |||||||
Finalize the scope | Initiate discussions with PTL (including Integration team) by creating Tasks/Sub-Tasks | |||||||
| TSC Final Prioritization |
|
|
|
|
|
| |
| Freeze Content + M1 reviewed with TSC Milestone Owners & ONAP Release Manager |
@Scott Blandford will schedule meeting with @Ofir Sonsino and @Vijay Kumar to clarify self-serve control loops.
@Pamela Dragosh - will be working with @John Keeney (Ericsson EST) and @Ram Krishna Verma and @Rashmi Pujar for the Operational Policy Type definition.
@Pamela Dragosh and @Vijay Kumar - schedule meeting with Alex regarding PEP Registration/Update strategy.
@Rashmi Pujar - work on the impacts, functional requirements for vFirewall. @Marco Platania can help.
RECORDING