Category Archives: vCloud

Awarded vExpert Cloud – A New vExpert Sub Program

Last week Corey Romero announced the inaugural members of the vExpert Cloud sub-program. This is the third vExpert sub-program following the vSAN and NSX programs announced last year. There are 135 initial vExpert Cloud members who have been awarded the title. As it so happens I am now a member of all three which reflects on the focus I’ve had and still have around VMware’s cloud, storage and networking products leading up to and after my move to Veeam last year.

Even with my move, that hasn’t stopped me working around these VMware vertices as Veeam works closely with VMware to offer supportability and integration with vCloud Director as well as being certified with vSAN for data protection. And more recently as it pertains specifically to the vExpert Cloud program, we are going to be supporting vCloud
Director in v10 of Backup & Replication for Cloud Connect Replication and also at VMworld 2017 we where announced as a launch partner for data protection for VMware Cloud on AWS.

For those wondering what does it take to be a part of the vExpert Cloud program:

We are looking for vExperts who are evangelizing VMware Cloud and delivering on the principles of the multi-cloud world being the new normal. Specificity we are looking for community activities which follow the same format as the vExpert program (blogs, books, videos, public speaking, VMUG Leadership, conference sessions speaking and so on).

And in terms of the focus of the vExpert Cloud program:

The program is focused on VMware Cloud influencer activities, VMware, AWS and other cloud environments and use of the products and services in way that delivers the VMware Cloud reality of consistency across multi-cloud environments.

Again, thank you to Corey and team for the award and I look forward to continuing to spread the community messaging around Cloud, NSX and vSAN.

Released: vCloud Director 8.10 and 8.20 Point Updates

Last week VMware snuck out two point releases for vCloud Director 8.10 and 8.20. For those still running those versions you now have 8.10.1.1 (Build 6878548) and for 8.20 there 8.20.0.2 (Build 6875354) available for download. These are both patch upgrades and resolve a number of bugs, some of which appear to be mirrored in both versions.

Scanning the Release Notes, below are some of the more notable fixes:

8.10

  • Resource limit change for a vCloud Edge Gateway Resolves an issue where the memory limit for a compact and full-4 Edge Gateway was insufficient. Memory was increased from 512MB to 2048MB
  • Performing hardware changes to a VM fails Resolves an issue where performing hardware changes to a VM in vCloud Director fails with an error message:
  • Degraded performance due to insufficient memory Resolves an issue that could lead to an insufficient memory reservation of the NSX Edge VMs, which might cause poor performance.
  • Catalog synchronization failure Resolves an issue where synchronization of a remote catalog item fails with an out of memory, causing the vCloud Director cell to crash.

8.20

  • Incorrect status update for VMs storage profile or disk-level storage Resolves an issue that could cause a VM storage profile or disk-level storage profile to be updated incorrectly when the VM is included in a recompose operation. This fix ensures that PvdcComputeGuaranteeValidator runs even when the deployment fails in Pay-As-You-Go allocation model. With this fix, the undeploy workflow ignores the VM deployment state if the undeploy operation is called with a force=true flag.
  • Failure to move virtual machines between shared datastores Resolves a storage issue where moving a virtual machine from one shared datastore to another fails.
  • Failure to revert VM snapshots Resolves an issue that could cause reverting to a virtual machine snapshot to fail
  • Failure to allocate an external IP address and a gateway IP address Resolves several issues in managing the allocation of external IP a gateway IP addresses during VM boot and runtime when the NAT service is enabled and IP Translation is set manually.
  • Failure to delete Organization VDC Resolves an issue that could cause various operations to fail.

So a small point release for good to see the team continuing to improve the platform for those not yet able to upgrade to the latest 9.0 release. If you have the entitlements, head to the MyVMware site to download the builds.

References:

http://pubs.vmware.com/Release_Notes/en/vcd/81011/rel_notes_vcloud_director_8-10-1-1.html

http://pubs.vmware.com/Release_Notes/en/vcd/82002/rel_notes_vcloud_director_8-20-0-2.html

vCloud Director 9.0: Digging into the new Standalone VM Feature

vCloud Director 9.0 was released late last month and brought with it a number of big new features and enhancements. If you are interested in a overview of what’s new, head here to my launch post. Getting back to this post I wanted to focus on what I think is a significant change to the way in which workloads are thought about in vCD…the Standalone VM.

