Flow needs to expand into a "Transit Gateway" that supports all future clouds similar to Aviatrix

  • 11 February 2021

In the cloud the Enterprises no longer have access to the physical or virtual network that is being provided by each major Cloud Service Provider.  You have basic networking constructs in the cloud that are quite different from each cloud provider that is a black box.  It is required to have a consistent SDN transit approach to be effective in a Multi-cloud world into the future when 5G rolls out, Edge technologies and mainly within the oncoming containerized API Matrix evolution to come.,  Telecom providers with MEC will put pressure on the large cloud providers where the hardware within the Cloud eco-system will become commoditized.  Various new players introduced into Multi-cloud will evolve very quickly and transform where  VPC and VNET will be at the edge and it will be a containerized world. Nutanix Cloud Flow needs to tranistion to a business model similar to Aviatrix Transit SDN approach.  Kubernetes containers will be a game changer in the future where Nutanix will need to shift its efforts in becoming a truly Multi-Cloud OS by adopting and building on network constructs that extend everywhere defying network latency and application latency.  Nutanix cannot solely rely on native constructs of the Cloud Providers where they deliberately do not provide good network transit service so your forced into Cloud vendor lock-in. 

The clustering approach that Nutanix is offering now will work with the large Cloud Providers but in the future it will be an Aviatrix SDN transit model across all clouds and distributed edges that will prevail in an SDN API future matrix world where everything will be interconnected to be at the heart of doing commerce.

*Wire speed encryption to and from On-prem to the Cloud and edge. Inside the cloud they support 90 Gig of encryption.is key.

*Multi-Cloud Segmentation with a consistent connection policy across clouds and edge.

*Service insertion and chaining works very well in the three layer supported model of Aviatrix where the Application Layer at the top has smart intelligence communicating with the transit Aviatrix layer which has smart intelligence built-in communicating with the Access layer of the Aviatrix model connecting to all clouds of the future.  Next-Gen Firewall and F5 Big –I P SSL decryption in a service chain works better within a SASE type model.  Insertion and Service chaingin handled very seamlessly sending traffic for inspection with an Aviatrix type of SDN model where Flow needs to go.

*Strong Visibility into the cloud with Aviatrix Co-pilot  is another game changer to gain visibility into the black box of Cloud to assist with troubleshooting. The Aviatrix multi-cloud backbone of SDN services with Controllers and Gateways is where Nutanix needs to go with Flow.

*Intially it might be easy to adopt native cloud resources in a multi-cloud world you need to inject a portable adoptable mechanism that will support VPC and VNET at the Edge as well as in the Cloud and On-Prem.

*How do you maintain accuracy as things flow and change within all of the different environments?

*IP reachability, symmetry, multiple path flows, DR scenarios, and traffic end-to-end correctness is end goal.  How does the overall framework stay the same as things grow and change?

*If you stretch work-loads across clouds latency how can Nutanix help with all clouds to optimize at the network layer, down into the container level, and up into the application level  so customers experience is delightful to concentrate on their business of transformation?  Work-load latency will also include automation, AI, Machine Learning, etc.  My recommendation is to seriously consider where a containerized world will be heading to where there will be many clouds and a transit layer is the glue to all of these new Cloud worlds that will evolve doing commerice within an API matrix.

I thought I would summairze:  Containerized Eco-Sytem and Edge will require optimized routing of traffic within a transit gateway type process similar to what Aviatrix has perfected with SDN.  Optimizes the Applications, workloads, and visibility are very important with the future multi-c;loud which includes TELECOM MEC getting involved and putting pressure on the big cloud players.  The future will entail many clouds so Nutanix Cloud Cluster approach will not work at the Edge and with MEC 5G there will be a huge matrix of API eco-system.  Nutanix will need to evolve flow to handle the transit servide to the new digital economy Eco-system of the API matrix of circuits and clouds.  The edge will be VPC and VNET like in and of itself as extensions of clouds.  Containers Nutanix needs to concentrate on network and security and the deeper levels into communicating directly with containers and Nutanix Flow also need to work at the higher application layers to optimize the Application layers   It is like in many respects the industry has ignored latency and what networking can do with SDN.  It can no longer be ignored in the new containerized API matrix world with 5G and now 6G in the works.

More information pertaining to Anthos.


