But maintaining network connectivity from the outside world is extremely difficult. Need an ISP or “redirection provider” that can dynamically proxy or redirect your inbound network traffic, each /32 from the internet to one cloud or the other, depending on where that particular virtual server actual lives.

So the HTTP request can get there.. more likely than not you instead want to add a server at the new provider, update DNS, drop the old server, for example.

The global internet won't let you just move IPs around and expect to get all your inbound traffic moved, assuming you can assign IP space to a cloud provider, well, the longest prefix you can do that with is normally /24.
Moving a /24 doesn't help to move just one VM without downtime though.

Or… you have your own cloud and do the same type of redirection.
Kind of defeats the point if the migration reason is DR.

You need apps that rely on DNS for public access, quickly update the DNS.
And replace the old VM with a temporary “shell” that establishes a tunnel with the destination cloud, and forwards errant traffic for a brief time.

Modern browsers with DNS pinning are working against you.

But maintaining network connectivity from the outside world is extremely difficult. Need an ISP or “redirection provider” that can dynamically proxy or redirect your inbound network traffic, each /32 from the internet to one cloud or the other, depending on where that particular virtual server actual lives.

So the HTTP request can get there.. more likely than not you instead want to add a server at the new provider, update DNS, drop the old server, for example.

The global internet won’t let you just move IPs around and expect to get all your inbound traffic moved, assuming you can assign IP space to a cloud provider, well, the longest prefix you can do that with is normally /24.
Moving a /24 doesn’t help to move just one VM without downtime though.

Or… you have your own cloud and do the same type of redirection.
Kind of defeats the point if the migration reason is DR.

You need apps that rely on DNS for public access, quickly update the DNS.
And replace the old VM with a temporary “shell” that establishes a tunnel with the destination cloud, and forwards errant traffic for a brief time.

Modern browsers with DNS pinning are working against you.

I would like to know this as well. I've been browsing around and there are comments that there eventually will (future tense) be this capability. However, it's hard to tell what can be done today. e.g. can I do things like point my premise vCenter to the private cloud to manage my guests running in that cloud? And do my host public could resources appear in my private vCenter so that I can move guests between private and public clouds.

I'm guessing some of this is future. Would be good to know how much of this is now, and if future, when we can expect some of these features?

But maintaining network connectivity from the outside world is extremely difficult. Need an ISP or “redirection provider” that can dynamically proxy or redirect your inbound network traffic, each /32 from the internet to one cloud or the other, depending on where that particular virtual server actual lives.

So the HTTP request can get there.. more likely than not you instead want to add a server at the new provider, update DNS, drop the old server, for example.

The global internet won't let you just move IPs around and expect to get all your inbound traffic moved, assuming you can assign IP space to a cloud provider, well, the longest prefix you can do that with is normally /24.
Moving a /24 doesn't help to move just one VM without downtime though.

Or… you have your own cloud and do the same type of redirection.
Kind of defeats the point if the migration reason is DR.

You need apps that rely on DNS for public access, quickly update the DNS.
And replace the old VM with a temporary “shell” that establishes a tunnel with the destination cloud, and forwards errant traffic for a brief time.

Modern browsers with DNS pinning are working against you.

I would like to know this as well. I've been browsing around and there are comments that there eventually will (future tense) be this capability. However, it's hard to tell what can be done today. e.g. can I do things like point my premise vCenter to the private cloud to manage my guests running in that cloud? And do my host public could resources appear in my private vCenter so that I can move guests between private and public clouds.

I'm guessing some of this is future. Would be good to know how much of this is now, and if future, when we can expect some of these features?

There has been a lot of talk about using OVF and vApps as the universal denominator between the private and public cloud. I think the main intent is to be able to easily upload VMs workloads to the cloud with the same tools you use today to migrate VMs to and from vSphere data centers.

It will get really interesting when somebody figures out how to get a live workload from the private enterprise to the cloud without disconnecting users!