Thanks to the VMware User Group I was recently able to share some of my thoughts on managing data at scale across VMware and Cloud environments. In the session I shared some stories covering how operators were managing data using VMware capabilities like vSphere’s DRS and Storage Policies, as well as concepts like Rubrik’s SLA Domains. I covered some interesting topics and customer stories, including:
VMworld 2018 is just a few short weeks away at this point. Many of those reading this post would no doubt have already filled out their schedule, for those of you who have procrastinated however here are a few sessions that I am looking forward to. To make it interesting I’m limiting my recommendations to one per day, while at the show I fully believe you should take advantage of mingling with others in the community and browsing the show floor to get a sense of some of the innovation that is happening around the ecosystem.
I don’t think I’m going to be able to watch this one live due to other commitments but will be eagerly watching the replay. I’ve presented with Wen before and also watched Aarthi present so I know this will be a great session for anyone attending.
Service providers networking is an interesting beast. If networking is your thing then this promises to be an interesting session and you can always trust Ray to get into the details and I expect Tina to bring the service provider perspective into the mix.
There’s a lot of excellent sessions happening on Wednesday, one that is a little out of my ordinary area though is this one on running confluent on top of Pivotal Container Services. Should be an interesting change from the usual VMworld topics.
I’m going to cheat and share another session on Wednesday just because I know it’s going to be cool and cover one of Rubrik (my employer’s) latest capabilities presented by a couple of excellent presenters. Promises to be enlightening!
I’ve had a bit of an inside view into what has been happening behind the scenes for this session. It’s going to be interesting to hear about some of the more challenging aspects of this project, and how they were addressed. Promises to be an informative and interesting session with some good presenters!
If the sessions above aren’t enough to fill your schedule there are several more excellent sessions being presented at VMworld this year. Here are a few of my favorite speakers, any of their sessions should be worth your time if you like to skew a bit more technical in your tastes:
Rebecca Fitzhugh – has an awesome array of presentations this year, all of which will no doubt be amazing
Duncan Epping – let’s just say he knows how to present and is not shy of addressing both the technical details and high level perspectives
Christian Dickmann – enjoy listening to his thoughts on simplifying operational management
Companies are considering a variety of migration strategies as they are looking to leverage the cloud. For VMware Cloud on AWS (VMC) migration is one of the key use cases that VMware have promoted (alongside Disaster Recovery). A key benefit touted by VMware for their offering is the ability to re-host applications without having to re-platform or re-architect, however, this is not without caveats when it comes to availability and resiliency.
For a customer migrating to the cloud, delivering the right level of resiliency and availability is a key concern. On AWS the Availability Zone is a key building block for designing available architectures. For customers who are willing to re-architect their application, designing the application to ensure resiliency in the face of an AZ loss is critical, as well as ensuring customers are eligible for AWS SLA credits in the event of an EC2 outage! But what options are available for delivering multi-AZ availability when pursuing a re-host migration strategy?
For VMware Cloud on AWS, delivering this re-host capability this is also one of the most significant limitations with what is currently available. When customers provisioned a new SDDC it could only be placed within a single Availability Zone (AZ). The combination of vSphere HA, vSAN’s erasure coding, and VMC’s auto-remediation of failed hosts ensured that failures of the individual bare metal EC2 instances could be handled well. However, there remained an issue of protecting against failures of entire Availability Zones.
With the unveiling of a technology preview of their new stretched clustering capability, VMware is presenting a differentiated offering. Stretched networking, by NSX, and stretched storage, from vSAN, combine with vSphere’s HA to deliver a platform that delivers resiliency against AZ failure, without having to re-architect or re-platform your application to take advantage of multiple Availability Zones. On the vSAN side, the increased costs of mirroring the storage are now offset by the introduction of deduplication and compression support. More details were shared during VMware’s recent Cloud Briefing event and I also spoke about VMware’s plans here during my VMC storage deep-dive session at VMworld.
It will be interesting to see how VMware’s customers evaluate this new offering when it moves out of tech preview status and into General Availability.
During VMworld 2017 I shared a tech preview, with GS Khalsa, of the VMware Site Recovery service that’s now available as an add-on to VMware Cloud on AWS. While we’ve already made several enhancements to the service, over and above what you’ll see in the tech preview, I think it still illustrates many of the exciting new options available with VMware Site Recovery today!
At VMworld earlier this year I presented a deep-dive on vSAN storage for VMware Cloud on AWS with Matt Amdur. This was an interesting topic as we’d had to deliver some enhancements to vSAN for deployment onto the Amazon EC2 Bare Metal instances, now that they’ve been released there are a few more public details that can be shared!
At VMworld we covered a few key topics including the host and cluster configuration on EC2 Bare Metal instances, how we were operating the storage in AWS that would be a little different from how on-premises customers would operate, and a few peaks into the unique features delivered for VMware Cloud on AWS and a look into our plans.
At the recent re:Invent conference, AWS launched their new EC2 Bare Metal instances. VMware were early customers of this instance and worked collaboratively with AWS to ensure the new bare metal platform was a good platform for running ESXi and vSAN. With the launch of the solution, AWS was more open about talking details on their platform. Check out the session by Aaron Blassius and Matt Wilson sharing details on the new platform we are using for VMware Cloud on AWS.
I was lucky enough to be able to share some details about the new VMware Site Recovery service at the AWS re:Invent conference alongside Wen Yu. In the VMware Cloud on AWS technical deep dive and native service integration session we covered some key use cases customers are looking to address with VMware Cloud on AWS including:
Securing web/content management
Check out the session (recorded the day before the official launch) on Youtube
At VMworld, back in August, the first version of VMware Cloud on AWS was launched. Now three months later we’re doing it again! As the Product Manager owning the storage and disaster recovery initiatives it’s been a great experience to work with the joint VMware and AWS teams as we delivered the storage platform for VMware Cloud on AWS (built with vSAN), and are now delivering new Disaster Recovery (DR) capabilities with VMware Site Recovery.
Delivering improved resiliency and DR options has been an important focus for VMware Cloud on AWS. This new capability allows customers to protect their mission-critical workloads running on-premises to VMware Cloud on AWS, or vice-versa. We also support protection between VMware Cloud on AWS SDDCs. This enables customers to protect workloads across different AWS Availability Zones, or even between AWS Regions with the newly announced support for US East (N. Virginia).
It’s also been a great experience to work closely with some of our forward-looking customers as we’ve been developing VMware Cloud on AWS. Listen to one of these early customers share their view of the collaboration between VMware and AWS, and the new capabilities we’re delivering.
More details on the VMware Site Recovery solutions can be found on the VMware Cloud Services site:
With the recent release of PowerCLI 6.5.1 the PowerCLI team moved to a more modular approach to delivering their capabilities. This new PowerCLI release also made some changes related to SRM, from their launch blog:
The SRM cmdlets have been removed from the Core module and a new SRM module has been created. The new module is named VMware.VimAutomation.Srm and features updated cmdlets that enable users to interact with the API views for the SRM 6.5 API!
The PowerCLI SRM module provides easy access to the SRM public API. To make it easier to work with the new SRM 6.5 public API I have updated my SRM advanced functions to work with the new PowerCLI 6.5.1 release and the new SRM 6.5 APIs. This new version of SRM-Cmdlets, v0.2, is not backwards compatible with earlier versions of PowerCLI and is intended for use with SRM 6.5, if you are using earlier versions of PowerCLI or SRM you should stick with the earlier release of these cmdlets.
I’ve been quiet on my personal blog (I aim to rectify that) but in the meantime here a list of some of the blogs I’ve written over at Virtual Blocks, the blog for the Storage and Availability Business Unit at VMware about VMware Virtual Volumes (VVols).