On Jul 1, 2009, at 10:58 PM, Brent Jones <br...@servuhome.net> wrote:
On Wed, Jul 1, 2009 at 7:29 PM, HUGE | David
Stahl<dst...@hugeinc.com> wrote:
The real benefit of the of using a separate zvol for each vm is the
instantaneous cloning of a machine, and the clone will take almost no
additional space initially. In our case we build a template VM and
then
provision our development machines from this.
However the limit of 32 nfs mounts per esx machine is kind of a
bummer.
-----Original Message-----
From: zfs-discuss-boun...@opensolaris.org on behalf of Steve Madden
Sent: Wed 7/1/2009 8:46 PM
To: zfs-discuss@opensolaris.org
Subject: Re: [zfs-discuss] ZFS, ESX ,and NFS. oh my!
Why the use of zvols, why not just;
zfs create my_pool/group1
zfs create my_pool/group1/vm1
zfs create my_pool/group1/vm2
and export my_pool/group1
If you don't want the people in group1 to see vm2 anymore just zfs
rename it
to a different group.
I'll admit I am coming into this green - but if you're not doing
iscsi, why
zvols?
SM.
--
Is there a supported way to multipath NFS? Thats one benefit to iSCSI
is your VMware can multipath to a target to get more speed/HA...
Yes, it's called IPMP on Solaris.
Define two interfaces in a common group with no failover (used to
probe network failures) then define any number of virtual interfaces
on each and if one interface goes down the virtual interfaces will
fail-over to the other physical interface. It will also do load
balancing between them, or you can create a LAG which does redundancy
and load balancing.
-Ross
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
