From fe6db1464c600c799a422b284e23ca059accd511 Mon Sep 17 00:00:00 2001 From: fracappa Date: Fri, 17 Jan 2025 15:24:26 +0100 Subject: [PATCH] Modifying notes on checksum to reflect recent updates regarding empty checksumType field Signed-off-by: fracappa changing line length --- docs/user-guide/src/bmo/provisioning.md | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/docs/user-guide/src/bmo/provisioning.md b/docs/user-guide/src/bmo/provisioning.md index f761d4c8..1d144a05 100644 --- a/docs/user-guide/src/bmo/provisioning.md +++ b/docs/user-guide/src/bmo/provisioning.md @@ -108,12 +108,9 @@ provisioning](./live-iso.md) that works differently from a normal one. ### Notes on checksums -Unlike Ironic itself, Metal3 currently assumes the checksum algorithm to be MD5 -when no `checksumType` value is provided. Since more secure algorithms, such as -SHA256 or SHA512, are popular nowadays, care must be taken to provide the -correct `checksumType`. The value of `auto` will make Ironic detect the -checksum type from its length and will become the default in the next version -of the BareMetalHost API. +Setting `checksumType` to `auto` or leaving it empty prompts Ironic to +automatically detect the checksum type based on its length and will become +the default in the next version of the BareMetalHost API. The `checksum` value can be provided either as a URL or as the hash value directly. Providing a URL is more convenient in case of public cloud images,