Platform Management

Billing Management

Billing Management includes bills and pricing list.

Bills of different resources under different projects, departments, and accounts are calculated and displayed in real time based on the unit price and time of usage defined in a pricing list. The time is accurate to seconds.

Pricing list, also known as price table, defines the unit price of different resources based on the resource specification and time of usage. After you attach a pricing list to a project or an account, the corresponding bills of resources will be generated accordingly.

Bills Notice

Resource bills are generated at a specified time, not in real time. By default, the system generates bills at 00:00 on a daily basis. You can set the bill generation time as needed. The method is as follows:
Go to Settings > Global Settings > Advanced, locate The time point of billing generation, and click the Edit icon. Default value: 0.
If you change the pricing list of a project or an account, bills of the associated resources will be generated immediately.
If you delete a up-to-date historical price in a pricing list, bills of the associated resources will be generated immediately.
The billing details, such as the bills of VM instances, root volumes, data volumes, GPU devices, and public IP addresses, in an account can be viewed by regular accounts and project members.

To view the project bills, obtain and install the license of the Enterprise Management Module in advance.
After you attach a pricing list to a project and set the unit price for each resource to be billed, the billing starts, and project bills will be generated accordingly.
Project bills can be viewed by the administrators, platform members, and project members.

To view the department bills, obtain and install the license of the Enterprise Management Module in advance.
After you add a project to a department, you can obtain the project-related billing data, including the historical data, and generate bills by department.
The billing data is directly related to projects. After you remove a project from a department, all relevant billing data (including the historical data) will be removed from the department bills.
Department bills can be viewed by the administrators, platform members, and head of departments.

After you attach a pricing list to an account and set the unit price for each resource to be billed, the billing starts, and account bills will be generated accordingly.
Account bills can be viewed by the administrators, platform members, and account owners.

Resource bills are generated at a specified time, not in real time. By default, the system generates bills at 00:00 on a daily basis. You can set the bill generation time as needed. The method is as follows:
Go to Settings > Global Settings > Advanced, locate The time point of billing generation, and click the Edit icon. Default value: 0.
The resource bills of VM instances and routers (including vRouters and VPC vRouters) are displayed on the VM instance tab page.
The resource bill of a VM instance includes the total billed amount of the compute resources, such as the memory and CPU.
The public IP resource bill includes two bill lists: public IP (flat network) and public IP (virtual IP).
The billing details, such as the bills of VM instances, root volumes, data volumes, GPU devices, and public IP addresses, in an account can be viewed by regular accounts and project members.

If you turn off the Switch for Billing in global settings, the Cloud will stop billing the resources, and no new bills will be generated.
When a VM instance is deleted but not expunged (completely deleted), compute resources, such as the CPU and memory, and IP resources, such as the public IP (flat network), will be released immediately. Therefore, the CPU, memory, and public IP resources are no longer billed.
When a VM instance or volume is deleted but not expunged, the VM instance or volume still occupies the physical storage resources (root volume and data volume). Therefore, the root volume and data volume continue to be billed until the corresponding VM instance or volume is completely deleted.
A VM instance in the Stopped state still occupies storage resources and IP resources. Therefore, the root volumes, data volumes, and public IP (flat network) will continue to be billed.
An uninstantiated VM instance is not billed. However, the VM instance will be immediately billed once instantiated. For example, a project or an account has an instantiated data volume, and does not attach the data volume to a VM instance. In this case, the data volume is still billed.
Change the resource owner: The fees generated before the resource owner changed are retained in the old accounts and projects, and new fees will be charged for the new accounts and project after the resource owner changed.

Pricing List Notice

A pricing list can be attached to more than one project or account. A project or an account can have only one pricing list attached.
The Cloud provides a default pricing list, which cannot be deleted. When you upgrade the Cloud, a default pricing list will be automatically created and attached to all projects or accounts according to the previous billing setting.

The default pricing list cannot be deleted.
The pricing list that is being used by a project or an account cannot be deleted. To delete such a pricing list, change a pricing list for the associated project or account, and then delete the pricing list.

Changes of public IP addresses are incurred only after QoS is set.
Currently, virtual IP addresses of the IPv6 type cannot be billed.

Pricing List lets you bill root volumes or data volumes according to disk performances via advanced parameters. The configuration metrics rely on priceUserConfig in the advanced parameters of an instance offering or disk offering. Make sure all configurations are strictly consistent. Otherwise, a pricing list cannot be generated.

When you delete a pricing history whose end date is the current date, the pricing records will also be deleted. Meanwhile, the corresponding bills will be generated immediately, and no more fees will be incurred any longer.
When you delete a pricing history whose end date is not the current date, only the pricing records will be deleted. The billing and bills are not affected.

Tag

With Tag, you can create tags for resources as needed, and quickly locate the required resources according to the tag type and tag name.

You can create tags with different colors, simple style, and brief language. You can also bind tags to resources and search resources by using tags. This will improve the search efficiency.
Two types of tag are available: admin tags and tenant tags.
- Admin tags are created and owned by administrators (admins or platform admins), and can be bound to VM instances, volumes, hosts, and bare metal instances.
- Tenant tags are created and owned by tenants (regular accounts or projects), and can be bound to VM instances and volumes.
Currently, you can bind tags to or unbind tags from VM instances, volumes, hosts, and bare metal instances.

Notice

Admin tags are created and owned by administrators (admins or platform admins), while tenant tags are created and owned by tenants (regular accounts or projects).
Tags created by tenants can only be bound to resources of the corresponding tenants, while admin tags can be bound to all of your resources.
Administrators can unbind or delete tenant tags.
Tags in a project are owned by the project. Therefore, all members, including the head of project, project administrator, and project member, can perform operations on these tags.
Currently, tag owners cannot be changed.
When you change a resource owner, all tenant tags bound to the resource will be unbound. However, the admin tags are not affected.
After the Cloud is upgraded seamlessly, the existing tags will be updated accordingly and displayed in the latest way. If an exception occurs, refresh your browser or create a new tag.

When you create a tag, the naming convention must satisfy the following rules:
- The length of the tag name cannot exceed 20 characters.
- The tag name is case-sensitive.
- Tags are unique. The same roles can have only one tag with the same name and color.

When you attach a tag, note the following:
- One resource can bind 50 tags at most, while a single tag can bind the unlimited number of resources.
- Many-to-many bindings between tags and resources are supported. That is, you can bind multiple tags to multiple resources.
- Tags that were created by a tenant can only be bound to resources owned by the tenant, while admin tags can be bound to all resources.
- An administrator can unbind or delete tenant tags.
- Resource tags can be sorted in order according to the creation time or tag names (priority: characters > numbers > Chinese characters > English characters). To change the sort order, choose Settings > Global Settings > Advanced, locate Tag sorting field, and click the Edit icon. By default, the tags are sorted in order by the tag name.
When you detach a tag, note the following:
- Multiple tags on a single resource can be unbound simultaneously. In addition, multiple resources on a single tag can also be unbound simultaneously.
- A tenant can only unbind tags from the resources owned by the tenant itself, while an administrator can unbind tags from all resources.

Application Center

Application Center provides enhanced functionality and fast access to various third-party applications. You can add the URLs of different third-party applications for centralized management and quick access.

Platform Management

Billing Management

Bills Notice

Pricing List Notice

Tag

Notice

Application Center

Products

Solutions

Help & Support

Contact Us