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:

Other Information:

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: 


  • No labels

3 Comments

  1. Andrew Fenner

    At the project approval there was some discussion about the fact that this could be tied to the larger use case for volte or vCPE which might have some problems with commercial VNFs and enviroments.

    Should this project not also produce a "simple" UC GUI for the vFW/vDNS use case, This would then be available to everyone and would act as the path breaker application associated with a use case.

    I know that there is probably still the need for the UI associated with the larger UC for demo purposes and that could still be done but the simple UC UI could act as the template for how a UC UI could be developed. I could I think have all the same features as the UI proposed for the larger UC.

    /Andrew

    1. Tao Shen

      The vFW/vDNS use case hasn't be approved so far. So I think we won't support this use case in R1.

      Could you clarify requirements of vFW/vDNS use case?

      If somebody is going to contribute source code for this use case, I will add this needs to R1 planning.

  2. Gildas Lanilis

    vFW/vDNS use case has been approved on June 15, 2017. Refer to topic # 6 in the link below for details

    http://ircbot.wl.linuxfoundation.org/meetings/onap-meeting/2017/onap-meeting.2017-06-15-13.57.html