Background:
Currently, the multi-cloud management platform on the market has similar business abstract architecture models. It has established a complete standard scenario and compatible processing of isomerized resources. However, the management of homogeneous resources such as mirror files is still relatively scattered, that is, each heterogeneous cloud environment has its own entrance and usage requirements for mirror management, and lacks centralized management and unified scheduling, which brings great use costs to the use of mirrors, including management costs and waste of storage resources. The Mirror Center aims to provide a unified management platform for different mirrors in heterogeneous multi-cloud environments to solve the above problems.
Features and functions:
- supports the deployment of mirror servers in heterogeneous multi-cloud environments, such as virtual machines or physical machines;
- realizes unified management of mirror server under different deployment forms, such as availability zone binding, network configuration entry, removal, etc.;
- mirror center service supports local upload, remote upload, compressed upload and other upload forms;
- supports multiple formats of image file storage and format reversal, such as QCOW2, RAW, ISO, etc.;
- supports batch image file storage and format reversal, such as QCOW2, RAW, ISO, etc.;
- supports batch image file storage and format reversal, such as QCOW2, RAW, ISO, etc.;
- supports batch of image files Scheduled issuance to a designated cloud environment or different storage locations;
- supports the synchronization of image files between the Availability Zone mirror servers;
- optimizes k8s, elastic scaling and other components to specify the mirror center image. The user experience of automatically issuing mirror images when the virtual machine is enabled;
- supports the synchronization of existing mirror images in heterogeneous multi-cloud environments to the image center;
overall architecture and process:
"Cloud management platform A mirror service uniformly manages image servers under multiple Availability Zones, and a mirror server can bind multiple Availability Zones." The overall architecture idea.
mirror server currently supports virtual machine deployment and activation in heterogeneous cloud environments such as the A-chao cluster or Vmvare cluster. The mirror servers that are activated according to the specified specifications and storage and network requirements can be entered at the mirror center service portal of the cloud management platform. The entry mainly includes the management network IP and transmission network IP and port and login password of the mirror server, as well as the binding of the availability zone. After a mirror server completes the entry and configuration in the mirror center, it can use other functions of the mirror center service, such as uploading, synchronization, issuing, format conversion, deleting, exporting, etc.
Mirror Center Service focuses on the full life cycle management of for image file business data and the access control of the mirror server. The mirror server mainly provides actual functions such as compressed storage, network transmission and format conversion of mirror files. Taking the user uploading the image and converting the image in format, and posting the image to the Anchao cluster as an example, a brief introduction to how the mirror center runs. The user first selects a mirror server that has been configured and entered at the entrance of the cloud tube mirror center management page, and forms a request for the pre-prepared image file URL or local file on the page. The mirror center service will perform a series of parameter verification on the mirror file. After the verification is correct, it will obtain the remote connection handle of the mirror server that has been initialized, form communication between the mirror center service and the mirror server, and remotely call the preset file transfer process on the server to upload the mirror file. After the asynchronous upload is completed, the MD5 or file size of the file is calculated and the mirror center service is notified. The mirror center service will improve the business data and push notifications to the front desk page after entering the database, and the upload is completed. Users need to convert the RAW format image file to QCOW2 format. Similarly, the operation on the cloud management platform triggers the image format conversion request. The mirror center service obtains the remote connection of the mirror server and executes the format conversion command. The image will complete the format conversion on the server, and asynchronously inform the mirror center service of the operation result and notify the front-end user of the operation. The mirror center service is compatible with the mirror management portal of heterogeneous multi-cloud environments. Therefore, when the mirror center service receives a request sent by the user to generate the mirror center image, it will encapsulate the remote address of the mirror file into the request parameter format for uploading each heterogeneous cloud environment file and request the corresponding cloud environment service to listen to the final result of the mirror to complete the entire issuance process.
At this point, the overall architecture and main functional processes of the mirror center have been explained.
Summary:
Mirror Center aims to provide a unified management platform for different mirrors in heterogeneous multi-cloud environments, open up the transmission of image files between various availability zones, optimize tenants' operating experience in deployment and use, reduce management difficulty, intensive storage resources, and make full use of the global network capabilities or storage resource characteristics of the cloud management platform to continuously enhance the functions provided by the mirror center.
