Difference between revisions of "ProxCP Admin - KVM"

From ProxCP Documentation
(Created page with "== KVM ISOs == asdf == KVM Templates == ProxCP KVM Templates == KVM Creation ==")
 
Line 1: Line 1:
 
== KVM ISOs ==
 
== KVM ISOs ==
  
asdf
+
Before creating a new KVM service, you must add one or more KVM ISOs to ProxCP.
 +
 
 +
To add a KVM ISO, click ADMIN > Manage KVM ISOs. In the Friendly Name field, enter a name for the ISO such as "CentOS 7". In the volume ID field, enter the volume ID of the ISO file. The format for this is {storage_name}:iso/{file_name}. For example, if the KVM ISO was stored in the "local-lvm" Proxmox storage, the volume ID would be local-lvm:iso/centos.iso.
 +
 
 +
ProxCP assumes that all KVM ISOs are available on all added Proxmox nodes.
  
 
== KVM Templates ==
 
== KVM Templates ==
  
[[ProxCP KVM Templates]]
+
There is documentation regarding KVM templates here: [[ProxCP KVM Templates]]
 +
 
 +
On the admin side of things, you need to tell ProxCP about the templates on the ADMIN > Manage KVM Templates page.
 +
 
 +
* '''Friendly Name:''' the friendly name to identify this template, such as "CentOS 7"
 +
* '''VMID:''' the VMID of the template in Proxmox
 +
* '''Template Type:''' whether the template is Linux or Windows. This setting determines if cloud-init is used or not among other VPS configuration options
 +
* '''Node:''' which node(s) is/are this template available on? Unlike ISOs and LXC templates, KVM templates do not need to be available on all Proxmox nodes
  
 
== KVM Creation ==
 
== KVM Creation ==
 +
 +
ADMIN > Manage KVM
 +
 +
* '''User ID:''' which user should this service be assigned to? You can find user IDs on the ADMIN > Manage Users page
 +
* '''Billing Account ID:''' what is the billing ID of this server? Generally, this should be synced with a service/account/billing ID from a billing platform like Hostbill, WHMCS, or Blesta but it can be any 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}_{service_id}" such as "client_104_2"
 +
* '''Node:''' which Proxmox node should this VPS be placed on?
 +
* '''KVM Hostname:''' the arbitrary hostname of this VPS
 +
* '''Operating System Installation Type:''' whether to use an ISO file or a template for installation
 +
* '''Operating System:''' choose an ISO file or KVM template to use
 +
* '''Operating System Type:''' the KVM ISO/template type
 +
* '''KVM NIC Driver:''' which NIC driver to use for the VPS
 +
* '''KVM Storage Driver:''' which storage driver to use for the VPS
 +
* '''IPv4:''' the IPv4 address assigned to this VPS
 +
* '''IPv4 Gateway:''' the IPv4 gateway that should be used
 +
* '''IPv4 Netmask:''' the IPv4 netmask that should be used
 +
* '''KVM CPU Cores:''' how many CPU cores should this VPS have?
 +
* '''KVM CPU Type:''' which CPU type should this VPS use?
 +
* '''KVM RAM:''' how much RAM should this VPS have?
 +
* '''KVM Storage Location:''' where should the virtual disk for this VPS be located?
 +
* '''KVM Storage Size:''' how big should the virtual disk for this VPS be?
 +
* '''KVM Bandwidth Limit:''' how much bandwidth should this VPS get each month?

Revision as of 22:53, 23 January 2019

KVM ISOs

Before creating a new KVM service, you must add one or more KVM ISOs to ProxCP.

To add a KVM ISO, click ADMIN > Manage KVM ISOs. In the Friendly Name field, enter a name for the ISO such as "CentOS 7". In the volume ID field, enter the volume ID of the ISO file. The format for this is {storage_name}:iso/{file_name}. For example, if the KVM ISO was stored in the "local-lvm" Proxmox storage, the volume ID would be local-lvm:iso/centos.iso.

ProxCP assumes that all KVM ISOs are available on all added Proxmox nodes.

KVM Templates

There is documentation regarding KVM templates here: ProxCP KVM Templates

On the admin side of things, you need to tell ProxCP about the templates on the ADMIN > Manage KVM Templates page.

  • Friendly Name: the friendly name to identify this template, such as "CentOS 7"
  • VMID: the VMID of the template in Proxmox
  • Template Type: whether the template is Linux or Windows. This setting determines if cloud-init is used or not among other VPS configuration options
  • Node: which node(s) is/are this template available on? Unlike ISOs and LXC templates, KVM templates do not need to be available on all Proxmox nodes

KVM Creation

ADMIN > Manage KVM

  • User ID: which user should this service be assigned to? You can find user IDs on the ADMIN > Manage Users page
  • Billing Account ID: what is the billing ID of this server? Generally, this should be synced with a service/account/billing ID from a billing platform like Hostbill, WHMCS, or Blesta but it can be any 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}_{service_id}" such as "client_104_2"
  • Node: which Proxmox node should this VPS be placed on?
  • KVM Hostname: the arbitrary hostname of this VPS
  • Operating System Installation Type: whether to use an ISO file or a template for installation
  • Operating System: choose an ISO file or KVM template to use
  • Operating System Type: the KVM ISO/template type
  • KVM NIC Driver: which NIC driver to use for the VPS
  • KVM Storage Driver: which storage driver to use for the VPS
  • IPv4: the IPv4 address assigned to this VPS
  • IPv4 Gateway: the IPv4 gateway that should be used
  • IPv4 Netmask: the IPv4 netmask that should be used
  • KVM CPU Cores: how many CPU cores should this VPS have?
  • KVM CPU Type: which CPU type should this VPS use?
  • KVM RAM: how much RAM should this VPS have?
  • KVM Storage Location: where should the virtual disk for this VPS be located?
  • KVM Storage Size: how big should the virtual disk for this VPS be?
  • KVM Bandwidth Limit: how much bandwidth should this VPS get each month?