Standalone Virtual machines can be instantiated and viewed along with virtual machines as part of a vApp container. A filter button creates a list based on Virtual machines, virtual applications or both.

The vApp container construct in vCloud Director carries divided opinion from both services providers and customers of vCD with one side liking the fact that VMs could be grouped into logical vApps and treated as a like group or VMs such as an Exchange Cluster. While others wanted the ability to deploy standalone VMs that where more like VM instances you find in public clouds. Historically from a programatic point of view the creation of a VM within a vApp had it’s challenges in a chicken and egg type of scenario where by the composition and recomposiontion of the VM within the vApp required a specific order. This was improved from 8.0 with enhancements to vApp functionality, including the ability to reconfigure virtual machines within a vApp, and network connectivity and virtual machine capability during vApp instantiation.

Standalone Virtual Machines:

In vCloud Director 9.0 you can now create and configure individual Virtual Machines form the new HTML5 Tenant UI. Under the compute menu you now have a Virtual Machines and vApps tab. From here you can view either standalone VMs, VMs in a vApp or both. This is also where you can create a new VM. Note that you can’t create new vApps from the new UI just yet…that still needs to be done in the Flash based UI.

You now have the ability to choose from three pre-canned instance sizes which come with default resources depending on the type of VM selected. However you can still customize the VM as shown below.

When provisioned the VM is available from the new tenant UI with all the normal operations possible. The biggest difference here is that you don’t need to worry about the vApp state and that it’s independent from any other VMs. As a side note as it’s not 100% obvious, to view the console of the VM click on the icon top right of the Virtual Machine box.

Standalone VMs in vCenter and Flash UI:

Taking a look under the covers of the HTML5 UI the standalone VMs are represented slightly differently in vCenter. in Previous versions each VM was created with the VM name plus a UUID…when a standalone VM is created the VM name is just that…the VM name.

However what is interesting is when you look in the Flash UI you will see that in fact the standalone VM is still contained within a vCD vAPP construct.

So in effect, that HTML5 UI is presenting the VM as standalone, but in actual fact there is still a one to one relationship with a vApp under the covers. Taking a look back in vCenter under the folder view it’s more representative of what you see in the Flash UI.

Standalone VMs via the API:

Querying the API shows that the Standalone VMs are indeed composed within a traditional vCD vApp.

References:

https://docs.vmware.com/en/vCloud-Director/9.0/rn/rel_notes_vcloud_director_90.html

Enabling, Configuring and Viewing Metrics in vCloud Director 9.0

Last week I released a post on configuring Cassandra for vCloud Director 9.0 metrics. As a refresher, one of the cool features released in vCloud Director SP 5.6.x was the ability to expose VM metrics that service providers could expose to their clients via a set of API calls. With the release of vCloud Director 9.0, the metrics can now be viewed from the new HTML5 tenant UI, meaning that all service providers should be able to offer this to their customers.

With the Cassandra configuration out of the way, the next step is to use the Cell Management Tool to tell the vCD cells to push the VM Metric data. Before this, if you log into the HTML5 UI you will notice no menu for Monitoring…this only gets enabled once the metrics have have been enabled by the tool.

The command has changed from previous versions in line with removing the dependancy on the KairosDB and we are now calling a cassandra argument that has the following options:

Those familiar with the previous command to configure the metrics will see a lot more options that specify the Cassandra nodes, the original command to configure the schema, the username and password to connect to the Cassandra database with and the ttl for the data, meaning that if you wanted you could keep more than two weeks of data.

If you tail the Cassandra system.log while the process is happening you will see a bunch of tables being created and populated with the initial data.

With the done, if you go into the new HTML5 Tenant UI and go to the Virtual Machine view you should now see a Monitoring Chart drop down in the menu in the main window. From here you can choose any of the available metrics across a half hour, hour, day and week timescale.

API Calls to Retrieve Current and Historical Metrics:

If you still want to go old school the following API Calls are used to gather current and historical VM metrics for vCD VMs. The Machine ID required used the VM GUID as seen in vCenter. The ID can be sourced from the VM Name. The vCD Machine ID shown below in the brackets is what you are after.



Configuring Cassandra for vCloud Director 9.0 Metrics

One of the cool features released in vCloud Director SP 5.6.x was the ability to expose VM metrics that service providers could expose to their clients via a set of API calls. Some service providers took advantage of this and where able to offer basic VM metrics to their tenants through customer written portals. Zettagrid was one of those service providers and while I was at Zettagrid, I worked with the developers to get VM metrics out to our customers.

