- NSX-T Policy API Explorer, Docs and Sample Updates for VMC
- Deploying a vCenter Server Appliance (VCSA) in VMC?
- NSX-T Opaque Networks now supported with Cross vCenter Workload Migration Fling
- Integrating Github Actions with vSphere and VMware Cloud on AWS
- ESXTOP and VMware Cloud on AWS
- vSphere Tag Attach/Detach events now in VMware Cloud on AWS
- Automating complete HCX deployment and configuration to first cloud migration using PowerCLI
- Running sk8s (Simple Kubernetes) on VMC with an AWS Elastic Load Balancer
- Which NSX-T Policy APIs are used in the NSX-T UI in VMC?
- How to retrieve the NSX-T Overview Info (SDDC Public IP, Appliance & Infra Subnet, etc.) in VMC?
- Common PowerCLI examples for VM Provisioning in VMware Cloud on AWS
- Using NSX-T Policy API to retrieve the Routing Table in VMC
- Changing the default behavior of the NSX-T Distributed Firewall (DFW) in VMC to Deny All
- Quick Tip – Import OVF/OVA as VM Template using OVFTool 4.3 Update 1
- New VMC API to rename SDDC
- How to retrieve the CSP Refresh Token expiry using the CSP API
- Managing Distributed Firewall Rules in VMC using PowerShell & NSX-T Policy API
- Learning more about the Nitro platform which will power VMware Cloud on AWS Outposts
- VMware Cloud on AWS reInvent sessions posted
- Can a VM in the VMC Compute Network access the SDDC Management Network?
- Automating Hybrid Cloud Extension (HCX) Manager initial configuration for VMC
- Quick Tip – How to clear all Hybrid Cloud Extension (HCX) Migrations in the vSphere UI
- Can I assign my Active Directory users a non-CloudAdmin vCenter Server role in VMC?
- Enhancements to Hybrid Linked Mode (HLM) in VMC using the new vCenter Cloud Gateway
- Nested ESXi on VMware Cloud on AWS (VMC)
- Automating new Cloud Motion with vSphere Replication using Hybrid Cloud Extension (HCX) API
- Automating Hybrid Cloud Extension (HCX) Manager OVA deployment
- NSX-T Policy PowerShell Community Module for VMC
- Create vCenter Alarms for monitoring HCX migration events
- vMotion across different VDS version between onPrem and VMC
- Getting started with the Hybrid Cloud Extension (HCX) APIs
- How to unregister Hybrid Cloud Extension (HCX) from your onPrem vCenter Server?
- Getting started with the new NSX-T Policy API in VMC
- Using VMC API to answer commonly asked questions about your SDDC
- Quick Tip – Requirements for using Guest Operation APIs (Invoke-VMScript & Copy-VMGuestFile) in VMC
- Creating a vSphere Content Library directly on Amazon S3
- Automation with the VMware Cloud Services Platform (CSP)
- VMworld US 2018 sessions on VMware Cloud on AWS
- Resource Pools, Folders & VMC now supported with Cross vCenter vMotion Utility Fling
- Automating VM Template management using Content Library in VMC
- Auditing detailed operations within VMware Cloud on AWS using the Activity Log API
- OVFTool and VMware Cloud on AWS
- New Adventure
- Getting started with Hybrid Cloud Extension (HCX) on VMware Cloud on AWS
- VMware Cloud on AWS – VM Creation Date available in vSphere API
- VPN Configuration to VMware Cloud on AWS using pfSense
- VMworld Hackathon Hardware/Software BOM
Search Results for: VMware HCX API
PowerCLI 11.2.0, was just released last week and for a "dot" release, it includes a number of new capabilities and enhancements. One of the most exciting features for me personally was the introduction of the VMware Hybrid Cloud Extension (HCX) PowerCLI module which I also had the pleasure of working on and providing early feedback to the HCX Engineering team. The new HCX module enables customers to use PowerCLI to now easily automate the HCX Fleet deployment (Interconnect, WAN Optimization and Network Extension) as well as perform bulk live migrations of workloads between two HCX-enabled environments, with on-premises vSphere to VMware Cloud on AWS (VMC) being the most popular.
I have written a number articles on HCX Automation using both the HCX REST API and PowerCLI and with this latest PowerCLI module, I realized that we now have complete end-to-end automation with PowerCLI from the HCX OVA deployment to initial configuration and fleet deployment to your very first HCX vMotion! This is quite exciting as I know a number of folks have been asking about automating the fleet deployment, especially for enabling quick proof of concepts and quickly showing the value of HCX to our customers for moving large amount of workloads without any downtime.
Below, you will find a breakdown of the HCX setup which I have split into three sections, each section includes the respective PowerCLI sample code that can easily be adapted to your own environment. I look forward to seeing what customers do with the new HCX PowerCLI module and if you have any feedback, be sure to leave a comment or better yet, file a feature enhancement using the PowerCLI Feature Request Tool.
Following up from my previous Hybrid Cloud Extension (HCX) Automation article which looked at deploying the HCX Manager OVA, this article will now focus on automating the initial configuration of HCX Manager including the registration to HCX Cloud which will enable the on-prem HCX Manager to be used with VMware Cloud on AWS (VMC). Once HCX Manager is up and running, customers can configure the system using the HCX VAMI interface which is available on port 9443 via the UI or in our case with the HCX VAMI APIs.
I have updated my HCX PowerShell Module to include 8 additional functions that can be used for initial configuration of HCX Manager:
During the development of my Cloud Motion with vSphere Replication automation script for Hybrid Cloud Extension (HCX), I extensively used the HCX vSphere UI for testing and debugging purposes.
Under the Migration view, you can see all active and completed migrations, including any failed migration attempts. In my particular environment, there had been a few hundred migrations and with my additional testing, that added quite a few more. Although you can filter by name or sort by the type of operation, it was still not very convenient for me while developing the script. I wanted a quick way to view the details after calling the HCX APIs and by the time I jumped to the UI, I would have missed a few of those updates.
In speaking with one of the HCX Engineers, I found out that you could simply drop all migration history from the internal database (this would remove all the history for past migrations including failures). In general, I do not see this being something customers would have a need for in Production, as you would want to keep all the history for auditing or debugging purposes. This is probably more for demo or testing purposes and below are the instructions on how to clear all migrations from your HCX Manager.
Cloud Motion with vSphere Replication is the newest migration type that has been added to the Hybrid Cloud Extension (HCX) solution, which was also demonstrated during the VMworld US 2018 keynote (watch here). Unlike the traditional Bulk Migration, which also uses vSphere Replication to perform the initial replication, Cloud Motion with VR does not incur any downtime during the VM switch over. This is possible with our most beloved vSphere feature, vMotion!
With Bulk Migration, the VM on the source vCenter Server must be shutdown before the newly replicated VM on the destination vCenter Server can be powered on or else a network conflict will occur. Using Cloud Motion with VR, the VM is simply vMotion'ed from the source vCenter Server to the destination vCenter Server and because the VM's storage has already been replicated, the only thing that needs to transfer is the memory state of the VM.
All three HCX Migration Types can be scheduled from the HCX UI using the vSphere Client or automated using the HCX API. The latter option is definitely ideal for customers with large number of migrations but it can also help with smaller migrations as it reduces the amount of user input required when using the UI and ultimately, this reduces user errors.
To help demonstrate the HCX Migration APIs, I have updated my VMware HCX PowerShell Module to include the following two new functions:
VMware Hybrid Cloud Extension (HCX) is the de facto VMware solution when it comes to Enterprise scale workload migration whether that is from onPrem to onPrem or from onPrem to Cloud, including our VMware Cloud on AWS (VMC) offering. In fact, one of the most popular use cases for HCX right now is datacenter evacuation/consolidation and customers are migrating their workloads to VMC because they want to get out of the business of running datacenters and get back to running their core business. This is especially attractive for customers wanting to expand to new markets without requiring the need of new datacenters. This makes a ton of sense, especially when you go beyond the initial CapEx, its the on-going OpEx costs that folks may not always be thinking about immediately and being able to easily scale up or down is not always possible for most onPrem environments.
HCX already provides a rich UI interface within the vSphere Client for scheduling migrations including the new Cloud Motion with vSphere Replication feature which was announced at VMworld US 2018.
However, it should come as no surprise that our customers are also interested in Automation, especially as it can help expedite migrations and remove potential user error, especially around mapping the destination networks which can be quite daunting for a large number of migrations. The good news is that HCX provides a Restful API that allows customers to automate all aspects of HCX including the HCX VAMI UI for initial configuration as well as consuming the HCX services which are exposed in the vSphere UI.