Dear Bryan, In https://wiki.opnfv.org/display/AUTO/Auto+Use+Cases
What kind of telemetry are you interested in and at what layers? E.g. Physical? Virtual? Security? Edge Cloud Section Description Title Service Provider's Management of Edge Cloud Primary Actor (s) 1. Service Provider 2. Cloud control plane and automation platform Preconditions 1. hardware environment in which Edge cloud may be deployed 2. a Edge cloud has been deployed and is ready for operation 3. ONAP has been deployed onto a cloud and is interfaced (ie provisioned for API access) to the Edge cloud Post Conditions Main Success Scenario (s) * lifecycle management - stop, stop, scale (dependent upon telemetry) * recovering from faults (detect, determine appropriate response, act); ie exercise closed-loop policy engine in ONAP * verify mechanics of control plane interaction * collection of telemetry for machine learning JIRA Traceability ID Auto-UC-01 Exception Scenarios Description As an NFV edge service provider, I need an edge platform that is both efficient (in terms of control/automation overhead) and largely autonomous for VNFs once launched. Thus ability to deploy the minimal subset of ONAP functions needed for autonomy under typical VNF lifecycle events, e.g. start, stop, scale, recover from faults, collect/process telemetry, ... Alternate Scenarios Thank you, Tina Tsou Enterprise Architect Arm [email protected]<mailto:[email protected]> +1 (408)931-3833 IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
_______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
