Looking at VMware.com/nsx, there is just NSX. Are there still different NSX products? Will the future integration with AWS (and hopefully Azure) work with the NSX at VMware.com/NSX, or does it need a different flavour of NSX?
Cross Cloud Services will use NSX-T. NSX-T supports both stateful and stateless rules
VMware Cloud on AWS (the Cloud Foundation SDDC stack) runs as a service and will use NSX-V
NSX on Amazon the following links may be helpful about how Vmware Cloudon Amazon works, it may be on bare metal ESXi hosts and NSX on AWS.
https://blogs.vmware.com/vsphere/2016/10/vmware-cloud-on-aws-a-closer-look.html
https://blogs.vmware.com/vsphere/2016/12/vmware-cloud-on-aws-videos.html
NSX-T (NSX Transformers) supports KVM, about Hyper-V don't know if in the future possible.
Regards,
So for cross-cloud, will that work with NSX, or NSX-T? And if it is NSX-T, is the NSX-T DFW stateless? I guess some of that might be clear soon..
Cross Cloud Services will use NSX-T. NSX-T supports both stateful and stateless rules
VMware Cloud on AWS (the Cloud Foundation SDDC stack) runs as a service and will use NSX-V
Do we need NSX-T if plan to use on premise and Amazon at the same time as a Hybrid Cloud Solution? If that's the case then for designs that support VMC on Amazon confider NSX-T on the first installation.
About licensing there is no difference between NSX-V and NSX-T, and it seems they are convertable to eachother if infrastructure changes in the future:
https://blogs.vmware.com/networkvirtualization/2017/02/nsx-winter-releases.html#.WJS3CNx95I0
Starting today, customers who purchase VMware NSX have the option of downloading and installing either platform and can switch between the two if needed without having to re-purchase NSX. And should your needs change, you can switch between the two.
About features switching from NSX-V to NSX-T, if currently services such as NAT, Load Balancing and VPN Used, is it possible to use both V and T concurrently?
https://vcdx133.com/2017/02/02/nsx-v-6-3-and-nsx-t-1-12-0-announcements/
Generally speaking hybrid cloud should use VMC on AWS using NSX-v, but speak to your local NSX SE to gather more specifics to determine the best model. As you know the obligatory "it depends" comment will come up as every use case is slightly different.
You are correct about the blog post on licensing. A NSX license entitles you to either or.
A mixed -V and t-T environment is not possible with native tools today. Each would be managed as a separate entity.