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.
----- Original Message ----- From: "Learmonth, Peter" Peter.Learmonth@netapp.com To: "Alan McLachlan" alanmac@technologist.com, toasters@mathworks.com Subject: RE: VMWare CIFS driver Date: Sun, 28 Oct 2007 19:10:27 -0700
Hi Alan Would you happen to have a URL instead of a IP address?
Given that this comes from an unidentifiable web site, I highly doubt this will get any support from VMware, and I can pretty much guarantee that this will get no support from NetApp.
More on the RPM itself... It contains only an object module, which appears to install in the service console Linux, not the VMKernel, although I could be wrong on that.
The version on that RPM matches the ESX 3.0.1 COS Linux kernel 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 some surprises when the storage fails over and CIFS drops the connections. It doesn't make any difference whose CIFS server you're using. I personally don't think VMware should waste any time developing an ESX kernel client.
Thanks anyway.
Peter
-----Original Message----- From: Alan McLachlan [mailto:alanmac@technologist.com] Sent: Sunday, October 28, 2007 4:24 PM To: toasters@mathworks.com Subject: VMWare CIFS driver
Hi,
Find it here:
http://89.105.41.70/sites/esx/Lists/Posts/Post.aspx?ID=1
Enjoy!
regards,
Alan McLachlan
----- Original Message ----- From: "Davies,Matt" MDAVIES@generalatlantic.com To: Peter.Learmonth@netapp.com, alanmac@technologist.com, toasters@mathworks.com Subject: RE: VMware / A-SIS Date: Sun, 28 Oct 2007 21:48:16 -0000
I was about to ask the same question.....
-----Original Message----- From: owner-toasters@mathworks.com owner-toasters@mathworks.com To: Alan McLachlan alanmac@technologist.com; toasters@mathworks.com toasters@mathworks.com Sent: Sun Oct 28 21:09:20 2007 Subject: RE: VMware / A-SIS
Ummmm.... What ESX CIFS driver?
-----Original Message----- From: Alan McLachlan [mailto:alanmac@technologist.com] Sent: Sunday, October 28, 2007 8:26 AM To: toasters@mathworks.com Subject: VMware / A-SIS
Hi Vaughn,
For small environments on a budget where the cost of additional licenses is an issue, you can use RDM's over iSCSI or FCP for both data LUN's _and_ the VM OS images. You still need VMDK pointer files to enable vmotion.
By using RDM's for the VM images you can use lun cloning for R/W snapshots within the same FlexVol, without paying for a FlexClone license and achieve a reasonable level of deduplication without paying
for an A-SIS licence. i.e. create "golden images" as source LUNs then use lun clones for the prod, dev, test and backup images of the VM's.
However, for larger environments using vmdk's on NAS from NFS exports or CIFS shares for the VM images is a far more scalable and manageable
solution as long as you're happy to pay for A-SIS to manage deduplication. I still wouldn't be putting data volumes inside the vmdk's though.
(Yes, you can use CIFS for vmdk's in ESX. Not as ideal as NFS for a whole bunch of reasons, but it works via the VMWare ESX CIFS driver and useful if you have to have CIFS for file server consolidation and don't want to pay for NFS licencing as well).
Either way, storing your application data in either RDM LUN's or as direct NAS shares makes managing snapshots for dev/test copies and online backups of the production data much simpler to manage. Putting data inside vmdk's limits your functionality particularly for backups.
MSCS requires an RDM for the quorum disk, but you can still use a NAS share for the data if your data profile and application characteristics indicate that it makes more sense to do that than use an RDM for the data.
regards,
Alan McLachlan.
-----Original Message----- From: owner-toasters@mathworks.com on behalf of M. Vaughn Stewart Sent: Sun 10/28/2007 8:07 AM To: Jack Lyons Cc: Page, Jeremy; toasters@mathworks.com Subject: Re: A-SIS questions
FlexClone will clone a datastore, for VM level cloning granularity you
gonna have to wait I think something is just around the corner.
As for MSCS you need RDMs as VMDKs are not supported with MSCS
RDMs can be either FCP or iSCSI VMDKs can be on NFS or VMFS (which is over FCP or iSCSI)
-- Want an e-mail address like mine? Get a free e-mail account today at www.mail.com!
This e-mail (including all attachments) is confidential and may be
privileged.
It is for the exclusive use of the addressee only. If you are not the addressee, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its
attachments and notify us immediately at help@generalatlantic.com mailto:help@generalatlantic.com. Thank You.
-- Want an e-mail address like mine? Get a free e-mail account today at www.mail.com!
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.
----- Original Message ----- From: "Learmonth, Peter" Peter.Learmonth@netapp.com To: "Alan McLachlan" alanmac@technologist.com, toasters@mathworks.com Subject: RE: VMWare CIFS driver Date: Sun, 28 Oct 2007 19:10:27 -0700
Hi Alan Would you happen to have a URL instead of a IP address?
Given that this comes from an unidentifiable web site, I highly doubt this will get any support from VMware, and I can pretty much guarantee
that this will get no support from NetApp.
More on the RPM itself... It contains only an object module, which appears to install in the service console Linux, not the VMKernel, although I could be wrong on that.
The version on that RPM matches the ESX 3.0.1 COS Linux kernel
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
some surprises when the storage fails over and CIFS drops the connections. It doesn't make any difference whose CIFS server you're using. I personally don't think VMware should waste any time developing an ESX kernel client.
Thanks anyway.
Peter
-----Original Message----- From: Alan McLachlan [mailto:alanmac@technologist.com] Sent: Sunday, October 28, 2007 4:24 PM To: toasters@mathworks.com Subject: VMWare CIFS driver
Hi,
Find it here:
http://89.105.41.70/sites/esx/Lists/Posts/Post.aspx?ID=1
Enjoy!
regards,
Alan McLachlan
----- Original Message ----- From: "Davies,Matt" MDAVIES@generalatlantic.com To: Peter.Learmonth@netapp.com, alanmac@technologist.com, toasters@mathworks.com Subject: RE: VMware / A-SIS Date: Sun, 28 Oct 2007 21:48:16 -0000
I was about to ask the same question.....
-----Original Message----- From: owner-toasters@mathworks.com owner-toasters@mathworks.com To: Alan McLachlan alanmac@technologist.com; toasters@mathworks.com toasters@mathworks.com Sent: Sun Oct 28 21:09:20 2007 Subject: RE: VMware / A-SIS
Ummmm.... What ESX CIFS driver?
-----Original Message----- From: Alan McLachlan [mailto:alanmac@technologist.com] Sent: Sunday, October 28, 2007 8:26 AM To: toasters@mathworks.com Subject: VMware / A-SIS
Hi Vaughn,
For small environments on a budget where the cost of additional licenses is an issue, you can use RDM's over iSCSI or FCP for both data LUN's _and_ the VM OS images. You still need VMDK pointer files
to enable vmotion.
By using RDM's for the VM images you can use lun cloning for R/W snapshots within the same FlexVol, without paying for a FlexClone license and achieve a reasonable level of deduplication without paying
for an A-SIS licence. i.e. create "golden images" as source LUNs then use lun clones for the prod, dev, test and backup images of the
VM's.
However, for larger environments using vmdk's on NAS from NFS exports or CIFS shares for the VM images is a far more scalable and manageable
solution as long as you're happy to pay for A-SIS to manage deduplication. I still wouldn't be putting data volumes inside the vmdk's though.
(Yes, you can use CIFS for vmdk's in ESX. Not as ideal as NFS for a whole bunch of reasons, but it works via the VMWare ESX CIFS driver and useful if you have to have CIFS for file server consolidation and don't want to pay for NFS licencing as well).
Either way, storing your application data in either RDM LUN's or as direct NAS shares makes managing snapshots for dev/test copies and online backups of the production data much simpler to manage. Putting data inside vmdk's limits your functionality particularly for backups.
MSCS requires an RDM for the quorum disk, but you can still use a NAS share for the data if your data profile and application characteristics indicate that it makes more sense to do that than use an RDM for the data.
regards,
Alan McLachlan.
-----Original Message----- From: owner-toasters@mathworks.com on behalf of M. Vaughn Stewart Sent: Sun 10/28/2007 8:07 AM To: Jack Lyons Cc: Page, Jeremy; toasters@mathworks.com Subject: Re: A-SIS questions
FlexClone will clone a datastore, for VM level cloning granularity you
gonna have to wait I think something is just around the corner.
As for MSCS you need RDMs as VMDKs are not supported with MSCS
RDMs can be either FCP or iSCSI VMDKs can be on NFS or VMFS (which is over FCP or iSCSI)
-- Want an e-mail address like mine? Get a free e-mail account today at www.mail.com!
This e-mail (including all attachments) is confidential and may be
privileged.
It is for the exclusive use of the addressee only. If you are not the addressee, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this
communication in error, please erase all copies of the message and its
attachments and notify us immediately at help@generalatlantic.com mailto:help@generalatlantic.com. Thank You.
-- Want an e-mail address like mine? Get a free e-mail account today at www.mail.com!
-- Want an e-mail address like mine? Get a free e-mail account today at www.mail.com!
Thanks for bringing this to our attention
V
Alan McLachlan wrote:
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.
----- Original Message ----- From: "Learmonth, Peter" Peter.Learmonth@netapp.com To: "Alan McLachlan" alanmac@technologist.com, toasters@mathworks.com Subject: RE: VMWare CIFS driver Date: Sun, 28 Oct 2007 19:10:27 -0700
Hi Alan Would you happen to have a URL instead of a IP address?
Given that this comes from an unidentifiable web site, I highly doubt this will get any support from VMware, and I can pretty much guarantee that this will get no support from NetApp.
More on the RPM itself... It contains only an object module, which appears to install in the service console Linux, not the VMKernel, although I could be wrong on that.
The version on that RPM matches the ESX 3.0.1 COS Linux kernel 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 some surprises when the storage fails over and CIFS drops the connections. It doesn't make any difference whose CIFS server you're using. I personally don't think VMware should waste any time developing an ESX kernel client.
Thanks anyway.
Peter
-----Original Message----- From: Alan McLachlan [mailto:alanmac@technologist.com] Sent: Sunday, October 28, 2007 4:24 PM To: toasters@mathworks.com Subject: VMWare CIFS driver
Hi,
Find it here:
http://89.105.41.70/sites/esx/Lists/Posts/Post.aspx?ID=1
Enjoy!
regards,
Alan McLachlan
----- Original Message ----- From: "Davies,Matt" MDAVIES@generalatlantic.com To: Peter.Learmonth@netapp.com, alanmac@technologist.com, toasters@mathworks.com Subject: RE: VMware / A-SIS Date: Sun, 28 Oct 2007 21:48:16 -0000
I was about to ask the same question.....
-----Original Message----- From: owner-toasters@mathworks.com owner-toasters@mathworks.com To: Alan McLachlan alanmac@technologist.com; toasters@mathworks.com toasters@mathworks.com Sent: Sun Oct 28 21:09:20 2007 Subject: RE: VMware / A-SIS
Ummmm.... What ESX CIFS driver?
-----Original Message----- From: Alan McLachlan [mailto:alanmac@technologist.com] Sent: Sunday, October 28, 2007 8:26 AM To: toasters@mathworks.com Subject: VMware / A-SIS
Hi Vaughn,
For small environments on a budget where the cost of additional licenses is an issue, you can use RDM's over iSCSI or FCP for both data LUN's _and_ the VM OS images. You still need VMDK pointer files to enable vmotion.
By using RDM's for the VM images you can use lun cloning for R/W snapshots within the same FlexVol, without paying for a FlexClone license and achieve a reasonable level of deduplication without paying
for an A-SIS licence. i.e. create "golden images" as source LUNs then use lun clones for the prod, dev, test and backup images of the VM's.
However, for larger environments using vmdk's on NAS from NFS exports or CIFS shares for the VM images is a far more scalable and manageable
solution as long as you're happy to pay for A-SIS to manage deduplication. I still wouldn't be putting data volumes inside the vmdk's though.
(Yes, you can use CIFS for vmdk's in ESX. Not as ideal as NFS for a whole bunch of reasons, but it works via the VMWare ESX CIFS driver and useful if you have to have CIFS for file server consolidation and don't want to pay for NFS licencing as well).
Either way, storing your application data in either RDM LUN's or as direct NAS shares makes managing snapshots for dev/test copies and online backups of the production data much simpler to manage. Putting data inside vmdk's limits your functionality particularly for backups.
MSCS requires an RDM for the quorum disk, but you can still use a NAS share for the data if your data profile and application characteristics indicate that it makes more sense to do that than use an RDM for the data.
regards,
Alan McLachlan.
-----Original Message----- From: owner-toasters@mathworks.com on behalf of M. Vaughn Stewart Sent: Sun 10/28/2007 8:07 AM To: Jack Lyons Cc: Page, Jeremy; toasters@mathworks.com Subject: Re: A-SIS questions
FlexClone will clone a datastore, for VM level cloning granularity you
gonna have to wait I think something is just around the corner.
As for MSCS you need RDMs as VMDKs are not supported with MSCS
RDMs can be either FCP or iSCSI VMDKs can be on NFS or VMFS (which is over FCP or iSCSI)
-- Want an e-mail address like mine? Get a free e-mail account today at www.mail.com!
This e-mail (including all attachments) is confidential and may be
privileged.
It is for the exclusive use of the addressee only. If you are not the addressee, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its
attachments and notify us immediately at help@generalatlantic.com mailto:help@generalatlantic.com. Thank You.
-- 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:
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.
----- Original Message ----- From: "Learmonth, Peter" Peter.Learmonth@netapp.com To: "Alan McLachlan" alanmac@technologist.com, toasters@mathworks.com Subject: RE: VMWare CIFS driver Date: Sun, 28 Oct 2007 19:10:27 -0700
Hi Alan Would you happen to have a URL instead of a IP address?
Given that this comes from an unidentifiable web site, I highly doubt this will get any support from VMware, and I can pretty much guarantee that this will get no support from NetApp.
More on the RPM itself... It contains only an object module, which appears to install in the service console Linux, not the VMKernel, although I could be wrong on that.
The version on that RPM matches the ESX 3.0.1 COS Linux kernel 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 some surprises when the storage fails over and CIFS drops the connections. It doesn't make any difference whose CIFS server you're using. I personally don't think VMware should waste any time developing an ESX kernel client.
Thanks anyway.
Peter
-----Original Message----- From: Alan McLachlan [mailto:alanmac@technologist.com] Sent: Sunday, October 28, 2007 4:24 PM To: toasters@mathworks.com Subject: VMWare CIFS driver
Hi,
Find it here:
http://89.105.41.70/sites/esx/Lists/Posts/Post.aspx?ID=1
Enjoy!
regards,
Alan McLachlan
----- Original Message ----- From: "Davies,Matt" MDAVIES@generalatlantic.com To: Peter.Learmonth@netapp.com, alanmac@technologist.com, toasters@mathworks.com Subject: RE: VMware / A-SIS Date: Sun, 28 Oct 2007 21:48:16 -0000
I was about to ask the same question.....
-----Original Message----- From: owner-toasters@mathworks.com owner-toasters@mathworks.com To: Alan McLachlan alanmac@technologist.com; toasters@mathworks.com toasters@mathworks.com Sent: Sun Oct 28 21:09:20 2007 Subject: RE: VMware / A-SIS
Ummmm.... What ESX CIFS driver?
-----Original Message----- From: Alan McLachlan [mailto:alanmac@technologist.com] Sent: Sunday, October 28, 2007 8:26 AM To: toasters@mathworks.com Subject: VMware / A-SIS
Hi Vaughn,
For small environments on a budget where the cost of additional licenses is an issue, you can use RDM's over iSCSI or FCP for both data LUN's _and_ the VM OS images. You still need VMDK pointer files to enable vmotion.
By using RDM's for the VM images you can use lun cloning for R/W snapshots within the same FlexVol, without paying for a FlexClone license and achieve a reasonable level of deduplication without paying
for an A-SIS licence. i.e. create "golden images" as source LUNs then use lun clones for the prod, dev, test and backup images of the VM's.
However, for larger environments using vmdk's on NAS from NFS exports or CIFS shares for the VM images is a far more scalable and manageable
solution as long as you're happy to pay for A-SIS to manage deduplication. I still wouldn't be putting data volumes inside the vmdk's though.
(Yes, you can use CIFS for vmdk's in ESX. Not as ideal as NFS for a whole bunch of reasons, but it works via the VMWare ESX CIFS driver and useful if you have to have CIFS for file server consolidation and don't want to pay for NFS licencing as well).
Either way, storing your application data in either RDM LUN's or as direct NAS shares makes managing snapshots for dev/test copies and online backups of the production data much simpler to manage. Putting data inside vmdk's limits your functionality particularly for backups.
MSCS requires an RDM for the quorum disk, but you can still use a NAS share for the data if your data profile and application characteristics indicate that it makes more sense to do that than use an RDM for the data.
regards,
Alan McLachlan.
-----Original Message----- From: owner-toasters@mathworks.com on behalf of M. Vaughn Stewart Sent: Sun 10/28/2007 8:07 AM To: Jack Lyons Cc: Page, Jeremy; toasters@mathworks.com Subject: Re: A-SIS questions
FlexClone will clone a datastore, for VM level cloning granularity you
gonna have to wait I think something is just around the corner.
As for MSCS you need RDMs as VMDKs are not supported with MSCS
RDMs can be either FCP or iSCSI VMDKs can be on NFS or VMFS (which is over FCP or iSCSI)
-- Want an e-mail address like mine? Get a free e-mail account today at www.mail.com!
This e-mail (including all attachments) is confidential and may be
privileged.
It is for the exclusive use of the addressee only. If you are not the addressee, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its
attachments and notify us immediately at help@generalatlantic.com mailto:help@generalatlantic.com. Thank You.
-- Want an e-mail address like mine? Get a free e-mail account today at www.mail.com!
-
Alan McLachlan -
Learmonth, Peter -
M. Vaughn Stewart -
Milazzo Giacomo