Tag Archives: VMware

VMware Cloud on AWS Availability with Veeam

It’s been exactly a year since VMware announced their partnership with AWS and it’s no surprise that at this year’s VMworld the solution is front and center and will feature heavily at Monday’s keynote. Earlier today Veeam was announced as an officially supported backup, recovery and replication platform for VMware Cloud on AWS. This is an exciting announcement for existing customers of Veeam who currently use vSphere and are interesting in consuming VMware Cloud on AWS.

In terms of what Veeam has been able to achieve, there is little noticeable difference in the process to configure and run backup or replication jobs from within Veeam Backup & Replication. The VMware Cloud on AWS resources are treated as just another cluster so most actions and features of the core platform work as if the cloud based cluster was local or otherwise.

Below you can see a screen shot of an VMC vCenter from the AWS based HTML5 Web Client. What you can see if the minimum spec for a VMC customer which includes four hosts with 36 cores and 512GB of RAM, plus vSAN and NSX.

In terms of Veeam making this work, there were a few limitations that VMware have placed on the solution which means that our NFS based features such as Instant VM Recovery, Virtual Labs or Surebackups won’t work at this stage. HotAdd mode is the only supported backup transport mode (which isn’t a bad thing as it’s my preferred transport mode) which talks to a new VDDK library that is part of the VMC platform.

With that the following features work out of the box:

  • Backup with In Guest Processing
  • Restores to original or new locations
  • Backup Copy Jobs
  • Replication
  • Cloud Connect Backup
  • Windows File Level Recovery
  • Veeam Explorers

With the above there are a lot of options for VMC customers to stick to the 3-2-1 rule of backups…remembering that just because the compute resources are in AWS, doesn’t mean that they are highly valuable from a workload and application availability standpoint. Customers can also take advantage of the fact that VMC is just another cluster from their on-premises deployments and use Veeam Backup & Replication to replicate VMs into the VMC vCenter to which end it could be used as a DR site.

For more information and the offical blog post from Veeam co-CEO Peter McKay click here.

Runecast: Overview and Service Provider Use Case

A few months ago I was lucky enough to spend time with a couple of the founders of Runecast, Stanimir Markov and Ched Smokovic and got to know a little more about their real time analytics platform for VMware based infrastructure. Soon after that I downloaded and deployed it in my lab and have been running it for a few months. In that time I’ve come to understand and appreciate the value that it adds to the operations and management of any vSphere platform.

Having been part of, and led teams that operated and managed large vSphere based cloud platforms one of the challenges of managing any platform of size is how to stay on top of issues operationally…not only when and as they happen, but also before then happen. Proactive monitoring and alerting that pinpoints issues before they happen is invaluable and up to this point I haven’t found a product that focuses in as specifically as Runecast does to help solve that challenge.

In the past I have researched and used more than a few tools on the market and probably the closest comparison that I can make with Runecast is what CloudPhysics tried to do with their Knowledge Base Adviser feature. For those that have used CloudPhysics in the past Runecast will feel somewhat similar in theory, however Runecast have taken what CloudPhsyics had done and taken it to the next level.

By using a number of resources within VMware’s knowledgebase Runecast is been able to deliver a platform that looks at best practices, log information and security hardening guides to monitor your vSphere infrastructure which in turn brings to your attention through a simple yet intuitive interface to issues that may exist.

Runecast for Service Providers:

Proactive analysis is the name of the game and it’s one of the holy grail’s for any operations team. Prevention of an issue before it occurs is what Runecast sets out to achieve and for service providers that are running critical line of business applications for their clients (which is all service providers) the ability to prevent service disruption is huge.

Apart from the obvious benefits around proactive analytics, one of the best features for service providers is the security hardening feature. Lots of service providers these days are being governed by specific regulations and compliance and security has become front and center of any platform owner. With the security hardening feature it points out specifically what passes and what fails as per the official VMware hardening guide.

I can also see how the specific inventory feature for vCenter objects can be developed in the future to allow service providers to expose certain information via the Runecast APIs to their tenants. I’d love to see some integration with vCloud Director, NSX and vSAN among other VMware platforms…there is serious potential here.

The API endpoints that are being exposed version to version means that service providers can take the information presented and manipulate it their hearts content. It providers a powerful way for service providers to take full advantage of the data that’s being collect and analyised.

Final Thoughts:

