The accounting information can be set to the product master as products for each element type (category) that consists of the L-Platform.
The categories that can be set as products are shown below. Note that the unit prices can be specified by yearly, monthly, or hourly.
Category | Explanation |
|---|---|
CPU | Unit price per CPU (*1)(*2). |
CPU clock | Unit price per CPU clock of 0.1GHz (*1)(*2). |
Memory capacity | Unit price per memory capacity of 0.1GB (*2). |
Virtual L-Server | Unit price per virtual L-Server. |
Physical L-Server | Unit price per physical L-Server. |
System disk capacity | Unit price per disk capacity of 0.1GB of system disk. (*4) |
Data disk capacity | Unit price per disk capacity of 0.1GB of data disk. (*3) (*4) |
Template | Unit price per L-Platform template. |
Snapshot | Unit price per disk capacity of 0.1GB of the disk from which snapshots are created.(*5) |
NIC | Unit price per NIC. |
*1: The price per CPU allocated as usage fee (the estimated price) is the sum of "Unit price per CPU" and "Unit price per CPU clock * CPU clock".
Example) A price calculation example is shown below.
[Conditions]
CPU Clock: $0.10/0.1GHz
CPU: $0.80/unit
[Example calculation]
Price for a CPU of 3.2GHz: $0.10 * 32 + $0.80 = $4.00
Price for two CPUs each of 1.0GHz: ( $0.10 * 10 + $0.80 ) * 2 = $3.60
*2: The estimated and actual charges for the physical L-Server are calculated based on the values entered in the [L-Platforms] tab of the ROR console.
*3: Estimated price for data disk capacity are added according to disk capacity usage for each storage pool, with no differentiation between extension disks and existing disks. Note also that if the same existing disk is attached to multiple L-Servers at this time, calculations for the existing disk capacity will be added together in accordance with the number of L-Servers to which the disk is attached. Resource allocation methods differ between extension disks and existing disks. For this reason, the storage pool used for an existing disk should not be the same as one used for an extension disk. For operations that use separate storage pools, charges for the existing disk can be calculated using the following two methods:
If charging according to the total capacity of an existing disk attached to L-Server(s):
In the storage pool, set the amount to be charged (in units of 0.1GB) when attaching an existing disk to an L-Server. If the same existing disk is attached to multiple different L-Servers at this time, the disk capacity will be added together for the total number of attached L-Servers and charged accordingly.
If charging by the available existing disk from the L-Platform:
Rather than setting the price for the existing disk defined by the storage pool, perform settings instead to include the usage charge for the available existing disk in the price for the L-Platform template.
*4: The unit price for the system disk capacity and the data disk capacity is set based on the storage pool. If [Auto-Select] is specified for the storage pool in the [L-Platforms] tab of the ROR console, calculations for estimated charges will be displayed based on a unit price of 0 for disk capacity. Usage charge calculations will be based on the unit price for the storage pool on which the disk was created.
*5: The unit price for snapshots is set based on the storage pools. The charges for snapshots are calculated based on the disk capacity of the virtual disk included with the virtual L-Server on the place where the snapshot was created and the storage pool.
If the storage pool for the system disk is different from the data disk of the virtual L-Server, then the charges for the snapshot will be calculated based on the disk capacity and unit price for each of those storage pools.
Point
L-Platform operation when reconfiguration is not permitted
L-Servers and others will be allocated using the system configuration defined in the template if the L-Platform template reconfiguration is not permitted in the operation. In this case, only the prices for the templates need to be set and the prices for the L-Servers need not.
About Setting Prices
In the Solaris container, although it is possible to allocate more CPU and memory to the non-global zone than is installed in the host operating system, if the CPU load and memory usage in each non-global zone increase, the allocated CPU function and memory capacity may become unusable.
In order to not exceed the capacity physically held by the host operating system when creating a non-global zone, it is possible to ensure the functionality of the allocated amount in the non-global zone by allocating CPU and memory.
However, if used for development environments or if non-global zones which exceed the physical CPU and physical memory are created, it is not possible to ensure the allocated amount of functionality. If CPU and memory are made the subject of charges in environments where the allocated functionality cannot be ensured, consider setting the CPU and memory unit prices at lower prices than normal.
As it may not be possible to ensure the functionality of allocated amounts of CPU and memory if overcommit is enabled in cases such as where L-Platform import from related L-Servers is performed using VMware and Hyper-V as virtual software, give some consideration to price settings.
When using the VDI coordination function, use a separate VM host pool for VDI, and do not set the unit price for the CPUs, CPU clocks, and memory size of the VM host pool dedicated to VDI coordination.
L-Servers created by VDI coordination can not be charged by operating time. Since VDI management software controls the power operation of the L-Servers automatically. To charge for L-Servers created by VDI coordination, set the accounting information to product categories which are charged by deployment time, such as L-Platform templates and Virtual L-Servers.
The usage fee (the estimated price) displayed on the [L-Platforms] tab of the ROR console and others is calculated as follows.
L-Platform usage fee (the estimated price) = monthly template price + monthly price for all L-Server
+ monthly price for all system disks + monthly price for all data disks
Template monthly price = template unit price * monthly amount conversion
Virtual L-Server monthly price = image unit price * monthly amount conversion
+(CPU unit price * monthly amount conversion
+ CPU clock unit price * CPU clocks * monthly amount conversion) * number of CPUs
+ memory unit price * amount of memory * monthly amount conversion
Physical L-Server monthly price = image unit price * monthly amount conversion
+(CPU unit price * monthly amount conversion
+ CPU clock unit price * CPU clocks * monthly amount conversion) * number of CPUs
+ memory unit price * amount of memory * monthly amount conversion
System disk monthly price = system disk unit price * amount of disk * monthly amount conversion
Data disk monthly price = data disk unit price * amount of disk * monthly amount conversion
NIC monthly charge = NIC unit price * used number of NICs * monthly amount conversionEstimated charges for snapshots Estimated charges for snapshots on the system disk = snapshot unit price * system disk capacity * monthly amount conversion Estimated charges for snapshots on the data disk = snapshot unit price * data disk capacity * monthly amount conversion
- If the price is hourly basis, usage fee (the estimated price) is calculated for 24 hours * 30 days.
- If the price is yearly basis, usage fee (the estimated price) is twelfth of that price.
- Usage fee (the estimated price) is rounded to nearest hundredths of dollar (cent) when displayed.
- Estimated charges for an L-Platform are displayed when an application is made to use an L-Platform, or when its configuration is changed.
- Estimated charges for a snapshot are displayed when a snapshot of a virtual server is taken and when the snapshot is referenced.