Draft.
Project Name:
- Proposed name for the project:
Microservices Platform
- Proposed name for the repository:
msp.onap.org
Project description:
Microservices Platform key infrastructure functionalities to support Microservice Architecture including service registration/discovery, service gateway, service load balancer. It's a pluggable architecture so it can plugin service provider options like AAF to provide Authentication & Authorization for APIs. Microservices Platform also provide a service portal and service requests logging, tracing and monitoring mechanism, etc.
Scope:
- Service registration
- Registration via Restful API
- Registration via portal
- Registration via proxy
- service discovery - Server side discovery
- service request routing
- service request load balancing
- Service discovery - Client side discovery
- client side discovery sdk
- Service discovery - DNS
- Discovery and load balancing by DNS server
- Service consumer directly talk to service provider
- service API Gateway
- Client request routing
- Client request load balancing
- Transformation, such as https to http
- Provide authentication & authorization for service request with plugin of auth service provider like AAF
- Service request logging
- Service Request Rate-limiting
- Service monitoring
- Request result cache
- Solve cross-domain issue for web application
- Other functionalities with the pluggable architecture capability ..
- 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
- Please Include architecture diagram if possible
- 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:
- Primary Contact RamKoya, HuabingZhao, Al Hua, Sanjay Agraharam, Brijesh Khandelwal
Names, gerritIDs, and company affiliations of the committer
Name Gerrit ID Company Email Time Zone Ram Koya AT&T rk541m@att.com Dallas, USA. CST/CDT John Murray AT&T Bedminster, USA EST/EDT Dominic Lunanuova AT&T dgl@research.att.com MiddleTown, USA EST/EDT
Zhaoxing Meng ZTE Beijing, China. UTC +8 Huabing Zhao HuabingZhao ZTE Beijing, China. UTC +8 Yonggang Wang ZTE Beijing, China. UTC +8 Tang Hua ZTE tang.hua52@zte.com.cn Beijing, China. UTC +8 Brijesh Khandelwal Tech Mahindra kbrijesh@TechMahindra.com CDT, USA. Hailong He ZTE he.hailong5@zte.com.cn Beijing, China. UTC +8
Names and affiliations of any other contributors
Name Gerrit ID Company Email Time Zone - Project Roles (include RACI chart, if applicable)
Other Information:
- link to seed code
https://gerrit.open-o.org/r/common-services-microservice-bus - Vendor Neutral
All proprietary trademarks, logos, product names, etc. have been removed. - Meets Board policy (including IPR)
Yes
Use the above information to create a key project facts section on your project page
Key Project Facts
Project Name:
- JIRA project name: Microservices Bus
- JIRA project prefix: MSB
...