Quality of service (QoS) is the overall performance of a telephony or computer network, particularly the performance seen by the users of the network. Above is the Quality of Service definition from the Wikipedia. Performance metrics can be bandwidth, delay, jitter, pocket loss and so on. Two Quality Of Service approaches have been defined by… Read More »
The post Do you really need Quality of Service ? appeared first on Network Design and Architecture.
The first half of 2015 was extremely productive – seven brand new webinars (or 22 hours of new content) were added to the ipSpace.net webinar library.
Most of the development focus was on SDN and network automation: OpenFlow, NETCONF and YANG, Ansible, Jinja and YAML, and Monitoring SDN networks. There was also the traditional Data Center Fabrics Update session in May, IPv6 Microsegmentation webinar in March, and (finally!) vSphere 6 Networking Deep Dive in April.
Do I have to mention that you get all of them (and dozens of other webinars) with the ipSpace.net subscription?
Read more ...The post Worth Reading: More Leaky Routes appeared first on 'net work.
There has been a plethora of docker-related info on the internet this week, thanks in no small part to DockerCon, and I was motivated to finish this blog post about container networking.
In short, it seems like most if not all container networking projects are going out of their way to give devs the feeling of a “flat” network. My question is - who cares?
Seems to me that "cloud-native" applications should be okay if two of the cattle are not on the same broadcast domain.
— Matt Oswalt (@Mierdin) June 24, 2015For this post, I am not talking about IaaS (which is arguably a declining use case). I am talking about an application cloud provider (i.e. SaaS, and maybe PaaS) where all IP addresses are assigned by the provider and under their control, within the context of the data center.
The way that most of these projects are being marketed to developers is that they provide one big flat network upon which to communicate. Why this choice of terminology? Why does “cloud-native” application design not by default include things like IPv6, or application nodes that are agnostic of what broadcast domain they are participating in?
I have Continue reading
There has been a plethora of docker-related info on the internet this week, thanks in no small part to DockerCon, and I was motivated to finish this blog post about container networking.
In short, it seems like most if not all container networking projects are going out of their way to give devs the feeling of a “flat” network. My question is - who cares?
Seems to me that "cloud-native" applications should be okay if two of the cattle are not on the same broadcast domain.
— Matt Oswalt (@Mierdin) June 24, 2015For this post, I am not talking about IaaS (which is arguably a declining use case). I am talking about an application cloud provider (i.e. SaaS, and maybe PaaS) where all IP addresses are assigned by the provider and under their control, within the context of the data center.
The way that most of these projects are being marketed to developers is that they provide one big flat network upon which to communicate. Why this choice of terminology? Why does “cloud-native” application design not by default include things like IPv6, or application nodes that are agnostic of what broadcast domain they are participating in?
I have Continue reading
In the networking world, we’re starting to see the term “cloud” more and more. When I teach classes, if I so much as mention the word cloud, I start to see some eyes roll. That’s completely understandable, as the term cloud was such an overused buzzword, only having been recently supplanted only by “software defined”.
Here’s real-life supervillain (dude owns an MiG 29 and an island with a volcano on it… seriously) Larry Ellison freaking out about the term cloud.
“It’s not water vapor! All it is, is a computer attached to a network!”
But here’s the thing, it’s actually a thing now. Rather than a catch-all buzzword, it’s being used more and more to define a particular type of operational model. And it’s defined by NIST, the National Institute of Standards and Technology, part of the US Department of Commerce. With the term cloud, we now get a higher degree of specificity.
The NIST definition of cloud is as follows:
That first item on the list, the on-demand self service, is a huge change in how we will be doing networking. Right now network Continue reading
This is a liveblog for the DockerCon 2015 session titled “Scaling New Services: From Container Creation to Automated Deployments”. This session is being led by the Disney Systems Engineering team and will feature a discussion/demo involving Docker, Mesos, Chef, Consul, and HAProxy.
The session starts with an introduction by Alex Williams, founder of The New Stack, who quickly turns it over to the Disney staff—Brian Scott and Patrick O’Connor. Brian starts with an overview of all the various companies within Disney, and the challenges that breadth creates. He then discusses the role of Disney’s Systems Engineering team, and the responsibilities of the team. That includes managing infrastructure, both on-premises as well as cloud-based infrastructure.
So, why Docker? To improve the guest experience, Disney needs to be able to move fast. They want to get away from managing VMs and cattle to managing containers and micro-bots. Brian talks about issues with onboarding developers, battling configuration drifts, and similar challenges. Disney started on their Docker journey 6-10 months ago, and lots of teams are still exploring the use cases for Docker. Some teams are already using it in the CI pipeline, and other teams are evaluating production use cases. CI is a Continue reading
This network design uses global/regional MPLS backbone as primary WAN connectivity method, with Cisco DMVPN backup. DMVPN spokes should have a regional primary hub with secondary hubs also based on location.
The post Designing A Multi-Region, Multi-Hub Phase 3 DMVPN With BGP appeared first on Packet Pushers Podcast and was written by Matt Love.
June usually signals two things in my household: the end of the school year, and the beginning of the trips to the multiplex for the latest family-friendly animated movie. This year is no different, and from everything we’ve heard, Disney / Pixar’s latest entrant, Inside Out, is a winner.
While animated and emotion-based avatars are cute and funny, it’s the reverse concept that’s driving a lot of service provider thinking. And that is, thinking from the ‘Outside In’.
What do I mean by this? It all depends on the point of view. For a service provider that’s managing a network, be it global, regional, or metro, there’s a natural tendency to think about starting from the core and extending it out to edge. For this network, it’s important to have a reliable, super fast core – big fast iron that can process packets and bandwidth at really fast rates.
This is certainly important, but in order to differentiate and add value to their customers, service providers are investing more at the edge. They are thinking about how to wrap up and package network functionality, offer these up as monetized services, and distribute these all the way to the customer premises. Continue reading
I’m recently been running down (or is it through) the Linux, systemd, networkd, udevd rabbit hole at full pelt and thought perhaps now was a good time to come up for some air and to share what I’ve learned so far. I could (and have elsewhere) written long essays on why Linux makes an excellent network […]
The post Linux Network Interface Configuration With udev appeared first on Packet Pushers Podcast and Continue reading
