Scott Berkun wrote another great article that’s equally applicable to the traditional notion of design (his specialty) and the network design. Read it, replace design with network design, and use its lessons. Here’s just a sample:
Today's Heavy Networking podcast, sponsored by Tempered Networks, dives into how Tempered builds a software-defined perimeter with native zero trust, leveraging the Host Identity Protocol (HIP), Tempered's Airwall software, cryptographic identities, and secure overlays. Our guests from Tempered are Jeff Hussey, Founder and CEO; and Bryan Skene, CTO.
The post Heavy Networking 574: Get HIP With Zero Trust And Tempered Networks (Sponsored) appeared first on Packet Pushers.
The Dominican Republic’s new Internet Exchange Point (IXP) already has 24 members, three of which began exchanging traffic in November 2020. Another four will start this quarter – including the largest operators in the country. The IX.DO was born after frustrated attempts. A government-led initiative in 2007 never became operational and the data center NAP […]
The post In the Dominican Republic IX.DO Begins Silent Production, with Several Committed Members appeared first on Internet Society.
Exhibit A:
It’s been a year and more and I think a lot of us are on the ragged edge of burning out completely. Those that think they are superhuman and can just keep grinding away at things without acknowledging what’s going on are kidding themselves. I know I’m feeling it too even though I have a pretty decent handle on what’s going on. Let’s explore some of the ways it’s impacting us and what should be done, if anything can even be done.
I don’t feel like doing anything remotely creative right now. The cooking will get finished. The dishes will be done. The things in my floor will be picked up and put away. But beyond that? Good. Luck. I’m not feeling any kind of drive to do anything beyond that.
Remember when everyone was picking up quarantine skills? Baking, cooking, knitting, crocheting, home improvement, or even an instrument? Those were fun days filled with massive uncertainty and a need to distract ourselves from what might be coming next. However, those skill pickups are things that need Continue reading
In the last blog I provided a review of data center network virtualization approaches with a focus on the pros...
The post Understanding Various Approaches to Data Center Network Automation appeared first on Pluribus Networks.
In the last part of my chat with David Bombal we discussed interesting technologies networking engineers could focus on if they want to grow beyond pure packet switching (and voice calls, if you happen to believe VoIP is not just an application). We mentioned public clouds, automation, Linux networking, tools like Git, and for whatever reason concluded with some of my biggest blunders.
AWX is now deployed on Kubernetes (since AWX release 18), which is great – the only thing is, what do you do if this is the only application you need Kubernetes for? It is a bit of a hassle setting up the K8s master and worker nodes just for a single application.
The documentation suggests you use Minikube for this, but that seems to be designed for local / testing use only. There’s no middle ground between these two options, so I decided to work it out on MicroK8s.
MicroK8s is Canonical’s minimal production Kubernetes environment. It installs on one host, but can be set up for high availability and even run on a Raspberry Pi!
Here are the instructions if you want to do the same.
Install an Ubuntu 20 host on a t2.medium or higher instance in AWS.
Give it 20Gb of general purpose SSD disk.
Create a security group that permits TCP/443 through from your location – only TCP/22 is permitted by default.
Install Microk8s on a new Ubuntu host in AWS:
ubuntu@ip-172-31-0-208:~$ sudo snap install microk8s --classic microk8s (1.20/stable) v1.20.5 from Canonical✓ installed ubuntu@ip-172-31-0-208:~$
Add the ‘ubuntu’ user you are logged in Continue reading