Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Mon, Sep 26, 2011 at 09:00:41AM +0200, Maciej Gałkiewicz wrote: > 2011/9/23 James R. Leu <jleu at inoc.com>: > > We just went through this exercise and went with AOE instead > > of iSCSI because we found the current crop of iSCSI target and > > initiators to be lacking in terms selectively bringing a LUN 'up' > > and 'down'. Specifically the iSCSI target implementations do not > > release the backstoring device when the LUN is marked as offline. > > Thus preventing DRBD from going secondary. (I posted a patch to the > > tgtd mailing list to add the functionality, but it was rejected). > > Do you plan on having the VM guests access the iSCSI server directly > > or use iSCSI to connect the LUNs to the VM host and then the > > host hands them to the guests as directly connected block devices? > > We choose the latter to try and keep the guests as simple as possible. > > I cannot use AOE because my servers are in different IP subnet. My VM > contacts with iSCSI server directly. In my infrastructure DRBD is not > on top of iSCSI. With iSCSI on top of DRBD, DRBD will not allow you to go secondary unless the iSCSI target releases the backend store. > > -- > Regards > Maciej Galkiewicz -- James R. Leu Software Architect INOC 608.204.0203 608.663.4555 fax jleu at inoc.com www.inoc.com *** DELIVERING UPTIME *** -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20110926/b540ab81/attachment.pgp>