Table of Contents | ||
---|---|---|
|
Declined by TSC as a stand-alone project TSC 2018-01-04. Recommended as a component of Active and Available Inventory Project
Project Name:
- Proposed name for the project: Image Manager
Project description:
Image Manager provide provides a reliable, visualized and logically centralized, user-friendly image management for ONAP at both the design time and run time, including . The managed objects include VM images, docker Docker images and application binaries. With software packages. By using image manager, system ONAP users can upload images to the target VIM from uniform server instead of private repositories. The system security will be improved by checking the VVP/VNF-SDK validation result before the images uesed in ONAP. ONAP operators can also read the image details easily, such as the provider/version/status/deploy-location, etc.
- Manageability/Usability
ONAP system, manage images via Image Manager portal and distribute images to target VIMs on demand.
Usability:
ONAP modules can't get the image information easily Onap modules can not get the image information at both the design time and run time due to lack of logically centralied image managementbecause images are scattered in the VIMs. Image Manager address addresses this by Store/Manage image metadata information and provide problem by providing a centralized image catalog view and APIs for the other modules and portal for ONAP operatorsto access image information.
- Performance:
Images usually are big file, the efficiency of upload/download should be considered. Image Manager address this by provide centrolized management for VM/docker images and application binaries across design time and run time.
- Security:
Manageability:
It’s very hard for ONAP user to figure out what images have been used by ONAP platform or uploaded to the VIMs. Image Manager addresses this challenge by providing a UI portal for ONAP user to manage images, including browse/upload/update/delete/distribute images.
- Performance:
Currently, If an image needs to be uploaded to multiple VIMs, it has to be done separately and manually via the VIM portals, which is inefficient(imagine there might be thousands of edge clouds). Image manager addresses this issue by providing a centralized view and the images can be distributed to multiple VIMs via the Image Manager portal, which is much more efficientIn current solution, images are uploaded to VIM manually without validation. Image Manager can ensure that the VVP/VNF-SDK validation result by checking the signing/certification along with the images before uploading images to ONAP.
Scope:
- Provide centrolize logically centralized management for VM/docker images and application binaries across design time and run time.
Provide image management portal to manage images.
Provide image information management.
Provide image storage adapter to adapt different kinds of tools according to image type.
Check image signing & attestation when upload images.
Image Upload at Design Time:
Download Image at Run Time:
...
- images used by ONAP system, which includes VM image, Docker image, and application package.
- Provide APIs to upload images to ONAP system.
- Provide APIs to access the image catalog and image information in ONAP system.
- Provide a UI portal in which the ONAP user can upload/update/delete/distribute images.
Architecture Alignment:
- How does this project fit into the rest of the ONAP Architecture?
- Image Manager(IM) is a common service across design time and run time.
Onboard images to ONAP system:
Dispatch images to VIMs:
- Image Manager(IM) is a common service across design time and run time.
- What other ONAP projects does this project depend on?
- SDC SO/VFC/VNFM
- Multi-VIM
- AAI/ESR
- MSB
- Integration
- APIs/Interfaces - OpenAPI/Swagger
- Information/data models - Swagger JSON
- APIs/Interfaces - MariaDB, ftp, nexus
- Integration Testing etc.
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 All proprietary trademarks, logos, product names, etc., have been removed?will be removed when submitting the seed codes.
- Meets Board policy (including IPR)
...
Key Project Facts:
Primary contact: Zi Li li.zi30@zte.com.cn zhao.huabing@zte.com.cn
Facts | Info |
---|---|
PTL (first and last name) | |
Jira Project Name | Image Manager |
Jira Key | IM |
Project ID | Image Manager |
Link to Wiki Space |
Release Components Name:
...
Components Name | Components Repository name | Maven Group ID | Components Description |
---|---|---|---|
Image Manager | im | im | Image Managerorg.onap. |
Resources committed to the Release:
...
Role | First Name Last Name | Linux Foundation ID | Email Address | Location | ||
---|---|---|---|---|---|---|
PTL | ||||||
Committers | ||||||
Zi Li | lili.zi30@zte.com.cn | |||||
Tao Shen | shentao@chinamobile.com | |||||
Hu Yuan | yuan.hu1@zte.com.cn | |||||
ContributorsZi | ||||||
LiBo Lv | lilv.zi30@ztebo163@zte.com.cn | |||||
Tao ShenQihui Zhao | shentao@chinamobile | |||||
Luman Wang | wanglm.bri@chinatelecom.cn | |||||
Chen Yan | Hu Yuan | yuan.hu1@zte.com | ||||
Eric Debeau | eric.debeau@orange.com | |||||
Kaiyue Wang | wangkaiyue@chinamoblie.com | Bo Lv | lv.bo163@zte.com.cn |