ProxCP Admin - LXC

From ProxCP Documentation
Revision as of 15:10, 22 July 2020 by Proxcp (talk | contribs) (→‎LXC Creation)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

LXC View

This page presents a table of all LXC services in ProxCP. The table shows relevant account information and allows Admins to manually suspend, unsuspend, and delete LXC accounts.

Suspending a service disables all ProxCP management features for that service. Unsuspending a service will re-enable these features.

Deleting a LXC service from this page will only delete the service details from ProxCP. You must also manually delete the LXC VPS on the associated Proxmox node to fully remove it.

LXC Templates

Before creating a new LXC service, you must add one or more LXC templates to ProxCP. Proxmox provides a bunch of pre-made LXC templates available for download or you can make your own. ProxCP does not supply any LXC templates as the Proxmox-specific templates are preferred.

To add a LXC template, click ADMIN > LXC > Manage LXC Templates. This page will scan your first Proxmox node for LXC templates that are not yet added in ProxCP then allow you to add them.

ProxCP assumes that all LXC templates are available on all added Proxmox nodes.

Alternatively, you can add LXC templates manually. In the Friendly Name field, enter a name for the template such as "CentOS 7". In the volume ID field, enter the volume ID of the template. The format for this is {storage_name}:vztmpl/{file_name}. For example, if the LXC template was stored in the "local-lvm" Proxmox storage, the volume ID would be local-lvm:vztmpl/template.tar.gz.

LXC Creation

ADMIN > LXC > Manage LXC

  • User ID: which user should this service be assigned to?
  • Billing Account ID: what is the billing ID of this service? Generally, this should be synced with a service/account/billing ID from a billing platform like WHMCS or Blesta but it can be any globally unique number
  • Pool ID: name of the Proxmox pool that should be created and used for this VPS. This can be in any format, but we recommend "client_{client_id}_{billing_id}" such as "client_104_2". This value should also be globally unique
  • Node: which Proxmox node should this VPS be placed on?
  • LXC Hostname: the arbitrary hostname of this VPS
  • Operating System: the LXC template that should be used
  • Operating System Type: the LXC template type
  • LXC NAT Enabled: is this service NAT-enabled?
    • NAT Public Ports: how many NAT ports should this NAT service be allowed to use?
    • NAT Domain Forwarding: how many NAT domains should this NAT service be allowed to have?
  • IPv4: the IPv4 address assigned to this VPS in CIDR format
  • IPv4 Gateway: the IPv4 gateway that should be used
  • IPv4 Netmask: the IPv4 netmask that should be used
  • LXC CPU Cores: how many CPU cores should this VPS have?
  • LXC RAM: how much RAM should this VPS have?
  • LXC Storage Location: where should the virtual disk for this VPS be located?
  • LXC Storage Size: how big should the virtual disk for this VPS be?
  • LXC Bandwidth Limit: how much bandwidth should this VPS get each month?
  • Network Speed Limit: optionally set a network speed limit on this service
  • MAC Address: optionally set your own MAC address for this service instead of a randomly generated MAC address

LXC TUN/TAP

It may be convenient to allow your users to enable/disable the TUN/TAP interface on LXC services by themselves in ProxCP. Proxmox does not provide a convenient way to do this therefore ProxCP requires special permissions to do this. You can add those permissions on the ADMIN > Settings > Manage Node SSH page. More details are shown there too.

Retrieved from "https://docs.proxcp.com/index.php?title=ProxCP_Admin_-_LXC&oldid=182"