Hello,
NSX-V 6.3 and NSX-T 1.1 is released about the same time, so there are new features around Microsegmentation, Application Continuity and Automation. The Design Guide for NSX 3.0 is for NSX Vsphere. Is there a similar guide for NSX-T also? In comparasion when can NSX-T may be more suitable, and when can NSX-V be appropriate for use cases? Is the licensing model the same for both products?
Some Points to note may be:
- NSX-T supports multiple Hyperviors, so it may be more appropriate for Hybrid Hypervisor Environments. What may be the thread offs if NSX-T is used for Vsphere, wrt Performance, Automation, Application Continuity, Network Services as Load Balancing, VPN, NAT?
- If containers as Photon or Docker, CoreOS, Kubernetes is used, or planned to be used in the future, if NSX-V or NSX-T more appropriate for Integration with these type of environments?
- Manageability, Orchestration and Automation for Cloud, Vmware Amazon Cloud, Openstack and Hybrid, Private Cloud design and architecture what may be the pros and cons comparing these environments?
http://thenewstack.io/vmware-foresees-future-photon-kubernetes-nsx-work-bare-metal/
https://my.vmware.com/web/vmware/details?productId=580&downloadGroup=NSX-T-101
https://www.vmware.com/support/pubs/nsx_pubs.html
https://www.vmguru.com/2017/02/vmware-nsx-6-3-is-here/
https://vminstructor.com/2017/02/02/introducing-vmware-nsx-for-vsphere-6-3-vmware/
https://blogs.vmware.com/networkvirtualization/2017/02/nsx-winter-releases.html#.WJQgCdx95I0
Thanks in Advance,
Regards,
