...
4.2 ONAP Architecture Principles: Business Imperatives (i.e. User Community Requirements)
4.2.1 Policy Driven Automation
...
:
ONAP should support high levels of automation at every phase of lifecycle management – e.g. onboard, design, deployment, instantiation, upgrade, monitoring, management, to end of life cycle. These automation should be policy driven, allowing users to dynamically control automation behavior via policy changes without recompiling ONAP code.
...
| Gliffy | ||||
|---|---|---|---|---|
|