Hedge 143: Being Prepared to be Laid Off with Giovanni Messina
Forty years ago there was an implied loyalty between companies and employees—but that world is long gone. As much as companies would like their employees to be loyal, layoff culture has crept into every corner of the modern world, especially as we move into an economic downturn. Giovanni Messina joins Russ White and Tom Ammon to talk about being prepared to be laid off, including such topics as being financially prepared, building skills for the long term, and finding community.
Day Two Cloud 159: DevOps Is A Failure
DevOps originated as a cultural movement to try and get developers and infrastructure operators to better work together to support applications in production. According to our guest Lee Briggs, that movement has failed. We discuss this premise on today's Day Two Cloud podcast.Tech Bytes: NVIDIA BlueField And Project Monterey (Sponsored)
On today’s Tech Bytes podcast, we talk Data Processing Units (DPUs) with sponsor NVIDIA. The context is VMware’s Project Monterey. Wes Kennedy, TME for BlueField at NVIDIA, is here to discuss how NVIDIA is partnering with VMware to enable offloads of applications such as NSX and VSAN.
The post Tech Bytes: NVIDIA BlueField And Project Monterey (Sponsored) appeared first on Packet Pushers.
Tech Bytes: NVIDIA BlueField And Project Monterey (Sponsored)
On today’s Tech Bytes podcast, we talk Data Processing Units (DPUs) with sponsor NVIDIA. The context is VMware’s Project Monterey. Wes Kennedy, TME for BlueField at NVIDIA, is here to discuss how NVIDIA is partnering with VMware to enable offloads of applications such as NSX and VSAN.The Hidden Values of Digital Transformation: Innovation and Adaptability
Digital transformation requires new skills and different approaches; approaches that, in large part, rely on modern tools and new capabilities.5 Challenges for Enterprises Considering LEO Satellite Services
The fast-growing sector may have businesses looking elsewhere and to alternatives with faster options to expand networks to remote offices and WFH residences.Troubleshooting microservices: Challenges and best practices
When people hear ‘microservices’ they often think about Kubernetes, which is a declarative container orchestrator. Because of its declarative nature, Kubernetes treats microservices as entities, which presents some challenges when it comes to troubleshooting. Let’s take a look at why troubleshooting microservices in a Kubernetes environment can be challenging, and some best practices for getting it right.
Why is troubleshooting microservices challenging?
To understand why troubleshooting microservices can be challenging, let’s look at an example. If you have an application in Kubernetes, you can deploy it as a pod and leverage Kubernetes to scale it. The entity is a pod that you can monitor. With microservices, you shouldn’t monitor pods; instead, you should monitor services. So you can have a monolithic workload (a single container deployed as a pod) and monitor it, but if you have a service made up of several different pods, you need to understand the interactions between those pods to understand how the service is behaving. If you don’t do that, what you think is an event might not really be an event (i.e. might not be material to the functioning of the service).
When it comes to monitoring microservices, you need to monitor at Continue reading
Route Servers and Loops
From the question pile: Route servers (as opposed to route reflectors) don’t change anything about a BGP route when re-advertising it to a peer, whether iBGP or eBGP. Why don’t route servers cause routing loops (or other problems) in a BGP network?
Route servers are often used by Internet Exchange Points (IXPs) to distribute routes between connected BGP speakers. BGP route servers
- Don’t change anything about a received BGP route when advertising the route to its peers (other BGP speakers)
- Don’t install routes received through BGP into the local routing table
Shouldn’t using route servers in a network—pontentially, at least—cause routing loops or other BGP routing issues? Maybe a practical example will help.
Assume b, e, and s are all route servers in their respective networks. Starting at the far left, a receives some route, 101::/64, and sends it on to b,, which then sends the unmodified route to c. When c receives traffic destined to 101::/64, what will happen? Regardless of whether these routers are running iBGP or eBGP, b will not change the next hop, so when c receives the route, a is still the next hop. If there’s no underlying routing protocol, c won’t know how Continue reading
Full Stack Journey 069: Network Automation Challenges For Engineers And Organizations
Today's Full Stack Journey podcast explores the barriers to network automation that individuals and organizations face. We also discuss how network engineers can overcome the inertia of just getting started, skills development tips, and more. Our guests are Matt Oswalt and Christian Adell.
The post Full Stack Journey 069: Network Automation Challenges For Engineers And Organizations appeared first on Packet Pushers.
Full Stack Journey 069: Network Automation Challenges For Engineers And Organizations
Today's Full Stack Journey podcast explores the barriers to network automation that individuals and organizations face. We also discuss how network engineers can overcome the inertia of just getting started, skills development tips, and more. Our guests are Matt Oswalt and Christian Adell.
HS030 Can Low Code Fit Your IT Strategy
Both sides of the low code/no code debate. We outline two sides of the debate, discuss four topics in favour of low code and then cover four negatives. Avoidance of toil coding, avoid skill shortage and viable testing are good things. Lockin, shadow IT and ownership are problematic. Its a solid debate on the topic.
The post HS030 Can Low Code Fit Your IT Strategy appeared first on Packet Pushers.
