Operating Steps

1. Create a BBC instance, and then deploy the application required for customers on this instance. For the custom image only packs a part of paths under the / partition (i.e., home partition), the customer's application must be installed in these paths. The packing path is shown as follows:

2. Select this BBC instance in the BBC Instance list, and then click “Create Custom Image” in “More Operations”.
3. Enter the custom image name, and then click “OK” to start to create the custom image.

4. The backend operation of custom image is actually to pack the image and upload the glance automatically. After the successful packing of image, you can view the created custom image.

The time to create a custom image depends on the size of application deployed by the customer. The larger the application, the more time it takes.

There are many considerations during the creation and use of custom image. If you want to use the custom image function, read the following recommendations and special instructions carefully.

Recommendations:

1. The custom image can be packed or partitioned only.
2. It is recommended to restart the application instance deployed according to the requirements to ensure that the custom image can be started normally.
3. Only the running server can create a custom image.
4. The custom image only supports the Linux system temporarily (CentOS & Ubuntu).
5. Check that the remaining space of system disk to ensure that there is enough space on the system disk to replicate the image.
6. The restart and shutdown operations are performed during the creation of image. Make sure to migrate the business and save the data.
7. The custom image can be only installed on the same model, and other models are not allowed to install temporarily.
8. The custom image is not supported on the system with upgraded kernel or operating system versions.
9. Do not adjust the partition of the system disk, and do not change the key system file, such as /sbin, /bin and /lib directory.

Special Notes

1.The custom image can be only created based on the operating system installed through the standard process.

2.It does not ensure that the custom image is installed successfully.

3.The backend does not reject the creation initiated by the custom image.

4.For the custom image is directly uploaded after the packing without test verification, it can not ensure the availability of image and the adaptation relationship with the corresponding machine. Therefore, the installation may fail.