As long as great science gets done on the final incarnation of the “Aurora” supercomputer at Argonne National Laboratory, based on Intel’s CPUs and GPUs but not on its now defunct Omni-Path interconnect, people will eventually forget all of – well, most of – the grief that it took to get the massive machine to market. …
Aurora Rising: A Massive Machine For HPC And AI was written by Timothy Prickett Morgan at The Next Platform.
Container Network Interfaces (CNIs) are plug-ins that enable networking capabilities. This video provides a brief overview of the Cillium CNI and the importance of network policies. https://www.youtube.com/watch?v=nzswIJpdPtY You can subscribe to the Packet Pushers’ YouTube channel for more videos as they are published. It’s a diverse a mix of content from Ethan and Greg, plus […]
The post Kubernetes Security And Networking 8: Loading The Cillium CNI – Video appeared first on Packet Pushers.
FortiGate firewalls are highly popular and extensively utilized for perimeter-based security in a wide range of applications, including monolithic applications developed and deployed using the traditional waterfall model. These firewalls establish a secure perimeter around applications, effectively managing inbound and outbound traffic for the organization. FortiGate relies on IP addresses for implementing “allow/deny” policies.
The use of IP addresses is effective for non-cloud native applications, where static IP addresses serve as definitive network identifiers. However, in a Kubernetes environment, workloads have dynamic IP addresses that change whenever they are restarted or scaled out to different nodes. This dynamic nature poses challenges when utilizing FortiGate with Kubernetes workloads, requiring continuous updates to firewall rules and the opening of large CIDR ranges for node-based access. This introduces security and compliance risks, as workloads running on these CIDR ranges gain unrestricted access to external or public services.
To facilitate the usage of FortiGate firewalls with Kubernetes workloads, it becomes crucial to identify workloads that necessitate access to external resources and assign them fixed IP addresses for utilization in FortiGate firewall rules. The integration of Calico with FortiGate firewalls and FortiManager offers an elegant solution, enabling the use of FortiGate firewalls while retaining existing Continue reading
A few years ago, DirectData Networks gave us a hint at the tectonic-like shifts that were emerging in datacenters at enterprises and high-end research institutions and were shaping the strategy of a company that had made its name in HPC with its parallel file system technology. …
Boosting AI Storage With QLC Flash And Deduplication was written by Jeffrey Burt at The Next Platform.
As you may recall, we introduced Event-Driven Ansible in developer preview last fall at AnsibleFest. Since that time, much work has been done across the community, the Red Hat development teams, customers, and last but not least, Red Hat partners. Today, we are pleased to announce that Event-Driven Ansible will be concluding its developer preview and will become generally available as part of Red Hat Ansible Automation Platform 2.4.
If you are new to Event-Driven Ansible, check out the developer preview blog I wrote last fall to learn the basics, and you may also be interested in this video on Ansible Rulebooks, as well as others in this playlist.
For many IT teams, there is too much work to do and not enough time to get it all done. Event-Driven Ansible can help your team work smarter, not harder. How often are you doing routine tasks that get in the way of key priorities? How often are you needing to “drop everything” to respond to a ticket enrichment request or handle a user administration issue? Have you had to wake up at night to remediate an issue? How often are Continue reading
As you may recall, we introduced Event-Driven Ansible in developer preview last fall at AnsibleFest. Since that time, much work has been done across the community, the Red Hat development teams, customers, and last but not least, Red Hat partners. Today, we are pleased to announce that Event-Driven Ansible will be concluding its developer preview and will become generally available as part of Red Hat Ansible Automation Platform 2.4.
If you are new to Event-Driven Ansible, check out the developer preview blog I wrote last fall to learn the basics, and you may also be interested in this video on Ansible Rulebooks, as well as others in this playlist.
For many IT teams, there is too much work to do and not enough time to get it all done. Event-Driven Ansible can help your team work smarter, not harder. How often are you doing routine tasks that get in the way of key priorities? How often are you needing to "drop everything" to respond to a ticket enrichment request or handle a user administration issue? Have you had to wake up at night to remediate an issue? How often are you adjusting Continue reading
Since we announced Event-Driven Ansible in developer preview at AnsibleFest last October, we have been working with a number of technology partners to provide integrated offerings via Ansible Content Collections for Event-Driven Ansible. We know that partner integrations are an important source of event intelligence that can be used to create full end-to-end event-driven automation across your Day 2 operations.
Many of these integrations are in the area of event-source plugins that make it possible for Event-Driven Ansible’s decisioning capability to receive intelligence about a condition in the IT environment that needs a response.
Today at Red Hat Summit, as we announce Event-Driven Ansible as a capability that will be included in Red Hat Ansible Automation Platform 2.4, we are pleased to unveil the initial set of partners who are creating Ansible Content Collections for Event-Driven Ansible. Many of these will be Red Hat Ansible Certified Content Collections, and some partners are already in the certification process. Others are planned to certify in the near future. As each Collection is complete, subscribers can find and download them in Ansible automation hub.
Keep an eye out for further communication around new certified collections, and in the meantime, Continue reading
Across every industry, automation at the edge is enabling emerging use cases, helping organizations drive the next wave of innovation as they explore and execute digital transformation initiatives. The introduction of Event-Driven Ansible is especially exciting when considering the impacts to edge environments.
The edge can bring new challenges of limited or no IT staffing in remote locations such as branches, stores, warehouses, or plant floors. These remote edge facilities are often more focused on Operational Technology (OT), or small form factor IT devices.
Having a single platform to enable manually and automatically initiated actions across an entire technology landscape – from data center to cloud to edge – is critical to facilitating IT/OT convergence, a necessity in order to maintain competitiveness.
Ansible Automation Platform does not require an agent to be present on a target system receiving an automated action, which is convenient and ideal for technologies that cannot host an agent, such as an edge device or network router. This feature makes Event-Driven Ansible a simpler solution to deploy and more capable of handling automation at the edge.
Many business executives are incompetent scumbags and yet they managed to get the job and get paid serious money. What can technology engineers learn from these fools so that they get the same results aka more money and less work.
The post HS048 Using Personal Product Branding To Be Better Paid Technology Engineer appeared first on Packet Pushers.
Sebastian described an interesting Cisco ACI quirk they had the privilege of chasing around:
We’ve encountered VM connectivity issues after VM movements from one vPC leaf pair to a different vPC leaf pair with ACI. The issue did not occur immediately (due to ACI’s bounce entries) and only sometimes, which made it very difficult to reproduce synthetically, but due to DRS and a large number of VMs it occurred frequently enough, that it was a serious problem for us.
Here’s what they figured out:
Sebastian described an interesting Cisco ACI quirk they had the privilege of chasing around:
We’ve encountered VM connectivity issues after VM movements from one vPC leaf pair to a different vPC leaf pair with ACI. The issue did not occur immediately (due to ACI’s bounce entries) and only sometimes, which made it very difficult to reproduce synthetically, but due to DRS and a large number of VMs it occurred frequently enough, that it was a serious problem for us.
Here’s what they figured out: