We have been talking about silicon photonics so long that we are, probably like many of you, frustrated that it already is not ubiquitous. …
Nvidia Shows What Optically Linked GPU Systems Might Look Like was written by Timothy Prickett Morgan at The Next Platform.
Reproducibility and consistency are two key traits that are the driving forces behind the popularity of containers. Consistency is also a principle found within Red Hat Ansible Automation Platform. With only a few lines of YAML-formatted manifests, thousands of instances can be set up and configured uniformly. While the management of target instances is simple, it is the control node, or where the Ansible execution is initiated, that can be the most challenging aspect. As Ansible is written in Python, does the machine have the correct version of Python installed? Are the necessary Python modules installed? Are there any operating system dependencies needed? The list goes on and on.
These concerns, along with many others, led to a desire to leverage the benefits of containers to perform the control node’s role and eventually ushered in the concept of automation execution environments in Ansible Automation Platform 2. Running Ansible within containers is not a new concept and has been used quite successfully for some time now. However, there was no consistent process for building the container or executing Ansible from within the container. It seemed like everyone and anyone had their own version of running Ansible in a container. Ansible Continue reading
If there is anything that hyperscalers and cloud builders value more than anything else, it is regularity and predictability. …
Like A Drumbeat, Broadcom Doubles Ethernet Bandwidth With “Tomahawk 5” was written by Timothy Prickett Morgan at The Next Platform.
As more enterprises embrace hybrid and multicloud strategies and begin to extend their IT reach out to the edge, scale becomes an issue. …
Managing Infrastructure At Cloud Scale Without The Hyperscaler Propellerheads was written by Jeffrey Burt at The Next Platform.
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.
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
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
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
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.
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.
Losing a friend can be just as painful as any other breakup. You may feel betrayed, rejected, and even like you’re grieving the loss of a relationship. If you’re struggling to cope with a friendship breakup, there are a few things you can do to make the process easier.
It’s normal to feel sad, angry, or even hurt after a friendship ends. Allow yourself to experience these emotions instead of pushing them away. This can help you come to terms with the loss and start to move on.
If you’re feeling up to it, try talking to your former friend about what happened. This can be a difficult conversation, but it can help you understand their side of the story and closure.
It’s important to remember that you still have other friends in your life. Spend time with them and pour your energy into these relationships. They can help you feel better and remind you that you’re not alone.
A friendship breakup can be a chance to focus on your own needs for a while. Do something that makes Continue reading
The Cloudflare Support team is excited to announce the launch of our brand-new Customer Support Portal. When our customers open support tickets, we understand that they want quick and accurate responses from us. For those of you who have opened a support ticket in the past, we are certain you will notice the improvements we've made! The new Support Portal lives where our ticket submission form has always been, dash.cloudflare.com/support, but that's where the similarities between the old and the new one end.
The new Support Portal will help you solve your problems quickly and effectively, by getting you on the fastest path to resolution. In some cases, the most efficient way to resolve your issue will be to use our self-help resources or our machine learning-trained Support Bot. Other times, the most efficient way to resolve your issue will be by working with one of our Support Engineers via ticket, phone or chat, depending on your plan type. Regardless of how we help you solve your issue, we will have more context about the products you are using and your issue up front, reducing time-consuming back and forth.