Project Name:
- Proposed name for the project: Usecase UI
- Proposed name for the repository: usecase-ui
Description
This project provides Graphical User Interface (GUI) to implement following use cases:
Scope of Usecase vCPE:
Portal/VID vCPE UI must provide model-based vCPE instance orchestration interface
The Portal/VID vCPE GUI will consume and interpret standard ONAP vCPE models
The Portal/VID vCPE GUI will call service orchestration systems to configure services and VNFs in the core and at the edge
- Service & VNF Lifecycle Management
- Instantiate
- Terminate
- Upgrade
- Downgrade
The Portal/VID vCPE GUI will use inventory systesm to determine currently defined inventory for core and edge services
End-user self-service management UI of provisioned vCPE elements
Scope of Usecase VoLTE:
Full and comprehensive usecase functions which includes, not limited to:
- Service Design
- LCM management (instantiate, terminate, scaling in/out)
- VNF management (upgrade, downgrade)
- VNF onboarding
- Performance monitoring and analysis
- Self-Service VNF Certification (VNF-SDK)
Architecture Alignment:
How does this project fit into the rest of the ONAP Architecture?
The Portal/VID vCPE UI sits between SDC and SO, processing the model from SDC and performing orchestration of network components in SO. Portal/VID vCPE UI fetches inventory data from A&AI.
This project depends on
ONAP Portal
SDC
SO
A&AI
How does this align with external standards/specifications?
Portal/VID will use provide an HTTP(s) web GUI and will interface with other systems using standard protocols like REST over HTTP(s)
Resources:
Amichai Hemli <ah0398@intl.att.com>
Jimmy Forsyth <jf2512@att.com>
Yoav Kluger (vCPE) <yoav.kluger@amdocs.com>
Tao Shen (VoLTE) <shentao@chinamobile.com>
Manoop Talasila <talasila@research.att.com>
Other Information:
Seed code: https://gerrit.onap.org/r/#/admin/projects/vid
- https://gerrit.onap.org/r/#/admin/projects/portal
- https://gerrit.onap.org/r/#/admin/projects/ecompsdkos
Committers/Maintainers:
Amichai Hemli ah0398@intl.att.com AT&T
Tao Shen shentao@chinamobile.com CMCCThis checklist is expected to be completed for the project to pass the M1 Release Planning Milestone.
| Info | ||
|---|---|---|
| ||
|
| Practice Area | Checkpoint | Yes/No | Evidence - Comment | How to? | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product Management | Are Product Backlog Epics entered in Jira? | Yes |
| |||||||||||
| Are Product Backlog Stories entered in Jira? | Yes |
| Create a Backlog item | |||||||||||
| Are Product Backlog Stories linked to Product Backlog Epics? | Yes | Product Backlog | Work in a Sprint | |||||||||||
| Are Product Backlog Stories prioritized? | Yes | Prioritize a Backlog item | ||||||||||||
| Is the project team ready to estimate the top Stories (for coming Sprint) in Product backlog? | Yes | Estimate a Backlog item | ||||||||||||
| Is the project team ready to create a 2 weeks Sprint in Jira? | Yes | Create a Sprint | ||||||||||||
| Are Team Members willing to create Tasks and associate them with Stories in Jira? | Yes | Create a Backlog item | ||||||||||||
| Release Management | Is there a Release Planning Template available and completed in wiki? | Yes | Release Planning Template | |||||||||||
| Have all the "Release Components Name" been defined in Resources and Repositories (Deprecated) for your project? (this includes all Sub-Components Names, Sub-Components Repositories Names, Maven Group ID, Sub-Components Description) | Yes | Resources and Repositories (Deprecated) | ||||||||||||
| Have all the "Resources committed to the Release" been defined in Resources and Repositories for your project? This includes First and Last names, LFID, Email Address and Location for PTL, Project Manager, Committers and Contributors. | Yes | Resources and Repositories (Deprecated) | ||||||||||||
| Have new developers made themself familiar on the Onboarding Process? | Yes | Onboarding | ||||||||||||
| Is the project team aware of the Release milestone? Any misses will required TSC exception. | Yes | |||||||||||||
| Integration and Testing | Has the Integration Team defined the vendor equipment list? | Link to evidence | ||||||||||||
| Has the Integration Team defined the End 2 End Release Test Case? | Link to evidence | |||||||||||||
| Development | Is the Project Team committed to develop Unit Test? | Yes | ||||||||||||
| Has the Project Team put in place an Automated Unit Test infrastructure? | Yes | |||||||||||||
| Is the Project Team committed to create Continuous System Integration Testing (CSIT) test case? | Yes | |||||||||||||
| Is the Project Team committed to perform Scrum ceremonies? | Yes | Scrum Overview | ||||||||||||
| Are the Project Team members aware of Continuous Integration Principles (don't break the build, Fix the build,...)? | Yes | Continuous Integration | ||||||||||||
| Has the Project Team a clear understanding on the Code Coverage expectations? | Yes | |||||||||||||
| Does the Project Team understand the Free and Open Source Software (FOSS) process? | Yes | Free and Open Source Software | ||||||||||||
| Is the Project Team willing to fill out accordingly the FOSS table? | Yes | Fill out sub-pages for each project under Free and Open Source Software | ||||||||||||
| Is the Project Team willing to comply to the Commit Process? | Yes | Commit Messages | ||||||||||||
| Does the Project Team understand the purpose of Code Review? | Yes | Code Review | ||||||||||||
| Is the Project Team aware of the Coding Guidelines? | Yes | Development Practices (Jave Coding Style) | ||||||||||||