| 2019-09-19 08:35:49 |
ramakrishnan |
description |
Upgrading from SMI-S based driver to RESTAPI based driver
Seamless upgrades from an SMI-S based driver to RESTAPI based driver, following the setup instructions above, are supported with a few exceptions:
1. Live migration functionality will not work on already attached/in-use legacy volumes. These volumes will first need to be detached and reattached using the RESTAPI based driver. This is because we have changed the masking view architecture from Pike to better support this functionality.
2. Consistency groups are deprecated in Pike. Generic Volume Groups are supported from Pike onwards.
Problem is with #1 - detaching the volume so that it can be attached again later into a new masking view with cascaded storage groups. I send the terminate_connection request using a connector like that PowerVC would have used to perform the original attach using SMI-S management. In the log can be seen this warning:
2019-02-04 17:24:48.448 128227 WARNING cinder.volume.drivers.dell_emc.vmax.fc [req-67448355-283e-4ebc-bcef-5406895555e9 c516a445257698992a7ae02c3a2eeba62147432cdea674d451bed35828522ecf 04f81a9bf1b74495be8d28428e12c310 - 201a3bd6c7a34802bbd66f3a9d345d92 201a3bd6c7a34802bbd66f3a9d345d92] Volume volume-csky-old-da6b04fc-00000004-boot-0-7d464d26-b652 is not in any masking view.
But this is not true. It is in a legacy masking view.
Our server hostnames are longer than 16 characters but shorter than the number of characters allowed in the SMI-S driver. For example, in the connector we may have 'host': 'csky-old-da6b04fc-00000004'
This is 26 characters long. |
Upgrading from SMI-S based driver to RESTAPI based driver Fails
Seamless upgrades from an SMI-S based driver to RESTAPI based driver, following the setup instructions above, are supported with a few exceptions:
1. Live migration functionality will not work on already attached/in-use legacy volumes. These volumes will first need to be detached and reattached using the RESTAPI based driver. This is because we have changed the masking view architecture from Pike to better support this functionality.
2. Consistency groups are deprecated in Pike. Generic Volume Groups are supported from Pike onwards.
Problem is with #1 - detaching the volume so that it can be attached again later into a new masking view with cascaded storage groups. I send the terminate_connection request using the connector that used to perform the original attach using SMI-S management. In the log can be seen this warning:
2019-02-04 17:24:48.448 128227 WARNING cinder.volume.drivers.dell_emc.vmax.fc [req-67448355-283e-4ebc-bcef-5406895555e9 c516a445257698992a7ae02c3a2eeba62147432cdea674d451bed35828522ecf 04f81a9bf1b74495be8d28428e12c310 - 201a3bd6c7a34802bbd66f3a9d345d92 201a3bd6c7a34802bbd66f3a9d345d92] Volume volume-csky-old-da6b04fc-00000004-boot-0-7d464d26-b652 is not in any masking view.
But this is not true. It is in a legacy masking view.
Our server hostnames are longer than 16 characters but shorter than the number of characters allowed in the SMI-S driver. For example, in the connector we may have 'host': 'csky-old-da6b04fc-00000004'
This is 26 characters long. |
|
