Project Name:
- Proposed name for the project: Service Capability Management (SCM)
- Proposed name for the repository: scm
Project description:
- The Service Capability Management provides highly Identifiable, loose coupling and ready to be exposed service capability for ONAP SDC/SO with user-friendly, operator level Design time and Running time environment functions. The SCM also coming with a Graphical User Interface (GUI) to present logical correspond service capability list for the operators and end-users.
- SCM provides capability encapsulation based on the micro-services registered on MSB. SCM functions also includes design, administration, classification, cataloging, publishing, version management, access control , presenting for the above encapsulated service capabilities.
SCM is facing service and end-user level, while micro service is facing system level.
Scope:
Target
- Available service capability registration into SC catalogues through corresponded API
Registered SC is managed / exposed to users with different levels.
Function Management: Service Functionality Description and Management
Version Management
External Service
Retrieve service
Routing service
High Level Architecture Diagram:
- Service Capability Management (SCM) uses a three-layer architecture to manage the service instance information.
Service Capability directory and register items both adopt '(system coding, directory)' to identify uniquely.
The directory items are defined untidily by the directory Administrator. And the SC items can implement new, open, and undo through API after audit.
Inner Workflow of SCM:
Architecture Alignment:
Service Capability Management (SCM) provides service capability management for the operators and end-users, and have enough scalability so as to adapt various operators and end-users.
Service Capability Management (SCM) adopts comprehensive and exclusive safety control system. The outside system needs to carry assigned token when they call service instance catalogues and the catalogues tree allows traverse from outside requests after result filter.
Service Capability Management (SCM) provides efficient and stable 24*7 service to all users and adopts specific rules when establish the catalogues tree to ensure stability.
SCM Example for E-vCPE:
Other Information:
- Link to seed code (if applicable)
Vendor Neutral
Meets Board policy (including IPR)
Use the above information to create a key project facts section on your project page
Key Project Facts:
Facts | Info |
|---|---|
| Jira Key | TBD |
| Jira Project Name | TBD |
| Link to Wiki Space | TBD |
| Project ID | TBD |
| PTL (first and last name) | TBD |
Release Components Name:
Components Name | Components Repository name | Maven Group ID | Components Description |
|---|---|---|---|
| Service Capability Management | org.onap. | ||
Resources committed to the Release:
Note 1: No more than 5 committers per project. Balance the committers list and avoid members representing only one company. Ensure there is at least 3 companies supporting your proposal.
Note 2: It is critical to complete all the information requested, that will help to fast forward the onboarding process.
Role | First Name Last Name | Linux Foundation ID | Email Address | Location |
|---|---|---|---|---|
| PTL | ||||
| Committers | ||||
| Contributors | ||||
Project Summarization:
Project Name:
- JIRA project name: JIRA project name: Service Capability Management (SCM)
- JIRA project prefix: JIRA project prefix: scm
Repo name: scm
Lifecycle State:
Primary Contact: Wang Luman (Wanglm.bri@chinatelecom.cn)
Project Lead: TBD
mailing list tag [Should match Jira Project Prefix]
Committers:
Please refer to the table above.
*Link to TSC approval:
Link to approval of additional submitters: