Heavy Wireless 010: Using Drones In Your WLAN Consulting

Drones can be a useful tool for outdoor wireless surveys. Drones can help an engineer figure out the best place to mount a radio, get line of sight between points, confirm antenna orientation, and save a lot of climbing up and down ladders. On today's Heavy Wireless, Keith Parsons speaks with Mike Wade, a wireless design engineer who uses drones in his survey work, about the certifications and requirements necessary to add a drone to your toolkit.

Heavy Wireless 010: Using Drones In Your WLAN Consulting

Drones can be a useful tool for outdoor wireless surveys. Drones can help an engineer figure out the best place to mount a radio, get line of sight between points, confirm antenna orientation, and save a lot of climbing up and down ladders. On today's Heavy Wireless, Keith Parsons speaks with Mike Wade, a wireless design engineer who uses drones in his survey work, about the certifications and requirements necessary to add a drone to your toolkit.

The post Heavy Wireless 010: Using Drones In Your WLAN Consulting appeared first on Packet Pushers.

Automate OpenShift with Red Hat Ansible Automation Platform

OpenShift meets Ansible

 

We have seen many organizations compare themselves on how agile they are in the innovation journeys. When we talk about innovation, there are several aspects around it, like optimizing the existing IT, integrating apps/data/processes, adding and managing cloud infrastructure or modernizing the applications. But in order to partner with lines of business to better compete, there is a need to introduce automation.

If someone asks, “What can we automate?” Below is my answer:

"Every non-interruptive CLI command or any UI which exposes a REST-API is an opportunity to automate." 

Whether it be orchestrating configurations, deploying applications or managing infrastructure, etc.

Red Hat Ansible Automation Platform does all that!

Whether managing cloud or cloud-native systems, there is no difference. In this article, I’ll go through integrating an OpenShift cluster with Ansible Automation Platform to help automating Day 0 and Day 2 activities.

 

Tying OpenShift with Ansible Automation Platform

When it comes to container orchestration, Red Hat OpenShift has emerged as the leading enterprise level solution, providing a robust platform to manage and scale complex applications with ease. However, manual deployment and management of these applications can be labor intensive and prone to issues.

Continue reading

Heavy Networking 698: Integrating Edge Networking And Compute With VMware Edge Cloud Orchestrator (Sponsored)

On today’s Heavy Networking we explore the edge. But where is the edge? In today's conversation with sponsor VMware, it's a remote location where data is being generated. It could be end users in a branch office, or IoT devices and sensors on a factory floor. These edge locations needs integrated compute and networking to run application workloads while also being able to  connect to cloud applications and services. We discuss the VMware Edge Cloud Orchestrator, which provides unified management for networking and compute at remote sites.

Heavy Networking 698: Integrating Edge Networking And Compute With VMware Edge Cloud Orchestrator (Sponsored)

On today’s Heavy Networking we explore the edge. But where is the edge? In today's conversation with sponsor VMware, it's a remote location where data is being generated. It could be end users in a branch office, or IoT devices and sensors on a factory floor. These edge locations needs integrated compute and networking to run application workloads while also being able to  connect to cloud applications and services. We discuss the VMware Edge Cloud Orchestrator, which provides unified management for networking and compute at remote sites.

The post Heavy Networking 698: Integrating Edge Networking And Compute With VMware Edge Cloud Orchestrator (Sponsored) appeared first on Packet Pushers.

Tech Bytes: Introducing The Network Automation Forum And AutoCon Event (Sponsored)

Today on the Tech Bytes podcast we discuss the Network Automation Forum (NAF) and its inaugural independent conference--AutoCon 0. The networking industry has been taking about automation forever, but most engineers and organizations don't get much beyond a few scripts. The Network Automation Forum wants to change that by serving as a salon where enterprises, service providers, and vendors can talk openly about what works, what doesn't, and how to advance the state of the art.

Tech Bytes: Introducing The Network Automation Forum And AutoCon Event (Sponsored)

Today on the Tech Bytes podcast we discuss the Network Automation Forum (NAF) and its inaugural independent conference--AutoCon 0. The networking industry has been taking about automation forever, but most engineers and organizations don't get much beyond a few scripts. The Network Automation Forum wants to change that by serving as a salon where enterprises, service providers, and vendors can talk openly about what works, what doesn't, and how to advance the state of the art.

The post Tech Bytes: Introducing The Network Automation Forum And AutoCon Event (Sponsored) appeared first on Packet Pushers.

HashiCorp Retools Licenses And Software To Grow Its Business

It is hard to make a living in the open source software business, although it is possible, through the contributions of many, to make great software.

The post HashiCorp Retools Licenses And Software To Grow Its Business first appeared on The Next Platform.

HashiCorp Retools Licenses And Software To Grow Its Business was written by Timothy Prickett Morgan at The Next Platform.

Network Break 445: Juniper Pairs With ChatGPT, Microsoft To Unpair Teams In The EU

