Say you are a network engineer, and you recently were told your company will be building applications using a distributed/microservices architecture with containers moving forward. You know how important this is for the developers — it gives them tremendous flexibility to develop and deploy money making applications. However, what does this mean for the network? It can be much more technically challenging to plan, operate, and manage a network with containers than a traditional network. The containers may need to talk with each other and to the outside world, and you won’t even know IF they exist, let alone WHERE they exist! Yet, the network engineer is responsible for the containers connectivity and high availability.
Since the containers are deployed inside a host — on a virtual ethernet network — they can be invisible to network engineers. Orchestration tools such as Docker Swarm, Apache Mesos or Kubernetes make it very easy to spin up and take down containers from various hosts on a network – and may even do this without human intervention. Many containers are also ephemeral and the traffic patterns between the servers hosting containers can be very dynamic and constantly shifting throughout the network.
Cumulus Networks understands Continue reading
The post Worth Reading: Hyperconvergence and silos appeared first on rule 11 reader.
It isolates communications between cloud apps and devices.
The platform supports Docker, Kubernetes, Mesos, CoreOS, Microsoft, Red Hat, and VMware.
Late entry into the storage space allowed for a platform designed for the cloud-native environment.
On this edition of the History of Networking at the Network Collective, we discuss the history of BGP churn and Add Paths with Daniel Walton of Cumulus Networks. The original post on the Network Collective can be seen here.
The post History of Networking: BGP Churn with Daniel Walton appeared first on rule 11 reader.
This is the company's first cloud-based platform.
Uncle John Stands Back, At Last.
The post Finally, a post-Chambers Cisco appeared first on EtherealMind.
Using closed hardware appliances creates risk regarding features and supplier responsiveness.