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
Folks we are very excited to announce the release of new version of vSphere OpenStack Virtual Appliance (VOVA) based on the new OpenStack Havana release. This release contains several additional improvements over the previous VOVA version based on the Grizzly release. Below are some of the highlights included with the new release:
Single Nova compute node can manage multiple clusters under single vCenter.
VMDK driver for Cinder enables creation of volumes using vSphere datastores. This allows OpenStack Cinder to present block storage from extensive range of storage solutions certified to work with vSphere
Removed the additional VNC password for accessing instances from console in Horizon.
First release of “vCenter Web Client Plugin for OpenStack”. This plugin presents OpenStack inventory directly in the vCenter web client. Admins can view the OpenStack related properties of instances along with traditional vCenter details.
Added support for vSphere Distributed Switch (vDS)
In addition to the features above there are significant stability improvements across all aspects of running OpenStack on VMware. To get started working and testing OpenStack on vSphere visit the VMware OpenStack community page at http://www.vmware.com/go/openstack.
We encourage you to try new VOVA and look forward to your feedback. All documentation for VOVA is available for download in the VMware OpenStack community site.
For future updates, be sure to follow me on Twitter at @PunchingClouds
A minor update to the vCenter Server 5.5 has been released
VMware vCenter Server™ 5.5.0a | 31 OCT 2013 | Build 1378901
vCenter Server Appliance 5.5.0a | 31 OCT 2013 | Build 1398493
Issues resolved with this release are as follows
Attempts to upgrade vCenter Single Sign-On (SSO) 5.1 Update 1 to version 5.5 might fail with error code 1603
Attempts to log in to the vCenter Server might be unsuccessful after you upgrade from vCenter Server 5.1 to 5.5
Unable to change the vCenter SSO administrator password on Windows in the vSphere Web Client after you upgrade to vCenter Server 5.5 or VCSA 5.5
VPXD service might fail due to MS SQL database deadlock for the issues with VPXD queries that run on VPX_EVENT and VPX_EVENT_ARG tables
Attempts to search the inventory in vCenter Server using vSphere Web Client with proper permissions might fail to return any results
vCenter Server 5.5 might fail to start after a vCenter Single Sign-On Server reboot
Unable to log in to vCenter Server Appliance 5.5 using domain credentials in vSphere Web Client with proper permission when the authenticated user is associated with a group name containing parentheses
Active Directory group users unable to log in to the vCenter Inventory Service 5.5 with vCenter Single Sign-On
Attempts to log in to vCenter Single Sign-On and vCenter Server might fail when there are multiple users with the same common name in the OpenLDAP directory service
Attempts to log in to vCenter Single Sign-On and vCenter Server might fail for OpenLDAP 2.4 directory service users who have attributes with multiple values attached to their account
Attempts to Log in to vCenter Server might fail for an OpenLDAP user whose account is not configured with a universally unique identifier (UUID)
Unable to add an Open LDAP provider as an identity source if the Base DN does not contain an “dc=” attribute
Active Directory authentication fails when vCenter Single Sign-On 5.5 runs on Windows Server 2012 and the AD Domain Controller is also on Windows Server 2012
The realese notes can be found here with full details, download now from www.vmware.com
Part of my role at VMware is to work closely with our customers and partners, sharing experiences and feedback with internal VMware Product Management and Engineers to help make our products better. One area that has been dominantly more focused than others over the last 12 months has obviously been vCenter Single Sign-On.
Due to this feedback, one of the drivers for the new vCenter Single Sign-On was to provide backwards compatibility and to highlight this, a recent Knowledge Base article released.