Four new demonstrations using the vSphere Big Data Extensions (BDE) have recently been made available on the VMwareTV area on Youtube for your use. They are all compact (less than 5 minutes in duration). The demos are described below.
BDE Demo #1: Installing and Configuring the vSphere Big Data Extensions
This demonstration shows the process for installing and configuring the vSphere Big Data Extensions feature. This capability is available as a free download with VMware vSphere Enterprise Plus. It allows you to provision Hadoop clusters on to vSphere virtual machines easily and quickly, and to manage them in a flexible way. It also provides a number of elasticity features for scaling your Hadoop virtual machines up or down automatically or manually.
I’ve had a number of requests for recommendations on the “best way” to restrict access to the ESXi host console. While this is easily done using the ESXi Lockdown Mode feature I’m finding there are some admins who are still under the impression that lockdown mode doesn’t work, and in order to prevent access to the host console you need to disable the console service. While there were some challenges with lockdown mode in the past, things changed in ESXi 5.1.
Over the last few months, many customers have been testing and familiarizing themselves with vSphere 5.5 however deployment into a production environment is usually stalled until the availability of the first update or service pack. As we are nearing the typical time frame of when such an update or service pack may become available, I wanted to share some findings that may affect your deployment selection of vCenter Single Sign-On when deploying or upgrading to vCenter Server 5.5
During the installation of vCenter Single Sign-On server you are asked on the deployment option of the vCenter Single Sign-On instance. Below is the intended use case for each deployment option.
You have probably heard the terms “Big Data” and “Hadoop” mentioned somewhere in the industry lately – they are both very popular subjects of discussion at the moment. This blog gives you an introduction to the core technology and explains some of the contributions that VMware continues to make to the Hadoop world.
I’m often asked if you can use vCenter Server Heartbeat to protect the Auto Deploy Server. The answer is yes and I’m happy to announce that we now have some videos and product walkthroughs that show how this is done.
To view the product walkthrough visit http://vmwarewalkthroughs.com and select the recently added vCenter Server Heartbeat section. Here you will see the walkthrough showing how to use vCenter Server Heartbeat to protect your Auto Deploy server.
While VMware highly recommends the deployment of all vCenter Server components into a single virtual machine (excluding the vCenter Server database), large enterprise customers running multiple vCenter Server instances within a single physical location can simplify the vCenter Single Sign-On architecture and management by reducing the footprint and required resources and specify a dedicated vCenter Single Sign-On environment for all local resources in each physical location.
For vSphere 5.5 the VMware recommendation is to centralize vCenter Single Sign-On when you have 8 or more vCenter Server instances in a given location (this is a soft recommendation).
Centralized vCenter Single Sign-On Architecture
Figure 1: A Centralized vCenter Single Sign-On Server environment
There can be increased risk when centralizing a vCenter Single Sign-On server (to why it is not recommended for smaller environments) due to the increased number of components affected if the vCenter Single-Sign-On server was to become unavailable, in short all vCenter Server components of all vCenter Servers registered will incur authentication loss (when compared to just the single vCenter Server instance when installed locally) and so availability of the vCenter Single Sign-On centralized server(s) is highly recommended. Continue reading →
Earlier this week I published an article announcing the availability of the new Havana version of the vSphere OpenStack Virtual Appliance and the vCenter Web Client Plug-in for OpenStack. For those of you that haven’t had the time to deploy the vSphere OpenStack Virtual Appliance and get some hands on experience with these tools and are curious to see the tools in action. The demonstration below showcases the plug-in’s configuration and working examples. The plug-in provides vSphere administrators the ability to identify OpenStack instances in vSphere by mapping the instances and properties information from the OpenStack Horizon portal to vSphere via the vSphere Web Client.
Again, It’s important to point out thatthe vSphere OpenStack Appliance and the vCenter Web Client Plug-in for OpenStack are both non-production tools, for which VMware doesn’t provide any official support.
These tools are made available as a proof of concepts and are design for provide an easy and simplified way for vSphere administrators to work with OpenStack frameworks and vSphere Infrastructures in order to provide a better and clear understanding on how OpenStack integrates with VMware.
The vCenter Web Client Plug-in for OpenStack can be view here at any time or on our VMwareTV channel on YouTube.
Save time and avoid frustration! in this “don’t miss” webinar, learn how Virtual SAN interoperates with Horizon View, vSphere Data Protection Appliance Advance (VDPA), vSphere Replication, Site Recovery manager (SRM), vCloud Automation Center, and OpenStack Framework.
Gain valuable insight from Rawlinson Rivera (@punchingclouds), Senior Architect at VMware for Software-Defined storage and integration products.
Mark your calendar to attend this webinar on Tuesday, at 8:30am PST