Wednesday 20 December 2017

VMware to Focus on its Multi-Cloud Management Platform in 2018


Our Warning Board individuals think back on VMware's advance in 2017 and offer forecasts for the organization's future in cloud, systems administration and security. 

VMware demonstrated in 2017 that it has made some amazing progress from its virtualization roots. After a couple of false begins, it appears to have at long last discovered its specialty in the cloud showcase, thanks in no little part to the organization's profitable association with Amazon Web Administrations. All signs point to proceeded with development and advancement toward this path as VMware attempts to end up noticeably a multi-cloud administration stage. 

It was likewise an important year for VMware organizing with the arrival of both NSX-T for non-vSphere situations and NSX as an administration. In light of these advancements, it's winding up progressively obvious that NSX will assume a crucial part in VMware's item portfolio later on, and that it could even move toward becoming, as VMware Chief Pat Gelsinger guaranteed at VMworld 2017, "the following vSphere." 

SearchVMware approached its Warning Board individuals for their musings on VMware's year and what could be likely to work out for VMware in 2018. 

Stuart Consumes, virtualization and Linux master

By and large, this has been a decent year for VMware - far superior to expected, as I would like to think. At first glance, there's a considerable measure of new stuff happening, including another NSX-T dispatch and highlight increases to VMware Cloud on AWS. 

NSX is the gem in the crown of the VMware arms stockpile since, so far as I'm mindful, no other organization has anything remotely comparative, and it gives all the usefulness a security and system chairman could want. 

VMware's association with Amazon Web Administrations (AWS) and the consequent arrival of VMware Cloud on AWS made for the greatest news of the year. VMware Cloud on AWS - which is at long last by and large accessible - is a VMware cloud on AWS equipment. VMware deals with all the client confronting things. 

Despite the fact that VMware Cloud on AWS is a decent item, as I would like to think, it's still more costly than it should be. So, I speculate the cost will descend after some time. 

VMware affiliates have thought of their own interpretation of VMware in the cloud, yet rather utilize two figure hubs and System Document Framework stockpiling, which lessens the passageway cost into the cloud. This technique requires at least three hubs due to the vSAN prerequisite of VMware Cloud on AWS. 

From a business point of view, VMware has played its hand well and is fashioning vital associations to suit its interests. It is VMware's expectation that these connections will enable it to end up noticeably the paste that empowers cloud portability, a striking yet fascinating thought. Regardless of the naysayers, numerous clients have really expanded their VMware homes over the previous year. 

The huge concentration for VMware in 2018 and past is to build up a predictable multi-cloud administration stage. Medium and expansive organizations are embracing mixture cloud as their default setup at a developing rate, and they are utilizing numerous stages to deal with their surroundings. This is an issue since utilizing diverse stages to oversee multi-cloud situations is an exercise in futility and assets, and it leaves a cloud frameworks executive with more stages to learn and possibly investigate. 

Another real territory of center - one that has been generally tranquil in virtualization news for reasons unknown - is computerization. Robotization devices, for example, vRealize Mechanization, give a scaffold between moderately basic organizations, which any frameworks overseer can do, and an all out entrance understanding. 

In spite of the fact that mechanization requires critical forthright venture, it streamlines the sending procedure while keeping up effortlessness and comfort for the end client. In extra to building up a multi-cloud administration stage, I speculate this is another territory in which VMware will keep on growing in 2018.

Thursday 6 April 2017

VCP5-DCV Sample Question

Question: 21

An ESXi 5.x host displays a warning icon in the vSphere console and its summary page lists a configuration issue "SSH for the host has been enabled." What are two ways to clear this warning? (Choose two.)

A. Using the Security Profile pane of the Configuration tab in the vSphere Client
B. Using the Direct Console User Interface (DCUI)
C. Using the Advanced Settings pane of the Configuration tab in the vSphere Client
D. Using the Networking pane of the Configuration tab in the vSphere Client

Answer: A,C

Wednesday 8 February 2017

VCP5-DCV Sample Question

Question: 20

Under which two conditions can vStorage APIs for Array Integration (VAAI) provide a performance benefit? (Choose two.)

A. When a virtual disk has VMDK files stored on an NFS datastore.
B. When a virtual disk is created using the New Virtual Machine wizard.
C. When cloning a virtual machine with snapshots.
D. When a virtual disk is deleted.

Answer: AD

Explanation:

A) With NFS, the default is alway thin provisioned. Provisioning there should not have much benefit from VAAI offloads, except when you are not creating a thin disk. In that case, you utilize the "space reservation" function of VAAI, which allows you to create an EZT disk, but that doesn't really mean I am creating the disk a lot faster. Actually, I'm not offloading the writing of zeroes at all via NFS, so performance is not the key part of this VAAI function.

B) The answer doesn't tell met what option is selected, regardless of the option I choose, I can either use features like for example ATS or Write-Same, depending on which type of disk I'm provisioning (obviously this applies to block storage).

C) VMware KB 1021976 clearly states "VAAI hardware offload cannot be used when: [..] Cloning a virtual machine that has snapshots (or doing a View replica or recompose), because this process involves consolidating the snapshots into the virtual disks of the target virtual machine". So this answer isn't correct in my opinion.

D) You should distinguish between the deletion of an entire disk, and the space reclaim function for thin provisioning (TP Unmap) which is covered by Cormac here: The Unmap primitive was actually introduced with vSphere 5.0, and did include the feature that, when a VM was vMotioned to a different disk, or a VM was deleted, Unmap would reclaim the space. Unfortunately, they noticed that this could cause a performance problem, and they disabled the primitive the vSphere 5.0 patch 2. They then re-enabled it, but as a manual process with vSphere 5.0U1.

Sunday 1 January 2017

VCP5-DCV Sample Question

Question: 19

An administrator is troubleshooting an ESXi 5.x host and needs to export diagnostic information. The host is currently managed by a vCenter Server instance. Which two ways can the information be gathered using the vSphere Client? (Choose two.)

A. Select Home. Under Administration, click System Logs and click the Export System Logs button. Select the affected ESXi host. Select Select All. Select a location and click Finish.
B. In the vSphere Client, select the affected ESXi host. Right-click the host and select Export Diagnostic Data. Select a location and click OK.
C. Log in to the ESXi host locally, Select Export System Logs.
D. In the vSphere Client, select the affected ESXi host. Select File, Export and Export System Logs. Select Select All. Select a location and click Finish.

Answer: A,D

Explanation:

You can collect information by selecting Home. Under Adminstration, click System logs and click export system logs button. Select the affected ESXi host. Select Select All. Select a location and click Finish. To export system logs from the ESXi host, the alternative way is to select the affected ESXi host in vSphere client. Select File, Export and Export System Logs. Select Select All. Select a location and click Finish.