A common question that I have seen recently around Virtual SAN (VSAN) is how limits on number of components, disks, etc., translate into capacity and policy limits. I will attempt to cover some of the basics in this post. However for a deeper explanation on the various sizing and design considerations, please check out the updated Design & Sizing Guide which you can find in the VSAN beta community documents section in the POC Kit folder. If you are not yet signed up for the VSAN beta, why not? Click here to register. The beta community has a wealth of information, including documentation, hardware guidance and some great discussions with our R&D engineers. A great place to start if you just want to read up on Virtual SAN, or indeed, kick its proverbial tires.
Category Archives: vCloud Suite
There is a new beta release of Virtual SAN (VSAN) available today for those of you participating in the beta. You can download the new bits of the beta refresh by clicking here (you will need a valid MyVMware login to access it). This post covers a number of areas around the beta refresh. It will cover how to upgrade to the new release, a fix for the AHCI controller issue that we encountered in the beta testing, the new PowerCLI fling, changes to certain VSAN limits and the winners of some of our VSAN contest and surveys. Read on to learn more about the changes in the VSAN beta refresh.
As an admin in the data center, you have to
- Ensure that your VM templates are up to date
- Maintain a set of scripts for customizing the guest OS’s, installing custom applications, etc.,
- Share all of them across sites and vCenter instances.
Therefore, we at VMware are trying hard to provide you with a simple and efficient solution to manage your VM templates, scripts, ISO images, etc. – collectively called “Content”.
We now need your input to ensure that we understand your current infrastructure, methodologies, and core use cases so that we build the right set of features and for the right scale.
We have kept this survey really short (7 questions) and we’d appreciate you taking the time to provide us your feedback. Thank you!
Survey link: http://bit.ly/vSContentMgmt (updated link)
Today Pivotal announced the availability of Pivotal CF. Jointly developed with VMware, the Pivotal CF product includes a packaged and supported version of the Cloud Foundry open PaaS for VMware vSphere.
In April 2011 VMware first launched Cloud Foundry, an Apache-licensed open source Platform as a Service (PaaS) and an associated vSphere-based public cloud service. A year later, in April 2012, we announced a DevOps toolchain called BOSH, used to deploy and manage Cloud Foundry at scale on virtualized infrastructure. In April 2013 VMware and EMC formed Pivotal, a spinout company using technology from both companies including Cloud Foundry.
VMware’s vision for Cloud Foundry has always been to deliver maximum agility to application developers across both public and private cloud environments. In working with Pivotal to deliver Pivotal CF we have fulfilled that vision, bringing the incredible productivity of Cloud Foundry to vSphere customers.
Since announcing of the release vSphere OpenStack Virtual Appliance (VOVA) earlier this summer at VMworld 2013 there has been a great amount of interest on this project. Since then, I have wanted to create a demonstration for VMware customers and the vSphere administrators interested in working with the OpenStack framework on vSphere. The demonstration below showcases the built-in integration between vSphere and the OpenStack projects Nova and Cinder.
As of today, the vSphere OpenStack Virtual Appliance does not include the configuration for o VMware NSX or Neutron but it is something the Team OpenStack @ VMware is looking into for future updates. It is important to know and understand the vSphere OpenStack Virtual Appliance is not an official VMware product, but only a proof of concept appliance for which VMware does not provide any official technical support. Please visit the VMwareTV YouTube channel for more OpenStack + vSphere demos in the future.
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
- 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
Please take a few minutes to fill out this Software Defined Datacenter survey and take advantage for an opportunity to influence the development of VMware products and services by providing your opinion and help us improve our products and services. As we plan for our next generation platform features, we would like to know more about you and the way you automate your datacenter.
For VMware, the future is all about the Software Defined Datacenter (SDDC). Integral to the SDDC vision is automation and policy. We are currently conducting a survey to see how our customers are doing in their journey to the SDDC. Your input will be critical as we take the next step down the road to the full realized SDDC.
The survey will take you no more than five minutes, thank you for your help and support.
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.
I was a little surprised how quickly these went live but can now share the VMworld vCenter Deep Dive and vSphere Upgrade series: Part 1 – vCenter Server breakout sessions from last weeks VMworld in Barcelona where my sessions were recorded and are now available for your viewing pleasure.
vCenter Deep Dive
vSphere Upgrade series Part 1: vCenter Server
We periodically survey our customers to try to understand how you use our products and to help us when developing new features. We are currently surveying SRM customers and would appreciate it if you could take approximately 10-15 minutes to share your feedback and thoughts about SRM.