To assign prices to resources for enterprises, create pricing models with prices for VM elements.
Creating a pricing model
Before you begin:
Add your currencies at Pricing → Currencies
Pre-create cost codes at Pricing → Extra charges to assign to resources, for example, hardware profiles or templates
Privileges: Access pricing view, Manage prices, View datacenter details, Manage enterprises
To create a pricing model:
Go to Pricing → Pricing models
To create a new pricing model when there is none assigned to your enterprise, click +add; or
To clone a pricing model, click the copy clone button. For a pricing model calledPricingModel
, the platform will name the new onePricingModel (c)
.
Warning: The platform will assign your user scope to the pricing model and only users with the same scope can edit the pricing modelComplete the dialog
If your enterprise already has a pricing model, the platform will base a new model on the existing one and let you apply a markup/discount to all prices. So you can set new resource prices using the existing prices as a guide.
Field | Description |
---|---|
Name | The name of your pricing model. The name can represent a service level agreement |
Description | Description of pricing model |
Change all resource prices | Only displays when the enterprise already has a pricing model assigned to it. Resellers can change all prices by adding this percentage. |
Period for prices | The charging period. Integrated on-premise billing will charge by calendar |
Minimum period for prices | The minimum charging period. |
Currency | The currency for this pricing model. Enter new currencies in the Currency tab before you create the pricing model |
Standing charge | Standing charge per charging period. You can include this value in the pricing estimate message and it is included in on-premise billing |
Minimum charge | Minimum charge per Minimum charging period. You can include this value in the pricing estimate message and it is included in on-premise billing |
Show charges before deployment | Select this checkbox to show a pricing estimate popup before deployment with the Deployment message you can customize in the box at the bottom of the popup. See the explanation below |
Insert variable | Choose a variable from the list to add to the pricing estimate message. The variables are described in the table below |
Deployment message | Enter the estimate message for VM deployment, including variables. See https://abiquo.atlassian.net/wiki/spaces/doc/pages/311370925/Pricing+view#Display-a-pricing-estimate-message |
Prices
You can enter general prices for datacenter resources.
Resource prices table
Field | Description |
---|---|
Currency | The currency for this location (datacenter or public cloud region) |
Hypervisor Datastores GB | Price of hypervisor datastores per gigabyte. In public cloud regions, the platform does not use this value |
Networks | Price per network. (The platform always creates a private network for each virtual datacenter) |
Public IPs | Price per public IP address reserved |
NAT IPs | Price per NAT IP address reserved |
CPU | Price per virtual CPU core for deployed virtual machines. If the location uses hardware profiles, pricing does not use this value. |
CPU on | Price per virtual CPU core when virtual machine is powered ON |
CPU off | Price per virtual CPU core when virtual machine is powered OFF |
Memory (GB) | Price of virtual memory in GB for deployed virtual machine. If the location uses hardware profiles, pricing does not use this value. |
Memory on | Price of virtual memory in GB when virtual machine is powered ON or OFF |
Virtual machine | Fee per VM in addition to charges for other VM items |
Virtual machine on | Fee per VM in addition to charges for other VM items |
Repository (GB) | Price of template repository use in GB for virtual machine templates. The platform does not include conversions. In public cloud regions, the platform does not use this value |
Backup (GB) | Price per gigabyte of backup used. See Backup prices for more details |
Anti-Affinity | Price per VM deployed in anti-affinity layer. In public cloud regions, the platform does not use this value |
Firewall | Price per firewall attached to VM |
Load balancer | Price per load balancer attached to VM |
DR protected VM | Price per VM protected by Disaster Recovery |
Datastore tiers
You can set prices for datastore tiers.
In a private cloud datacenter, datastore tiers set service levels for storage. See Manage datastore service levels with datastore tiers.
Persistent storage
In private cloud, you can set prices for the persistent storage tiers. In public cloud regions, the platform automatically imports the storage tiers from the providers so you can price them.
Hardware profiles
You can price hardware profiles in public cloud and in private cloud datacenters with hardware profiles, see Hardware profiles.
The platform can retrieve hardware profile costs from AWS and Azure. See Import hardware profile prices from AWS.
In private cloud and VCD, you can also use cost codes for hardware profile pricing. Pricing and billing of dynamic hardware profiles also includes the usage cost of CPU and RAM.
Backup prices
In private cloud datacenters and VCD public cloud regions, you can set prices for backup policies. You can also set prices for backup policies for size per GB that will have priority over datacenter backup size pricing.
When users request a pricing estimate for their virtual appliance, the platform will include the price of the backup policies of each VM in the VM_PRICES list.
The platform can bill backups with a monthly fixed cost per policy and/or a separate cost for backup size.
In version 6.1, the accounting process saves the usage of backup policies and backup size in GB. To calculate the backup size, it adds up the total size of valid (non-expired) backups in GB.
For example, a customer has a VM with 50 GB of hard disk, and the size of their non-expired backups is 42 GB. And the customer is using a daily backup policy, with a backup policy price of $20. The the backup price per GB is $1. In Abiquo 6.1+, the customer will pay $20 + ($42 * $1) = $62 per month.
Before version 6.1, the platform did not account for backup usage, only the backup policy. With the backup price (GB) for the backup policy, the platform used the VM disk size in GB in the platform to calculate the bill. For the above example, in previous versions of Abiquo, the customer would pay $20 + (50 * $1) = $70 per month.
Extra charge prices
See Manage extra charges with cost codes
Troubleshooting access to pricing models
If a user cannot access pricing model as expected, check the following points.
When you create a pricing model, Abiquo automatically assigns the same scope as your user. The Abiquo UI does not display the scope of the pricing model
Users with pricing privileges can always display the pricing model of their own enterprise. Administrators who can switch to another enterprise can display the current pricing model of the enterprise, even if the pricing model has a different scope
To display or manage the pricing model of another enterprise in Pricing view, you must have the same scope as the creator of the pricing model