Is Container Networking Holding On To The Past?
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.Is Container Networking Holding On To The Past?
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.The Cloud Is Now A Thing
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:
- On-demand self service
- Broad network access
- Resource pooling (multi-tenant)
- Rapid Elasticity
- Measured service
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
Liveblog: Scaling New Services
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
Designing A Multi-Region, Multi-Hub Phase 3 DMVPN With BGP
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.
Author information
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.
How More Services Providers Are Thinking ‘Outside In’
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 latestHow More Services Providers Are Thinking ‘Outside In’
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
Linux Network Interface Configuration With udev
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 […]
Author information
The post Linux Network Interface Configuration With udev appeared first on Packet Pushers Podcast and Continue reading
GNS3 Weekly Development Report: June 22th
We publish weekly development reports in an effort to provide the community with increased transparency on what the development team isArista Networks Ships CloudVision, Strengthening SDN Story
EOS takes a step closer to SDN by integrating with Nuage and NSX controllers.
Solving the “jabber-config.xml” File Mystery
The jabber-config.xml file is an essential piece of configuration for the Jabber client. Sure, the client has the ability to operate just fine without this file. Video calling, deskphone control, instant messaging, etc. all work flawlessly. However, if you need to add any additional options, policies, or directory integrations, the jabber-config.xml file becomes necessary. Within the realm of the CCIE Collaboration certification, we are specifically concerned about two different configurations: UDS Directory Integration and SIP URI Dialing.
User Data Service (UDS) simply put, is the name for the End User database within Cisco Unified Communications Manager (CUCM). It contains all relevant information about that user, as would any other directory. UDS, however, is not enabled by default on the Jabber client. In fact, Jabber is geared towards integration with an LDAP source “out of the box”. This means that we must instruct the Jabber client to use UDS if we would like to be able to search the CUCM database to communicate with other users. Since this will have to be done by using the jabber-config.xml file, we must first determine how to create it. Thankfully, the Cisco documentation does not disappoint in this regard. From the Continue reading
Liveblog: DockerCon 2015 Day 2 General Session
This is a liveblog from the day 2 general session at DockerCon 2015. I was running late from some early morning meetings (sorry folks), so I wasn’t able to catch the first part of the general session (about the first 15 minutes or so). Here’s what I was able to capture.
Chris Buckley, Director of DevOps at Business Insider, took the stage to provide an overview of how Business Insider (BI) started using Docker. Buckley provides some “lessons learned”:
- Building for production first was grandiose was misguided.
- Porting it back to development wasn’t the right approach.
This led BI to Fig (now Docker Compose), which led to a decrease in the time it took to get a development environment up and running. With the combination of Vagrant and Docker, BI was able to reduce that to just a couple of hours. When BI revisited production apps, they turned to use Upstart/SysV scripts for containers, but this wasn’t quite the right fit. BI turned back to Puppet, building a parameterized Puppet class to create containers, links, set environment options, and define dependencies on other containers/services starting first.
Before Docker, the workflow was developers to GitHub to Jenkins, which then pushed to Continue reading