It's 2020 and the world is coming to an end. Everyone is in lock down due to some kind of killer bat virus. I have always wanted to grow a beard and seeing every one with their awesome lock down beards has inspired me to grow one of my own. The Problem I'll be 41 this year. I was...continue reading
It's 2020 and the world is coming to an end. Everyone is in lock down due to some kind of killer bat virus. I have always wanted to grow a beard and seeing every one with their awesome lock down beards has inspired me to grow one of my own. The Problem I'll be 41 this year. I was...continue reading
https://codingpackets.com/blog/growing-a-beard
https://codingpackets.com/blog/growing-a-beard
https://codingpackets.com/blog/growing-a-beard
https://codingpackets.com/blog/growing-a-beard
https://codingpackets.com/blog/growing-a-beard
I must have built OpenStack demos a dozen times or more over the past few years, for the purposes of learning, training others, or providing proof of concept environments to clients. However these environments always had one thing in common – they were purely demo environments, bearing little relation to how you would build OpenStack in a real production environment. Indeed, most of them were “all-in-one” environments, where every single service runs on a single node, and the loss of that node would mean the loss of the entire environment – never mind the lack of scalability!
Having been tasked with building a prototype OpenStack environment for an internal proof of concept, I decided that it was time to start looking at how to build OpenStack “properly”. However I had a problem – I didn’t have at my disposal the half-dozen or so physical nodes one might typically build a production cluster on, never mind a highly resilient switch core for the network. The on-going lockdown in which I write this didn’t help – in fact it made obtaining hardware more difficult.
I’ve always been inspired by the “cldemo” environments on Cumulus Networks’ GitHub and my first thought was Continue reading
Today, more than 30 civil society organizations joined in launching the Global Encryption Coalition, to promote and defend encryption in key countries and multilateral gatherings where it is under threat. The new coalition is led by a Steering Committee consisting of the Center for Democracy & Technology (CDT), the Internet Society, and Global Partners Digital.
“The spread of COVID-19 has underlined the necessity of secure, private internet communications. Those who are fortunate enough to have strong internet connections are likely sharing increasing amounts of sensitive data online. At the same time, governments around the world are considering policies that put the security of that data at risk,” said Greg Nojeim, CDT’s Senior Counsel and Director of the Freedom, Security and Technology Project. “Encryption enables people to have private and secure digital lives.”
Working together with a membership that will quickly grow to include companies and technologists, CDT and the Coalition will help activists on the ground in key countries where it is under threat, like Canada, Australia, India, and Brazil, beat back proposals that would weaken encryption. “The Coalition will alert technologists to encryption threats around the world, and create mechanisms through which they can deliver expert analysis Continue reading
The IPv6 Buzz crew examine how the recent increase in working from home have affected Internet traffic as a whole--and IPv6 in particular. Will recent developments push IPv6 closer to a "tipping point"? What is VPN breakout and how is it impacted by IPv6? They discuss these topics and more.
The post IPv6 Buzz 051: How The Work-From-Home Movement Affects IPv6 And The Internet appeared first on Packet Pushers.
I don’t know what’s wrong with me, but I rarely get emails along the lines of “I deployed SD-WAN and it was the best thing we did in the last decade” (trust me, I would publish those if they’d come from a semi-trusted source).
What I usually get are sad experiences from people being exposed to vendor brainwashing or deployments that failed to meet expectations (but according to Systems Engineering Director working for an aggressive SD-WAN vendor that’s just because they didn’t do their research, and thus did everything wrong).
Here’s another story coming from Adrian Giacometti.
If you're thinking about migrating applications from your data center to the cloud, prepare to do a lot of planning. Today's Day Two Cloud podcast delves into the gritty details with guest Sarah Lean, a Cloud Advocate at Microsoft. We discuss migration business drivers, what apps are better off staying on prem, tips to minimize migration pain, and more.
The post Day Two Cloud 048: Migrating Your Data Center To The Cloud appeared first on Packet Pushers.
When you think of new Ethernet standards, you probably think about faster and optical. There is, however, an entire world of buildings out there with older copper cabling, particularly in the industrial realm, that could see dramatic improvements in productivity if their control and monitoring systems could be moved to IP. In these cases, what is needed is an Ethernet standard that runs over a single copper pair, and yet offers enough speed to support industrial use cases. Peter Jones joins Jeremy Filliben and Russ White to discuss single pair Ethernet.
Respnding to Phil's assertion that DHCP isn't Intent
The post Response: DHCP is not Intent Based Networking – Networkphil appeared first on EtherealMind.