Videos
Network Insight.
- Premium Consultancy, Ebooks, Videos and Elearning
-
Distributed Tracing Explained
We generally have two types of telemetry data. We have log data and time-series statistics. The time-series data is also known as metrics.
In the context of a microservices environment. The metrics, for example, will allow you to get an aggregate understanding of what’s happening to all instances of a given service.
Then we have Logs, on the other hand, that provide extremely fine-grained detail on a given service. But have no built-in way to provide that detail in the context of a request.
Due to the nature of how distributed systems fail, you can't use metrics and logs to discover and address all of your problems. We need a third piece to the puzzle and this is distributed tracing. -
OpenShift Networking Explained
In the past, the application stack had very few components, maybe just a cache, web server, and database.
The most common network service simply allows a source to reach an application endpoint or load balance to a number of endpoints using a load balancing algorithm. The sole purpose of the network was to provide endpoint reachability.
Changes inside the data center are driving networks and network services towards becoming more integrated with the application.
Nowadays, the network function exists no longer solely to satisfy endpoint reachability; it is fully integrated and in the case of Red Hat's Openshift the network is represented as a Software-Defined Networking (SDN) layer -
Site Reliability Engineering | Observability
So the most important feature of any system is reliability, and it's not a feature that a vendor can sell you. So if someone tries to sell you an add-on solution called Reliability, don’t buy it, especially if they offer you 100% reliability.
In this video, we will discuss the importance of distributed systems and the need to fully understand them with practices like Chaos Engineering and Site Reliability Engineering (SRE). We will also discuss the issues with monitoring and static thresholds -
Observability vs Monitoring
We will start by discussing how our approach to monitoring needs to adapt to the current megatrends, such as the rise of microservices. Failures are unknown and unpredictable. Therefore a pre-defined monitoring dashboard will have a hard time keeping up with the rate of change and unknown failure modes. For this, we should look to have the practice of observability for software and monitoring for infrastructure. -
OpenShift Security: Getting Started
Containers in non OpenShift environments have some pretty big security concerns when left to their defaults. In this video we will go through what some of the host security issues are and how OpenShift overcomes them with Security Context Constraints. -
Highlighting Docker Containers
In this video we will go through some basics of containers. The building blocks of containers are namespaces and control groups. However, they share the host kernal which is a security concern. We will also address container orchestratros with Kubernetes and discuss PODs, Services, NAT and VXLAN. -
Chaos Engineering: How to Start A Project
This educational tutorial will start with guidance on how the application has changed from the monolithic style to the microservices-based approach along with how this has affected failures.
I will introduce to you how this can be solved by knowing exactly how your application and infrastructure perform under stress and what are their breaking points.
Chaos Engineering is vital in all projects to determine these points.
Thank you
Matt -
Product Demonstration for OpenShift Networking
Getting started with OpenShift Networking.
Product demonstration on OpenShift networking. We will go through the different OpenShift networking concepts including the OpenShift routes, services, pods, replica sets, and much more! At the end of the demonstration, you will have a good understanding of the OpenShift default networking and how to configure external access.
The entire video is a full demo with animated diagrams helping you stay focused for the entire duration!
Thank you,
Matt Conran
www.network-insight.net -
The Visual Age: Topic Selection
The video should be integrated into every stage of the buyer's journey. Traditionally, there are three stages of the buyer's journey; awareness, consideration, and decision.
Marketers play a key role in using video in these stages along with the post-sale stages. -
The Visual Age: The Starting Point
The video should be integrated into every stage of the buyer's journey. Traditionally, there are three stages of the buyer's journey; awareness, consideration, and decision.
Marketers play a key role in using video in these stages along with the post-sale stages. -
The Visual Age: The Marketing Revolution
With the evolution of buyer behavior and marketing. The future of sales in the digital age is virtual selling and prospective buyers will pursue this journey in a self-service manner.
How do you start the world of video and where can video be placed? -
Tech Brief Video Series - Enterprise Networking | Multipath TCP Connection Setup
The 13th video in the Enterprise Networking series. More information at www.network-insight.net
The aim of the connection is to have a single TCP connection with many subflows. The two endpoints using MPTCP are synchronised and have connection identifiers for each of the subflows.
MPTCP starts the same as regular TCP. If additional paths are available additional TCP subflow sessions are combined into the existing TCP session. The original TCP session and other subflow sessions appear as one to the application, and the main Multipath TCP connection seems like a regular TCP connection. The identification of additional paths boils down to the number of IP addresses on the hosts.
The TCP handshake starts as normal, but within the first SYN, there is a new MP_CAPABLE option ( value 0x0 ) and a unique connection identifier. This allows the client to indicate they want to do MPTCP. At this stage, the application layer just creates a standard TCP socket with additional variables indicating that it wants to do MPTCP.
If the receiving server end is MP_CAPABLE it will reply with the SYN/ACK MP_CAPABLE along with its connection identifier. Once the connection is agreed the client and server will set up state. Inside the kernel, this creates a Meta socket acting as the layer between the application and all the TCP subflows.
Music from bensound.