This is, for the most a targeted analytics system that focuses on getting you the relevant information quickly and without fuss and allows you to ascertain issues and work towards their resolution. I’m looking forward to seeing what the guys come up with over the next twelve to eighteen months as they further enhance the capabilities.

For your free 14 day Trial register here and if you are heading to VMworld this year make sure to visit them at Booth #832

Disclaimer: Runecast are sponsors of Virtualization is Life!

VMworld 2017 – Session Breakdown and Analysis

Everything to do with VMworld this year feels like it’s earlier than in previous years. The call for papers opened in Feburary with session voting happening around the end of March. A couple of weeks ago presenters where notified if their session was accepted…or if it was rejected and the content catalog for the US event went live last week! At the moment there is 736 sessions listed which will grow when the #vBrownBag Tech Talks hosted by the VMTN Community get added.

As I do every year I like to filter through the content catalog and work out what technologies are getting the airplay at the event. What first struck me as being interesting was the track names:

Do you see a common thread? They obviously centre around the “digital transformation” theme that we have been fed at every major conference for the last four to five years. I don’t mind it so much, but I know it’s becoming a bit of an industry joke when we hear the same messaging around transformation, digital workspace and modernization.

Shown above are all the products and topics listed in the content catalog and previously when the public voting took place I did some analysis around the number of sessions relating to the filters shown below.

  • vCD 32
  • vCloud 305
  • vCloud Director 64
  • NSX 426
  • NSX-T 116
  • vSAN 223
  • AWS 51
  • Containers 85
  • Devops 69
  • Automation 223

Using those same filters, below are the numbers from what made the cut and are in the content catalog for 2017.

What’s interesting in looking at the submitted sessions vs what was picked up…to be included in the content catalog for the event if you want a better than even chance of having your session accepted, submit around NSX, NSX-T, vSAN, AWS and Containers. In the case of vSAN and Containers, working with these numbers about 60% of the submitted sessions got approved and in the case of AWS the number of sessions approved was more than what was submitted!

Even though the number of vCD related sessions didn’t make it through the numbers are still well up from the dark days of vCD around the 2013 and 2014 VMworlds. For anyone working on cloud technologies this year promises to be a bumper year for content so if you haven’t registered for VMworld 2017 yet…what are you waiting for!

Register here:

VMware vSphere 6.5 Host Resources Deep Dive – A Must Have!

Just after I joined Zettagrid in June of 2013 I decided to load up vSphere 5.1 Clustering Deepdive by Duncan Epping and Frank Denneman on my iPad to read on my train journey to and from work. Reading that book allowed me to gain a deeper understanding of vSphere through the in depth content that Duncan and Frank had produced. Any VMware administrator worth their salt would be familiar with the book (or the ones that proceeded it) and it’s still a brilliant read.

Fast forward a few versions of vSphere and we finally have follow up:

VMware vSphere 6.5 Host Resources Deep Dive

This time around Frank has been joined by Niels Hagoort and together they have produced another must have virtualization book…though it goes far beyond VMware virtualization. I was lucky enough to review a couple of chapters of the book and I can say without question that this book will make your brain hurt…but in a good way. It’s the deepest of deep dives and it goes beyond the previous books best practice and dives into a lot of the low level compute, storage and networking fundamentals that a lot of us have either forgotten about, never learnt or never bothered to learn about.

This book explains the concepts and mechanisms behind the physical resource components and the VMkernel resource schedulers, which enables you to:

  • Optimize your workload for current and future Non-Uniform Memory Access (NUMA) systems.
  • Discover how vSphere Balanced Power Management takes advantage of the CPU Turbo Boost functionality, and why High Performance does not.
  • How the 3-DIMMs per Channel configuration results in a 10-20% performance drop.
  • How TLB works and why it is bad to disable large pages in virtualized environments.
  • Why 3D XPoint is perfect for the vSAN caching tier.
  • What queues are and where they live inside the end-to-end storage data paths.
  • Tune VMkernel components to optimize performance for VXLAN network traffic and NFV environments.
  • Why Intel’s Data Plane Development Kit significantly boosts packet processing performance.

If any of you have read Frank’s NUMA Deep Dive blog series you will start to get an appreciation of the level of technical detail this book covers, however it is written in a way that allows you absorb the information in a way that is digestible, though some parts may need to be read twice over. Well done to Frank and Niels on getting this book out and again, if you are working in and around anything to do with computers this is a must read so do yourself a favour and grab a copy.

