Resource List

The following are resources used by the API:

  • Allocation Limits. Resellers may allocate a maximum amount of resources that any given Reseller or End Client may use on each Node. Accounts may not modify their own Allocation Limits but may modify the Allocation Limit of any Account that it owns.
  • Billing. The Billing resource is used to produce reports on rated usage for Accounts.
  • Firewalls. A Firewall is automatically created when the first Virtual Machine (VM) is created and each Account may have one Firewall per Node.
  • Images. Images are copies of Virtual Machines that may include software and customizations made by an account. Images allow account to quickly clone VMs in a ready-to-go fashion as opposed to setting up VMs and then installing all customizations one at a time.
  • Load Balancers. Load Balancers are used to manage traffic to VMs. Accounts are able to manage any number of Load Balancer pools in any of the nodes it has access to.
  • Network Storage. Network Storage volumes can be created in NFS or iSCSI formats, and the API can be used to list, create, delete, and view details of network storage devices. These devices can be mounted from VMs as well as from your own physical servers or computers outside of our network.
  • Nodes. Any Account may have access to several PNCP Nodes and each node can have different properties (even different geographical locations). Current nodes are:

Node ID
Node Name
Phoenix NAP
Asburn, VA

  • Operating System Templates. Each VM requires an Operating System installation. Accounts can select from available templates for each VM.
  • Accounts. Accounts are entities that own and manage Virtual Machines, Load Balancers, Firewalls, and Public IPs in PNCP. Resellers may own accounts that are not their own (other resellers and/or End Clients) and are allowed to act on the behalf of accounts that they own.
  • Pricing Profiles. Pricing Profiles are used to assign pricing to the services Resellers and End Clients use. Resellers can create any number of pricing profiles and assign them to any Account that they own.
  • Public IPs. Accounts can assign Public IPs to VMs or Load Balancer pools. They can also reserve a limited number of Public IPs that are not presently assigned for use in future planning.
  • Tasks. Many API requests are not completed instantly. These requests can create task resources that the API uses to poll for status of asynchronous calls.
  • User Accounts. An Account can create and manage User Accounts for its own access control.
  • Virtual Machines. Accounts can create, modify, or delete Virtual Machines (VMs) in any of the nodes they have access to. Resellers may also perform the same functions on any Account that they own.