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

Compare with Current View Page History

« Previous Version 3 Next »

Project Name:

  • Proposed name for the project: Microservice Framework
  • Proposed name for the repository: msf.onap.org

Project description:a

  • 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
  • microservice to support logging, tracing  and monitoring mechanism
  • Support large number and scale of microservices
  • Produce a white paper to include all the above scope items.

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

Resources:

  • Primary Contact Person
  • Names, gerrit IDs, and company affiliations of the committers
  • Names and affiliations of any other contributors
  • Project Roles (include RACI chart, if applicable)

Other Information:

  • link to seed code (if applicable)
  • Vendor Neutral
    • if the proposal is coming from an existing proprietary codebase, have you ensured that all proprietary trademarks, logos, product names, etc., have been removed?
  • 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:
  • JIRA project prefix:

Repo name:
Lifecycle State:
Primary Contact:
Project Lead:
mailing list tag [Should match Jira Project Prefix] 
Committers:
foo@bar.com
baz@qux.com
*Link to TSC approval: 
Link to approval of additional submitters: 


  • No labels