samedi 20 août 2011

Nexentastor 3.1.1, mais que reste-t-il aux grands ?

La sortie de NexentaStor 3.1.1 frappe un grand coup avec l'intégration des fameuses VMware‟s vStorage API for Array Integration (VAAI) d'ESXi 5.0 chargées de faire de l'offload pour le stockage. Bien entendu, si vous utilisez l'appliance Nexenta en VM sur un serveur non dédié, l'intérêt sera plus limité puisque la CPU du serveur sera de toute façon mise à contribution.

Reprise de la release note au sujet de VAAI :

-SCSI Write Same: When creating a new virtual disk VMware must write‟s zeros to every block location on the disk. This is done to ensure no residual data exists on the
disk which could be read by the new VM. Without Write Same support the server‟s CPU must write each individual block which consumes a lot of CPU cycles. With the Write Same command VMware can direct the storage array to perform this function, offloading it from the CPU and thereby saving CPU cycles for other operations. This is supported in ESX/ESXi 5.0 and later.

- SCSI ATS: Without ATS support, when VMware clones a VM it must lock the entire LUN to prevent changes to the VM while it is being cloned. However, locking the entire LUN affects all other VM‟s that are using the same LUN. With ATS support VMware is able to instruct the array to lock only the specific region on the LUN being cloned. This allows other operations affecting other parts of the LUN to continue unaffected. This is supported in ESX/ESXi 5.0 and later.

- SCSI Block Copy: Without Block Copy support, cloning a VM requires the server CPU to read and write each block of the VM consuming a lot of server CPU cycles. With Block Copy support VMware is able to instruct the array to perform a block copy of a region on the LUN corresponding to a VM. This offloads the task from the server‟s CPU thereby saving CPU cycles for other operations. This is supported in ESX/ESXi 5.0 and later.

- SCSI Unmap: Provides the ability to return freed blocks in a zvol back to a pool. Previously the pool would only grow. This enables ESX to destroy a VM and return the freed storage back to the zvol. ESX 5.0 and later support this functionality.

Toutes ces fonctionnalités sont reprises dans la version gratuites limitée à "seulement" 18To Comme quoi il est bon de stocker ses VMs dans le girafon.

Aucun commentaire: