OpenStack Network Topology 101


OpenStack is rapidly becoming the de-facto standard in cloud computing. OpenStack helps organizations of all types discover the increased flexibility and speed to market that a self-service Infrastructure as a Service (IaaS) cloud provides. As enterprises and service providers adopt deployment and operational models of Web IT companies, it’s imperative that the clouds must be designed and deployed properly with best practices. Being open source, the OpenStack community has embraced choice across software layers. 

OpenStack Typical Topology:


PXE and IPMI to enable bare metal provisioning for servers - OpenStack allow network teams the ability to use commodity server hardware to build scale-out IT environments. 

All devices within an OpenStack cloud require some form of network connectivity. In some cases, nodes require access to more than one network segment. The design must account for sufficient network capacity and bandwidth to ensure that all communications within the cloud — traffic across the network (also known as east-west) as well as in and out of the system (also known as north-south) have sufficient resources available.

Standard well proven leaf-spine network topology are the super highways for directional traffic that like transit traffic that requires ingress/egress  north-south and  low latency data traffic that needs to traverse east-west. 


OpenStack Benefits:

Large-scale cloud providers are showing success through deploying repeatable and scalable infrastructure that adopts a scale-out model rather than a standard scale-up model  espoused by traditional virtualization vendors. OpneStack accommodates a solution for both a simple VLAN or the modern VXLAN implementation.


■■  Agility

By enabling true cloud capabilities through a scale-out, Web IT architectural approach, OpenFlow enables OpenStack deployments to achieve the same goals that hyper-scale Web companies can in terms of automation and business agility — such as minimal downtime, improved SLAs, scalability and the ability to respond to market dynamics in a full self-service and on-demand manner.


■■ CapEx:

OpenStack represents the emergence of a commodity cloud approach. By deploying OpenStack in conjunction with IP FABRICS services leveraging commodity hardware can lead to significant lower capital expenses.


■■ OpEx:

Beyond CapEx, significant benefits of deploying OpenStack with are realized through vast reductions in OpEx, including improvements in automation, self service and rapid activation that enable networks to be managed in conjunction with compute resources.