|
4 | 4 |
|
5 | 5 | CSC provides a set of standard images that are well suited for cloud |
6 | 6 | use. In most cases, you can use these images instead of creating your |
7 | | -own. The images are created automatically using _diskimage-builder_. |
| 7 | +own. The images are created automatically using _diskimage-builder_. |
8 | 8 | If you are interested in the details of how |
9 | 9 | these images are created, see this [GitHub page]. The images are |
10 | 10 | updated at regular intervals so that they contain the latest security |
11 | 11 | updates at the time virtual machines are launched. |
12 | 12 |
|
13 | 13 | It is possible that for some use cases the automatically created |
14 | 14 | images are not suitable. In this case, it is possible to create your |
15 | | -own images and use them instead. However, there are some caveats |
| 15 | +own images and use them instead. However, there are some caveats |
16 | 16 | to consider when creating your own images that you would not |
17 | 17 | need to consider when using the default images. For more information,, |
18 | 18 | see [Advanced images](adding-images.md) |
@@ -82,6 +82,12 @@ This can be useful for doing tests in Pouta, such as testing if the network work |
82 | 82 | how fast you can launch an instance. You should not use this for persistent |
83 | 83 | VMs, and you should always delete the instance when you are done with |
84 | 84 | testing. There is very little reason for end-users using this image, and if |
85 | | -you are unsure, CentOS and Ubuntu are better choices 99% of the time. |
| 85 | +you are unsure, CentOS and Ubuntu are better choices 99% of the time. |
86 | 86 |
|
87 | 87 | [GitHub page]: https://github.com/CSC-IT-Center-for-Science/diskimage-builder-csc-automation |
| 88 | + |
| 89 | +## Image metadata |
| 90 | +Images updated since November of 2025 might have metadata reporting the type and version of |
| 91 | +the operating system (os_type, os_distro). That information allow OpenStack to create |
| 92 | +[ephemeral](ephemeral-storage.md) disks with the more appropriate format ext4 instead of vfat. Be |
| 93 | +aware that this might affect your workflow or automations. |
0 commit comments