The current Amazon locals that have access to purchase the book can be found below:

Amazon US: http://www.amazon.com/dp/1540873064
Amazon France: https://www.amazon.fr/dp/1540873064
Amazon Germany: https://www.amazon.de/dp/1540873064
Amazon India: http://www.amazon.in/dp/1540873064
Amazon Japan: https://www.amazon.co.jp/dp/1540873064
Amazon Mexico: https://www.amazon.com.mx/dp/1540873064
Amazon Spain: https://www.amazon.es/dp/1540873064
Amazon UK: https://www.amazon.co.uk/dp/1540873064

Quick Fix: VCSA 503 Service Unavailable Error

I’ve just had to fix one of my VCSA’s again from the infamous 503 Service Unavailable error that seems to be fairly common with the VCSA even though it’s was claimed to be fixed in vCenter version 6.5d. I’ve had this error pop up fairly regularly since deploying my homelab’s vCenter Server Appliance as a version 6.5 GA instance and for the most part I’ve refrained from rebooting the VCSA just in case the error pops up upon reboot and have even kept a snapshot against the VM just in case I needed to revert to it on the high change that it would error out.

503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http20NamedPipeServiceSpecE:0x0000559b1531ef80] _serverNamespace = / action = Allow _pipeName =/var/run/vmware/vpxd-webserver-pipe)

After doing a Google search for any permanent solutions to the issue, I came across a couple of posts referencing USB passthrough devices that could trigger the error which was plausible given I was using an external USB Hard Drive. IP changes seem to also be a trigger for the error though in my case, it wasn’t the cause. There is a good Reddit thread here that talks about duplicate keys…again related to USB passthrough. It also links externally to some other solutions that where not relevant to my VCSA.

Solution:

As referenced in this VMware communities forum post, to fix the issue I had to first find out if I did have a duplicate key error in the VCSA logs. To do that I dropped into the VCSA shell and went into /var/logs and did a search for any file containing device_key + already exists. As shown in the image above this returned a number of entries confirming that I had duplicate keys and that it was causing the issue.

The VMware vCenter Server Appliance vpxd 6.5 logs are located in the /var/log/vmware/vmware-vpx folder

What was required next was to delete the duplicate embedded PostGres database table entries. To connect to the embedded postgres database you need to run the following command from the VCSA shell:

To remove the duplicate key I ran the following command and rebooted the appliance, noting that the id and device_key will vary.

Once everything rebooted all the services started up and I had a functional vCenter again which was a relief given I was about five minutes away from a restore or a complete rebuild…and ain’t nobody got time for that!

vCenter (VCSA) 6.5 broken after restart from vmware

Reference:

https://communities.vmware.com/thread/556490

 

Quick Thought: VMUG is now part of DTUC

I awoke this morning to the news that an announcement was made at DELL|EMC World that VMUG had been rolled into a the recently formed Dell Technologies User Community (DTUC – doesn’t quiet roll off the tongue now does it?) …I also awoke to a lot of VMware community backlash on Twitter not only in response to the news but also in the way in which it was not communicated to the existing local VMUG leadership and steering committee members.

From the reaction i’ve seen, most people are fairly ticked off with the fact that almost everybody found out about this through public channels…mainly Twitter. It’s worth watching the video below to get an overview of the changes from the VMUG President and CEO as it does go some way to clarifying the what’s what of the announcement.

Just to clarify, VMUG is not changing it’s name to DTUC.

https://dtusercommunity.com

My Take:

I think everybody knew that VMUG was in trouble from an organisational standpoint with a lot of changes during the first few months of 2017 and some interesting moves around the removing of Nutanix staff from leadership role. So this news isn’t a total surprise however for me, the one key ingredient that VMUG offered is now well and truly in danger of being wiped away…and that is it’s relative independence.

The VMUG community was born out of the technology ecosystem that grew around VMware’s success in the virtualization market and it meant that all of VMware’s technology and alliance partners where given a seat at the table in terms of event sponsorship and presentations. It was a place equally where smaller startup’s could come and talk about their new technology solutions and where the more established vendors could talk around why there where still cool and relevant.

Now, with DELL|EMC plus VMware product portfolio my fear is that finding sponsors will become even more of a challenge as it has been worldwide for the last 12 to 18 months. This is an interesting move but again, but not a surprising one given what I’ve seen with my involvement in VMUG over the past two years. It’s not all doom and gloom though as I feel the VMUG UserCons are still brilliant events as was the case with the recent ones held in Sydney and Melbourne.

