When considering containers and how they connect to the physical network, it may be easy to assume that this paradigm is identical to the connectivity model of virtual machines. However, the advent of container technology has really started to popularize some concepts and new terminology that you may not be familiar with, especially if you’re new to the way linux handles network resources.
It’s important to understand this concept, because containers are NOT simply “miniature virtual machines”, and understanding namespaces is very important to conceptualizing the way a host will allocate various system resources for container workloads.
Generally, namespaces are a mechanism by which a Linux system can isolate and provide abstractions for system resources. These could be filesystem, process, or network resources, just to name a few.
The man page on linux namespaces goes into quite a bit of detail on the various types of namespaces. For instance, mount namespaces provide a mechanism to isolate the view that different processes have of the filesystem hierarchy. Process namespaces allow for process-level isolation, meaning that two processes in separate process namespaces can have the same PID. Network namespaces - the focus of this particular post - allow Continue reading
When considering containers and how they connect to the physical network, it may be easy to assume that this paradigm is identical to the connectivity model of virtual machines. However, the advent of container technology has really started to popularize some concepts and new terminology that you may not be familiar with, especially if you’re new to the way linux handles network resources.
It’s important to understand this concept, because containers are NOT simply “miniature virtual machines”, and understanding namespaces is very important to conceptualizing the way a host will allocate various system resources for container workloads.
Generally, namespaces are a mechanism by which a Linux system can isolate and provide abstractions for system resources. These could be filesystem, process, or network resources, just to name a few.
The man page on linux namespaces goes into quite a bit of detail on the various types of namespaces. For instance, mount namespaces provide a mechanism to isolate the view that different processes have of the filesystem hierarchy. Process namespaces allow for process-level isolation, meaning that two processes in separate process namespaces can have the same PID. Network namespaces - the focus of this particular post - allow Continue reading
This is a liveblog of the Day 1 keynote at the OpenStack Summit here in Tokyo, Japan. As is quite often the case at conferences like this, the wireless network is strained to its limits, so I may not be able to publish this liveblog until well after the keynote ends (possibly even later in the day).
After a brief introduction by one of the leaders of the OpenStack Japan User Group (I couldn’t catch his name), Jonathan Bryce takes the stage. Jonathan takes a few minutes to welcome the attendees, thank the conference sponsors, and go over some logistics (different hotels, meals, getting help, etc.). Jonathan announces the first individual certification for OpenStack—the Certified OpenStack Administrator. The certification test will be available starting in 2016. Not many details are given; I assume that more details will be released in the coming days and weeks.
Jonathan also takes a moment to talk about Liberty, the 12th release of OpenStack. Based on the features added, he feels that manageability, scalability, and extensibility were the key themes for Liberty. This leads Jonathan into a discussion of users and developers, sometimes (not beneficially) separated by sales and product management. Jonathan feels that Continue reading
Oracle's IaaS is tuned for an Oracle world, not surprisingly.
ParStream would help Cisco crunch all of that IoT data.
The year-old startup is stocked with former government security experts.
Grupo Santander wants a self-service internal cloud and a migration to KVM.
Network Break analyzes Dell's acquisition strategy, examines HP's decision to shutter its public cloud offering and sell TippingPoint, discusses SolarWinds going private, celebrates a milestone for the Let's Encyrpt project, and more!
The post Network Break 59: Dell’s Vision, HP Folds Public Cloud, HTTPS Advances appeared first on Packet Pushers.
We wrap up our series on the new SDx infrastructure (SDxI) with some final thoughts on how to help your organization succeed in a changing SDx world.
By 2025, Oracle expects to rule the cloud.
Whatever you design , it should be usable first. Computer network design is not an exception.You are not designing a network to support one service only such as VPN or Internet.It should provide enough functionality for today and future needs. Your design should be usable today and the future ! It was so common to use… Read More »
The post Your design should be usable ! appeared first on Network Design and Architecture.
When quality and reliability issues dog UC deployments, most of the time the problem is with the underlying network. UC SDN can help resolve these issues so organizations get the most out of UC systems.