In our last article we demonstrated how to use the new vSphere PowerCLI 5.8 SPBM cmdlets to create vSphere Storage Policies. In this article we will demonstrate how to quickly associate a vSphere Storage Policy with a new or existing VM.
Example Provisioning Scenario
To illustrate how to leverage PowerCLI to associate vSphere Storage Policies with VMs we will continue with the provisioning example from our previous article.
Single virtual disk
Virtual SAN datastore
Follow these links for more information on creating vSphere Storage Policies for Virtual SAN:
Previously in order to create, manage, and associate vSphere Storage Policies with VMs using PowerCLI, one would need to leverage an intermediary method as well (e.g. Esxcli, RVC, REST API, etc). Often this could require the use of third party applications to bridge the gap in interfacing with the vSphere Storage Policy Based Management service. This resulted in added complexities and additional processing time for workflows that were automated with PowerCLI.
With the new PowerCLI 5.8 cmdlets for vSphere Storage Policy Based Management we are able to greatly reduce the complexity of vSphere Storage Policies with PowerCLI now by using PowerCLI exclusively. In the example below, we will demonstrate how to enhance the VM provisioning process by associating a vSphere Storage Policy with a virtual machine.
One of the relatively newer use cases for SRM is planned migration. With this use case, customers can migrate their business critical workloads to the recovery or cloud provider sites in a planned manner. This could be in planning for an upcoming threat such as a hurricane or other disaster or an actual datacenter migration to a different location or cloud provider. Continue reading →
Big Data Extensions enables the deployment of Hadoop and HBase clusters in virtual machines on the VMware vSphere platform. This article gives you a brief introduction to the new features in BDE version 2.1. BDE ships as a virtual appliance (an OVA file) and it is a free download for users of vSphere Enterprise or Enterprise Plus.
BDE users are interested in using their favorite management tools from their Hadoop distro vendors, along with BDE and vCenter, to manage their newly created virtualized Hadoop clusters. The 2.1 release of BDE implements this feature in an elegant way!
Now you can use BDE and Cloudera Manager or Ambari together to install and manage your Hadoop clusters without leaving your Web Client BDE seat. You can also use the earlier styles of provisioning a Hadoop cluster as shown under the “BDE Only” and “BDE 2.0″ headings below. The first method on the left allows BDE to use a repository to install the Hadoop vendor’s software on to the virtual machines. BDE does the whole job of provisioning everything in this case – hence referred to as “BDE Only”.
Using BDE 2.0 (shown in the center column) you can create a basic cluster, i.e. one with no Hadoop software in it. Then you can use the Hadoop vendors’ installation and configuration tool to install the Hadoop software on those virtual machines. With BDE 2.1 you don’t have to go between the different tools; the full Hadoop installation can be done inside BDE’s user interface, but using the vendor’s APIs under the covers to do that. The difference between the BDE 2.0 and 2.1 methods is that in 2.1 the management tool from the Hadoop vendor is called by BDE directly.
Welcome to part 2 of the vSphere Storage Policy Based Management Overview. In our previous article, we looked at challenges with traditional storage provisioning models, the advantages of the Software-Defined Storage model, as well as an introduction and background to VMware vSphere Storage Policy Based Management. If you have not yet had opportunity to read it, it might be beneficial to glance through before continuing on.
In today’s article, we will be carrying on with the vSphere Storage Policy Based Management (SPBM) theme as we look to understand the components of the vSphere Storage Policy. Afterwards we will display a few policy examples for single VM provisioning and options for a collection of VMs as well.
With this release, we now have the ability to interface with the vSphere Storage Policy Manager through the addition of the new VMware.VimAutomation.Storage snap-in. This snap-in provides PowerCLI cmdlets that let you manage vSphere policy-based storage from the PowerCLI command line or by automating through PowerCLI scripting.
In this blog series we will look to provide indepth coverage along with real-world scripting examples for each of the cmdlets. All scripts provided will be examples only and unsupported however I do validate each script with great scrutiny in multiple testing environments so you may not require much adaptation, if any, if you choose to leverage them in your own environments. As always, please ensure all coding is validated in a non-production environment prior to production deployment.
Learn about how customers are rapidly adopting Pivotal CF on VMware, the enterprise Platform-as-a-Service (PaaS) that enables customers to experience turnkey PaaS capabilities on familiar vSphere and now vCloud Air environments.
Jointly hosted by VMware and Pivotal, the speakers are:
Jay Marshall, who is a Principal Cloud Development Strategist at VMware, who has spent almost 20 years working in enterprise application development and specializes in next generation application architecture on VMware’s vCloud Air cloud platform.
Rosie Pongracz, who leads Pivotal CF and PaaS Product Marketing at Pivotal, with over 20 years of experience bringing enterprise technology to market.
A few days ago there was an announcement on some security vulnerabilities potentially affecting Linux based machines (see here: VMware Security Advisory). Well, today we announced the availability of more patches for various versions of VMware Orchestrator here: VMware Orchestrator Express Patch.
Please refer to the knowledge base articles above for steps to upgrade and/or patch your current systems that may be vulnerable. Note that if you are running VMware Orchestrator installed on Windows, this machine is not impacted by this vulnerability.
Check here for the download page for these relevant patches.
In August 2014, Unisphere Research fielded a study among the members of the Independent Oracle Users Group (IOUG) to examine the current state of Oracle database sites, including the key issues, priorities and solutions being adopted by organizations. A total of 338 qualified responses were collected and analyzed. Respondents came from organizations of all sizes and across various industries. The survey was commissioned jointly by EMC2 and VMware. The sponsors of the survey were not revealed to the respondents.
Below are few of the highlights/excerpts:
VMware vSphere is used for virtualizing Oracle environments substantially more than all other virtualization solutions combined (57% of organizations reported using VMware vSphere, followed by Oracle VM, reported by 9% of organizations). The use of vSphere for Oracle software, while widespread, has been increasing in the last few years, with almost two-thirdsof organizations reporting increases over the past year.
Although many respondents report that the top objection to virtualization is the potential for increased license costs, over 50% of respondents report that cost reduction is a primary benefit of their virtualization effort. A reasonable inference to this finding is that the potential increased licensing costs are more perception than reality, as suggested by reports of organizations with virtualization efforts experiencing significant aggregate cost reductions.
Apart from reduced costs, the most common benefits that organizations report as a result of using virtualization within their Oracle database environments are
Consolidation (54% of respondents)
Standardization of infrastructure (47%)
Greater agility (39%)
Increased automation/reduced provisioning times (26%)
Welcome to another episode of our Virtual SAN Troubleshooting series. In our last article we detailed guidelines and troubleshooting steps around the Virtual SAN networking requirement for layer 2 multicast. In today’s article we will show you how to quickly automate the modification of the Virtual SAN multicast group address in the event the need arises.
PowerCLI 5.8 release 1
- (Note: It is likely to work with PowerCLI version 5.5 or above however I just happened to have version 5.8 on my test system).
Hello and welcome to the Virtual SAN Troubleshooting blog series. This series of articles is dedicated to and driven by requests from you our readers. Today we will be focusing upon one of our most requested troubleshooting topics, Layer 2 Multicast functionality from the Virtual SAN Networking requirements.
You are probably familiar with the Virtual SAN networking requirement of Layer 2 Multicast but today we would like to discuss why Virtual SAN leverages multicast forwarding for a portion of its network traffic as well as provide troubleshooting steps when it seems as though multicast traffic is not being received by the Virtual SAN VMkernels. The goal of this article is to educate the networking novice as well as provide clarification for the networking experts so we will be taking a thorough, ground up approach for our discussion.
Click the link if you need to jump directly to the testing examples Testing Multicast functionality. You will also want to make sure that you are following the guidelines below.