Time will tell how this plays out, but there is one thing I believe the wider VMware community doesn’t want to see drop off or disappear…and that is the community it’s self!

NSX Bytes: NSX-T 2.0 Released

A couple of months ago in my NSX-v 6.3 and NSX-T 1.1 release post I focused around NSX-v features as that has become the mainstream version that most people know and work with…however NSX, in it’s Nicira roots has always been about multi-hypervisor and has always had an MH version that worked with Openstack deployments. The NSBU has big plans for NSX beyond vSphere and during the NSX vExpert session we got to see a little about how NSX-T will look beyond version 1.1.

NSX-T’s main drivers relate to new data centre and cloud architectures with more hetrogeneality driving a different set of requirements to that of vSphere that focuses around multi-domain environments leading to a multi-hypervisor NSX platform. NSX-T is highly extensible and will address more endpoint heterogeneity in future releases including containers, public clouds and other hypervisors. As you can see before the existing use cases for NSX-T are mainly focused around devops, micro-segmentation and multi-tenant infrastructure.

What’s in NSX-T 2.0:
The short answer to this is a focus on expanding NSX to public clouds, containers and platform as a service workloads. We have already seen a tech preview at VMworld of NSX working with AWS instances and the partnership between VMware and AWS is even more of a driver for this cross cloud compute and networking landscape to allow NSX-T to shine.
Expanded Networking and Security into Public Cloud and Containers:
  • Centralised security policy management
  • NSX for Public Cloud (AWS)
  • NSX for Cross-Cloud Services (AWS)
  • NSX for Containers and PaaS (Kubernetes, Openshift)

Platform Capabilities:

  • Distributed L3 at scale decoupled from vCenter
  • Intel DPDK Edge Line Rate packet performance
  • L2/L3 redundant control and data plane
  • ESXi and KVM (RHEL/Ubuntu)
  • Independant NSX interface thats multi vCenter
  • Scale out control plane and scale out edge cluster
  • VM and Containers Hosts

Feature Capabilities:

  • Distributed Routing, eBGP, NAT, BFD, ECMP, route-maps, 4 byte ASN
  • REST/JSON OpenAPI Specification
  • VIO, Upstream Openstack support
  • Geneve Encapsulation, QoS, Software L2 Bridge
  • Distributed stateful firewall, tag based security grouping
  • DHCP Server and Relay
  • IPFIX, Port Mirroring, Port Connectivity, Trace Flow, Backup & Restore
  • Log Insight Content Management Pack

Where do NSX-v and NSX-T Play:

Conclusion:

When it comes to the NSX-T 2.0 feature capabilities, many of them are a case of bringing NSX-T up to speed to where NSX-v is, however the thing to think about is that how those capabilities will or could be used beyond vSphere environments…that is the big picture to consider here around the future of NSX!

For an overview of what’s was released in NSX-T 2.0, the release notes can be found here, or have a read of my launch post here.

References:

vForumAU 2016 Recap: Best Event In Years!

Last week I was in Sydney for the 2016 edition of vForumAU…I’ve been coming to vForumAU since 2011 and this years event was probably up there with the best that I have attended in that time. For the past couple of years the event has had to shift venues due to the Sydney Exhibition Center being knocked down and rebuilt and in that time the it’s been at Luna Park and Star City Casino…both of which presented their own challenges for VMware, sponsors and attendees. This years event was held at The Royal Hall of Industries in Moore Park which offered a perfect venue for the event and helped deliver on what was a great vForumAU.

Adding to the venue was the calibre of speakers that VMware ANZ was able to bring out for this years event…in fact it was the best lineup that I’ve seen or heard of outside of VMworld. We had Pat Gelsinger, Kit Colbert, Paul Strong and Bruce Davie to add to the local VMware talent and given that this event fell after both VMworld US and Europe, I felt that the content was more complete in terms of announcements, products and overall strategy and vision.

I heard Pat deliver the keynote at VMworld US a few months back and the deck was largely the same, however I felt he delivered the message better and talked to the key points around VMware’s hybrid cloud strategy a lot more concisely and with a lot more tact in terms of ensure that vCloud Air Network providers where still very much in the reckoning for VMware’s future strategy around Hybrid cloud. There is no doubt that the partnership’s with AWS and IBM has caused some unease in the vCAN but every key slide had vCAN representation which was pleasing to see.

