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

Compare with Current View Page History

« Previous Version 23 Next »

Draft.

Project Name:

  • Proposed name for the project: Microservice Bus
  • Proposed name for the repository: msb.onap.org

Project description:

  • Standardize ONAP platform Microservies concepts & principles and provide key framework features such as service discovery and routing, standard interfaces, multi-tenancy support, authentication/authorization integration, service portal, and standard logging, tracing and monitoring mechanism, etc.

Scope:

  • Standardize microservice definition, principles and positioning paper on microservices adoption in ONAP
  • Service Discovery: Consumer should able to discover an ONAP Microservices
  • Service Identification: Each service is identifiable and consumer should able to invoke a service 
  • Service routing: Routing of microservice to right instance
  • Create microservices templates
  • Specify any interface/API specification proposed
  • Support for multi-tenancy
  • Support for Service Authentication & Authorization
  • Support standard logging and tracing mechanism
  • Support large number and scale of microservices
  • Identify the usecase in the Release 1

    • VoLTE usecase, such as the service discovery & routing of all the components involved in the VoLTE use case.

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?
      • Integration
  • How does this align with external standards/specifications?
    • APIs/Interfaces - OpenAPI/Swagger
    • Information/data models - Swagger JSON or YAML models
  • Are there dependencies with other open source projects?
    • APIs/Interfaces - OpenResty
    • Integration Testing
    • etc.

Resources:

  • Names and affiliations of any other contributors

    NameGerrit IDCompanyEmailTime Zone







  • Project Roles (include RACI chart, if applicable)

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:
  • JIRA project prefix:

Repo name:
Lifecycle State:
Primary Contact: RamKoya, HuabingZhao, Al Hua, Sanjay Agraharam, Brijesh Khandelwal
Project Lead: Huabing Zhao huabing.zhao@zte.com.cn
mailing list tag [Should match Jira Project Prefix] 
Committers:

*Link to TSC approval: 
Link to approval of additional submitters: 


  • No labels