Skip to main content

ACE Network Manager

Safe network configuration manager for edge deployments with automatic rollback protection.

Problem

The netplan tool in Ubuntu 20.04 and 24.04 has critical bugs that fail to properly restore:

  • Routing tables after a failed netplan try
  • DHCP-acquired settings
  • Complex multi-interface configurations

This causes production issues in edge environments where physical access is difficult or impossible.

Solution

ACE Network Manager provides:

  • Atomic configuration changes with automatic rollback
  • Timeout-based confirmation requiring user verification (default: 5 minutes)
  • Semaphore-based state tracking that persists across reboots
  • Systemd integration for post-reboot restoration
  • Human-readable backups with timestamped versions
  • Network connectivity validation before finalizing changes

Installation

# Install with UV
uv pip install ace-network-manager

# Or from source
git clone https://github.com/aceiot/ace-network-manager
cd ace-network-manager
uv sync
uv run ace-network-manager --version

Quick Start

# Apply a new network configuration (5 minute timeout)
sudo ace-network-manager apply /etc/netplan/00-new-config.yaml

# Confirm the configuration is working
sudo ace-network-manager confirm

# Or manually rollback if something went wrong
sudo ace-network-manager rollback

# Check current status
ace-network-manager status

Features

Safe Configuration Changes

  1. Pre-change backup - Creates timestamped backup of current config
  2. Comprehensive validation - Pydantic-based validation with 10+ error checks
  3. Apply - Applies configuration via netplan
  4. Connectivity check - Validates network is working
  5. Timeout watcher - Monitors for user confirmation
  6. Auto-rollback - Reverts if not confirmed within timeout
  7. Post-reboot check - Restores on boot if pending confirmation

Comprehensive Validation (NEW!)

Type-safe Pydantic models catch errors before applying:

  1. Gateway validation - Ensures gateways are host IPs, not network addresses (.0 or .255)
  2. Subnet overlap detection - Prevents multiple interfaces in same subnet
  3. Gateway in subnet check - Verifies gateway is reachable from interface
  4. CIDR notation enforcement - IP addresses must include subnet mask
  5. MTU range validation - MTU must be 68-9000 bytes
  6. MAC address format validation - Validates MAC address syntax
  7. VLAN ID validation - VLAN IDs must be 1-4094
  8. VLAN parent existence - VLAN parent interfaces must exist
  9. DNS server validation - DNS servers must be valid IP addresses
  10. Version validation - Netplan version must be 2

All models are fully type-hinted to prevent human errors during development!

Backup Management

Backups are stored in human-readable format:

/var/lib/ace-network-manager/backups/
  2024-10-30-143022-550e8400/
    metadata.json
    00-installer-config.yaml
    checksums.sha256
  latest -> 2024-10-30-143022-550e8400/

State Tracking

State is tracked with JSON semaphore files that survive reboots:

{
  "state_id": "550e8400-e29b-41d4-a716-446655440000",
  "status": "pending",
  "timeout_at": "2024-10-30T14:35:22.123456Z",
  "backup_path": "/var/lib/ace-network-manager/backups/...",
  ...
}

CLI Commands

prepare

NEW! Prepare a copy of the current network configuration for editing:

ace-network-manager prepare [OPTIONS]

Options:
  -o, --output PATH     Output file path (default: ./netplan-config-<timestamp>.yaml)
  --source-dir PATH     Source netplan directory (default: /etc/netplan)
  --validate/--no-validate  Validate configuration (default: validate)

Examples:
  # Copy current config to local directory with timestamp
  ace-network-manager prepare

  # Copy to specific file
  ace-network-manager prepare -o my-network-config.yaml

validate

NEW! Validate a netplan configuration file without applying it:

ace-network-manager validate CONFIG_FILE

Performs comprehensive validation including:
  - YAML syntax checking
  - Schema validation
  - Gateway in subnet verification
  - Duplicate subnet detection
  - 10+ common network configuration error checks