The Cross Cloud Foundation is something also that still sits uneasily with a lot of vCAN Providers but I have to admit that the tech preview of the Cross Cloud Platform was very very slick and shows how much VMware has changed tact when it comes to playing with other public clouds. There is no doubt that Cloud is the new Hardware and VMware want to be there to manage it and offer it’s customers tools that do the same. Hybrid cloud is here to stay, and they hyper-scalers certainly have a share…however on-premises and partner hosted IaaS will remain significant and relevant for the next 10-15 years.

Moving on from Pat’s keynote there was a super session Technical Keynote that was held after lunch that featured 20-30 minutes on every new product enhancement or release that has been announced of late. From vSphere 6.5 to VSAN 6.5 and a look at NSX futures as well as VMware’s container platforms this was a brilliant couple of hours of presentations. Highlights for me was Paul Strong talking VSAN, Kit Colbert going over the various Photon platforms and Bruce Davie talking around NSX extensibility into AWS. Of note was Bruce Davie (who also presented at the main keynote) who I have come to seriously admire as a speaker over the past couple of years.

The Sponsors hall has a very VMworld feel to it this year which elements of VMworld brought to the event such as VMVillage, special lounges for All Access Pass visitors and probably the best food that I’ve experienced at a vForumAU by way of specialised food trucks bringing a wide array of foods to enjoy. Though the first day wasn’t as well received by exhibitors (AAP attendees pay for sessions, not so much visiting sponsors) in talking with some people on the booths, the second day was very busy and the venue and location had everything to do with that. Again well done do the VMware events team for bringing the event to The Royal Hall of Industries.

Finishing off this recap, once again there was great spirit and community around both sponsors and the attendees to which the venue offered a great chance to catch up socially with people from the VMware community and that fact shouldn’t be lost on the benefit of attending such an event. And while I didn’t attend the offical party I heard that it went really well and was highly entertaining with a lot of food!

Well done to VMware ANZ for putting on a great event!


As a side note, I also attended my final VMware vChampion event on the Wednesday morning where Kit Colbert facilitated an open discussion on containerised platforms and the new continuous integration and continuous deployment methodologies that are creeping their ways into mainstream IT. Again, thanks to the vChampion team!

VMware vChampion Farewell!

About four years ago I was invited to join a program called the VMware vChampions…this program is run and operated by the VMware ANZ Channel and Marketing teams and is an invite only advocacy group who’s members are made up exclusively from VMware’s top partners and service providers in the ANZ region. The numbers have varied over the past couple of years, but at any one time there are about 30-40 vChampions in the group.

With my new role at Veeam I have had to leave the program and this week at #vForumAU will be my last as a member of the group. Before I sign off I wanted to openly thank the people who have made the program such instrumental not only from a personal work point of view, but also from the point of view of enhancing my engagement with the wider VMware community. Probably of most importance, superseding both work and community benefits the program has allowed me to develop friendships with those I have come to meet through the program…some of those people I now consider some of my closest friends.

The program helped take me to my first VMworld in 2012 which is still one of the highlights of my career and an experience that included an VMware Executive Brief at the VMware campus and an introduction to the global VMware community. At vForumAU that same year, the vChampion’s where briefed by then CTO Steve Herrod. The following year at PEX ANZ I was able to work towards landing a dream role at Zettagrid and also establish friendships that are still going strong today. Later that year at vForumAU the vChampions had a whole day event that included a discussion with Martin Casado just shortly after Nicira had been acquired by VMware…the inspiring talk by Martin was, again a career highlight and lit of flame under me that got me into Network Virtualization and deeper into automation.

Over the last couple of years the vChampion program scaled back it’s activities and bi-annual meetings become once a year get togethers however the team was still able to secure guest speakers such as Sanjay Poonen and Kit Colbert. In an amongst the speakers the group was given insider NDA access and product roadmaps…and there in lies the true value of the group for VMware and in equipping the vChampion’s with knowledge and updates the group is equipped to go back to their companies and advocated VMware technologies to the rest of their peers and hopefully also spoke out in the community about VMware technologies.

All in all the value that the program has added to my career can not be understated and I would like to thank, Katrina Jones, Anthony Segren, John Donovan, Rhody Burton and Eugene Geaher for allowing me to be part of such a brilliant program. Also a special mention to Grant Orchard and Greg Mulholland for being the vChampion Champions within VMware and for always being there to help organise and support the vChampions.