Networking is the foundation for all distributed computing micro-services architecture in the future like Anthos and Istio, which includes many network-to-network, constructs that need to work together. Anthos Multi-Cloud infrastructure resolves many problems dealing with application performance.  The network piece is critical you need a robust advanced networking system within a Multi-Cloud OS (FLOW) to run across multiple clouds and On-Prem.  Moving packets from one cloud to another place amongst clouds requires FLOW to evolve.  You can copy templates to move Anthos environments between clouds to have consistency in your micro-services environments.

Networking and workload portability will directly rely on Flow for Nutanix future success with distributed micro-services computing.  Aviatrix like models helps with the complex encryption aspects of micro-service communication between clouds which is important to include within FLOW.  Micro-segmentation is also key to success of segregating traffic to and from On-prem and amongst clouds.  If you send traffic out to SASE type models the network constructs are also critical within a micro-services environment to incorporate within FLOW capabilities.

The issue with native cloud constructs for Transit is when you join it to the other major cloud providers it doesnt scale well.  You need a networking abstraction layer full mesh like Aviatrix or future Nutanix Flow so you have a single pane of glass to connect all of the other transit.  You need to look past the major cloud providers in the future and build the network transit abstraction layer with MEC Telecom and other API Matrix ecommerce of the future.  API Matrix ecommerce is key to consider it is like the internet for Ecommerce utilizing Virtual Machines to communicate between companies with containers Anthos and Isidio.

VDC.Cloud is using Aviatrix as a hosted environment for its Global clients.  They build a multi-cloud backbone across Global Multi-Cloud Regions to bring solution to as many customers as they want because Aviatrix transit model scales out horizontally very well to as many Cloud Providers as you want MEC Telecom 5g & 6G or traditional. You can easily segment networks in the Multi-cloud environment as well.  Internet and or Private solutions can scale out. It would be nice to see Nutanix with Flow scale out in a similar manner globally.  I have been in Infrastructure industry for close to 30 years and the Aviatrix model is the true North.  For Nutanix to survive at scale they need to market this concept. 


The Ultimate Cloud Networking Framework For Global Software Service Providers



The API economy is another article for Nutanix to review it goes hand-in-hand with Aviatrix transit model to for Application Optimization, Anthos & Isdios along with Nutanix VM Multi-Cloud OS within the constructs of the new Internet economy led by Nutanix eco-system.   You will see in the article they explicitly talk about the API economy if Nutanix digs deep into this I think this is the true North.  I can foresee all customers wanting to be a-part of the API economy for digital transformation.




Ravi, Further thoughts about SASE investments and even SDWAN can be replaced with the Aviatrix abstraction layer approach.


The future of multi-cloud requires more than turning over the future to the native cloud constructs from each major cloud provider, the goal is to speak to a transit abstraction layer with gateway constructs that acts like an abstraction layer across all clouds with simple terraform templates.  The terraform templates approach can  be used On-prem, at the Edge, distributed cloud, amongst all clouds as an API matrix in tandem with building the Nutanix Eco-system ecommerce for all.  The Aviatrix model allows you to service chain with high integrity encryption performance, availability, scale, low latency, and visibility & control that enterprise want and need that Nutanix can easily adopt with flow. 


 I strongly feel Nutanix and its customers do not need to invest in a SDWAN vendor and or even a traditional SASE on-ramp vendor.   Adopting the Aviatrix transit model with controllers and gateways in-the-cloud along with on-prem and edge HCI VM containerized innovations that replace traditional Telecom routers.  The Aviatrix is a solution for in-the-cloud but you can extend gateways on-prem when there are more and more Edge VDC & VNET’s spread-out when adopting 5G, 6G, and IOT, etc.  The future entails a distributed cloud to service a new ecommerce Internet API matrix via containerized constructs via Anthos, Istio, and Nutanix HCI containerized Cloud OS approach.


Lumen is partnering with Dell \ VMWare to configure edge VMware based products to communicate to-the-cloud and in-the-cloud (Distributed) for 5G, 6G, and IOT future e so from a competitive landscape it is important to leverage flow as a transit construct in tandem with say Nutanix HCI innovations to allow VM’s to act like edge router gateways with a containerized approach.  I think this is a smart idea for Nutanix to develop and partner with a Telecom Vendor that can be serviced via HCI VM or containerized.  I think Nutanix can capitalize off the HCI appliances connected at the edge, distributed edge, on-prem, in-the-cloud versus SDWAN approach.  I think it is best to bypass SDWAN and SASE traditional approach and use Aviatrix transit abstraction with gateways on-prem gateway in Nutanix VM’s and in-the-cloud distributed gateways.  The Nutanix flow controller and gateway constructs scale out beautifully to address encryption scaling issues and SASE service-chaining so Nutanix could truly be a SASE provider with FLOW utilizing the Nutanix transit controller & gateway adoption methodology attaching to every VPC and VNET at the edge and in-the-cloud.  I am not a fan of service-chaining unless you have the visibility with the SDN gateway attached approach so next-gen Firewalls can do their next-gen security anywhere in the cloud and on-prem at scale with high integrity performance. Nutanix flow allows for easy micro-segmentation, zero trust, and SASE constructs so Nutanix can easily join this digital transformation with network and security working together as one with low latency via the flow controller with gateway constructs.  You can mix and match flow 3.0 with cloud native constructs within any cloud.  You can leverage infrastructure as code and you can merge infrastructure as code joining network and application aspects as one evolution that all customers can take advantage of.  You can create a common pipeline with Devops, Ops, and Engineering.

