Project Name:
- Proposed name for the project: Usecase UI
- Proposed name for the repository: usecase-ui
Project description:
- Usecase UI is the ONAP subsystem that provides Graphical User Interface (GUI) for operators and end-users from the point of view of use cases. As a whole project, Usecase UI requiremetns not only includes service design and run-time management (resource, performance, fault, security, configuration, etc.) for operators, but also includes self-service management for end-users.
- This project targets identifying all GUI requirements which operators and end-users need ONAP to support, coordinating GUI parts of each ONAP subsystem, filling the gaps for improving GUI functionalities for use cases. All GUI functionalities of ONAP system can be well showed to satisfy the requirements from different customers.
Scope:
- The Designer Role:
- Service design (implemented by SDC)
- VNF onboarding (implemented by SDC)
- Policy design (implemented by Policy Framework)
- Closed Loop design (implemented by CLAMP)
- The Operator Role:
- Service LCM that complex services can be simply done by one click (implemented by this project)
- Inventory for services and resources (implemented by A&AI)
- Monitor system alarms (implemented by this project)
- Alarm correlation (implemented by Holmes)
- Show system performance (implemented by this project)
- The User Role: (Implemented by this project)
- Provide model-based service instance orchestration interface
- Consume and interpret standard ONAP 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 elements
Architecture Alignment:
- How does this project fit into the rest of the ONAP Architecture?
- Usecase UI is one of the key functional GUI blocks in the ONAP Architecture
- What other ONAP projects does this project depend on?
- Portal Platform
- DCAE
- A&AI
- SO
- SDC
- Policy Framework
- CLAMP
- How does this align with external standards/specifications?
- Usecase UI will provide an HTTP(s) web GUI and will interface with other systems using standard protocols like REST.
- Are there dependencies with other open source projects?
- N/A
Resources:
- Primary Contact Person: Tao Shen (China Mobile), Amichai Hemli (AT&T)
Names, gerrit IDs, and company affiliations of the committers
Name Gerrit ID Company Email Time Zone Tao Shen shentao999 CMCC shentao@chinamobile.com Beijing, China. UTC +8 Amichai Hemli ahemli AT&T ah0398@intl.att.com Huabing Zhao HuabingZhao ZTE zhao.huabing@zte.com.cn Beijing, China. UTC +8 Xin Jin jinxin1983 Huawei saw.jin@huawei.com Beijing, China. UTC +8 Names and affiliations of any other contributors
Name Gerrit ID Company Email Time Zone Jimmy Forsyth AT&T jf2512@att.com Yoav Kluger Amdocs yoav.kluger@amdocs.com Manoop Talasila AT&T talasila@research.att.com Karthik Arun IBM Middletown, USA. EDT Hu Dong donghu1102 RaiseCom donghu@raisecom.com Beijing, China. UTC +8 - Project Roles (include RACI chart, if applicable)
Other Information:
- link to seed code (if applicable)
- Vendor Neutral
- The project is vendor neutral.
- 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: usecase-ui
- JIRA project prefix: usecase-ui
Repo name: usecase-ui
Lifecycle State:
Primary Contact: Tao Shen (China Mobile), Amichai Hemli (AT&T)
Project Lead: Tao Shen (China Mobile), Amichai Hemli (AT&T)
mailing list tag [Should match Jira Project Prefix]
Committers: please refer to the above table
*Link to TSC approval:
Link to approval of additional submitters: