Admin VPN Infrastructure Operations

This flow explains how infrastructure teams run node capacity, routing quality, and delivery readiness.

What admins can do

• Register and maintain node servers
• Configure node clients and protocol offerings
• Control node availability and maintenance state
• Monitor node health, usage, and quality trends
• Observe package queue delivery and activation behavior

Infrastructure operation flow

flowchart TD
    onboard[OnboardNodeServer] --> config[ConfigureNodeClientProfiles]
    config --> publish[ExposeEligibleNodesByGroup]
    publish --> monitor[MonitorHealthAndTraffic]
    monitor --> maintain[MaintenanceOrCapacityAdjustment]
    maintain --> monitor

Node operations

• Keep node metadata accurate (location, route class, capacity intent).
• Validate protocol configuration before publishing.
• Use maintenance states to protect customer experience during changes.

Access and delivery relationship

• Customer package policy controls which nodes users can access.
• Package queue health affects when customers become active on service.
• Infrastructure and commercial operations must coordinate release windows.

Observability checklist

• node online/offline trends
• abnormal traffic spikes
• package activation lag
• failed delivery or queue backlog
• regional quality degradation

What admins cannot do

• Expose nodes to customers without matching package access scope
• Ignore maintenance signaling during disruptive changes
• Treat node-client configuration and package policy as independent concerns
• Assume delivery is healthy without queue and activation monitoring