Part of the backend configuration to enable the vCloud Director cells to export the metric data was to stand up a Cassandra/KairosDB cluster. This wasn’t a straight forward exercise but after a bit of tinkering due to a lack of documentation, most service providers where able to have the backend in place to support the metrics.

With the release of vCloud Director 9.0, the requirement to have KairosDB managed by Apache has been removed and metrics can now be accessed natively in Cassandra using the cell management tool. Even cooler is that the metrics can now be viewed from the new HTML5 tenant UI, meaning that all service providers should be able to offer this to their customers.

Cassandra is an open source database that you can use to provide the backing store for a scalable, high-performance solution for collecting time series data like virtual machine metrics. If you want vCloud Director to support retrieval of historic metrics from virtual machines, you must install and configure a Cassandra cluster and use the cell-management-tool to connect the cluster to vCloud Director. Retrieval of current metrics does not require optional database software.

The vCloud Director online docs have a small install guide but it’s not very detailed. It basically says to install and configure the Cassandra cluster with four nodes, two of which are seed nodes, enabling encryption and user authentication with Java Native Access installed. Not overly descriptive. I’ve created an script below that installs and configures a basic single node Cassandra cluster that will suffice for most labs/testing environments.

Setting up Cassandra on Ubuntu 16.04 LTS:

I’ve forked an existing bash script on Github and added modifications that goes through the installation and configuration of Cassandra 2.2.6 (as per the vCD 9.0 release notes) on a single node, enabling authentication while disabling encryption in order to keep things simple.

This will obviously work on any distro that supports apt-get. Once configured you can view the Cassandra status by using the nodetool status command as shown below.

The manual steps for the Cassandra installation are below…note that they don’t include the configuration file changes required to enable authentication and set the seeds.

From here you are ready to configure vCD to push the metrics to the Cassandra database. I’ll cover that in a seperate post.

References:

https://docs.vmware.com/en/vCloud-Director/9.0/com.vmware.vcloud.install.doc/GUID-E5B8EE30-5C99-4609-B92A-B7FAEC1035CE.html

https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/vcloud/vmware-vcloud-director-whats-new-9-0-white-paper.pdf

vCloud Director 9.0: Manual Quick fix for VXLAN Network Pool Error

vCloud Director 9.0, released last week has a bunch of new enhancements and a lot of those are focused around it’s integration with NSX. Tom Fojta has a what’s new page on the go with a lot of the new features being explained. One of his first posts just after the GA was around the new feature of being able to manually create VXLAN backed Network Pools.

VXLAN Network Pool is recommended to be used as it scales the best. Until version 9, vCloud Director would create new VXLAN Network Pool automatically for each Provider VDC backed by NSX Transport Zone (again created automatically) scoped to cluster that belong to the particular Provider VDC. This would create multiple VXLAN network pools and potentially confusion which to use for a particular Org VDC.

In vCloud Director 9.0 we now have the option of creating a VXLAN backed network pool manually instead of one being created at the time of a setting up a Provider vDC. In many of my environments for one reason or another the automatic creation of VXLAN network pool together with NSX would fail. In fact my current NextedESXi SliemaLabs vCD instance shows the following error:

There is a similar but less serious error that can be fixed by changing the replication mode from within the NSX Web Client as detailed here by Luca, however like my lab I’ve know a few people to run into the more serious error as shown above. You can’t delete the pool and a repair operation will continue to error out. Now in vCD 9.0 we can create a new VXLAN Network Pool form the Transport Zones created in NSX.

Once that’s been done you will have the newly created VXLAN Network Pool that’s truly more global and tied to best practice for NSX Transport Zones and one that can be used with the desired replication mode. The old one will remain, but you can now configure Org vDCs to consume the VXLAN backed network pool over the traditional VLAN backed pool.

References:

vCloud Director 9: What’s New

vCloud Director 9: Create VXLAN Network Pool

Released: vCloud Director 9.0 – The Most Significant Update To Date!

Today is a good day! VMware have released to GA vCloud Director 9.0 (build 6681978) and with it come the most significant feature and enhancements of any previous vCD release. This is the 9th major release of vCloud Director, now spanning nearly six and half years since v1.0 was released in Feburary of 2011 and as mentioned from my point of view it’s the most significant update of vCloud Director to date.

