source/adminguide/locale/zh_CN/LC_MESSAGES/usage.mo (25 lines of code) (raw):
�� L | | } � � � � � � � � � � � 4 �
� � � � � � ]
$ / 4 A & X ' � � � � � � � [ `
p ~ 0 �
� � � + � & B F � � ? � � � � � V � � ^ � R m � � � � g *! 0 �" �# � �# �$ , �% + �% & & ,& G& # _& @ �& - �& �& > ' K N' N �' �' �( * 9+ P T, 3 �, �, �, - - 2- G- $ Y- ~- � �- 4 r. = �. 1 �. 1 / A I/ �/ �/ �/ �/ �/ � 0 �0 �0 h �0 01 . 91 h1 H �1 N �1 2 32 C2 L2 / \2 E �2 ` �3 34 F4 Z4 m4 �4 � �4 Y 75 A �5 * �5 j �5 6 i6 8 �6 0 �6 2
7 3 =7 5 q7 � �7 ; X9 = �9 5 �9 7 : ? @: A �: 8 �: : �: ; 6; = r; 8 �; : �; J $< � o< : = < Q= = �= O �= % > � B? � @ { �@ � jA � fC [E gF a �F � �F W yG �G 2 �G [ H � wH �H � {I \ 'J � �J � (K � �K _ gL � �L �M �M / �M �M �M � �M �P �P
�P �P
�P � Q # �Q
�Q � �Q �R � �R �S �S �S T C %T E iT 9 �T ; �T 8 %U ^U . yU > �U �U �U V 0V " EV hV ~V �V �V �V �V �V " W 'W =W � PW ( �W X " X * CX - nX : �X < �X 9 Y / NY ( ~Y �Y �Y �Y �Y g �Y i _Z �Z � �Z R �[ B �[ !\ H 5\ _ ~\ k �\ a J] �] �] , �]
^ ! )^ ( K^ t^ � �^ @ H_ �_ ? �_ & �_ 8 ` A` [` s` B �` D �` 2 a & Ja ( qa � �a oc qc tc wc zc }c c �c �c �c �c �c �c ) �c
�c � �c � fd � �d �e �e �e �e # �e % f � *f � �g � bi j 5j Qj C jj �j
�j �j * �j k
k k -k ( Lk ; uk � �k 0 �l � �l � {m B 4n � wn Q Zo �o �o �o �o f �o Qq " cr ! �s h �s � t $ �t ' u ?u Ou fu �u ! �u 3 �u 1 �u v A :v ? |v B �v �v x y /z B ?{ ) �{ �{ �{ �{ �{ �{ | $ "| G| � `| 0 �| & .} ' U} * }} 9 �} �} �} ~ ~ %~ � 9~ �~ �~ r �~ R ( [ � < � ? � � +� 8� A� ' N� v� T �� �� � � � !� f 6� V �� - � ' "� B J� ' �� 0 �� $ � ' � ' 3� ' [� G �� - ˅ - �� ' '� 0 O� 2 �� 2 �� ' � * � $ 9� * ^� 0 �� - �� < � � %� 0 �� 0 � 6 � / I� 5 y� � �� � q� p 2� � �� { L� � ȏ �� B ϐ [ � P n� �� # ؑ 6 �� p 3� p �� � � - �� q ד � I� N є - � � N� � � ! �� !� 4� F A� �� �� �� ��
� ͘ q� �� � �� S� � `� � 9� R� h� . � = �� # � ) � 1 :� l� - �� . �� � �� � -� " B� e� {� �� �� �� ˝ � " � $� :� t M� ֞ & � � 4� = S� = �� / ϟ % �� %� B� U� i� ~� \ �� [ � K� m d� G ҡ < � W� A n� U �� ` � R g� �� գ , � � ! 7� ( Y� �� � �� , =� j� 6 }� # �� $ إ �� � &� D ;� D �� , Ŧ � " � 1 11 12 13 14 2 3 4 5 6 7 8 9 A value of -1 shows that there is no limit in place. ALLOCATED\_VM All CloudStack API requests are submitted in the form of a HTTP GET/POST with an associated command and any parameters. A request is composed of the following whether in HTTP or HTTPS: Be sure the Usage Server has been installed. This requires extra steps beyond just installing the CloudStack software. See Installing the Usage Server (Optional) in the Advanced Installation Guide. Because the special value 1440 has been used for usage.stats.job.aggregation.range, the Usage Server will ignore the data between midnight and 2 AM. That data will be included in the next day's run. CPU limits CPUs Click Apply. Click Global Settings. Click the Edit button |editbutton.png| Click the Edit button. |editbutton.png| CloudStack allows the configuration of limits on a domain basis. With a domain limit in place, all users still have their account limits. They are additionally limited, as a group, to not exceed the resource limits set on their domain. Domain limits aggregate the usage of all accounts in the domain as well as all the accounts in all the sub-domains of that domain. Limits set at the root domain level apply to the sum of resource usage by the accounts in all the domains and sub-domains below that root domain. CloudStack allows you to control resource usage based on the types of resources, such as CPU, RAM, Primary storage, and Secondary storage. A new set of resource types has been added to the existing pool of resources to support the new customization model—need-basis usage, such as large VM or small VM. The new resource types are now broadly classified as CPU, RAM, Primary storage, and Secondary storage. The root administrator is able to impose resource usage limit by the following resource types for Domain, Project, and Accounts. CloudStack provides several administrator control points for capping resource usage by users. Some of these limits are global configuration parameters. Others are applied at the ROOT domain and may be overridden on a per-account basis. Configuring the Usage Server Dates in the Usage Record Default Account Resource Limits Default data transfer rate in megabits per second allowed per user (supported on XenServer) Default: 00:15. Default: 1440 Default: GMT Default: The time zone of the management server. Definition Description Disk Volume Usage Record Format Edit the following as per your requirement: Example response from listUsageRecords For IP address usage the following fields exist in a usage record. For any resource type, if a domain has limit X, sub-domains or accounts under that domain can have there own limits. However, the sum of resource allocated to a sub-domain or accounts under the domain at any point of time should not exceed the value X. For disk volumes, the following fields exist in a usage record. For example, if a domain has the CPU limit of 40 and the sub-domain D1 and account A1 can have limits of 30 each, but at any point of time the resource allocated to D1 and A1 should not exceed the limit of 40. For example, suppose that your server is in GMT, your user population is predominantly in the East Coast of the United States, and you would like to process usage records every night at 2 AM local (EST) time. Choose these settings: For network usage (bytes sent/received), the following fields exist in a usage record. For network usage, the start date and end date again define the range in which the number of bytes transferred was calculated. If a user downloads 10 MB and uploads 1 MB in one day, there will be two records, one showing the 10 megabytes received and one showing the 1 megabyte sent. For running and allocated virtual machine usage, the following fields exist in a usage record: Globally Configured Limits IP Address Usage Record Format IP\_ADDRESS ISO If any operation needs to pass through two of more resource limit check, then the lower of 2 limits will be enforced, For example: if an account has the VM limit of 10 and CPU limit of 20, and a user under that account requests 5 VMs of 4 CPUs each. The user can deploy 5 more VMs because VM limit is 10. However, the user cannot deploy any more instances because the CPU limit has been exhausted. If the admin reduces the resource limit for an account and set it to less than the resources that are currently being consumed, the existing VMs/templates/volumes are not destroyed. Limits are imposed only if the user under that account tries to execute a new operation using any of these resources. For example, the existing behavior in the case of a VM are: If usage.stats.job.aggregation.range is also set, and its value is not 1440, then its value will be added to usage.stats.job.exec.time to get the time to run the Usage Server job again. This is repeated until 24 hours have elapsed, and the next day's processing begins again at usage.stats.job.exec.time. In Actions, click the Edit icon. In Search, type usage. Find the configuration parameter that controls the behavior you want to set. See the table below for a description of the available parameters. In a zone, the guest virtual network has a 24 bit CIDR by default. This limits the guest virtual network to 254 running instances. It can be adjusted as needed, but this must be done before any instances are created in the zone. For example, 10.1.1.0/22 would provide for ~1000 addresses. In the left navigation tree, click Accounts. In the left navigation tree, click Domains. Instance Limits LOAD\_BALANCER\_POLICY Limit Usage Considerations Limiting Resource Usage Limiting Resource Usage in a Domain Load Balancer Policy or Port Forwarding Rule Usage Record Format Log in to the CloudStack UI as administrator. Log in to the CloudStack UI. Maximum RAM that can be used for an account. Default is 40960. Maximum number of CPU cores that can be used for an account. Default is 40. Maximum primary storage space that can be used for an account. Default is 200. Maximum recurring daily snapshots to be retained for a volume. If the limit is reached, snapshots from the start of the day are deleted so that newer ones can be saved. This limit does not apply to manual snapshots. If set to 0, recurring daily snapshots can not be scheduled Maximum recurring hourly snapshots to be retained for a volume. If the limit is reached, early snapshots from the start of the hour are deleted so that newer ones can be saved. This limit does not apply to manual snapshots. If set to 0, recurring hourly snapshots can not be scheduled Maximum recurring monthly snapshots to be retained for a volume. If the limit is reached, snapshots from the beginning of the month are deleted so that newer ones can be saved. This limit does not apply to manual snapshots. If set to 0, recurring monthly snapshots can not be scheduled. Maximum recurring weekly snapshots to be retained for a volume. If the limit is reached, snapshots from the beginning of the week are deleted so that newer ones can be saved. This limit does not apply to manual snapshots. If set to 0, recurring weekly snapshots can not be scheduled Maximum secondary storage space that can be used for an account. Default is 400. Maximum size for a downloaded template or ISO in GB Maximum size for a volume in GB Memory (RAM) Memory limits (MB) NETWORK\_BYTES\_RECEIVED NETWORK\_BYTES\_SENT NETWORK\_OFFERING Network Offering Usage Record Format Network Usage Record Format Note: The start date is not the time a virtual machine was started, and the end date is not the time when a virtual machine was stopped. The start and end dates give the time range within which usage was calculated. Number of disk volumes that can exist for an account Number of public IP addresses that can be owned by an account Number of snapshots that can exist for an account Number of templates that can exist for an account Number of virtual machine instances that can exist for an account PORT\_FORWARDING\_RULE Parameter Name Parameter Name Description Primary Storage (Volumes) Primary Storage limits (GB) Primary or Secondary storage space refers to the stated size of the volume and not the physical size— the actual consumed size on disk in case of thin provisioning. Public IP Limits RUNNING\_VM Restart the Management Server (as usual with any global configuration change) and also the Usage Server: SNAPSHOT Secondary Storage (Snapshots, Templates, ISOs) Secondary Storage limits (GB) Select the account you want to modify. The current limits are displayed. Select the domain you want to modify. The current domain limits are displayed. Setting Usage Limits Snapshot Limits TEMPLATE Template Limits Template, ISO, and Snapshot Usage Record Format The Usage Server is an optional, separately-installed part of CloudStack that provides aggregated usage records which you can use to create billing integration for CloudStack. The Usage Server works by taking data from the events log and creating summary usage records that you can access using the listUsageRecords API call. The Usage Server runs at least once per day. It can be configured to run multiple times per day. The default is 20. The default is 200. The default is 40. The default is 400. The default is 40960. The domain administrators are allowed to list and change these resource limits only for the sub-domains and accounts under their own domain or the sub-domains. The end users will the privilege to list resource limits. Use the listResourceLimits API. The following table lists limits set in the Global Configuration: The following table shows all usage types. The following table shows the global configuration settings that control the behavior of the Usage Server. The number of CPU cores that can be used for a domain. The number of CPU cores that can be used for an account. The number of RAM that can be used for a domain. The number of RAM that can be used for an account. The number of VPCs that can be created in a domain. The number of VPCs that can be created in an account. The number of days between sanity checks. Set this in order to periodically search for records with erroneous data before issuing customer invoices. For example, this checks for VM usage records created after the VM was destroyed, and similar checks for templates, volumes, and so on. It also checks for usage times longer than the aggregation range. If any issue is found, the alert ALERT\_TYPE\_USAGE\_SANITY\_RESULT = 21 is sent. The number of disk volumes that can be created in a domain. The number of disk volumes that can be created in an account. The number of instances that can be used in a domain. The number of instances that can be used in an account. The number of public IP addresses that can be used in a domain. The number of public IP addresses that can be used in an account. The number of snapshots that can be created in a domain. The number of snapshots that can be created in an account. The number of templates that can be registered in a domain. The number of templates that can be registered in an account. The primary storage space that can be used for a domain. The primary storage space that can be used for an account. The root admin will have the privilege to list and update resource limits. The root administrator, domain administrators and users are able to list resources. Ensure that proper logs are maintained in the ``vmops.log`` and ``api.log`` files. The secondary storage space that can be used for a domain. The secondary storage space that can be used for an account. The time from when a VPN user is created until it is removed. The time from when a network offering was assigned to a VM until it is removed. The time period in minutes between Usage Server processing jobs. For example, if you set it to 1440, the Usage Server will run once per day. If you set it to 600, it will run every ten hours. In general, when a Usage Server job runs, it processes all events generated since usage was last run. The time when the Usage Server processing will start. It is specified in 24-hour format (HH:MM) in the time zone of the server, which should be GMT. For example, to start the Usage job at 10:30 GMT, enter “10:30”. The time zone of usage.stats.job.exec.time. Valid values for the time zone are specified in `Appendix A, *Time Zones* <http://docs.cloudstack.apache.org/en/latest/dev.html?highlight=time%20zones#time-zones>`_ The usage records show the amount of resources, such as VM run time or template storage space, consumed by guest instances. There is one case where the start date and end date do not correspond to midnight and 11:59:59pm when daily aggregation is used. This occurs only for network usage records. When the usage server has more than one day's worth of unprocessed data, the old data will be included in the aggregation period. The start date in the usage record will show the date and time of the earliest event. For other types of usage, such as IP addresses and VMs, the old unprocessed data is not included in daily aggregation. There is special handling for the case of 1440 (once per day). In this case the Usage Server does not necessarily process all records since Usage was last run. CloudStack assumes that you require processing once per day for the previous, complete day’s records. For example, if the current day is October 7, then it is assumed you would like to process records for October 6, from midnight to midnight. CloudStack assumes this “midnight to midnight” is relative to the usage.execution.timezone. Time zone of usage records. Set this if the usage records and daily job execution are in different time zones. For example, with the following settings, the usage job will run at PST 00:15 and generate usage records for the 24 hours from 00:00:00 GMT to 23:59:59 GMT: To configure the usage server: To control the behaviour of this feature, the following configuration parameters have been added: To modify global configuration parameters, use the global configuration screen in the CloudStack UI. See Setting Global Configuration Parameters To override a default limit for a particular account, set a per-account resource limit. To set a domain limit: Tracks the public IP address owned by the account. Tracks the time from when a port forwarding rule was created until the time it was removed. Tracks the total number of bytes received by all the VMs for an account. Cloud.com does not currently track network traffic per VM. Tracks the total number of bytes sent by all the VMs for an account. Cloud.com does not currently track network traffic per VM. Tracks the total running time of a VM per usage record period. If the VM is upgraded during the usage period, you will get a separate Usage Record for the new upgraded VM. Tracks the total time a disk volume has been created to the time when it has been destroyed. Tracks the total time a load balancer policy has been created to the time it has been removed. Cloud.com does not track whether a VM has been assigned to a policy. Tracks the total time a template (either created from a snapshot or uploaded to the cloud) has been created to the time it has been destroyed. The size of the template is also returned. Tracks the total time an ISO has been uploaded to the time it has been removed from the cloud. The size of the ISO is also returned. Tracks the total time from when a snapshot has been created to the time it have been destroyed. Tracks the total time the VM has been created to the time when it has been destroyed. This usage type is also useful in determining usage for specific templates such as Windows-based templates. Type ID Type Name Type the desired value and click the Save icon. Usage Record Format Usage Types Usage records include a start date and an end date. These dates define the period of time for which the raw usage number was calculated. If daily aggregation is used, the start date is midnight on the day in question and the end date is 23:59:59 on the day in question (with one exception; see below). A virtual machine could have been deployed at noon on that day, stopped at 6pm on that day, then started up again at 11pm. When usage is calculated on that day, there will be 7 hours of running VM usage (usage type 1) and 12 hours of allocated VM usage (usage type 2). If the same virtual machine runs for the entire next day, there will 24 hours of both running VM usage (type 1) and allocated VM usage (type 2). User Permission VOLUME VPC limits VPN User Usage Record Format VPN\_USERS Valid values for the time zone are specified in `Appendix A, *Time Zones* <http://docs.cloudstack.apache.org/en/latest/dev.html?highlight=time%20zones#time-zones>`_ Virtual Machine Usage Record Format Volume Limits With this configuration, the Usage job will run every night at 2 AM EST and will process records for the previous day’s midnight-midnight as defined by the EST (America/New\_York) time zone. Working with Usage You can limit resource use by accounts. The default limits are set by using Global configuration parameters, and they affect all accounts within a cloud. The relevant parameters are those beginning with max.account, for example: max.account.snapshots. account - name of the account account – name of the account accountid - ID of the account accountid – ID of the account description - A string describing what the usage record is tracking description – A string describing what the usage record is tracking domainid - ID of the domain in which this account resides domainid – ID of the domain in which this account resides enable.usage.server Whether the Usage Server is active. enable.usage.server = true iselastic - True if the IP address is elastic. issourcenat - Whether source NAT is enabled for the IP address max.account.cpus max.account.primary.storage (GB) max.account.public.ips max.account.ram (MB) max.account.secondary.storage (GB) max.account.snapshots max.account.templates max.account.user.vms max.account.volumes max.project.cpus max.project.primary.storage (GB) max.project.ram (MB) max.project.secondary.storage (GB) max.template.iso.size max.volume.size.gb migrateVirtualMachine: The users under that account will be able to migrate the running VM into any other host without facing any limit issue. name – The name of the virtual machine network.throttling.rate offeringid – Network offering ID offeringid – The ID of the disk offering offeringid – The ID of the service offering rawusage - A number representing the actual usage in hours rawusage – A number representing the actual usage in hours recoverVirtualMachine: Destroyed VMs cannot be recovered. size – Size of the template, ISO, or snapshot size – The amount of storage allocated snapshot.max.daily snapshot.max.hourly snapshot.max.monthly snapshot.max.weekly startdate, enddate - The range of time for which the usage is aggregated; see Dates in the Usage Record startdate, enddate – The range of time for which the usage is aggregated; see Dates in the Usage Record templateid – ROOT template ID templateid – The ID of the template or the ID of the parent template. The parent template value is present when the current template was created from a volume. templateid – – Included only for templates (usage type 7). Source template ID. type – Device type (domain router, external load balancer, etc.) type – Hypervisor usage - String representation of the usage, including the units of usage usage - String representation of the usage, including the units of usage (e.g. 'Hrs' for hours) usage – String representation of the usage, including the units of usage (e.g. 'Hrs' for VM running time) usage – String representation of the usage, including the units of usage (e.g. 'Hrs' for hours) usage.aggregation.timezone usage.execution.timezone usage.execution.timezone = America/New\_York usage.sanity.check.interval usage.stats.job.aggregation.range usage.stats.job.aggregation.range = 1440 usage.stats.job.exec.time usage.stats.job.exec.time = 07:00. This will run the Usage job at 2:00 AM EST. Note that this will shift by an hour as the East Coast of the U.S. enters and exits Daylight Savings Time. usageid - ID of the load balancer policy or port forwarding rule usageid - IP address ID usageid – Device ID (virtual router ID or external device ID) usageid – ID of the network offering usageid – The ID of the the template, ISO, or snapshot usageid – The volume ID usageid – VPN user ID usageid – Virtual machine usagetype - A number representing the usage type (see Usage Types) usagetype – A number representing the usage type (see Usage Types) virtualMachineId – The ID of the virtual machine zoneid - Zone where the usage occurred zoneid – Zone where the usage occurred Project-Id-Version: Apache CloudStack Administration RTD
Report-Msgid-Bugs-To:
POT-Creation-Date: 2014-06-30 12:52+0200
PO-Revision-Date: 2014-06-30 12:05+0000
Last-Translator: FULL NAME <EMAIL@ADDRESS>
Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Language: zh_CN
Plural-Forms: nplurals=1; plural=0;
1 11 12 13 14 2 3 4 5 6 7 8 9 值为-1表明此处没有任何限制。 ALLOCATED\_VM 所有CloudStack API请求都是以HTTP GET/POST形式提交, 同时附上相关的命令和参数. 无论是HTTP或HTTPS, 一个请求都有以下内容组成: 确定使用服务器已经被安装。它要求安装额外的CloudStack软件步骤。参见高级安装手册中的使用服务器（可选）。 由于在usage.stats.job.aggregation.range中使用特殊值1440，用量服务器将忽略午夜到凌晨2：00之间的数据。这些数据将会包含在第二天的统计中。 CPU限制 CPUs 点击应用 单击全局设置 单击编辑按钮 |editbutton.png| 单击编辑按钮。|editbutton.png| CloudStack允许在一个域基础上配置限制。使用域限制的地点是所有的用户都有其账户的的限制。它们有额外的限制，例如群组，不能执行设置在它们域上的资源限制。域限制聚集了任何域中使用的账户和任何账户的所有域的子域。限制设定在根域层次应用于所有域的账户和子域使用的资源综合都低于根域的限制。 CloudStack允许根据资源类型控制资源使用，例如CPU,RAM,主存储，辅助存储。一个新的资源类型集已经被添加到了已经存在的支持新通俗模型的资源池-基于需要使用，例如大型VM或者小型VM.新的资源类型被广泛分类在如CPU,RAM,主存储和辅助存储中。超级管理员能够利用下列资源的使用限制，例如域，项目或者账户。 CloudStack提供多个管理员控制点以便控制用户资源使用。其中一些限制是全局配置参数。其他一些应用在root域，并且会覆盖每个账号的基本配置 配置使用服务器 在使用记录中的数据 默认账户资源限制 默认的传输速率是允许用户按照Mb每秒(支持XenServer) 默认：00:15。 默认：1440 默认：GMT 默认时区是管理服务器的时区。 定义 描述 磁盘用量记录格式 编辑下列每一条要求： listUsageRecords指令的反应示例： 对于IP地址使用下列字段存在于使用记录中。 对于更多资源类型，如果一个域存在限制X，这个域的子域或者账户也能也有它们自身的限制。尽管如此，一个子域允许分配的资源总和或者域中账户在任何时间点都不能执行X限制。 对于磁盘，用量记录存在下列字段。 例如，当一个域有CPU的限制数量为40，其子域D1和账户A1可以有每个30的限制，但是任何时候分配给D1和A1的资源都不能超过限制40. 比如,假设你服务器时区是GMT，你的用户主要在美国东海岸，而你有打算在当地时间（EST）每天凌晨两点执行使用记录统计。选择这些选项： 网络用量(发送/接收字节数)记录中存在以下字段： 对于网络用量，开始日期和结束日期定义为一定数量的比特传输统计的时间范围。如果用户一天内下载10MB并上传1M，将会有两个记录，一个显示10MB接受和一个显示1MB发送。 对运行或者已分配虚拟机使用，下列字段存在于使用记录中： 全局配置限制 IP地址使用记录格式 IP\_ADDRESS ISO 如果一些操作需要通过两个或更多的资源限制核查，最少的两个限制将被执行，例如：如果一个账户有10个限制VM和20个限制CPU,用户在账户中申请每4个CPU5个VM。用户可以部署5个或更多的VM,因为VM的限制个数是10。尽管如此，用户不能部署任何实例，因为CPU的限制已经用尽。 如果管理员为账户减少资源限制，并设置少于目前设定的资源数，已经存在的VM/模板/卷也不会破坏。限制仅在账户中的用户试图使用这些资源执行新的操作时表现出来。例如，在一个VM中倘若存在下列行为： 如果同时设置了usage.stats.job.aggregation.range参数，并且该参数值不是1440，这个值将被添加到usage.stats.job.exec.time到时再次运行使用服务器任务。重复此过程,直到24小时已经过去,第二天到达 usage.stats.job.exec.time处理任务开始。 在操作栏点击编辑图标。 在搜索栏输入 usage。找到no需要改变的配置参数。下表是这些参数的详细描述。 在一个域中，客户虚拟网络默认有24位CIDR.它限制了客户网络运行上线是254个实例。它可以根据需求调节，但必须在域中实例创建之前。例如，10.1.1.0/22 将提供 ~1000 地址。 在导航树左侧，单击账户。 在导航栏左侧树中，单击域。 实例限制： LOAD\_BALANCER\_POLICY 限制使用注意事项： 限制资源使用 在一个域中限制资源使用 负载均衡策略或端口导向用量记录格式 作为管理员登录到CloudStack用户界面。 登录到CloudStack的界面 最大的可以被账户使用的RMA容量。默认值是40960。 最大的可以被账户使用的CPU核心个数。默认是40. 最大的可以被账户使用的主存储个数。默认是200。 最大的可再现时时性快照可以保存在卷中。如果数量的限制达到，早期的来自开始阶段的快照就会被删除以使新的快照可以被存储。这种限制方法不支持手工快照。若设为0，可再现性时时快照将没有保存。 最大的可再现时时性快照可以保存在卷中。如果数量的限制达到，早期的来自开始阶段的快照就会被删除以使新的快照可以被存储。这种限制方法不支持手工快照。若设为0，可再现性时时快照将没有保存。 最大的可再现时时性快照可以保存在卷中。如果数量的限制达到，早期的来自开始阶段的快照就会被删除以使新的快照可以被存储。这种限制方法不支持手工快照。若设为0，可再现性时时快照将没有保存。 最大的可再现时时性快照可以保存在卷中。如果数量的限制达到，早期的来自开始阶段的快照就会被删除以使新的快照可以被存储。这种限制方法不支持手工快照。若设为0，可再现性时时快照将没有保存。 最大的可被账户使用的辅助存储空间。默认是400。 下载的模板或ISO最大的单位是GB 卷的最大单位是GB Memory (RAM) 内存限制(MB) NETWORK\_BYTES\_RECEIVED NETWORK\_BYTES\_SENT NETWORK\_OFFERING 网络服务方案用量记录格式 网络用量记录格式 注意：开始日期不是虚拟机启动时间，结束日期不是虚拟机停止时间。开始日期和结束日期在用量统计的给定范围内。 磁盘卷的数量也可能存于一个记述中 账户可拥有的公用IP地址个数 快照的数量存在于一个记述中 模板的数量可能存于一个记述中 虚拟机实例的数量也可能存在于一个记述中 PORT\_FORWARDING\_RULE 参数名称 参数名描述 主存储(卷) 主存储限制(GB) 主存储或者辅助存储空间参考启动的容器大小而不是物理容量，实际使用的物理空间要小于提供的空间。 公共IP限制 RUNNING\_VM 重新启动管理服务器（通常在改变了全局配置之后都要进行这步）并重启使用服务器。 SNAPSHOT 辅助存储（快照，模板，ISOs） 辅助存储限制(GB) 选择你想修改的账户。当前限制将显示出来。 选择你想修改的域。当前域限制将被显示出来。 设置使用限制 快照限制 TEMPLATE 模板限制 模版、ISO和快照用量记录格式 使用服务器是CloudStack一个可选项,分别安装产品的一部分,提供了聚合使用记录您可以使用它来创建计费集成产品。使用服务器通过使用数据从事件日志和创建汇总使用记录,您可以访问使用listUsageRecords API调用。 使用服务器运行至少每天一次。它可以被配置为每天多次运行。 默认是20个。 默认是200。 默认是40。 默认是400。 默认值是40960。 域管理员仅允许列出和改变在其拥有的域或者子域的子域和账户的资源限制。 终端用户拥有改变列出资源限制的特权。使用listResourceLimits API.。 下表列出了设置全局配置的限制： 下表显示了所有的用量类型。 下表列出了全局配置中控制使用服务器的配置项。 可以在域中使用的CPU核心数。 在账户中可以使用的CPU内核的个数。 可以在域中使用的RAM数量。 在账户中可以使用的RAM数量。 可以被创建在域中的VPC的个数 在账户中可以创建的VPC数量。 完整性检查时间间隔。设置此值来定期在生成用户账单之前检查出错误的数据。比如，他能检查虚拟机被销毁之后的使用记录和模板，卷等的类似记录。还会检查超过聚合时间的使用时间。如果发生了错误就会发送ALERT_TYPE_USAGE_SANITY_RESULT = 21 警告。 可以被创建在雨中的磁盘卷的个数 在账户中可以创建的磁盘卷个数。 可以被用在域中的实例的个数 在一个账户中可以适用的实例个数。 可以被用在域中的公共IP地址的个数。 在账户中可以使用的公共IP地址个数。 可以被创建在域中的快照个数 在账户中可以创建的快照数量。 可以在域中注册的模板数量 在账户中可以注册的模板数量。 在域中可以使用的主存储空间大小。 在账户中可以使用的主存储空间。 超级管理员将有列出和升级资源限制的特权。 超级管理员，域管理员和用户能够列出资源。确保合适的属性日至保存在 ``vmops.log`` 和 ``api.log``文件中。 在域中可使用的辅助存储空间大小。 在账户中可以使用的辅助存储空间。 计时从VPN用户创建时开始，移除时结束。 从网络方案分配到VM到移除的时间。 使用服务器执行任务时间间隔（分钟为单位）。比如，如果你将此值设为1440，使用服务器将每天执行一次。如果你将此值设为600，则会10小时执行一次。一般情况下使用服务器执行任务时会继续在上次的使用统计基础上处理所有事件。 使用服务器处理任务的启动时间。采用24小时格式 （HH:MM），时区为服务器的时区，应该为GMT。比如要在GMT时区10:30 启动用量任务，请输入“10:30” 域时间项usage.stats.job.exec.time。时间域的有效值被具体化在`Appendix A, *Time Zones* <http://docs.cloudstack.apache.org/en/latest/dev.html?highlight=time%20zones#time-zones>`_ 使用记录显示数量的资源,比如虚拟机运行时间或模板存储空间，以被客人消耗为例。 当每日统计使用时，只有一种情况开始日期和结束日期不响应午夜到11:59:59。它仅发生在网络用量记录。当用量记录服务器有超过一天的未处理数据时，旧数据将被包含在统计区间内。用量记录中的开始日期将显示最早的事件的日期和时间。对于其它类型的用量，例如IP地址和VM,旧的未处理数据是不包含在每日统计中的。 当值为1440（一天一次）时有点特殊。该情况下，用量服务器并不需要处理上次运行之后的所有事件。&PRODUCT;假定您要一天一次处理昨天的，完成每日记录。例如，如果今天是10月7号，会假定您要处理6号的记录，从0点到24点。CloudStack假定的0点到24点采用的时区为 usage.execution.timezone的值。 记录使用信息所用的时区。如果使用记录和日程工作执行在不同的时区时进行设置。例如，进行下列设置，使用任务运行在PST 00:15和24小时内产生的从00:00:00GMT到23:59:59GMT的使用记录： 配置使用服务器 为了控制该特征的行为，以下配置参数已经添加： 使用CloudStack中的用户界面中的全局配置界面可以修改全局配置参数。 对于覆盖一个默认限制的特殊账户，设置per-account资源限制。 设定一个域限制： 追踪拥有公共IP地址的账户 追踪端口导向规则从创建到移除的时间。 追踪一个账户接受所有VM的比特的总时间。Cloud.com不仅追踪当前网络传输时的每个VM。 追踪一个账户发送所有VM的比特的总时间。Cloud.com不仅追踪当前网络传输时的每个VM。 追踪VM每个用量记录时期所有运行时间总和。如果VM在用量时期升级，你将会获得新升级后的VM单独的用量记录。 追踪磁盘从创建到销毁的总时间。 追踪负载均衡策略从创建到移除的总时间。Cloud.com不追踪VM是否已经分配到了的策略。 追踪模板（包含从快照中创建的或是已经上传到云的）从创建到销毁的总时间。模板的大小也被返回。 追踪ISO在云中从上传到移除的总时间。ISO的大小也被返回。 追踪快照从创建到销毁的总时间。 追踪VM从创建到销毁的所有时间总和。这个用量类型也是在终止例如 Windows-based模板这样的具体模板用量上是有用的。 类型ID 类型名称 输入数值点击保存图标。 使用记录格式 用量类型 用量记录包含了开始日期和结束日期。这些日期定义了原始用量数字的统计时间阶段。如果每天统计被使用，开始日期是问题出现的的当天午夜，结束日期是问题(关于异常，参见本内容）出现的当天23:59:59。虚拟机可以被部署到当天正午，在次日6pm,然后在11pm重启。在用量统计的当天，将有7小时运行VM用量(用量类型1)和12个小时分配VM用量(用量类型2)。如果同一个VM完全运行到下一天，将会有24小时的运行VM用量(类型1)和已分配用量(类型2)。 用户许可 VOLUME VPC限制 VPN用户用量记录格式 VPN\_USERS 时间域的有效值已经被具体化到 `Appendix A, *Time Zones* 中 <http://docs.cloudstack.apache.org/en/latest/dev.html?highlight=time%20zones#time-zones>`_ 虚拟机使用记录格式 卷限制 在这种配置下，使用任务 会在东部时间每天2 AM执行，同时会如定义的一样以东部时间(美国纽约时间)统计前一天的“午夜到午夜使用记录。” 使用服务 你可以限制账户使用的资源。默认限制通过全局配置参数设置，它们影响在云中的所有账户。其相关参数开始于max.account,例如:max.account.snapshots。 account - 账户的名称 account--账户的名字 accountid-账户的ID accountid--账户的ID description – 字符描述追查用量记录 description – 字符描述，用于追查使用量的记录 domainid-本账户具有的鱼的ID domainid --在此账户存在的域的 ID enable.usage.server是否开启使用服务器。 enable.usage.server = true iselastic - 如果IP地址是弹性的为True issourcenat - IP地址的NAT资源是否有效 max.account.cpus max.account.primary.storage (GB) max.account.public.ips max.account.ram (MB) max.account.secondary.storage (GB) max.account.snapshots max.account.templates max.account.user.vms max.account.volumes max.project.cpus max.project.primary.storage (GB) max.project.ram (MB) max.project.secondary.storage (GB) max.template.iso.size max.volume.size.gb 迁移虚拟机：在账户中的用户试图迁移一个正在运行的VM到任何不面临限制问题的主机。 name - 虚机名称 network.throttling.rate offeringid – 网络服务方案的ID offeringid - 磁盘方案的ID offeringid - 计算方案的ID rawusage – 代表以小时为单位实时使用量的数字 rawusage – 代表以小时为单位实时使用量的数字 恢复虚拟机：破坏的VM不能被修复。 size - 模版、ISO或快照的大小 size - 分配的存储大小 snapshot.max.daily snapshot.max.hourly snapshot.max.monthly snapshot.max.weekly startdate, enddate – 一定时间范围内的用量总和; 参见 用量记录中的日期 startdate, enddate –一定时间内的使用量总和; 参见 使用量记录中的日期 templateid - 根模版ID templateid – 模版或父模版的ID。当模版是从磁盘卷创建时，此处会使用父模版的ID。 templateid -- 仅模版（用量类型为7）时包括。源模版ID。 type - 设备类型(虚拟路由器、外部负载均衡等) type - 虚拟化平台 usage – 代表使用量的字符串，包括使用量的单位 usage – 代表使用量的字符串，包括使用量的单位 (如 'Hrs'是小时) usage – 代表使用量的文字，包括使用量的单位(如 'Hrs'代表虚机运行时间) usage – 代表使用量的文字，包括使用量的单位 (如 'Hrs'是小时) usage.aggregation.timezone usage.execution.timezone usage.execution.timezone = America/New\_York usage.sanity.check.interval usage.stats.job.aggregation.range usage.stats.job.aggregation.range = 1440 usage.stats.job.exec.time usage.stats.job.exec.time = 07:00。这将会在东部时间2：00执行使用任务。注意考虑进出白昼保存时间在将时间迁移大U.S.东海岸。 usageid -负载均衡或端口导向规则ID usageid-IP地址ID usageid - 设备ID(虚拟路由器ID或外部设备ID) usageid – 网络服务方案的ID usageid - 模版、ISO或快照的ID usageid - 磁盘ID usageid - VPN用户ID usageid -- 虚拟机 usagetype – 代表使用量类型的数字 (参见使用量类型) usagetype – 代表使用量类型的数字 (参见使用量类型) virtualMachineId – 虚拟服务器的ID号 zoneid-已经使用的域ID zoneid – 使用资源域的ID号