Hi Peter,
I can't disagree with anything you have said, particularly re. failover (see my post that followed).
Incidentally though, it was an internal Network Appliance whitepaper that alerted me to the possibility of using CIFS for .vmdk files.
See section 9.1.3 on page 58 of TR-3505i.
I understand that being an internal paper I shouldn't be mentioning it here, and the published version of that paper on A-SIS eliminates the discussion of VMWare, I suspect because support issues haven't been nailed down yet.
Still waiting on feedback from my contact in VMWare, will post when I hear something.
There are other reasons beside statefulness of CIFS connections to prefer NFS (performance, etc.), but that's the main issue. I only mentioned it so as not to exclude it as a technical possibility, my followup posts were intended to stop anyone getting too excited about it at this stage. Also even if VMWare were to build it into the kernal, I'd still be pushing clients to pay for an NFS licence instead. The issue here is the cost of the NFS licence, which can be considered high for some Windows-only shops.
regards,
Alan.
OK, fair enough. Thanks for clearing that up!
-----Original Message----- From: Alan McLachlan [mailto:alanmac@technologist.com] Sent: Sunday, October 28, 2007 8:36 PM To: toasters@mathworks.com Subject: RE: VMWare CIFS driver
Hi Peter,
I can't disagree with anything you have said, particularly re. failover (see my post that followed).
Incidentally though, it was an internal Network Appliance whitepaper that alerted me to the possibility of using CIFS for .vmdk files.
See section 9.1.3 on page 58 of TR-3505i.
I understand that being an internal paper I shouldn't be mentioning it here, and the published version of that paper on A-SIS eliminates the discussion of VMWare, I suspect because support issues haven't been nailed down yet.
Still waiting on feedback from my contact in VMWare, will post when I hear something.
There are other reasons beside statefulness of CIFS connections to prefer NFS (performance, etc.), but that's the main issue. I only mentioned it so as not to exclude it as a technical possibility, my followup posts were intended to stop anyone getting too excited about it at this stage. Also even if VMWare were to build it into the kernal, I'd still be pushing clients to pay for an NFS licence instead. The issue here is the cost of the NFS licence, which can be considered high for some Windows-only shops.
regards,
Alan.
version.
Besides, while I think NFS is great for VMware, I think CIFS is horrible. People who have tried it with VMware server or GSX have had
-- Want an e-mail address like mine? Get a free e-mail account today at www.mail.com!
Hi
vmdk images streamed on CIFS? :-) Sorry if I smile but performances will be...terrible!!! That's the reason for the NFS usage available on VMWare. And, after all, VMWare is a RHEL 4.x Linux distribution..to "read" CIFS the service console should have a SAMBA interface on it...heavy role!!!
I agree with the license cost of NFS and CIFS together but, after all..iSCSI is free on NetApp. Create an iSCSI LUN and map it to VMWare...best practice!
Bye
________________________________
Da: owner-toasters@mathworks.com per conto di M. Vaughn Stewart Inviato: lun 29/10/2007 5.45 A: Alan McLachlan Cc: toasters@mathworks.com Oggetto: Re: VMWare CIFS driver
Thanks for bringing this to our attention
V
Alan McLachlan wrote:
-
Alan McLachlan -
Learmonth, Peter -
M. Vaughn Stewart -
Milazzo Giacomo