Having been part of the BETA program I’ve been able to test some of the new features and enhancements over the past couple of months and even though from a Service Provider perspective there is a heap to like about what is functionally under the covers, but the biggest new feature is without doubt the HTML5 Tenant Portal however as you can see below there is a decent list of top enhancements.

Top Enhancements:

 

  • Multi-Site vCD – Single Access point URL for all vCD instances within same SP federated via SSO
  • On-premises to Cloud Migration – Plugin that enables L2 connectivity, warm and cold migration
  • Expanded NSX Integration – Security Groups, Logical Routing for east-west traffic and audit logging
  • HTML5 Tenant UI – Streamlined workflows for VM deployment, UI Extensibility for 3rd party services/functionality
  • HTML5 Metrics UI – Basic Metrics for VMs shown through tenant portal
  • Extensible Service Framework – Service enablement, SSO Ready
  • Application Extensibility – Plugin Framework
  • PostGres 9.5 Support – In addition to MSSQL and Oracle, Postgres is now supported.
  • …and more under the hood bits

I’m sure there will be a number of other blog posts focusing on the list above, and i’ll look to go through a few myself over the next few weeks but for this GA post I wanted to touch on the new HTML5 Tenant UI.

There is a What’s New in vCloud Director 9.0 PDF here.

New HTML5 Tenant UI:

The vCD team laid the foundation for this new Tenant UI in the last release of vCD in bringing the NSX Advanced HTML5 UI to version 8.20. While most things have been ported across there may still be a case for tenants to go back to the old Flex UI to do some tasks, however from what I have seen there is close to 100% full functionality.

To get to the new HTML5 Tenant UI you go to: https://<vcd>/tenant/orgname

Once logged in you are greeted with a now familiar looking VMware portal based on the Clarity UI. It’s pretty, it’s functional and it doesn’t need Flash…so haters of the existing flex based vCD portal will have to bite their tongues now 🙂

The Networking menu is inbuilt into this same Tenant portal and you you can access it directly from the new UI, or in the same way as was the case with vCD 8.20 from the flex UI. Below is a YouTube video posted by the vCD team that walks through the new UI.

There is also VM Metrics in the UI now, where previously they where only accessible after configuring the vCD Cells to route metric data to a Cassandra database. The metrics where only accessible via the API and some providers managed to tap into that and bring vCD Metrics into their own portals. With the 9.0 release this is now part of the new HTML5 Tenant UI and can be seen in the video below.

As per previous releases this only shows up to two weeks worth of basic metrics but it’s still a step in the right direction and gives vCD tenant’s enough info to do basic monitoring before hitting up a service desk for VM related help.

Conclusion:

vCloud Director 9.0 has delivered on the what most members of the VMware Cloud Provider Program had wanted for some time…that is, a continuation of the commitment to the the HTML5 UI as well as continuing to add features that help service providers extend their reach across multiple zones and over to hybrid cloud setups . As mentioned over the next few weeks, I am going to expand on the key new features and walk through how to configure elements through the UI and API.

Compatibility with Veeam, vSphere 6.5 and NSX-v 6.3.x:

vCloud Director 9.0 is compatible with vSphere 6.5 Update 1 and NSX 6.3.3 and supports full interoperability with other versions as shown in the VMware Product Interoperability Matrix. With regards to Veeam support, I am sure that our QA department will be testing the 9.0 release against our integration pieces at the first opportunity they get, but as of now, there is no ETA on offical support.

A list of known issues can be found in the release notes.

#LongLivevCD

References:

https://docs.vmware.com/en/vCloud-Director/9.0/rn/rel_notes_vcloud_director_90.html

https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/vcloud/vmware-vcloud-director-whats-new-9-0-white-paper.pdf

VMware Announces New vCloud Director 9.0

What’s in a name? VSPP to vCAN to VCPP

Prior to VMworld there where rumours floating around that the vCloud Air Network was going to undergo a name change and sure enough at VMworld 2017 in the US, the vCAN was no more and that the VMware Cloud and Service Provider program would be renamed to the VMware Cloud Partner Program. There has been a number of announcements around the VCPP including the upcoming release of vCloud Director 9.0, a new verification program and also at VMworld Europe new cross cloud capabilities with VMware HCX.

