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

Compare with Current View Page History

« Previous Version 3 Next »

Project Name:

  • Proposed name for the project: Usecase UI
  • Proposed name for the repository: usecase-ui

Project description:

  • Usecase UI?ONAP????????????????????????????????Usecase UI???????????????????????????????????????
  • ?????????????????????ONAP??????????????ONAP????????????ONAP??????????????????ONAP?????????????????????

Scope:

  • The Designer Role:
    • Service design (SDC????)
    • VNF onboarding (SDC????)
    • Policy design (Policy Framework????)
  • The Operator Role:
    • Service LCM (VID?????)
    • Inventory for services and resources (AAI????)
    • Monitor (??DCAE?API?????????)
    • Alarm correlation (Holmes????)
    • Performance (??DCAE?API?????????)
  • The user Role:
    • Provide model-based vCPE instance orchestration interface.
    • Consume and interpret standard ONAP vCPE models.
    • Call service orchestration systems to configure services and VNFs in the core and at the edge.
    • Use inventory systesm to determine currently defined inventory for core and edge services.
    • End-user self-service management UI of provisioned vCPE elements.

Architecture Alignment:

  • How does this project fit into the rest of the ONAP Architecture?
    • Please Include architecture diagram if possible
    • What other ONAP projects does this project depend on?
  • How does this align with external standards/specifications?
    • APIs/Interfaces
    • Information/data models
  • Are there dependencies with other open source projects?
    • APIs/Interfaces
    • Integration Testing
    • etc.

Resources:

  • Primary Contact Person
  • Names, gerrit IDs, and company affiliations of the committers
  • Names and affiliations of any other contributors
  • Project Roles (include RACI chart, if applicable)

Other Information:

  • link to seed code (if applicable)
  • Vendor Neutral
    • if the proposal is coming from an existing proprietary codebase, have you ensured that all proprietary trademarks, logos, product names, etc., have been removed?
  • Meets Board policy (including IPR)

Use the above information to create a key project facts section on your project page

Key Project Facts

Project Name:

  • JIRA project name:
  • JIRA project prefix:

Repo name:
Lifecycle State:
Primary Contact:
Project Lead:
mailing list tag [Should match Jira Project Prefix] 
Committers:
foo@bar.com
baz@qux.com
*Link to TSC approval: 
Link to approval of additional submitters: 


  • No labels