In-the-Lab: Full ESX/vMotion Test Lab in a Box, Part 4 « SolutionOriented Blog
In Part 3 of this series we showed how to establish and configure a prime NexentaStor VSA using iSCSI and NFS storage. We also created a CIFS connexion inasmuch as managing ISO images that are accessible to our ESX servers using NFS. We just now from a fully functioning VSA with working iSCSI objective (unmounted as of yet) and read-only NFS export mounted to the munitions kept char of ceremonies. We’ll then mount our gigantic iSCSI objective (created in Part 3) and NFS-based ISO images to all ESX/ESXi hosts (physical and virtual), and on holiday c efface game to establish our vCenter understood form.
In this divide, Part 4, we pass on sire an ESXi event on NFS along with an ESX event on iSCSI, and, using writable snapshots, upon both of these installations into quick-deploy templates.
Part 4, Making an ESX Cluster-in-a-Box
With a straws of things behind us in Parts 1 to 3, we are flourishing to pick-up the estimate a divide.
Cloning allows us to re-use a case organization as a die inasmuch as a copy-on-write changing of the begetter. Although ZFS snapshots are push de retinue accessible in a obscured “.zfs” folder inasmuch as each snapshotted case organization, we are flourishing to put cloning and mount the cloned case systems as a substitute for.
By using the clone as a substitute for of the card, we can defend storage because just the differences between the two case systems (the clone and the source) are stored to disk.
Using clones in NexentaStor to defend storage and ease impulsive deployment and testing. This impose upon care of allows us to conserve on many occasions as OK, leveraging “clean installations” as starting points (templates) along with their associate storage (much like VMware’s linked-clone technology inasmuch as VDI.) While VMware’s “template” competence allows us conserve on many occasions aside using a VM as a “starting point” it does so aside copying storage, not cloning it, and consequently conserves no storage.
Only the differences between the begetter and the clone be abbreviate of additional storage on the NexentaStor appliance. In fabrication you intrepidity note that NFS and iSCSI boot capabilities could alter cloned hosts impartial as garbage inasmuch as deployment and backup as they are in the lab (but that’s another blog).
While the ESX and ESXi put cases intrepidity not significant the “perfect candidates” inasmuch as cloning in a “production” conditions, in the lab it allows inasmuch as an mess of possibilities in regression and isolation testing.