VMware is continuing to make significant investments to expand and enhance our portfolio of cloud products and services. At the same time, we will continue to grow and refine our program to better address your needs as a partner and, as a result, enable you to provide even better cloud service options to our mutual customers around the globe.

The VMware Cloud Verified program is interesting and I’m still a little unsure what it delivers above and beyond non verified VMware Clouds…however it seems like a good logo opportunity for providers to aspire to.

This name change was expected given the wrapping up of vCloud Air, however from talking with a lot of people within the old vCloud Air Network, the name will be missed. To me it was the best thing to come out of the whole vCloud Air experiment but I understand why it had to be changed. This isn’t so much a fresh start for the program but more of a signal that it’s growing and improving and is looking to remain a key cornerstone of VMware multi/hybrid cloud strategy.

Even though I am out of the program and not working for a partner anymore, I am very much connected by way of my interactions with the Veeam Cloud and Service Provider program (VCSP) and the success of both is tied back to not only the individual companies remaining innovative and competitive against the large hyper-scalers. It’s also incumbent on VMware and Veeam to continue to offer the tools to be able to make our providers successful.

As a critical component of the Cloud Provider Platform, the recently-announced vCloud Director 9.0 (vCloud Director 9.0 announcement blog) enables simplified cloud consumption for tenants, a fast path to hybrid services, and rapid vSphere-to-cloud migrations for cloud providers worldwide. VMware continues to demonstrate its commitment to investing in the critical products, tools, and solutions that help cloud providers rapidly deploy and monetize highly scalable cloud environments with the least amount of risk.

The name doesn’t matter…but the technology and execution of service sure as hell does!

Note: Visit CloudProviders.VMware.com. Subscribe to the VMware Cloud Provider Blog, follow @vmwarecloudprvd on Twitter or ‘like’ VMware Cloud on Facebook for future updates.

VMworld 2017: vCloud Air Network Again Out in Force

Last year saw a resurgence in vCloud related sessions at VMworld and the trend has continued this year at the 2017 event. Looking through the sessions at Partner Exchange and VMworld proper the refocus on the vCloud Air Network that was announced at VMworld 2015 has gathered steam. This together with the subsequent release of vCloud Director SP 8.20 and the pending release of the next version of vCD, things are looking good for service providers that have built their platforms on VMware technologies.

If you are attending Partner Exchange there are a number of sessions that should be on your list for the Sunday. The sessions seem to be down on last year but that’s due to vCloud Air no longer being a going concern. I’ve listed down my top picks below added links to them for easy searchability in the VMworld Session Catalog. I’ve added a session on AWS and a session on vSAN as service providers should understand how both technologies fit into their strategy.

  • PAR4360BU – Cloud Service Provider Platform: Evolution and Future
  • PAR4358BU – How to Build a Hybrid Cloud Using NSX and vCloud Director-A Service Provider Perspective
  • PAR4383BU – Delivering Hybrid Cloud Architectures for Your Customers with VMware Cloud on AWS
  • PAR4382BU – Embracing VMware Cloud on AWS – How Can You Deliver Value to Your Customers
  • PAR4367BU – What’s New in vSAN 6.6 – A Deep Dive 

Looking through the breakout sessions there are 20 sessions directly relating to vCloud Director which is an excellent result. The rest that i’ve listed below tie in a mix of disaster recovery, hybrid cloud and NSX related networking sessions.

  • LHC1661BU—Getting Started with vCloud Air Network (Technical Tips and Tricks)
  • LHC1716BU—On-Ramp to the Cloud: Migration Tools and Strategies
  • LHC1753BU—Case Study: How VMware NSX Is Empowering a Service Provider to Help Customers Achieve and Maintain Industry Compliance
  • LHC1809BU—Use NSX to Deploy a Secure Virtual Network Bridging Multiple Locations for a True Hybrid Cloud
  • LHC1951BU—Automated Cloud Recovery for When You are Nuked from Orbit
  • LHC2424BU—200 to 40,000 VMs in 24 Months: Building Highly Scalable SDDC on Hybrid Cloud: Real-World Example
  • LHC2573BU—Achieving Hybrid Cloud Data Agility Securely with VMware NSX
  • LHC1739GU—Disaster Recovery to the Cloud: What Has Changed in the Past Year?
  • LHC3179GU—Choosing the Ideal Cloud Provider Partner
  • LHC3180GU—Effective DR Strategies
  • LHC1566PU—Ask the vCloud Air Network Cloud Experts
  • LHC3139SU— Achieving Success in a Multi-Cloud World
  • LHC2626BU—Build VMware Powered Hybrid Clouds: See How vCloud Director and NSX work together to build true Hybrid Clouds