Terraform by Hashicorp Video below stresses the importance of API standardization if and whenever possible and open standards practices for vendors when developing Multi-Cloud etiquette (infrastructure as code) (Infrastructure of and for the future) with everything multi-cloud and distributed cloud is key.  Below is the other key piece that goes along with Aviatrix transit approach. I am not sure if calm can be geared more towards open standards of template and scripting models similar to the practices of Hashicorp with Terraform.  Enterprises do not want many different versions of automation tools and within different proprietary platforms.  Maintenance, learning and upkeep is a cumulative headache.  Example:  Hashi corp language as code  feeds Terraform > which feeds providers native constructs within many clouds like AWS, Azure, and Google, etc.


Challenges & Opportunities of Multi-Cloud Adoption   API Standardization and open standards when building out infrastructure as code.

Good Video below from Hashicorp



Aviatrix Transit Technical Features Overview -  Includes Micro-Segmentation and high lights all of the transit features very well - Infrastructure as Code included as well.


Note:  I would look for talent from anyone that has experience at Hashicorp and or Aviatrix.  Simply amazing multi-cloud heaven.




Watch this video if you could at your leisure, please very insightful.  I could see this coming to fruition and there is a short video to highlight you no longer need SDWAN.  I refereced in another post  that we no longer need SDWAN in the picture with the Aviatrix model there are new ways to effectively do this better.  The power of the Aviatrix model has so much flexibility it can replace so many other technologies to become SASE, Micro-segmentation, zero trust, effective traffic steering (service-insertion done the right way, encryption at scale, etc; because all clouds will be the center of the universe through a transit abstraction layer with key placement of the Aviatrix gateways is key off-prem and on-prem to utilize as true Multi-Cloud done right.  I have been in the infrastructure for close to 30 years.  Please look into this Aviatrix model.  You no longer need SDWAN which is huge.  There are SAML tie-ins and other constructs to help connect you to the Cloud as highlighted in the video below.





HashiCorp is a very important key for the transit abstraction layer model to work via Nutanix Multi-Cloud OS in the future and stich into any cloud.  It is via Teraform but maybe Calm can capitalize off the same constructs that Terraform does via Hashicorp model.  Must watch video as well for the whole Multi-Cloud to work effectively and seamlessly with many rich features that alleviate stale ineffective native cloud constructs that simply don’t scale.




LCAAS - Local Cloud As-A-Service new-model kicked off from Lenova Channel Excecutive is predicted to grow as a competitive advantage for vendors to work together.  This type of model is very intriguing for Nutanix to be a part of.  The power is in numbers that are a part of a best-of-breed team.  This is a channel partner initiative that is very interesting for all businesses.  I know the Nutanix CEO loves anything Channel Partner Specific.  This goes along with everything above as a multi-cloud inititiatve.



Towards the End of This Video a Great Question:  “What does SnowFlake look like connecting across clouds within Aviatrix because Snow Flake is new in Azure and continually growing as the Defacto Data Lake platform standard.  Can Nutanix emulate Snowflake like Data Lake PaaS service across clouds?  Abstracting storage from Compute.  Abstracting enivornments is in Nutanix Wheelhouse so abstracting storage and data from compute is Nutanix Eco-system friendly.



Note:  I mention this because connecting PaaS service between clouds will be very important within a Multi-Cloud OS Eco-system.



I thought the questions would be beneficial for Nutanix to understand as well in regards to what is important from a large legacy SILO Enterprise trying to adopt more cloud in the Multi-Cloud OS new world we live in.


SASE Questions:

Secure SDWAN EDGE Fortigate  - Security and SDWAN combined together.  What are some of the uses cases as to why company X wouldn’t align with and SDWAN \ Security Vendor at the edge with SDN orchestration versus Internet Gateway to the Cloud?



Segmentation & legacy tunnels roadmap transition to application Fabric network and security model from Vendor X?


Palo Alto Prisma complaint from Security is the bandwidth model per megabyte is too expensive.  Not sure how to understand per user Vendor X model of a SASE provider costs?


SDWAN for Metro-E backhaul model for New York.  How does this come into play if SASE provider owns SDWAN?


Describe the backhaul internet traffic cost savings model of  SASE provider X.  I am speaking about New York in general where many of the remote Sites are Metro-E and go to a central New York Hub.  Do you feel with the SASE X model it would be more beneficial to have local internet breakout with larger bandwidth consumption per Site? 


Cloud, mobile access, IOT, security and management is it very complex without SDWAN? Encrypted Underlay across all your various types of network transports.  Will Company X need a SASE Vendor X offering plus alignment with an SDWAN vendor?  Currently we are using VERSA through Century Link for an SDWAN solution.  It appears Palo Alto purchased Cloudgenix so I am trying to understand SASE at the Edge minus SDWAN for Zscaler.


How many tunnels can you support?  Do we have visibility?


Important to align with CISO initiatives.


What does SASE mean to Prisma versus Zscaler?


Dual-stack Internal DNS access to applications because of happy eyeballs.


Can the internet be the new backbone?


What does In Region mean versus a pop that takes you to Microsoft Teams Regional Microsoft Data Center presence?


SDWAN Local Firewalls versus Vendor X Internet Gateway and Private Access models?  Does SDWAN orchestration work well enough to give you all of the visibility you need?


Cloud enabled, mobile, IOT, Guest WIFI at branch Segmentation, Zero Trust, Cisco ISE.


 With Change Comes Challenges:

*Networking Related Challenges

  • Deliver a multi-cloud environment
  • Global Visibility into all IT assets
  • Management at Scale
  • Automation of IT Workflows

*Security Related Challenges – App Centric Policy Focus

  • Increased Attack Surface
  • Complex Threat Landscape
  • Overburdened Security Operation Teams
  • Threat Detection and Remediation at Scale

*Vendors Pivotal a Role in Network Modernization

  • Cloud - Public, Private, Multi, Hybrid (Orchestration) IAAS, SAAS, and PAAS
  • Containerization
  • Software Defined Perimeter
  • Internet of Things

Note: What does Nutanix believe is foundational to drive Enterprise Modernization within its platform?

*Vendor Perspective & Strategy

  • Enabling Multi-cloud and direct internet access (DIA) from edge locations has become the paradigm shift for Enterprises
  • Operational Simplicity and a Devops deployment model for networks are critical factors for agility
  • Cloud Native delivery platform Network \ Security services will be delivered increasingly as-a-service (Data Cloud is very Interesting to separate Compute from Storage – Data-as-a-service

Note: Multi-Cloud Modernization and Edge Modernization are keys to the new Paradigm shift

Steps To Becoming a Fully Operational Smart City Provider: Nutanix Future Market Opportunities

{Nutanix Continually Evolving to Become a Fully Operational Smart City Provider}

How does Nutanix Reach Out to this Industry (TAM)?

Building upon open digital systems.

Cities need to begin integrating API gateway software to enable smart initiatives and create an ecosystem in which it’s easier and more efficient to add new technologies best-of-breed. This simplifies complex procurement processes and quickens the pace of innovation.   Very important to create a matrix of ecommerce for all businesses to participate in the new digital economy of smart cities.

Planning for Big Ideas.

Start planning now for the technology advancements so they can happen quickly and a great deal of R&D will need to go into WIFI infrastructure and smart city initiatives to back next generations technology.  Cities must exercise forethought and anticipate innovation to eliminate the need for retrofitting later.

Encouraging private and public partnerships

Choosing the Right Networking Technology to Support Smart City Initiatives is what all of the future cities will be navigating upon their journey.   How can Nutanix help build the Smart Cities environment for the future with its vast product-line offerings (Is the API key to build around with Flow Multi-Cloud OS Transit themes similar to Aviatrix)?  How can Nutanix package the various product offerings (Eco-system) into tangible products that meet the requirements spelled out by the various Cities?  How can Nutanix differentiate its offerings over other companies?


*Network is the Foundation – Rethinking the Infrastructure.

*Simple, Secure, automated network topologies.

*IOT and Public WIFI offerings packaged.

*Telemetry and information that allows for better visibility and planning.