From 96ae45212be24b8900dd0b327b00b83f29f16ab0 Mon Sep 17 00:00:00 2001 From: whoami-rajat Date: Wed, 25 Sep 2019 23:16:01 +0530 Subject: [PATCH] Releasenote followup: Untyped to default volume type Change-Id: I18494739ba9780bc994038dc001543ecfbc72d2d --- ...untyped_to_default_type-0068e6bc8000986c.yaml | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/releasenotes/notes/untyped_to_default_type-0068e6bc8000986c.yaml b/releasenotes/notes/untyped_to_default_type-0068e6bc8000986c.yaml index bd23bbd38d2..80372582af5 100644 --- a/releasenotes/notes/untyped_to_default_type-0068e6bc8000986c.yaml +++ b/releasenotes/notes/untyped_to_default_type-0068e6bc8000986c.yaml @@ -3,8 +3,16 @@ features: - | Added a new default volume type ``__DEFAULT__`` which will be used when - - A new volume is created without any type + + - A new volume is created without a type - The `default_volume_type` option is unset in cinder.conf - The volume will be assigned the ``__DEFAULT__`` type. - All existing volume, snapshots without a type will - be migrated to the ``__DEFAULT__`` type. + + Then the volume will be assigned the ``__DEFAULT__`` type. +upgrade: + - | + The db migration script will create a volume type named + ``__DEFAULT__`` + The online migration will migrate all existing untyped + volumes, snapshots to the ``__DEFAULT__`` type. + An invalid/non-existent type specified with `default_volume_type` + option in cinder.conf will result in VolumeTypeNotFoundByName exception.