From dd5adf68a8cef80718f936d828c44ff88ae23f4c Mon Sep 17 00:00:00 2001 From: Arne Wiebalck Date: Fri, 10 Jan 2020 11:30:09 +0100 Subject: [PATCH] [doc] Images need some metadata for software RAID This is a follow-up for change #686580 to add some docs on the need for image metadata when deploying with software RAID. Change-Id: Iabc7e5482049df7aa6933053576ceb3f55e251b4 Story: #2006649 Task: #37081 --- doc/source/admin/raid.rst | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/doc/source/admin/raid.rst b/doc/source/admin/raid.rst index b836896ac2..fe0e1d2b87 100644 --- a/doc/source/admin/raid.rst +++ b/doc/source/admin/raid.rst @@ -378,6 +378,21 @@ There are certain limitations to be aware of: * There is no support for partition images, only whole-disk images are supported with Software RAID. See :doc:`/install/configure-glance-images`. +Image requirements +------------------ + +Since Ironic needs to perform additional steps when deploying nodes +with software RAID, there are some requirements the deployed images need +to fulfill. Up to and including the Train release, the image needs to +have its root file system on the first partition. Starting with Ussuri, +the image can also have additional metadata to point Ironic to the +partition with the root file system: for this, the image needs to set +the ``rootfs_uuid`` property with the file system UUID of the root file +system. The pre-Ussuri approach, i.e. to have the root file system on +the first partition, is kept as a fallback and hence allows software +RAID deployments where Ironic does not have access to any image metadata +(e.g. Ironic stand-alone). + Using RAID in nova flavor for scheduling ========================================