The VMware Mobile Knowledge Portal iOS and Android app has recently been updated. It sports a great new look and feel and makes finding the information you need even easier by grouping it by area in our SDDC vision.
Category Archives: vCloud Suite
When I joined the Technical Marketing team last September I was tasked with vCenter Availability and Scalability along with providing coverage for all things vCenter and SSO.
Since that time I’ve branched out and am also covering Resource Management (more on this coming soon!) and also features in the Enterprise Plus SKU. I’m really excited about this as to this day one of my favorite and I feel underused features is the vSphere Distributed Switch, or VDS.
VMware vSphere Mobile Watchlist allows you to monitor the virtual machines you care about in your vSphere infrastructure remotely on your phone. Discover diagnostic information about any alerts on your VMs using VMware Knowledge Base Articles and the web. Remediate problems from your phone by using power operations or delegate the problem to someone on your team back at the datacenter.
IMPORTANT NOTE: A VMware vSphere installation (5.0 and above) is required to use VMware vSphere Mobile Watchlist. Access to your vSphere infrastructure may need a secure access method like VPN. Contact your IT department for further assistance.
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
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
Folks! it’s finally here. The first official Getting Started OpenStack and VMware vSphere White Paper. This paper is focus around the ease of deployment and integration of OpenStack frameworks onto vSphere environments with VMware’s Virtual OpenStack Virtual Appliances (VOVA). This guide provides logical diagrams showcasing the different OpenStack Projects VMware vSphere currently integrate with. Included are also a few procedures and examples on how to get you stated playing with OpenStack on vSphere quickly.
vSphere has a long history of being a stable and resilient platform that offers many benefits to host cloud infrastructures. As an enterprise-class hypervisor with production-level features and support, vSphere is an excellent solution for enhancing OpenStack. Many vSphere features facilitate the implementation of OpenStack by simplifying configuration and reducing the number of steps required to provide resources.
vSphere platform capabilities are exposed to OpenStack using drivers that map OpenStack requests into equivalents that VMware solutions can interpret. VMware provides these drivers to the OpenStack community free of charge. Drivers for Cinder and Nova. Significant effort is being applied to the creation of additional drivers, such as one that leverages VMware NSX™ to provide advanced networking functionality via Neutron.
Feel free to download the white paper directly through this link or from the VMware technical papers resource page. For the latest and greatest information about any related OpenStack and VMware vSphere related information please visit the VMware OpenStack community site.
For future updates, be sure to following me on Twitter: @PunchingClouds
For those of you using array based replication with SRM, here’s some good news that came out of the holidays:
SRM can now support up to 1500 protected virtual machines!
There is, of course, a caveat or two about which you must be aware. First, it will only work with VC/SRM/vSphere all at 5.5 and even then you must be using a very specific patch release of vSphere 5.5.
If these criteria are not met the old limit of 1000 VMs is still in place. This also does not increase the total number of VMs you can protect with vSphere Replication; that limit stays at 500. You can however mix and match. For example if you are using both array replication and vSphere Replication, and have ESXi patched as above, you could choose to protect up to 1500 VMs with say 1000 array protected and 500 VR protected, or 1250 array and 250 VR, and so forth up to the maximum of 500 VR will support and the 1500 ABR will support. The point is the total needs to stay below 1500 and the VR number below 500.
So that’s some exciting news, increasing the scale of the total number of protected VMs by 50%! Make sure you go read the KB article detailing operational limits for SRM before you change anything, and make sure you understand both the prerequisites and the supported totals.
Happy new year!
One question that we often get from customers is how to load balance SSO. While we do have documentation and support for setting up Apache to load balance SSO many customers already own a load balancer or do not wish to use Apache.
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.
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)