Uploading Images

IBM® Cloud Infrastructure Center can deploy virtual machines from either local storage or persistent storage, different type of images should be uploaded.

Please remember to check the integrity of the image you are going to upload. Deploying a virtual machine with an incomplete image causes IBM Cloud Infrastructure Center to hang for a long time. Use following steps to check the integrity of the image:

Get the MD5 checksums of the image. When you get an image or create an image, you should record the MD5 checksums of the images. When the images are going to be transferred, the MD5 checksums should be tranferred together with the images. Because the MD5 checksums is necessary data to check the image's integrity. Save the original MD5 checksums to a file md5sum_original for example.
Run following to get the MD5 checksums of the image file when the tranfer complete:
```
md5sum <file path of the image file>
```
The output should be like:
```
ac83e6cc221a90331d45b78934989513  <the name of image>
```
Save the the 32 bytes string into a file called md5sum_current for example.
Compare the checksums by running:
```
diff md5sum_current md5sum_original
```
If no output, the image you are using should be same with the original one.

Note:

If you are going to upload image using IBM Cloud Infrastructure Center UI, you would need to first transfer the image from the current location on compute node onto the server where you would run the IBM Cloud Infrastructure Center UI, since the UI would only browse locations on the local server for security considerations.

As an alternative to avoid uploading image from your local system, you can copy the image file to the management node and use the openstack CLI to upload the image. For the detail command to fulfil that, refer to the corresponding subsection in this chapter according to your image type.