jpetazzo/pipework
Pipework
Pipework is a software-defined networking toolkit and management utility designed to automate network configurations for Linux Containers. It provides tools for managing IP addresses, creating virtual network topologies, and integrating containers into various network architectures.
The project distinguishes itself through specialized support for InfiniBand IPoIB device configuration, including the management of partition keys. It also features integration with Open vSwitch for bridge automation and VLAN isolation, as well as the ability to bind containers directly to physical host hardware via macvlan subinterfaces.
Its broader capabilities cover comprehensive network management, including static and DHCP IP assignment, routing rule manipulation, and default gateway configuration. It also includes utilities for monitoring interface readiness and simulating network conditions such as latency and packet loss within container namespaces.
Features
- Software-Defined Networking Services - A software-defined networking toolkit to automate virtual network topologies and interface assignments for containers.
- Functional Network Topologies - Creates virtual network interfaces and bridges to connect containers into custom architectural layouts.
- Network Namespace Virtualization - Executes network configuration commands directly within isolated Linux network namespaces to ensure container traffic separation.
- Container Networking Configurations - Automates the creation of custom virtual network layouts and bridges to define container communication architectures.
- Container IP Assignments - Assigns MAC addresses, static IPs, and physical network bindings to Linux container instances.
- IPoIB Device Virtualization - Provides specialized support for creating virtual IPoIB devices to enable high-performance InfiniBand networking within containers.
- Physical - Binds containers directly to physical host hardware using macvlan subinterfaces or exclusive network namespaces.
- Open vSwitch Integrations - A networking utility that connects containers to Open vSwitch bridges and manages VLAN isolation.
- Virtual Network Bridging - Connects multiple containers through software bridges to create isolated private network segments on the host.
- Macvlan Virtual Network Creation - Implements macvlan subinterfaces to allow containers direct L2 network access via unique MAC addresses on a physical host interface.
- LXC Network Management - Manages IP addresses, MAC addresses, and network interfaces for LXC containers using a software-defined approach.
- LXC Networking Utilities - Provides a set of utilities for configuring IP addresses, routing, and interfaces for Linux Containers.
- Container Networking - Connects LXC containers to InfiniBand interfaces as virtual IPoIB devices with support for partition keys.
- IPoIB Configurators - Provides a utility for creating virtual IPoIB devices and managing partition keys within container namespaces.
- Open vSwitch Integration - Interfaces with Open vSwitch to automate virtual bridge creation and VLAN tag assignment for container traffic isolation.
- Traffic Shaping - Applies traffic control rules within container namespaces to simulate network conditions like latency and packet loss.
- Container VLAN Attachments - Attaches containers to specific VLAN IDs via physical interfaces or Open vSwitch to isolate network traffic.
- Device Attachment - Creates virtual IPoIB devices for containers with support for partition key assignments.
- Network Condition Emulation - Uses traffic control tools within container namespaces to simulate packet loss and latency for network testing.
- Network Condition Simulation - Simulates network conditions such as packet loss and latency within container namespaces using traffic control.
- Networking And Proxies - Software-defined networking for Linux containers.
Star history
How this analysis was created: This summary and feature list were written by an AI model that read the project's README and public documentation pages. Each feature links to the documentation it came from; stars, license and language come straight from the GitHub API. The model does not read the source code, and the analysis is refreshed when the project is re-analysed. Learn more on our About page.