Today on Network Break we discuss Juniper integrating ChatGPT with its AI digital assistant, Microsoft's plan to unbundle Teams in the EU to fend off regulators, financial results from soon-to-be-paired Broadcom and VMware, a 5G follow-up, and more.

The post Network Break 445: Juniper Pairs With ChatGPT, Microsoft To Unpair Teams In The EU appeared first on Packet Pushers.

3 types of incremental forever backup

A traditional backup starts with an initial full backup and is followed by a series of incremental or cumulative incremental backups (also known as differential backups). After some period of time, you will perform another full backup and more incremental backups. However, the advent of disk-based backup systems has given rise to the concept of the incremental forever approach, where only one backup is performed followed by a series of incremental backups. Let’s take a look at the different ways to do this.File-level incremental forever The first type of incremental forever backup is a file-level incremental forever backup product. This type of approach has actually been around for quite some time, with early versions of it available in the ‘90s. The reason why this is called a file-level incremental is that the decision to backup an item happens at the file level. If anything within a file changes, it will change its modification date (or archive bit in Windows), and the entire file will be backed up. Even if only one byte of data was changed within the file, the entire file will be included in the backup.To read this article in full, please click here

Incrementing and decrementing numeric variables in bash

When preparing scripts that will run in bash, it’s often critical to be able to set up numeric variables that you can then increment or decrement as the script proceeds. The only surprising part of this is how many options you have to choose from to make the increment or decrement operation happen.Incrementing numeric variables First, to increment a variable, you first need to set it up. While the example below sets the variable $count to 1, there is no need to start at 1.$ count=1 This would also work:$ count=111 Regardless of the initial setting, you can then increment your variable using any of the following commands. Just replace $count with your variable name.To read this article in full, please click here

3 types of incremental forever backup

A traditional backup starts with an initial full backup and is followed by a series of incremental or cumulative incremental backups (also known as differential backups). After some period of time, you will perform another full backup and more incremental backups. However, the advent of disk-based backup systems has given rise to the concept of the incremental forever approach, where only one backup is performed followed by a series of incremental backups. Let’s take a look at the different ways to do this.File-level incremental forever The first type of incremental forever backup is a file-level incremental forever backup product. This type of approach has actually been around for quite some time, with early versions of it available in the ‘90s. The reason why this is called a file-level incremental is that the decision to backup an item happens at the file level. If anything within a file changes, it will change its modification date (or archive bit in Windows), and the entire file will be backed up. Even if only one byte of data was changed within the file, the entire file will be included in the backup.To read this article in full, please click here

Incrementing and decrementing numeric variables in bash

When preparing scripts that will run in bash, it’s often critical to be able to set up numeric variables that you can then increment or decrement as the script proceeds. The only surprising part of this is how many options you have to choose from to make the increment or decrement operation happen.Incrementing numeric variables First, to increment a variable, you first need to set it up. While the example below sets the variable $count to 1, there is no need to start at 1.$ count=1 This would also work:$ count=111 Regardless of the initial setting, you can then increment your variable using any of the following commands. Just replace $count with your variable name.To read this article in full, please click here

3 types of incremental forever backup

A traditional backup starts with an initial full backup and is followed by a series of incremental or cumulative incremental backups (also known as differential backups). After some period of time, you will perform another full backup and more incremental backups. However, the advent of disk-based backup systems has given rise to the concept of the incremental forever approach, where only one backup is performed followed by a series of incremental backups. Let’s take a look at the different ways to do this.File-level incremental forever The first type of incremental forever backup is a file-level incremental forever backup product. This type of approach has actually been around for quite some time, with early versions of it available in the ‘90s. The reason why this is called a file-level incremental is that the decision to backup an item happens at the file level. If anything within a file changes, it will change its modification date (or archive bit in Windows), and the entire file will be backed up. Even if only one byte of data was changed within the file, the entire file will be included in the backup.To read this article in full, please click here

Incrementing and decrementing numeric variables in bash

When preparing scripts that will run in bash, it’s often critical to be able to set up numeric variables that you can then increment or decrement as the script proceeds. The only surprising part of this is how many options you have to choose from to make the increment or decrement operation happen.Incrementing numeric variables First, to increment a variable, you first need to set it up. While the example below sets the variable $count to 1, there is no need to start at 1.$ count=1 This would also work:$ count=111 Regardless of the initial setting, you can then increment your variable using any of the following commands. Just replace $count with your variable name.To read this article in full, please click here

Random Thoughts on Zero-Trust Architecture

When preparing the materials for the Design Clinic section describing Zero-Trust Network Architecture, I wondered whether I was missing something crucial. After all, I couldn’t find anything new when reading the NIST documents – we’ve seen all they’re describing 30 years ago (remember Kerberos?).

In late August I dropped by the fantastic Roundtable and Barbecue event organized by Gabi Gerber (running Security Interest Group Switzerland) and used the opportunity to join the Zero Trust Architecture roundtable. Most other participants were seasoned IT security professionals with a level of skepticism approaching mine. When I mentioned I failed to see anything new in the now-overhyped topic, they quickly expressed similar doubts.