Could you just point me which driver has done this? Thanks Dilip
From: Trinath Somanchi [mailto:trinath.soman...@nxp.com] Sent: Tuesday, June 14, 2016 1:25 PM To: Dilip Sunkum Manjunath; 'openstack@lists.openstack.org' Cc: 'itzdi...@gmail.com' Subject: RE: [Cinder] Facing a problem in cinder manage code You may check the other vendor alike drivers for your reference. / Trinath From: Dilip Sunkum Manjunath [mailto:dilip.sunkummanjun...@toshiba-tsip.com] Sent: Tuesday, June 14, 2016 1:00 PM To: 'openstack@lists.openstack.org' <openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>> Cc: 'itzdi...@gmail.com' <itzdi...@gmail.com<mailto:itzdi...@gmail.com>> Subject: [Openstack] [Cinder] Facing a problem in cinder manage code Hi all, I was implementing the cinder driver for cinder mange existing volume, Base line: 1. Our storage api has a unique number<deviceid/lun number> alone to recognise the lun in storage 2. When I import using the horizon I have to enter the same unique number to fetch the details from storage api Problem facing : 1. Same same unique ID am able import more then one time (duplicate imports) I know we should not use the "DB " calss in drivers, am not sure how to fetch avilable volume and run check over it, to ensure same LUN from storage is not imported more then once! When I went though the different driver, I saw LVM has the below method, which needs refrence to DB Question : Is it ok to use like this? Or Is there any better solution? Please suggest Thanks Dilip [cid:image001.png@01D1C644.01496CC0] [cid:image002.png@01D1C644.01496CC0] The information contained in this e-mail message and in any attachments/annexure/appendices is confidential to the recipient and may contain privileged information. If you are not the intended recipient, please notify the sender and delete the message along with any attachments/annexure/appendices. You should not disclose, copy or otherwise use the information contained in the message or any annexure. Any views expressed in this e-mail are those of the individual sender except where the sender specifically states them to be the views of Toshiba Software India Pvt. Ltd. (TSIP),Bangalore. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by Toshiba Software India Pvt. Ltd, for any loss or damage arising in any way from its use. The information contained in this e-mail message and in any attachments/annexure/appendices is confidential to the recipient and may contain privileged information. If you are not the intended recipient, please notify the sender and delete the message along with any attachments/annexure/appendices. You should not disclose, copy or otherwise use the information contained in the message or any annexure. Any views expressed in this e-mail are those of the individual sender except where the sender specifically states them to be the views of Toshiba Software India Pvt. Ltd. (TSIP),Bangalore. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by Toshiba Embedded Software India Pvt. Ltd, for any loss or damage arising in any way from its use.
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
