Image Manager

Project Name:

• Proposed name for the project: Image Manager

Project description:

Image Manager provide a reliable, visualized and logically centralized image management for ONAP at both design time and run time, including VM images, docker images and application binaries. With image manager, system 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 modules can not get the image information at both the design time and run time due to lack of logically centralied image management. Image Manager address this by Store/Manage image metadata information and provide APIs for the other modules and portal for ONAP operators.

• 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:

In 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 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:
  

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.
    
  • What other ONAP projects does this project depend on?
    • SDC
    • SO/VFC/VNFM
    • Multi-VIM
    • AAI/ESR
    • MSB
    • Integration
• How does this align with external standards/specifications?
  • APIs/Interfaces - OpenAPI/Swagger
  • Information/data models - Swagger JSON
• Are there dependencies with other open source projects?
  • 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 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:

Primary contact: Zi Li  li.zi30@zte.com.cn

Release Components Name:

Note: refer to existing project for details on how to fill out this table

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.

Note 2: It is critical to complete all the information requested, that we help to fast forward the onboarding process.