Madhu Rajanna 0f8813d89f rbd:store/Read volumeID in/from PV annotation ... In the case of the Async DR, the volumeID will not be the same if the clusterID or the PoolID is different, With Earlier implementation, it is expected that the new volumeID mapping is stored in the rados omap pool. In the case of the ControllerExpand or the DeleteVolume Request, the only volumeID will be sent it's not possible to find the corresponding poolID in the new cluster. With This Change, it works as below The csi-rbdplugin-controller will watch for the PV objects, when there are any PV objects created it will check the omap already exists, If the omap doesn't exist it will generate the new volumeID and it checks for the volumeID mapping entry in the PV annotation, if the mapping does not exist, it will add the new entry to the PV annotation. The cephcsi will check for the PV annotations if the omap does not exist if the mapping exists in the PV annotation, it will use the new volumeID for further operations. Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>		2021-04-07 11:46:27 +00:00
..
persistentvolume	rbd:store/Read volumeID in/from PV annotation	2021-04-07 11:46:27 +00:00
controller.go	rbd: add new controller to regenerate omap data	2020-11-28 18:50:00 +00:00