Hosting plans and creating a server

What a hosting plan sets for its servers, how to create one, how placement picks a node, and how administrators and customers create a server.

A hosting plan is a server size you sell: the vCPUs, memory and disk every server of the plan gets, where it is offered, its network, limits, and what its owner may do. Customers and resellers always create servers from a plan; administrators may also give a server a size of its own. A change to a plan reaches the servers that follow it, as each section of the form says.

Create a plan#

  1. Go to Customers › Hosting plans and press Add plan. The form is a full page with its sections in order.
  2. In General, give the plan a Name, choose its Owner (the panel, or a reseller) and its Virtualization: KVM virtual machine or LXC container. See KVM virtual machines and LXC containers for what the choice changes.
  3. Fill in Size, then the sections you need (table below). Empty fields mean "no limit" or "the node's setting"; nothing is filled in for you.
  4. Press Add plan. The plan is listed under Virtual machines or Containers, with a KVM or LXC badge.

The plan's name must be unique within its kind: a KVM plan and an LXC plan may both be called "VPS 1". The kind cannot change once a server uses the plan.

Section What it sets
General Owner, name, virtualization, the container-only switches (for an LXC plan), active or not, position in the list
Size vCPUs, memory (GB, in steps of 0.5), disk (GB), and a Storage tag: its servers go only on node storages with that tag (Any storage: every storage that takes new servers)
CPU and disk I/O CPU limit (% of each vCPU), CPU weight, and read/write IOPS and MB/s for each disk. Panel plans only: a reseller's plans take the server limits an administrator set on the reseller. See Disks, CPU limits and GPUs
Network Traffic a month and what happens past it, speed in and out, Public or Behind NAT, port forwards and website domains included, IPv4 and IPv6 addresses, IPv6 prefix per server, floating IPs and load balancers included
Network and processor Outbound SMTP, inbound ping, traffic counting, nested virtualization, AMD topoext, CPU model, machine type (each "Node's" by default), Dedicated CPU, and GPU with GPUs per server
Locations The locations it is offered in. None ticked: every location (for a reseller's plan, every location the reseller may use)
Placement The Placement rule for its servers and Excluded nodes (below)
Required firewall templates Templates every server of the plan gets and its owner cannot remove
Extra disks Disks every server gets, the most extra disks and the most extra disk space an owner may add
Backups and snapshots When its servers are backed up, where to, and how many snapshots they keep (Backups, Snapshots)
Setup, trial and reinstalls High availability, whether new servers wait for their owner to set them up, a trial length and what happens at expiry, and the Reinstall limit (reinstalls per server per day, week or month)
What customers may do The customer switches of the plan's servers (Customer permissions) and Images for reinstalls and setup: Every image or Only the images chosen here
Abuse and auto-scaling The plan's abuse policy (Abuse detection, Auto-scaling)

Sections that do not apply are not shown: an LXC plan has no machine type, CPU model, dedicated CPU, GPU or extra disks; a section whose feature is not installed on the panel is left out.

How a node is chosen#

A customer chooses a location; the panel then chooses the node. Only nodes that qualify are considered: online, not in maintenance and taking new servers, with a free address, room for the size within the node's capacity, and able to run what was asked (containers, the image's firmware and CPU level, Windows, FreeBSD, dedicated CPUs, a GPU). Among those, the Placement rule decides:

Rule Chooses
Most memory left The node with the most memory left to sell. Spreads servers by memory. This is the default of every location.
Most storage left The node with the most room on the storage the server's disk would go on.
Fewest servers The node with the fewest servers, whatever their size.
Round-robin Each node in turn, by name, skipping those that cannot take the server.
Fill first The node with the least memory left that still fits: fills one node before the next, keeping others empty.

Each location has its own rule (Infrastructure › Locations). A plan's Placement rule overrides it for the plan's servers; Each location's own rule keeps the location's. Excluded nodes are passed over for the plan's servers, but an administrator who names a node on the create form is not refused.

Every decision is written to System › Placement log, with the reason each node was passed over.

Create a server as an administrator#

  1. Go to Servers › Servers and press Create server.
  2. If both kinds can be offered, choose the Type of server: Virtual machine (KVM) or Container (LXC). The choice filters the plans and images that follow.
  3. Choose the Owner (the account the server counts against).
  4. Under Place on, choose A node (then the Node) or A node group (the first node of the group, in its order, with room). Nodes that cannot run the chosen type are greyed out with the reason. With more than one storage on the node, choose a Storage or leave Automatic (the plan's storage tag and the node's fill order).
  5. Choose a Plan, or Custom size to type the vCPUs, memory, disk, traffic, speed and network yourself.
  6. When the server is for another account, choose Who installs it: Install now, or Let the owner set it up (the server waits in Awaiting setup until its owner chooses the system, hostname and keys; nothing is sent to the node until then).
  7. Under Install from, choose Image, Application or ISO (Images, One-click applications, ISOs).
  8. Set the hostname (optional: left empty, the panel makes one such as vps-k3x9q2), the root password (generated, or typed: 12 to 72 characters), Allow SSH login with the password, and SSH public keys.
  9. Check the Summary and press Create server.

If the server would oversell the node, the form says so; tick I know this oversells the node and press Create anyway only if you mean it.

The server is created as Building. Its page shows the progress; administrators get a build log of each create.

How customers create a server#

A customer (or reseller) sees the same form with fewer choices: a Location instead of a node, the plans offered there, and the images their plan allows. The plan's limits and the account's own limits apply; a plan too small for the chosen image is shown with the reason and cannot be chosen.

A link such as https://panel.example.com/servers/create?plan=12 opens the form with plan 12 chosen, when the account may use it; for a plan offered in a single location, that location is chosen too. Billing modules use the API instead.