Thanks guys and I hope the program can continue to deliver!

VMware on AWS: vCloud Director and What Needs to be Done to Empower the vCAN

Last week VMware and Amazon Web Services officially announced their new joint venture whereby VMware technology will be available to run as a service on AWS in the form of bare-bones hardware with vCenter, ESXi, NSX and VSAN as the core VMware technology components. This isn’t some magic whereby ESXi is nested or emulated upon the existing AWS platform, but a fully fledged dedicated virtual datacenter offering that clients can buy through VMware and have VMware manage the stack right up to the core vCenter components.

Earlier in the week I wrote down some thoughts around the possible impact to the vCloud Air Network this new offering could have. While at first glance it would appear that I was largely negative towards the announcement, after having a think about the possible implications I started to think about how this could be advantageous for the vCloud Air Network. What it comes down to is how much VMware was to open up the API’s for all components hosted on AWS and how the vCloud Director SP product team develops around those API’s.

From there it will be on vCloud Air Network partners that have the capabilities to tap into the VMC’s. I believe there is an opportunity here for vCAN Service Providers to go beyond offering just IaaS and combine their offerings with the VMware AWS offering as well as help extend out to offer AWS PaaS without the worry that traditional VM workloads will be migrated to AWS.

For this to happen though VMware have to do something they haven’t done in the past…that is, commit to making sure vCAN providers can cash in on the opportunity and be empowered by the opportunity to grow VMware based services… as I mentioned in my original post:

In truth VMware have been very slow…almost reluctant to pass over features that would allow this cross cloud compatibility and migration be even more of a weapon for the vCAN by holding back on features that allowed on-premises vCenter and Workstation/Fusion connect directly to vCloud Air endpoints in products such as Hybrid Cloud Manager. I strongly believed that those products should have been extended from day zero to have the ability to connect to any vCloud Director endpoint…it wasn’t a stretch for that to occure as it is effectively the same endpoint but for some reason it was strategically labeled as a “coming soon” feature.

Extending vCloud Director SP:

I have taken liberty to extend the VMWonAWS graphic to include what I believe should be the final puzzle in what would make the partnership sit well with existing vCloud Air Network providers…that is, allow vCloud Director SP to bridge the gap between the on-premises compute, networking and storage and the AWS based VMware platform infrastructure.

vCloud Director is a cloud management platform that abstracts physical resources from vCenter and interacts with NSX to build out networking resources via the NSX Manager API’s…with that it’s not hard in my eyes to allow any exposed vCenter or NSX Manager to be consumed by vCloud Director.

With that allowed, any AWS vCenter dedicated instance can become a Virtual Datacenter object in vCloud Director and consumed by an organisation. For vCloud Air Network partners who have the ability to programatically interact with the vCloud Director APIs, this all of a sudden could open up another 70+ AWS locations on which to allow their customers to deploy Virtual Datacenters.

Take that one step further and allow vCD to overlay on-premises compute and networking resources and then allow connectivity between all locations via NSX hybridity and you have a seriously rock solid solution that extends a customer on-premises to a more conveniently placed (remember AWS isn’t everywhere) vCloud Air Network platform that can in turn consume/burst into a VMware Dedicated instance on AWS and you now have something that rivals the much hyped Hybrid Cloud Strategy of Microsoft and the Azure Stack.

What Needs to Happen:

It’s pretty simple…VMware need to commit to continued/accelerated development of vCloud Director SP (which has already begun in earnest) and give vCloud Air Network providers the ability to consume both ways…on-premises and on VMware’s AWS platform. VMware need to grant this capability to vCloud Air Network providers from the outset and not play the stalling game that was apparent when it came to feature parity with vCloud Air.

What I have envisioned isn’t far off becoming a reality…vCloud Director is mature and extensible enough to do what I have described above, and I believe that in my recent dealings with the vCloud Director product and marketing teams at VMworld US earlier this year that there is real belief in the team that the cloud management platform will continue to improve and evolve…if VMware allow it to.

Further improving on vCloud Directors maturity and extensibility, if the much maligned UI is improved as promised…with the upcoming addition of full NSX integration completing the network stack, the next step in greater adoption beyond the 300 odd vCAN SPs currently use vCloud Director needs a hook…and that hook should be VMWonAWS.

Time will tell…but there is huge potential here. VMware need to deliver to their partners in order to have that VMWonAWS potential realised.

 

« Older Entries