What do I run at home?
I have decided to do a little series on “What I run at home” with regards to networking, labs, and …
The post What do I run at home? appeared first on Fryguy's Blog.
I have decided to do a little series on “What I run at home” with regards to networking, labs, and …
The post What do I run at home? appeared first on Fryguy's Blog.
Hello my friend,
This vlog episode I’m alone. Eh… But I have an opportunity to share with you the talk I’ve delivered an the NetLdn #6 event two weeks ago. Now you have an opportunity to watch this talk as well!

In this episode you will see the high-level description of the Data Centre Fabric Project I’ve been doing this year with the focus on the closed-loop automation using open-source tools. Additionally, you will see LIVE DEMO of the closed-loop automation as an extension to ZTP, where the full data centre fabric running Cumulus switches will be provisioned from zero to full operational state.
If you’ve recently read about Mellanox/Cumulus, the same approach perfectly fits this pair.
But it is not only about Cumulus. Any network supplier we’ve discussed (Arista, Nokia, Cisco and much more) can be provisioned in such a way, and you can find the sample templates in the GitHub repo.
Two weeks ago I replied to a battle-scar reaction to 7-layer OSI model, this time I’ll address a much more nuanced view from Russ White. Please read his article first (as always, it’s well worth reading) and when you come back we’ll focus on this claim:
The OSI Model does not accurately describe networks.
Like with any tool in your toolbox, you can view the 7-layer OSI model in a number of ways. In the case of OSI model, it can be used:
Two weeks ago I replied to a battle-scar reaction to 7-layer OSI model, this time I’ll address a much more nuanced view from Russ White. Please read his article first (as always, it’s well worth reading) and when you come back we’ll focus on this claim:
The OSI Model does not accurately describe networks.
Like with any tool in your toolbox, you can view the 7-layer OSI model in a number of ways. In the case of OSI model, it can be used:
Read more ...
A real privacy headache: Internet of Things devices potentially expose consumer information to other parties, according to a recent study featured on Vice.com. Many IoT devices collect and share a wealth of information including the IP address, usage habits, and location data. That data is then often shared with “a laundry list” of third parties.
Encryption objections: ISP trade groups are objecting to a plan by Google to a new encryption regime for domain name lookups in its Chrome browser and Android operating system, Broadcasting and Cable reports. The plan would give Google too much power, the groups have told U.S. lawmakers.
Moving to the country: Microsoft and Nextlink Internet have unveiled a plan to bring broadband to millions of people living in the rural U.S., WindowsCenteral.com says. The Microsoft Airband Initiative’s goal is to extend broadband access to more than 3 million unserved U.S. residents by mid-2022, with more areas covered by 2024.
The FBI wants in: The U.S. FBI tried to get the operators of encrypted phone carrier Phantom Secure to create a backdoor, as a way to spy on the Sinaloa drug cartel, Vice.com reports. The company was accused Continue reading
IBM Cloud has made a massive shift to Kubernetes. From an initial plan for a hosted Kubernetes public cloud offering it has snowballed to tens of thousands of production Kubernetes clusters running across more than 60 data centers around the globe, hosting 90% of the PaaS and SaaS services offered by IBM Cloud.
I spoke with Dan Berg, IBM Distinguished Engineer, to find out more about their journey, what triggered such a significant shift, and what they learned along the way.
It must have been 3 years ago. At that time, IBM had been building customer-facing services in the cloud for several years implemented as traditional VM or Cloud Foundry workloads. One of the services we offered was a container as a service (CaaS) platform that was built under the covers using Docker and OpenStack. With this platform, we were the first in the industry to provide a true CaaS experience, but in some ways it was ahead of its time, and people weren’t ready to embrace a pure container as a service platform.
To this day we are still seeing double digit Continue reading
The startup says “five of the top five” cloud and colocation service providers are testing its...
The NSX-T 2.5 release marks a cornerstone in NSX-T as announced at VMworld 2019 by SVP Umesh Mahajan. 2019 has been a year of phenomenal growth for VMware’s NSX-T with its wide adoption by enterprises across several verticals. In 2019, we introduced two ground-breaking releases NSX-T 2.4 and NSX-T 2.5. With these two releases, we are fully embarking on enterprise ready system becoming the de-facto enterprise software-defined networking (SDN) platform of choice.
To support our customers in their network and security virtualization journey, we introduced the NSX-T design guide on the NSX-T 2.0 release and provided design guidance on how customers should design their data centers with NSX-T.
Today, we are excited to announce the next version of the NSX-T design guide based on generally available NSX-T release 2.5. It is the foundation overhaul to design guidance and leading best practices. There have been numerous L2-L7 features additions and platform enhancements since NSX-T release 2.0. This design guide covers functional aspects of these enhancements and provides design guidance for them.
What readers can expect in the new NSX-T Design Guide:
The new lasers and the line of arrayed waveguide grating multiplexers are designed to bolster...
The 300,000-square-foot factory will begin commercial operations early next year in Lewisville,...
The group is working with service providers to define and create VNF reference architectures for...

Kubernetes’s gravity as the container orchestrator of choice continues to grow, and for good reason: It has the broadest capabilities of any container orchestrator available today. But all that power comes with a price; jumping into the cockpit of a state-of-the-art jet puts a lot of power under you, but how to actually fly the thing is not obvious.
Kubernetes’ complexity is overwhelming for a lot of people jumping in for the first time. In this blog series, I’m going to walk you through the basics of architecting an application for Kubernetes, with a tactical focus on the actual Kubernetes objects you’re going to need. I’m not, however, going to spend much time reviewing 12-factor design principles and microservice architecture; there are some excellent ideas in those sort of strategic discussions with which anyone designing an application should be familiar, but here on the Docker Training Team I like to keep the focus on concrete, hands-on-keyboard implementation as much as possible.
Furthermore, while my focus is on application architecture, I would strongly encourage devops engineers and developers building to Kubernetes to follow along, in addition to readers in application architecture Continue reading
Co-authored with Rajiv Prithvi, Product Manager Networking and Security Business Unit at VMware
During VMworld US 2019, we announced several new transformative capabilities in VMware NSX-T 2.5 release which is now shipping! The release strengthens the NSX platform’s intrinsic security, multi-cloud, container, and operational capabilities.
We also announced the successful FIPS 140-2 validation of NSX-T 2.5. FIPS compliance is mandatory for US federal agencies and has also been widely adopted in non-governmental sectors (e.g. financial services, utilities, healthcare). FIPS-140-2 establishes the integrity of cryptographic modules in use through validation testing done by NIST and CSE. With this validation, we further deliver on our confidentiality, integrity and availability objectives and provide our customers with a robust networking and security virtualization platform.
NSX-T 2.5 is configured to operate in FIPS mode by default. Any exceptions or deviations from established compliance norms are identified in a compliance report which can be used to review and configure your NSX-T Data Center environment to meet your IT policies and industry standards. Any exceptions to FIPS compliance including configuration errors can be retrieved from the compliance report using NSX Manager UI or APIs.
A sample FIPS Continue reading