Today on the Tech Bytes podcast we’re talking about OpenTelemetry with sponsor Cisco ThousandEyes. OpenTelemetry is an open collection of tools, APIs, and SDKs to help share telemetry data among different monitoring and analysis platforms to improve data correlation and visibility. ThousandEyes, the first network visibility platform to support OpenTelemetry, joins the podcast to discuss how it works, use cases, and more.
The post Tech Bytes: ThousandEyes Enhances Data Correlation With OpenTelemetry (Sponsored) appeared first on Packet Pushers.
One of the things that I’ve seen as a common thread among people in the industry as of late is the subject of burnout. Sure, burnout is a common topic no matter what year we’re in but a lot more of what I’m starting to hear about is self-inflicted burnout. Taking on too many projects, doing more than one job, and even having too many things going on outside of your specific role are all contributors to burnout. How can we keep that from happening?
For me, one of the biggest reasons why I find myself swimming in frustration is because I am very quick to volunteer to do things. In part it’s because I want to make sure the job is done correctly. In another part it’s because I want to be seen as someone that is always willing to get things done. Add in a dash of people pleasing and you can see how this spirals out of control. I’m sure you’ve even heard that as a career advice at some point. I’ve even railed against it many times on this blog.
How can you overcome the impulse to want to volunteer to do Continue reading
Is the private 5G market big enough to justify HPE's acquisition of Athonet? Is saving money worth retreating from public cloud? Why are organizations still getting bit by basic cloud misconfigurations? Will an appetite for AI deliver results for Nvidia? We explore these and other questions in the latest Network Break podcast.
The post Network Break 419: HPE Buys Athonet For Private 5G; Exit Public Cloud, Save Millions? appeared first on Packet Pushers.
This post originally appeared in the Packet Pushers’ Human Infrastructure newsletter. You can get the newsletter for free here. Or don’t. That’s fine too. The tech sector has recently gone through a spasm of layoffs. Tens of thousands of jobs have been cut at companies such as Microsoft, Google, Cisco, and Salesforce. The cuts are […]
The post Who Are The Most Overpaid Tech CEOs? appeared first on Packet Pushers.
A networking engineer tired of waiting for network devices to start sent me this question:
Can you suspend VMs in netlab? I use this trick in vSphere with CSR1Kv.
TL&DR: Maybe. Probably not.
Dear friend,
Source of Truth plays crucial role in network automation as this is the basis we are automating our IT and network infrastructure against. It doesn’t mean to be monitoring system in any capacity. At the same time, it may be useful to quickly do some checks against your network infrastructure and to update some metadata in the Source of Truth.
Yes, we are. NetBox is a leading tool in the source of truth framework. Being open-source, it by far outpaces all other open-source and commercial tools existing worldwide in this area. On top of its wide built-in capabilities, it is highly extensible via plugins and scripts.
The good news is that we covered NetBox in our Zero-to-Hero Network Automation Training, and you can benefit from learning it from the context of network automation with integrations to Python and Ansible tools, which you create during our training.
We offer the following training programs for you:
During these trainings you will learn the following topics:
How will the Data Processing Unit (DPU) market evolve? Are there new use cases for this infrastructure platform? Greg Ferro from the Packet Pushers and Joseph White, Fellow at Dell Technologies, look into the crystal ball to see where DPUs might go. This video is sponsored by Dell Technologies. You can subscribe to the Packet […]
The post What’s Next For DPUs? – Packet Pushers Livestream With Dell Technologies – Video appeared first on Packet Pushers.
As a warning to everyone, I am not a developer. I am a network engineer who is trying to do some automation stuff. Some of what I’m doing sounds logical to me, but I would not trust my own opinions for production work. I’m sure you can find a Slack channel or Mastodon instance with people who can tell you how to do things properly.
I use too many print statements to figure out what’s going on. Get an object and print it to screen to make sure it’s right. Do a calculation and print the result. There are so many print statements in my code that I had to start using a debug variable to tell it when to print stuff. I even use that technique in my functions.
# Don't do stuff like this
def myFunc(string_to_return, debug=False):
if debug:
print(f"Returning \"{string_to_return}\"")
return string_to_return
local_debug = True
string_to_send = "Aaron wastes a lot of time with print statements."
if local_debug:
print(f"I'm sending \"{string_to_send}\"")
myString = myFunc(string_to_send, debug=True)
print(myString)
It’s painful to look at this code. I need a better solution, and I found Python’s logging module.
Very simply, you associate your messages with one of five logging levels (debug, info, warning, error, Continue reading
Passwords suffer from an inherent risk: whoever possess the password inherits the privileges granted by that password. If the possessor is the intended person, then all is good. Otherwise, all is not so good because it means an unintended person has access to the system the password is guarding.