Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Reverted from v. 17

...

Use Cases

vFW/vDNS/vCPE/VOLTE /CCVPN - Test only support

Minimum Viable Product

...

Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.

...

List the API this project is expecting from other projects.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.

Prior to the delivery date, it is a good practice to organize an API review with the API consumers.

...

API this project is delivering to other projects.

API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
Policy Client APIThis API is used by other ONAP components to create, update and delete policy(s).Beijing version - no changesn/aPolicy API
Policy Query APIThis API is used by other ONAP components responsible for enforcing policy during runtime.Beijing version - no changesn/aPolicy API
Policy Lifecycle APIThe new Policy Lifecycle API description, documentation, models, etc.API will be designed and documented over the course of Casablanca. We do not expect our clients to be able to utilize this API in Casablanca.End of CasablancaTBD
  • Third Party Products Dependencies

...

Risk identifiedMitigation PlanContingency Plan
Not enough resources to meet all the functional requirements.All Epics are assessed a priority.
Need the SO API defined by a reasonable timeframe for implementation to happenWe will use the current SO RESTful API until the new API is in place.
  • Resources

Fill out the Resources Committed to the Release centralized page.

  • Release Milestone

...