You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

Desired Outcome

  • Enable use of TOSCA as the "normative", supplier and operator neutral way to package and model/describe network service and functions in ONAP.
  • Enable specification of deployment targets, other then virtual machines (e.g. K8S, Azure, etc.).
  • Do not preclude use of alternative packaging and modeling approaches.

Lifecycle Stages

  • On-boarding Time
  • Design Time
  • Instantiation Time
  • Operation Time

Contributions...

No files shared here yet.

  • No labels