A high-visibility win for Ericsson's prized HDS 8000.
Another step toward putting Linux containers into production.
So as we’re all busy network professionals, I’m sure you’ve ran into the problem of a work-life balance. I personally know lots of engineers that have burned out at one time, or their family life has suffered, and their kids barely know them. Now granted these are extreme case scenarios, but it could happen to […]
The post QOS Your Life appeared first on Packet Pushers.
So as we’re all busy network professionals, I’m sure you’ve ran into the problem of a work-life balance. I personally know lots of engineers that have burned out at one time, or their family life has suffered, and their kids barely know them. Now granted these are extreme case scenarios, but it could happen to […]
The post QOS Your Life appeared first on Packet Pushers.
All the answers you can ask for regarding SDN training & certification, the OCSA & OCSE exams and more from the ONF SDN Training Webinar Q&A are now live! Read it now!
This week I have two major themes to discuss on the topic of security, and one interesting bit of research. Let’s start with some further thoughts on security by obscurity.
I’ve heard this at least a thousand times in my life as a network engineer, generally stated just about the time someone says, “well, we could hide this server…” Reality, of course, is far different; I still put curtains on my house even though they don’t increase the amount of time it takes a thief to break in. Whether or not we want to believe it, obscurity does play a positive role in security.
But there are two places where obscurity is a bad thing in the world of security. The first is the original reference of this common saying: algorithms and implementations. Hiding how you encrypt things doesn’t improve security; in fact, it decreases the overall security of the system. The second place? Communication between companies and security professionals about the types, frequency, and methods of attack. Imagine, for a moment, that you were commanding a unit on a battlefield. You hear the sounds of combat in the distance. Realizing a unit in your army is Continue reading
We broke records last week with over 500 people attending AnsibleFest London last week. If you were able to attend, we hope you enjoyed the event and will come again in 2017. If you couldn't attend, don't worry, we plan on 2 more events this year.
Follow Ansible on Twitter to get the latest news and details.
Deploying a Mesos Based Visual Effects Studio, Industrial Light and Magic
Continuous Deployment for an Order System, Atlassian
Ansible 2.0 and Windows, M*Modal
Ansible Accelerates Deployment at Societe Generale, Theodo
Managing Your Cisco Data Center Network with Ansible, Cisco
Immutable Infrastructure at Scale with Ansible, Beamly
View all of the presentations here.
Making a system work in one datacenter is hard. Now imagine you move to two datacenters. Now imagine you need to support multiple geographically distributed datacenters. That’s the journey described in another excellent and thought provoking paper from Google: High-Availability at Massive Scale: Building Google’s Data Infrastructure for Ads.
The main idea of the paper is that the typical failover architecture used when moving from a single datacenter to multiple datacenters doesn’t work well in practice. What does work, where work means using fewer resources while providing high availability and consistency, is a natively multihomed architecture:
Our current approach is to build natively multihomed systems. Such systems run hot in multiple datacenters all the time, and adaptively move load between datacenters, with the ability to handle outages of any scale completely transparently. Additionally, planned datacenter outages and maintenance events are completely transparent, causing minimal disruption to the operational systems. In the past, such events required labor-intensive efforts to move operational systems from one datacenter to another
The use of “multihoming” in this context may be confusing because multihoming usually refers to a computer connected to more than one network. At Google scale perhaps it’s just as natural Continue reading
The best network engineers are curious, think holistically, and enable others to succeed.