Kate Matsudaira wrote a nice article explaining how to deal with emotional attachment to a project you spent a lot of time working on. While she's focusing on software development, the same fallacies apply to networking - sometimes it's time to let the old pile of **** die and replace it with something created in this decade.
“If I have a threat space that is bounded and measurable, why wouldn’t you go whole hog after...
Typically Linux admins always appreciate VI editor, I always used to like Nano Editor until I realized how good VI actually is.
But this post is not about Vi Editor as such, this more about Tmux a Terminal Emulator
What is the beauty, Its more like a GNU Screen Program, but does so much more than GNU screen.
Example is below
-Rakesh
OK, this isn’t a really a controversial opinion. This is more as a guide for those who run into these problems when trying to setup their first whitebox/homelab systems for ESXi.
So it goes something like this: You’ve got an old desktop, gaming rig, or workstation. You decide you’ll retire it to your home data center (or basement, or laundry room) as a hypervisor. ESXi by itself (no vSphere controller) is free, and here’s how to download and get the license key.
For most desktop/workstation type of hardware, you can install ESXi from the general ESXi installer except for one aspect: Many of these types of systems use Realtek, Marvell, or other desktop/consumer grade NICs, and there’s not an ESXi driver for these. And for good reasons: They suck.
So you have the choice: Try to use a special custom ISO installer with the Realtek?Marvell/etc. driver loaded, or buy a different NIC. In most of IT, there’s usually more than one right answer, and a heaping dose of “it depends”. However, for this particular question (Realtek or buy another NIC) there’s only right right answer: Buy another NIC.
Realtek NICs suck. They don’t perform well, they’re a pain to Continue reading
Last month, the Chapters Advocacy Workshop for the Middle East, took place in Beirut Lebanon. The two-day event hosted Chapter leaders and representatives from Bahrain, Egypt, Jordan, Lebanon, Saudi Arabia, Morocco, Palestine, Somalia, Syria, United Arab Emirates, and Yemen. While the focus was on MANRS (Mutually Agreed Norms for Routing Security), it also included representatives from the Blockchain SIG (Special Interest Group).
During the two days, we discussed many issues related to the Middle East Chapters and their concerns, the 2019 plan of the Middle East Bureau, the strategic vision for the Internet Society, and the 2020 planning process. We acquired feedback from the delegates on our plans and community facing processes. We had ample staff representation that contributed immensely to the workshop, including, Sally Wentworth, Salam Yamout, Konstantinos Komaitis, Sally Harvey, Nermine El Saadany, and Aftab Siddiqui.
Aftab initiated the workshop with an introductory session on MANRS. He gave a technical breakdown on what MANRS is about before moving onto a hands-on workshop. The second day opened with an introduction to the 2020 Strategic Plan, followed by a PEST analysis led by Sally. Participants gave feedback on what’s important to their Chapters and to themselves as members Continue reading
SDxCentral Weekly Wrap for May 24, 2019: HPE buys Cray for $1.3B; Affirmed claims 5G first; and...
Telstra has started building out 5G coverage in 10 cities and plans to expand the network almost...
Check out our fifth edition of The Serverlist below. Get the latest scoop on the serverless space, get your hands dirty with new developer tutorials, engage in conversations with other serverless developers, and find upcoming meetups and conferences to attend.
Sign up below to have The Serverlist sent directly to your mailbox.
Vodafone OpCos in Portugal and Spain made use of two gamers to demonstrate 5G roaming capabilities.
CEO Antonio Neri blamed declining revenue on trade tensions, longer than expected sales cycles with...
On today's Heavy Networking, recorded live at Gluware Intent 19, the Packet Pushers dive into network automation, learn about sponsor Gluware's capability to bring automation into brownfield environments and derive business intent from existing networks, and explore real-world use cases from customers Merck and Terracon.
The post Heavy Networking 451: Intelligent Network Automation And Intent Engineering With Gluware (Sponsored) appeared first on Packet Pushers.
Access to quantum computing systems are likely to be through cloud connections because of the...
If you are a fan of the work we do each week with our Gestalt IT Rundown on Facebook, you probably saw a story in this week’s episode about the race for 5G spectrum causing some potential problems with weather forecasting. I didn’t have the time to dig into the details behind the story on that episode, so I wanted to take a few minutes and explain why it’s such a big deal.
First, you have to know that 5G (and many other) speeds are entirely dependent upon the amount of spectrum they can use to communicate. The more spectrum available to them, the more channels they have available to communicate. Which increases the speed they can exchange information and reduces the amount of interference between devices. Sounds simple right?
Except mobile devices aren’t the only things that are using the spectrum. We have all kinds of other devices out there that use radio waves to communicate. We’ve known for several years that there are a lot of devices in the 5 GHz spectrum used by 802.11 that interfere with wireless devices. Things like ISM radios for industrial and medical applications or government radar systems. The government has instituted Continue reading
In this Short Take, Russ compares overlays and service meshes/service fabrics as they relate to network engineering as well as identifying where each might be used.
The post Short Take – Service Fabrics appeared first on Network Collective.
At The Next AI Platform event on May 9 in San Jose, we brought together a wide range of people leading the charge throughout the AI infrastructure stack. …
I/O Bubbles to Top of AI Infrastructure Conversations was written by Nicole Hemsoth at .
Do you still use spreadsheets to keep track of all your device inventory? Do you have Infoblox Appliances deployed in your infrastructure? Do you want to start automating without the burden of maintaining a static register of devices? If you answered yes to any of these questions, this blog is for you.
Operations teams often struggle to keep their Configuration Management Databases (CMDBs) up-to-date, primarily because they were not involved in the specification process to share what pieces of information are relevant to them, or even if they were, once it is put in place: Teams are not allowed to change any of their Configuration Items (CI) because they have only read-only access!
The reality is that a lot of the time when we talk about a CMDB, we are talking about tables in a database without any version control mechanism, therefore only read access is provided to end users.
The impact is that in order to perform lifecycle management (Create/Update/Decommission) of their configuration items, teams must go through a fastidious and manual process until they give up changing CIs (Configuration Items) in the CMDB and just leave everything as it is. What happens next? Different teams start Continue reading
A few years ago we “celebrated” 512K day - the size of the full Internet routing table exceeded 512K (for whatever value of K ;) prefixes, overflowing TCAMs in some IP routers and resulting in interesting brownouts.
We’re close to exceeding 768K mark and the beware 768K day blog posts have already started appearing. While you (RFC 2119) SHOULD check the size of your forwarding table and the maximum capabilities of your hardware, the more important question should be “Why do I need 768K forwarding entries if I’m not a Tier-1 provider”
Read more ...Storage is no longer an afterthought when it comes to systems of any reasonable scale. …
In the Age of AI, Storage is No Longer an Afterthought was written by Nicole Hemsoth at .
Compress objects, not cache lines: an object-based compressed memory hierarchy Tsai & Sanchez, ASPLOS’19
Last time out we saw how Google have been able to save millions of dollars though memory compression enabled via zswap. One of the important attributes of their design was easy and rapid deployment across an existing fleet. Today’s paper introduces Zippads, which compared to a state of the art compressed memory hierarchy is able to achieve a 1.63x higher compression ratio and improve performance by 17%. The big idea behind zippads is simple and elegant, but the ramifications go deep: all the way down to a modified instruction set (ISA)! So while you probably won’t be using Zippads in practice anytime soon, it’s a wonderful example of what’s possible when you’re prepared to take a fresh look at “the way we’ve always done things.”
Existing cache and main memory compression techniques compress data in small fixed-size blocks, typically cache lines. Moreover, they use simple compression algorithms that focus on exploiting redundancy within a block. These techniques work well for scientific programs that are dominated by arrays. However, they are ineffective on object-based programs because objects do not fall neatly Continue reading