ABOUT THE AUTHOR

Łukasz Drzewiecki

Senior Network Engineer

Łukasz Drzewiecki is a Senior Network Engineer with twenty years of experience. He has worked on projects involving development of automation tools, supporting customers with complex multi-environment deployments with SmartNICs, and development of components for mobile services. He has a strong DevOps profile, leveraging his knowledge of automation tools and Python to optimize performance. He specializes in Python, Go, SQL, and has a strong skill set in Red Hat and Debian derivatives, services administration, network architecture, virtualization and clouds.

Łukasz Drzewiecki

Recent posts by Łukasz:

Thumbnail of an article about What is Policy Based Routing (PBR)?
NETWORKS

What is Policy Based Routing (PBR)?

Nowadays, network traffic nature becomes very complicated in terms of the mixture of applications and their connectivity requirements. Achieving these requirements by means of traditional routing mechanisms may become cumbersome or even impossible and requires special dedicated solutions. Additionally, organizations need to focus on operational costs more strictly than in the past. One good direction to achieve this goal is the optimization of resource usage within different domains. Networking is one such domain, where the objective is to rationally maximize the usage of existing infrastructure rather than making an investment in increasing its capacity.
Thumbnail of an article about Example use case of network troubleshooting during the VNF lifecycle
NETWORKS

Example use case of network troubleshooting during the VNF lifecycle

This article will guide you through a proposition of an implementation of network monitoring and troubleshooting during the Virtual Network Function (VNF) lifecycle, based on a combination of data gathered from SDN - in our case Tungsten Fabric (TF) - and OpenStack. This article is a promised follow up to our article Network traffic troubleshooting during the VNF lifecycle - aspects of Tungsten Fabric flows. In the case presented in this article, the main challenge with network monitoring and proactive troubleshooting is to identify the root cause of potential flow-related errors before they cause a service outage.