Example:
  ace-network-manager validate /path/to/config.yaml

apply

Apply a new network configuration with rollback protection:

ace-network-manager apply [OPTIONS] CONFIG_FILE

Options:
  --timeout INTEGER              Seconds until auto-rollback (default: 300)
  --skip-connectivity-check      Skip network validation (dangerous!)

confirm

Confirm that a pending configuration is working correctly:

ace-network-manager confirm [OPTIONS]

Options:
  --state-id TEXT  Specific state to confirm (default: latest)

rollback

Manually roll back to a previous configuration:

ace-network-manager rollback [OPTIONS]

Options:
  --state-id TEXT  State to roll back (default: latest pending)
  --backup PATH    Specific backup file to restore

status

Show current status of network configuration management:

ace-network-manager status [OPTIONS]

Options:
  --json  Output as JSON

Architecture

NetworkConfigManager (orchestrator)
  StateTracker (semaphore files, cross-reboot persistence)
  BackupManager (timestamped backups with checksums)
  TimeoutWatcher (async monitoring, automatic rollback)
  NetplanBackend (validation, apply, connectivity checks)
  SystemdIntegration (boot-time restoration service)

Development

Setup

# Clone and install dependencies
git clone https://github.com/aceiot/ace-network-manager
cd ace-network-manager
uv sync --dev

# Run linting
uv run ruff check src/

# Run type checking
uv run pyrefly src/

# Run tests
uv run pytest tests/ -v

Testing

# Unit tests
uv run pytest tests/unit/ -v

# Integration tests (requires systemd)
uv run pytest tests/integration/ -v -m requires_systemd

# Coverage
uv run pytest tests/ --cov=ace_network_manager --cov-report=html

Implementation Status

  • Phase 1: Project structure and tooling
  • Pydantic models for netplan validation
  • State models with comprehensive type hints
  • Network configuration validation (10+ error checks)
  • CLI commands: prepare and validate
  • Unit tests for validation (22 tests passing)
  • Phase 2: State management implementation
  • Phase 3: Backup system implementation
  • Phase 4: Network integration (netplan apply)
  • Phase 5: Timeout watcher
  • Phase 6: Systemd integration
  • Phase 7: Core orchestration
  • Phase 8: CLI command implementation (apply, confirm, rollback, status)
  • Phase 9: Integration testing
  • Phase 10: Documentation and polish

Documentation

License

MIT

Credits

Developed by ACE IoT Solutions for safe network management in edge deployments.


Metadata

Release files for ace-network-manager 0.3.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for ace-network-manager 0.3.3
File Size Uploaded
ace_network_manager-0.3.3.tar.gz 317.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for ace-network-manager 0.3.3
File Interpreter ABI Platform
ace_network_manager-0.3.3-py3-none-any.whl Python 3 none any Details

Total release size: 367.0 kB

Release files / ace_network_manager-0.3.3.tar.gz

Download URL ace_network_manager-0.3.3.tar.gz
Size 317.9 kB
Tags Source
SHA-256 checksum
How to use checksums
f54ffdfdb7abe9069669ec423e3e3ef1d9a9f6e82e17b946abee757c6e623b38
BLAKE2b-256 checksum
How to use checksums
638a78f871286a36a6a653002413560e75bcfc6d445f80a2db619d227d6a7360
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 9, 2025.

Transparency log

Release files / ace_network_manager-0.3.3-py3-none-any.whl

Download URL ace_network_manager-0.3.3-py3-none-any.whl
Size 49.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f48d4b5eca03261e8e178d0b58c0c52a7acccd19519403bbefe873d964aff549
BLAKE2b-256 checksum
How to use checksums
b0f9f7728a24640f7ba8bdc574f67a4cb52d2aaeb4881384b543a0845b3032e0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 9, 2025.

Transparency log

Release history Release notifications | RSS feed

This release

0.3.3 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page