Skip to content

Infrastructure

Infrastructure is everything between the provider connection and a customer's VPS: where the hardware is, what runs on it, how it is reached and where its data lives.

Concept Page Summary
Locations Locations Commercial regions that group hypervisors.
Hypervisors Hypervisors Managed nodes and their status/capacity.
Scheduler Scheduler How a plan + location + image becomes a placement.
Networking & IPAM Networking / IPAM Networks, pools and address lifecycle.
Storage Storage Tiers, pools, provider mappings and reservations.
Images Images The OS image library and provider template mappings.
Compute Compute CPU pools, profiles, NUMA, hugepages, hardware.

Plans

A plan is the booked resource envelope for an instance (CPU, memory, disk, networking limits, storage tier, backup quota and optional compute intent). Plans are managed under Admin → PteroCloud → Plans and chosen by the customer at creation time.

Plans

Structured provisioning defaults (username/credential policy, timeouts, networking defaults) are managed under Admin → PteroCloud → Settings → Provisioning and are resolved per instance at provision time.

Settings

The setup assistant

The setup assistant reads the real backend configuration and reports readiness. Steps: License → Provider → Hypervisor → Location → Networking → IP Pool → Storage → Image → Provisioning Defaults → Plan → Test VPS → Verification.

php artisan pterocloud:setup:verify --json

See Verification.