Networking in a Hyperconverged
In a previous article, we covered the three different types of data traffic that are involved in a converged private cloud network and need to be able to run side by side without affecting each other. In this article, we’ll discuss three challenges that are associated with network deployment in a hyperconverged private cloud environment, and share several methods that we’ve developed internally to overcome them.
The Main Challenge: Bring Your Own (Physical) Network
One of the main challenges of deploying a hyperconverged solution in a data center is the diverse physical configurations. The smart network layer may be the leading component that is tasked with the need to automatically learn the physical network layer’s topology and capabilities. Modern data center operations are expected to be automated and fast. There is no place for traditional customized, cumbersome installation and integration processes. And when deploying hyperconverged smart on top of a data center , running a fast and automated deployment is necessary.
In every organization, IT operations leaders have their own philosophy regarding how to deploy, integrate and manage network traffic. In most cases, they are not going to change easily. From our discussions with enterprise network experts, I’ve found that they all have their own specific “network philosophy” that generally includes the following phrases:
“We believe in running internal and guest networks over the same physical network”
“We believe in running the external communications over the 1G on-board configuration interface, while the rest of the traffic runs on 10G”
“We like to keep things super simple and run everything on a single Interface”
Since IT organizations invest in their data centers that have their own custom built, established networks (devices and ), adjusting a hyperconverged cloud solution accordingly can be quite complicated.
1. Deploying Logical Over Physical
Physical networks are a group of appliances that are connected using protocols. Logical networks are constructed out of different types of traffic and are completely agnostic to physical networks, yet still need to run on them.
Let’s say that data center traffic can be segmented into three types: red, green, and blue. Let’s also assume that according to the network admin’s philosophy, red is 1G, routed externally, and green and blue are both 10G, isolated and non-routable. It is important to ensure that each node is linked to each of the three different logical networks on certain physical interfaces. Only when the physical is connected we can connect the logical layer. This can be done by separating the types of traffic from the physical source (the node), then allocating each logical type of traffic to a physical network. In the end, each of the networks (red, green and blue) is connected to the related physical interface.
2. Automatic and Scalable Deployment
In comparison to custom deployments, which tend to be cumbersome processes mainly done by integrators, building a hyperconverged smart solution needs to deploy an environment with hundreds of nodes in a matter of minutes. In order to achieve this, deployment needs to be automatic, easy, and bulletproof. In addition, deployment techniques should not require user intervention per node, which means that users should not manually configure the network, or analyze how each server is physically connected to the network. Smart hyperconverged solutions need to automatically discover and analyze an underlying network’s ………..