There are also a number of vCloud Air Network partners on the exhibit floor.

  • CenturyLink
  • OVH
  • Faction
  • phoenixNAP
  • Fujitsu
  • Rackspace
  • IBM
  • SkyTap
  • iland
  • SwissCom
  • Navisite
  • Virtustream

Apart from what I have listed above there will also be a lot of vCAN talent hovering around the conference so make sure you make an effort to connect, network and share vCAN experiences. The vCloud Air Network is a symbiotic ecosystem and if the vCAN grows stronger…the ecosystem grows stronger.

#LongLivevCD

References:

Have You Signed Up for Your VMworld Cloud Provider Sessions?”

Reserve Your Seat Today to Learn How vCloud Air Network Partners Can Accelerate Your Success in the Cloud

CPU Overallocation and Poor Network Performance in vCD – Beware of Resource Pools

For the longest time all VMware administrators have been told that resource pools are not folders and that they should only be used under circumstances where the impact of applying the resource settings is fully understood. From my point of view I’ve been able to utilize resource pools for VM management without too much hassle since I first started working on VMware Managed Service platforms and from a managed services point of view they are a lot easier to use as organizational “folders” than vSphere folders themselves. For me, as long as the CPU and Memory Resources Unlimited checkbox was ticked nothing bad happened.

Working with vCloud Director however, resource pools are heavily utilized as the control mechanism for resource allocation, sharing and management. It’s still a topic that can cause confusion when trying to wrap ones head around the different allocation models vCD offers. I still reference blog posts from Duncan Epping and Frank Denneman written nearly seven years ago to refresh my memory every now and then.

Before moving onto an example of how overallocation or client undersizing in vCloud Director can cause serious performance issues it’s worth having a read of this post by Frank that goes through in typical Frank detail around what resource management looks like in vCloud Director.

Proper Resource management is very complicated in a Virtual Infrastructure or vCloud environment. Each allocation models uses a different combination of resource allocation settings on both Resource Pool and Virtual Machine level

Undersized vDCs Causing Network Throughput Issue:

The Allocation Pool model was the one that I worked with the most and it used to throw up a few client related issues when I worked at Zetttagrid. When using the Allocation Pool method which is the default model you are specifying the amount of resources for your Org vDC and also specifying how much of these resources are guaranteed. The guarantee means that a reservation will be set and that the amount of guaranteed resources is taken from the Provider vDC. The total amount of resources specified is the upper boundary, which is also the resource pool limit.

Because tenants where able to purchase Virtual Datacenters of any size there was a number of occasions where the tenants undersized their resources. Specifically, one tenant came to us complaining about poor network performance during a copy operation between VMs in their vDC. At first the operations team thought that is was the network causing issues…we where also running NSX and these VMs where also on a VXLAN segment so fingers where being pointed there as well.

Eventually, after a bit of troubleshooting we where able to replicate the problem…it was related to the resources that the tenant had purchased or lack thereof. In a nutshell because the allocation pool model allows the over provisioning or resources not enough vCPU was purchased. The vDC resource pool had 1000Mhz of vCPU with a 0% reservation but he had created 4 dual vCPU VMs. When the network copy job started it consumed CPU which in turn exhausted the vCD CPU allocation.

What happened next can be seen in the video below…

With the resource pool constrained ready time is introduced to throttle the CPU which in turn impacts the network throughput. As shown in the video when the resource pool has the the unlimited button checked the ready goes away and the network throughput returns to normal.

Conclusion:

Again, its worth checking out the impact on the network throughput in the video as it clearly shows what happens what tenants underprovision or overallocate their Virtual Datacenters in vCloud Director. Outside of vCloud Director it’s also handy to understand the impact of applying reservations on Resource Pools in terms of VM compute and networking performance.

It’s not always the network!

References:

http://www.vmware.com/resources/techresources/10325

http://frankdenneman.nl/2010/09/24/provider-vdc-cluster-or-resource-pool/

http://www.yellow-bricks.com/2012/02/28/resource-pool-shares-dont-make-sense-with-vcloud-director/

https://kb.vmware.com/kb/2006684

Allocation Pool Organization vDC Changes in vCloud Director 5.1

« Older Entries