WO2021258719A1 - 容器平台计费方法及系统 - Google Patents

容器平台计费方法及系统 Download PDF

Info

Publication number
WO2021258719A1
WO2021258719A1 PCT/CN2021/070294 CN2021070294W WO2021258719A1 WO 2021258719 A1 WO2021258719 A1 WO 2021258719A1 CN 2021070294 W CN2021070294 W CN 2021070294W WO 2021258719 A1 WO2021258719 A1 WO 2021258719A1
Authority
WO
WIPO (PCT)
Prior art keywords
container
charged
data
cluster
charging
Prior art date
Application number
PCT/CN2021/070294
Other languages
English (en)
French (fr)
Inventor
谢海琴
王海涛
刘安
李东会
Original Assignee
海尔数字科技（上海）有限公司
青岛海尔工业智能研究院有限公司
海尔数字科技(青岛)有限公司
海尔卡奥斯物联生态科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 海尔数字科技（上海）有限公司, 青岛海尔工业智能研究院有限公司, 海尔数字科技(青岛)有限公司, 海尔卡奥斯物联生态科技有限公司 filed Critical 海尔数字科技（上海）有限公司
Publication of WO2021258719A1 publication Critical patent/WO2021258719A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/141—Indication of costs
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 

Definitions

  • the embodiments of the present application relate to the technical field of container platforms, for example, to a charging method and system for a container platform.
  • the container platform is the core application of the cloud computing platform. It provides a rich application programming interface (API) for upper-level applications, and provides network API services to the outside in the form of an open platform. With the help of the container platform, users do not need to think too much about the underlying hardware, and can more easily build application-time services.
  • API application programming interface
  • Tenants may need to use multiple container clusters to develop a project on the container platform.
  • the billing method in related technologies cannot perform compatible data collection and billing for multiple container clusters in the container platform. Only one container can be charged. Each container in the cluster performs corresponding data collection and billing. Therefore, how to charge multiple container clusters in the container platform at the same time has become an urgent problem to be solved.
  • the embodiments of the present application provide a method and system for charging a container platform, so as to realize multi-cluster data collection, charging, and fee display for compatibility with multiple container clusters in the container platform.
  • an embodiment of the present application provides a charging method for a container platform, including:
  • the cost data of each container cluster to be charged is sent to the front-end system for display through the external interface.
  • an embodiment of the present application also provides a charging system for a container platform, including: a determination module, a preset number of data collectors in the form of plug-ins, a data processing module, and an external interface;
  • the determining module is configured to determine a preset number of container clusters to be charged in the container platform
  • the data collector is configured to obtain the native interface provided by the management node of the target to-be-billed container cluster, and to interface with the native interface, and collect the billing information of the target to-be-billed container cluster through the native interface;
  • a data processing module configured to perform charging processing on the collected charging information of each of the container clusters to be charged to obtain the cost data of each of the container clusters to be charged;
  • the external interface is configured to send the cost data of each container cluster to be charged to the front-end system for display.
  • FIG. 1 is a flowchart of a method for charging a container platform in Embodiment 1 of the present application
  • FIG. 2 is a flowchart of a method for charging a container platform in the second embodiment of the present application
  • FIG. 3 is a flowchart of a method for charging a container platform in the third embodiment of the present application.
  • Fig. 4 is a schematic structural diagram of a charging system for a container platform in the fourth embodiment of the present application.
  • Fig. 1 is a flowchart of a method for charging a container platform in the first embodiment of the present application. This embodiment is applicable to the case of performing multi-cluster data collection and charging for multiple container clusters at the same time. This method can be used by the container
  • the platform's billing system can be implemented, which can include the following steps:
  • Step 110 Determine a preset number of container clusters to be charged in the container platform.
  • the container cluster includes multiple containers.
  • the container generally refers to the Docker container. Any application and all its dependencies can be packaged into a file and placed in a portable container, and then published to any container engine installed On the server, perform application deployment.
  • the container cluster to be billed includes container clusters rented by tenants to deploy applications and occupy platform resources.
  • the preset number represents the number of container clusters rented by a tenant in the container platform.
  • the container platform includes a multi-cluster version of the PaaS platform.
  • the container platform may be a PaaS platform including multiple container clusters, where the PaaS platform may provide an application development and operating environment.
  • the container platform charges tenants based on the amount of resources used, in the multi-container cluster multi-tenant mode, it is necessary to collect billing information for multiple container clusters to be billed leased by each tenant at the same time , In order to calculate the tenant's cost data in real time.
  • Step 120 Obtain the native interfaces provided by the management node of each container cluster to be charged, which are data collectors in the form of connectors for each native interface, and collect charging information for each container cluster to be charged through the data collector.
  • the container cluster includes a management node and a plurality of working nodes.
  • the management node is the management control center of the container cluster and can maintain and manage each working node in the cluster.
  • the working node is a container for running business applications. In order to obtain the number of resources used by each container cluster to be billed, you can first obtain the native interface provided by the management node of each container cluster to be billed, and then connect a data collector to each native interface, so that each data collector can be connected through the docking The native interface of the to-be-charging container cluster collects charging information.
  • the data collector in order to be able to flexibly select container clusters in the container platform for data collection, the data collector is set in the form of a plug-in, so that the data collector has a pluggable feature.
  • the data collector By inserting the data collector into the management node of the container cluster to be charged, the data collector can be used to collect the charging information of the container cluster to be charged.
  • collecting billing information for each container cluster to be billed through the data collector may include: real-time access from the management node through the native interface of the management node of the target container cluster to be billed that is docked with the current data collector Obtain the service operation record fed back by each working node in the target container cluster to be charged; use the operation record of the target service with operation update as the charging information of the target container cluster to be charged.
  • the service in the application is used as the granularity to collect billing information on the container cluster.
  • the real-time service operation records reported by each worker node stored in the management node can be obtained in real time, and the target service with operation update can be selected from it.
  • the operation records corresponding to each target service are used as the billing information of the target container cluster to be billed.
  • Claim PVC persistently stores the charging information in the database.
  • the native interface provided by the management node of the container cluster to be charged includes a Kubernetes interface.
  • the Kubernetes interface provided by the management node of the cluster is the only operation entry to obtain the resource usage of the container cluster. Therefore, by monitoring the Kubernetes interface of the management node, the resources of each container in the container cluster to be charged can be obtained in real time. Use variation.
  • Step 130 Perform charging processing on the collected charging information of each container cluster to be charged, and obtain the cost data of each container cluster to be charged.
  • the collected billing information of each container cluster to be billed statistics are made on the resource usage of each container cluster to be billed, for example, the usage of resources such as CPU, memory, and disk is counted, and According to the charging strategy of the container platform, the detailed cost data of each container cluster to be charged and the total cost data that tenants need to pay are calculated.
  • the obtained expense data is persistently stored in the database as an expense bill provided to the outside world.
  • each container cluster to be charged corresponds to a charging policy
  • each container cluster to be charged of the same tenant may correspond to the same charging policy or different charging policies.
  • Step 140 Send the cost data of each container cluster to be charged to the front-end system for display through the external interface.
  • the relevant cost data of each container cluster to be charged can be obtained from the database through the external interface, and sent to the front-end system for display.
  • the front-end system can be a portal website.
  • the external interface is a Restful interface.
  • the HyperText Transfer Protocol can be followed, and the cost data in the JSON format can be provided to the outside through the Restful interface.
  • the Restful interface can realize the separation of front and back ends, that is, the back end processes the data and transmits it in JSON format. After the front end receives the data, it is only responsible for displaying and rendering the data, and does not do any other processing on the data.
  • the technical solution of the embodiment of the present application is to determine a preset number of container clusters to be billed in the container platform; obtain the native interfaces provided by the management nodes of each container cluster to be billed, and collect data in the form of connectors for each native interface.
  • the external interface sends the cost data of each container cluster to be billed to the front-end system for display, which solves the problem that the related technology can only perform corresponding data collection and billing for each container in a container cluster, and realizes the container platform Multi-cluster data collection, billing, and fee display for compatible multi-cluster data collection in multiple container clusters.
  • FIG. 2 is a flowchart of a method for charging a container platform in the second embodiment of the present application. This embodiment is modified on the basis of the above-mentioned embodiment to provide charging information for collected container clusters to be charged.
  • Step 210 Determine a preset number of container clusters to be charged in the container platform.
  • Step 220 Obtain the native interfaces provided by the management node of each container cluster to be charged, which are data collectors in the form of connectors for each native interface, and collect charging information for each container cluster to be charged through the data collector.
  • Step 230 Taking the unit charging time as the timing length, periodically classify the charging information of the current container cluster to be charged within the current unit charging time, so as to convert the underlying basic data in the charging information into business data.
  • the unit charging time is the charging interval, which is a minute-level time length, which can be 5 minutes, 8 minutes, or other time lengths.
  • the current unprocessed billing information of the current container cluster to be billed is classified for every unit of charging time, so as to classify the currently unprocessed billing
  • the underlying basic data in the information is converted into business data that meets the requirements, such as CPU usage, memory usage, and disk usage, so as to facilitate subsequent statistics on the number of billable resources of the container cluster.
  • the burst processing of charging information can be optimized, and it can be ensured that the data delay time for displaying the charging data is less than the unit charging time. For example, if the charging information processing cycle is performed every 5 minutes, there is a data delay of less than 5 minutes in the display of the charging data.
  • Step 240 Count the number of charging resources used by the current container cluster to be charged in the current unit charging time according to the service data, and calculate the cost increment data corresponding to the number of charging resources according to the charging strategy.
  • the business data obtained is counted, and the number of charging resources used by the current container cluster to be charged in the charging interval is determined, and then according to the current container cluster to be charged
  • the corresponding charging strategy calculates the cost incremental data corresponding to the number of charging resources, that is, the cost data of the consumption of the current container cluster to be charged in the current unit charging time.
  • the incremental cost data helps tenants understand the running status of applications or services in the current container cluster to be charged.
  • Step 250 Sum the incremental cost data and the historical cost data of the current container cluster to be charged to obtain the cost data of the current container cluster to be charged.
  • the tenant since the tenant finally needs to pay for the total data consumed by the current container cluster to be billed, each time the incremental data of the current unit charging time of the current container cluster to be billed is calculated, it is necessary to store The current incremental cost data is used as the detailed cost data in the cost bill, and the current incremental cost data and the historical cost data are accumulated to obtain the total cost data accumulated by the current container cluster to be charged to the current moment.
  • the cost data of the container cluster to be billed may further include: paying for the cost data of the container cluster to be billed through the H-Base1 interface.
  • the H-Base1 interface may be provided to the tenants, through the H-Base1 interface, the fees of the container cluster to be charged are paid, and the charging records are persistently stored in the database.
  • Step 260 Send the cost data of each container cluster to be charged to the front-end system for display through the external interface.
  • the relevant cost data of each container cluster to be charged can be obtained from the database through the external interface, for example, charging information, cost bills, and charging records, and the relevant cost data can be sent to the front-end docked with the external interface The system displays.
  • the method may further include: configuring a corresponding external interface for each container cluster to be billed, and connecting each to the external Interfaces are respectively mounted to the front-end system in the container platform in the form of plug-ins.
  • each container cluster to be billed is configured with a one-to-one corresponding external interface, for example, a Restful interface, and each The external interfaces are respectively mounted to different front-end systems in the form of front-end plug-ins.
  • sending the cost data of each container cluster to be billed to the front-end system for display through an external interface may include: through the target external interface corresponding to the target container cluster to be billed, the cost of the target container cluster to be billed The data is sent to the front-end system mounted on the target's external interface for display.
  • the target Restful interface corresponding to the target container cluster to be billed is first obtained, and through the target Restful interface, the target container cluster to be billed
  • the charging information, cost bills, and charging records are sent to the front-end system mounted on the target Restful interface, for example, displayed on the front-end portal website.
  • the technical solution of the embodiment of the present application is to determine a preset number of container clusters to be billed in the container platform; obtain the native interfaces provided by the management nodes of each container cluster to be billed, and collect data in the form of connectors for each native interface.
  • the external interface sends the cost data of each container cluster to be billed to the front-end system for display, which solves the problem that the related technology can only perform corresponding data collection and billing for each container in a container cluster, and realizes the container platform Multi-cluster data collection, billing, and fee display for compatible multi-cluster data collection in multiple container clusters.
  • FIG. 3 is a flowchart of a method for charging a container platform in the third embodiment of the present application. This embodiment can be combined with the various optional solutions in the foregoing embodiments. In an embodiment, referring to FIG. 3, the method may include the following steps:
  • Step 310 Perform multi-cluster data collection on a preset number of container clusters to be billed in the PaaS platform through a data collector in the form of a plug-in, to obtain billing information of each container cluster to be billed.
  • the PaaS platform is a multi-cluster version of the container platform.
  • the Kubernetes interface provided by the management node of each container cluster to be billed is connected to a data collector, so that the data collector can be connected through the docking
  • the Kubernetes interface of Kubernetes monitors the service operation records of each worker node stored in the management node in real time, and obtains the operation records with service status changes as billing information, for example, records of operations such as deployment, modification, deletion, and stopping of the service, Monitoring indicators include CPU, memory, and disk usage.
  • the charging information collected by the data collector is unprocessed basic data.
  • the billing system separates the data collector and integrates it into the Web project in the form of a service, abolishes the scanning data collection method, and configures a data collector for each container cluster to be billed in the PaaS platform.
  • Step 320 Perform charging processing on the charging information of each container cluster to be charged at regular intervals, and perform persistent storage on the obtained cost data of each container cluster to be charged.
  • the timed task is set in the unit charging time, and the charging information of each container cluster to be charged stored in the database is regularly charged.
  • the charging processing is divided into two aspects. One is that due to the underlying basic data There is a big difference from business data. First, classify the underlying basic data in the billing information to become business data that meets the requirements; second, perform statistics on the business data to determine that the current container cluster to be billed is charged by the unit. The number of billing resources used within the time is calculated according to the billing strategy and the expense data corresponding to the number of billing resources is calculated, and the expense data is persistently stored in the database, which is used as external data and also as the charging history.
  • the hourly minimum billing unit is abolished, and the unit billing time is modified to the minute level to optimize the burst processing of billing information and ensure that the data delay time for displaying billing data is less than the unit billing time. For example, if the charging information processing cycle is performed every 5 minutes, there is a data delay of less than 5 minutes in the display of the charging data.
  • the application status changes in each container cluster to be charged are collected and recorded in real time through the interface, and then the changes in the number of resources used by the cluster are determined based on the collected information, and the cost calculation of the container cluster is adjusted in real time according to the number of resources used to generate new Cost data.
  • Step 330 Send the cost data of each container cluster to be charged to the corresponding front-end system through the Restful interface in the form of a plug-in.
  • the purpose of persistent storage of charging information and cost data is to provide data services to the outside world, so that the cost data of each cluster of containers to be charged can be displayed in different front-end systems, respectively, for each container to be charged.
  • the cluster is configured with the corresponding Restful interface, and each Restful interface is directly mounted in the form of a plug-in to the front-end dashboard of the PaaS platform.
  • the docking deduction module can directly call the billing interface to obtain the application based on the API. Cost information.
  • the H-Base1 interface may be provided to the tenants, through the H-Base1 interface, the fees of the container cluster to be charged are paid, and the charging records are persistently stored in the database.
  • Step 340 Display the received cost data of the container cluster to be charged through the front-end system.
  • the Restful interface will be inserted into the front-end portal in the form of a front-end plug-in, and the charging information, fee bills, and charging records of the container cluster will be aggregated to the portal for selective display and display.
  • the data includes at least three parts: total cost data, detailed cost data, and disk billing status.
  • FIG. 4 is a schematic structural diagram of a charging system for a container platform in Embodiment 4 of the present application. This embodiment is applicable to the case of concurrent scheduling of tasks.
  • the system includes: a determining module 410, a preset number of data collectors 420 in the form of plug-ins, a data processing module 430, and an external interface 440;
  • the determining module 410 is configured to determine a preset number of container clusters to be charged in the container platform;
  • the data collector 420 is configured to obtain the native interface provided by the management node of the target container cluster to be billed, and to interface with the native interface, and collect billing information on the target container cluster to be billed through the native interface;
  • the data processing module 430 is configured to perform charging processing on the collected charging information of each container cluster to be charged to obtain the cost data of each container cluster to be charged;
  • the external interface 440 is configured to send the cost data of each container cluster to be charged to the front-end system for display.
  • the data collector 420 may be configured to: obtain each target container cluster in the target to-be-billed container cluster from the management node in real time through the native interface of the management node of the target to-be-billed container cluster docked with the current data collector.
  • the service operation record fed back by the working node; the operation record of the target service with operation update is used as the charging information of the target container cluster to be charged.
  • the data processing module 430 may be configured to: take the unit charging time as the timing length, and periodically classify the charging information of the current container cluster to be charged within the current unit charging time, so as to classify the charging information
  • the underlying basic data in is converted into business data; According to the business data, count the number of billing resources used by the current container cluster to be billed in the current unit charging time, and calculate the cost incremental data corresponding to the number of billing resources according to the billing strategy; The cost incremental data and the historical cost data of the current container cluster to be charged are summed to obtain the cost data of the current container cluster to be charged.
  • a payment module configured to pay for the cost data of the container cluster to be billed through the H-Base1 interface after obtaining the cost data of the container cluster to be billed.
  • a mounting module configured to configure corresponding external interfaces for each container cluster to be charged before sending the cost data of each container cluster to be charged to the front-end system for display through the external interface, and Mount each external interface to the front-end system of the container platform in the form of plug-ins.
  • the external interface 440 can be configured to send the cost data of the target container cluster to be charged to the front-end system mounted on the target external interface for display through the target external interface corresponding to the target container cluster to be charged.
  • the native interface provided by the management node of the container cluster to be charged includes a Kubernetes interface.
  • the external interface is a Restful interface.
  • the container platform includes a multi-cluster version of the PaaS platform.
  • the technical solution of the embodiment of the present application is to determine a preset number of container clusters to be billed in the container platform; obtain the native interfaces provided by the management nodes of each container cluster to be billed, and collect data in the form of connectors for each native interface.
  • the external interface sends the cost data of each container cluster to be billed to the front-end system for display, which solves the problem that the related technology can only perform corresponding data collection and billing for each container in a container cluster, and realizes the container platform Multi-cluster data collection, billing, and fee display for compatible multi-cluster data collection in multiple container clusters.
  • the technical solution of the embodiment of the present application is to determine a preset number of container clusters to be billed in the container platform; obtain the native interfaces provided by the management nodes of each container cluster to be billed, and collect data in the form of connectors for each native interface.
  • the external interface sends the cost data of each container cluster to be billed to the front-end system for display, which solves the problem that the related technology can only perform corresponding data collection and billing for each container in a container cluster, and realizes the container platform Multi-cluster data collection, billing, and fee display for compatible multi-cluster data collection in multiple container clusters.

Abstract

本申请公开了一种容器平台的计费方法及系统。该方法包括：在容器平台中确定预设数量的待计费容器集群；获取每个待计费容器集群的管理节点提供的原生接口，分别为每个所述原生接口对接插件形式的数据采集器，并通过所述数据采集器对每个待计费容器集群进行计费信息采集；对采集的每个待计费容器集群的计费信息进行计费处理，得到每个待计费容器集群的费用数据；通过对外接口将每个待计费容器集群的费用数据发送至前端系统进行展示。

Description

容器平台计费方法及系统
本公开要求在2020年06月23日提交中国专利局、申请号为202010582466.2的中国专利申请的优先权，以上申请的全部内容通过引用结合在本公开中。
技术领域
本申请实施例涉及容器平台技术领域，例如涉及一种容器平台的计费方法及系统。
背景技术
容器平台是云计算平台的核心应用，为上层应用提供了丰富的应用程序编程接口(Application Programming Interface,API)，以开放平台的形式，向外部提供网络API服务。借助容器平台，用户无须过多考虑底层硬件，可以更加方便地构建应用时的服务。
租户在容器平台上开发一个项目可能需要使用多个容器集群，而相关技术中的计费方法，无法对容器平台中的多个容器集群进行兼容性的数据采集和计费，只能对一个容器集群中的每个容器进行对应的数据采集和计费。因此，如何对容器平台中的多个容器集群同时进行计费成为亟待解决的问题。
发明内容
本申请实施例提供一种容器平台的计费方法及系统，以实现对容器平台中的多个容器集群进行兼容性的多集群数据采集、计费以及费用展示。
第一方面，本申请实施例提供了一种容器平台的计费方法，包括：
在容器平台中确定预设数量的待计费容器集群；
获取每个待计费容器集群的管理节点提供的原生接口，分别为每个原生接 口对接插件形式的数据采集器，并通过数据采集器对每个待计费容器集群进行计费信息采集；
对采集的每个待计费容器集群的计费信息进行计费处理，得到每个待计费容器集群的费用数据；
通过对外接口将每个待计费容器集群的费用数据发送至前端系统进行展示。
第二方面，本申请实施例还提供了一种容器平台的计费系统，包括：确定模块，预设数量的插件形式的数据采集器，数据处理模块以及对外接口；
确定模块，被配置为在容器平台中确定预设数量的待计费容器集群；
数据采集器，被配置为获取目标待计费容器集群的管理节点提供的原生接口，并与原生接口对接，通过原生接口对所述目标待计费容器集群进行计费信息采集；
数据处理模块，被配置为对采集的每个所述待计费容器集群的计费信息进行计费处理，得到每个所述待计费容器集群的费用数据；
对外接口，被配置为将每个所述待计费容器集群的费用数据发送至前端系统进行展示。
附图说明
图1是本申请实施例一中的一种容器平台的计费方法的流程图；
图2是本申请实施例二中的一种容器平台的计费方法的流程图；
图3是本申请实施例三中的一种容器平台的计费方法的流程图；
图4是本申请实施例四中的一种容器平台的计费系统的结构示意图。
具体实施方式
下面结合附图和实施例对本申请作进一步的详细说明。可以理解的是，此处所描述的具体实施例仅仅用于解释本申请。另外还需要说明的是，为了便于描述，附图中仅示出了与本申请相关的部分而非全部结构。
实施例一
图1是本申请实施例一中的一种容器平台的计费方法的流程图，本实施例可适用于对多个容器集群同时进行多集群数据采集和计费的情况，该方法可以由容器平台的计费系统来执行，可以包括如下步骤：
步骤110、在容器平台中确定预设数量的待计费容器集群。
其中，容器集群中包括多个容器，容器一般指Docker容器，任何应用程序和它的所有依赖项都可以打包成一个文件放入到一个可移植的容器中，然后发布到任何安装有容器引擎的服务器上，进行应用程序部署。待计费容器集群包括租户租来部署应用程序并且占用平台资源的容器集群，预设数量表示一个租户在容器平台中租用的容器集群数量。
可选的，容器平台包括多集群版本的PaaS平台。
本实施例中，容器平台可以是包括多个容器集群的PaaS平台，其中，PaaS平台可以提供应用程序的开发和运行环境。
本实施例中，由于容器平台是根据使用的资源数量向租户进行收费的，因此，在多容器集群多租户模式下，需要对各租户租用的多个待计费容器集群同时进行计费信息采集，以便于实时计算该租户的费用数据。
步骤120、获取各待计费容器集群的管理节点提供的原生接口，分别为各原生接口对接插件形式的数据采集器，并通过数据采集器对各待计费容器集群进行计费信息采集。
本实施例中，容器集群包括管理节点和多个工作节点，其中，管理节点是 容器集群的管理控制中心，可以对集群中的各工作节点进行维护管理，工作节点是运行业务应用的容器。为了获取各待计费容器集群使用的资源数量，可以先获取各待计费容器集群的管理节点提供的原生接口，然后分别为各原生接口对接一个数据采集器，以使各数据采集器通过对接的原生接口对待计费容器集群进行计费信息采集。
本实施例中，为了能够灵活选择容器平台中的容器集群进行数据采集，将数据采集器设置为插件形式，使得数据采集器具有可插拔的特点。通过将数据采集器插入待计费容器集群的管理节点上，即可利用该数据采集器采集该待计费容器集群的计费信息。
可选的，通过数据采集器对各待计费容器集群进行计费信息采集，可以包括：通过与当前数据采集器对接的目标待计费容器集群的管理节点的原生接口，实时从管理节点中获取目标待计费容器集群中的各工作节点反馈的服务操作记录；将存在操作更新的目标服务的操作记录作为目标待计费容器集群的计费信息。
本实施例中，为了提高计费精度，以应用程序中的服务为粒度，对容器集群进行计费信息采集。可以通过与当前数据采集器对接的目标待计费容器集群的管理节点的原生接口，实时获取管理节点中存储的各工作节点实时上报的服务操作记录，并从中选择出存在操作更新的目标服务，例如，存在部署、修改、删除以及停止等操作的服务，将各目标服务对应的操作记录作为目标待计费容器集群的计费信息，通过目标服务所在容器上挂载的存储卷声明(Persistent Volume Claim，PVC)将计费信息持久化存储到数据库中。
可选的，待计费容器集群的管理节点提供的原生接口包括Kubernetes接口。
本实施例中，集群的管理节点提供的Kubernetes接口是获取容器集群的资 源使用情况的唯一操作入口，因此，通过监控管理节点的Kubernetes接口，可以实时获取待计费容器集群中的各容器的资源使用变化量。
步骤130、对采集的各待计费容器集群的计费信息进行计费处理，得到各待计费容器集群的费用数据。
本实施例中，根据采集到的各待计费容器集群的计费信息，分别对各待计费容器集群的资源使用量进行统计，例如，统计CPU、内存和磁盘等资源的使用量，并根据容器平台的计费策略，计算出各待计费容器集群的详细费用数据，以及租户需要支付的总费用数据。将得到的费用数据持久化存入数据库中，作为对外提供的费用账单。
其中，每个待计费容器集群对应一个计费策略，同一个租户的各个待计费容器集群可以对应相同的计费策略，也可以对应不同的计费策略。
步骤140、通过对外接口将各待计费容器集群的费用数据发送至前端系统进行展示。
本实施例中，为了使租户得知当前待支付的总费用数据以及详细费用数据，可以通过对外接口从数据库中获取各待计费容器集群的相关费用数据，并发送至前端系统进行展示。其中，前端系统可以是门户网站。
可选的，对外接口为Restful接口。
本实施例中，可以遵循超文本传输协议(HyperText Transfer Protocol，HTTP)，将JSON格式的费用数据通过Restful接口形式对外提供。其中，Restful接口可以实现前后端分离，即，后端处理数据并以JSON格式传输出去，前端接收到数据后，只负责对数据进行展示和渲染，不对数据做其他任何处理。
本申请实施例的技术方案，通过在容器平台中确定预设数量的待计费容器集群；获取各待计费容器集群的管理节点提供的原生接口，分别为各原生接口 对接插件形式的数据采集器，并通过数据采集器对各待计费容器集群进行计费信息采集；对采集的各待计费容器集群的计费信息进行计费处理，得到各待计费容器集群的费用数据；通过对外接口将各待计费容器集群的费用数据发送至前端系统进行展示，解决了相关技术中只能对一个容器集群中的各容器进行对应的数据采集和计费的问题，实现了对容器平台中的多个容器集群进行兼容性的多集群数据采集、计费以及费用展示。
实施例二
图2是本申请实施例二中的一种容器平台的计费方法的流程图，本实施例在上述实施例的基础上进行改动，提供对采集的各待计费容器集群的计费信息进行计费处理，得到各待计费容器集群的费用数据的步骤中可以包括的步骤，以及，通过对外接口将各待计费容器集群的费用数据发送至前端系统进行展示的步骤中可以包括的步骤。
下面结合图2对本申请第二实施例提供的一种容器平台的计费方法进行说明，包括以下步骤：
步骤210、在容器平台中确定预设数量的待计费容器集群。
步骤220、获取各待计费容器集群的管理节点提供的原生接口，分别为各原生接口对接插件形式的数据采集器，并通过数据采集器对各待计费容器集群进行计费信息采集。
步骤230、以单位收费时间为定时长，定时对当前待计费容器集群在当前单位收费时间内的计费信息进行归类处理，以将计费信息中的底层基础数据转换为业务数据。
本实施例中，单位收费时间也就是收费间隔，是分钟级别的时间长度，可 以是5分钟、8分钟或者其他的时间长度。根据获取到的各待计费容器集群的计费信息，每间隔单位收费时间，就对当前待计费容器集群的当前未处理的计费信息进行归类处理，以将当前未处理的计费信息中的底层基础数据，转换为CPU使用量、内存使用量以及磁盘使用量等符合要求的业务数据，以便于后续对容器集群的计费资源数量进行统计。
本实施例中，通过将单位收费时间由原来的小时级别修改为分钟级别，可以实现对计费信息的迸发处理优化，并且可以保证展示计费数据的数据延迟时间小于单位收费时间。例如，计费信息的处理周期为每5分钟进行一次，则计费数据的展示存在小于5分钟的数据延迟。
步骤240、根据业务数据统计当前待计费容器集群在当前单位收费时间内使用的计费资源数量，根据计费策略计算与计费资源数量对应的费用增量数据。
本实施例中，对计费信息进行归类处理后，对得到的业务数据进行统计，确定当前待计费容器集群在收费间隔内使用的计费资源数量，然后根据与当前待计费容器集群对应的计费策略，计算与计费资源数量对应的费用增量数据，即当前待计费容器集群在当前单位收费时间内的消费的费用数据。其中，费用增量数据有助于租户了解应用或者服务在当前待计费容器集群中的运行情况。
步骤250、将费用增量数据与当前待计费容器集群的历史费用数据进行求和，得到当前待计费容器集群的费用数据。
本实施例中，由于租户最终需要对当前待计费容器集群消费的总数据进行支付，因此，每次计算出当前待计费容器集群当前单位收费时间内的费用增量数据后，既要存储当前的费用增量数据作为费用账单中的详细费用数据，又要将当前的费用增量数据与历史费用数据进行累加，求得当前待计费容器集群到当前时刻为止累积的总费用数据。
可选的，在得到待计费容器集群的费用数据之后，还可以包括：通过H-Base1接口对待计费容器集群的费用数据进行支付。
本实施例中，为了便于租户进行费用支付，可以向租户提供H-Base1接口，通过H-Base1接口对待计费容器集群的费用进行支付，并将收费记录持久化存储到数据库中。
步骤260、通过对外接口将各待计费容器集群的费用数据发送至前端系统进行展示。
本实施例中，可以通过对外接口从数据库中获取各待计费容器集群的相关费用数据，例如，计费信息、费用账单以及收费记录，并将相关费用数据都发送至与对外接口对接的前端系统进行展示。
可选的，在通过对外接口将各待计费容器集群的费用数据发送至前端系统进行展示之前，所述方法还可以包括：为各待计费容器集群配置对应的对外接口，并将各对外接口，分别以插件形式挂载到容器平台中的前端系统。
本实施例中，为了使得各待计费容器集群的相关费用数据可以分别展示在不同的前端系统，分别为各待计费容器集群配置一一对应的对外接口，例如，Restful接口，并将各对外接口以前端插件的形式分别挂载到不同的前端系统。
可选的，通过对外接口将各待计费容器集群的费用数据发送至前端系统进行展示，可以包括：通过与目标待计费容器集群对应的目标对外接口，将目标待计费容器集群的费用数据发送至目标对外接口所挂载的前端系统进行展示。
本实施例中，当要对目标待计费容器集群的相关费用数据进行展示时，先获取与目标待计费容器集群对应的目标Restful接口，通过目标Restful接口，将目标待计费容器集群的计费信息、费用账单以及收费记录发送到目标Restful接口挂载的前端系统中，例如，前端门户网站中进行展示。
本申请实施例的技术方案，通过在容器平台中确定预设数量的待计费容器集群；获取各待计费容器集群的管理节点提供的原生接口，分别为各原生接口对接插件形式的数据采集器，并通过数据采集器对各待计费容器集群进行计费信息采集；对采集的各待计费容器集群的计费信息进行计费处理，得到各待计费容器集群的费用数据；通过对外接口将各待计费容器集群的费用数据发送至前端系统进行展示，解决了相关技术中只能对一个容器集群中的各容器进行对应的数据采集和计费的问题，实现了对容器平台中的多个容器集群进行兼容性的多集群数据采集、计费以及费用展示。
实施例三
图3是本申请实施例三中的一种容器平台的计费方法的流程图，本实施例可以与上述实施例中各个可选方案结合。在一实施例中，参考图3，该方法可以包括如下步骤：
步骤310、通过插件形式的数据采集器，对PaaS平台中的预设数量的待计费容器集群进行多集群数据采集，得到各待计费容器集群的计费信息。
本实施例中，PaaS平台是多集群版本的容器平台。为了能够对PaaS平台中的多个待计费容器集群同时进行兼容性的数据采集，分别为各待计费容器集群的管理节点提供的Kubernetes接口对接一个数据采集器，使得数据采集器可以通过对接的Kubernetes接口，实时监听管理节点中存储的各工作节点的服务操作记录，并获取存在服务状态变化的操作记录作为计费信息，例如，对服务进行部署、修改、删除以及停止等操作的记录，监控指标包括CPU、内存以及磁盘的使用量。并实时将获取的操作记录存储到数据库中，避免使用轮询接口由于时间误差无法实时获取服务状态变化的情况，准确实时的获取应用中的服务 创建、删除、修改等信息。其中，数据采集器采集的计费信息为未经处理的基础数据。
本实施例中，计费系统将数据采集器独立出来，以服务形式集成在Web项目内，废除扫描的数据采集方式，为PaaS平台中的每一个待计费容器集群都配置一个数据采集器，负责采集该容器集群中存在服务状态变化的操作记录作为计费信息，并持久化存储到数据库中。通过实时的将计费信息写入数据库，保证获取准确的资源数据变化时间，精准计费。
步骤320、定时对各待计费容器集群的计费信息进行计费处理，并对得到各待计费容器集群的费用数据进行持久化存储。
本实施例中，以单位收费时间设置定时任务，定时对数据库中存储的各待计费容器集群的计费信息进行计费处理，计费处理分为两个方面，其一，由于底层基础数据与业务数据有较大差别，先对计费信息中的底层基础数据进行归类处理，变成符合要求的业务数据；其二，对业务数据进行统计，确定当前待计费容器集群在单位收费时间内使用的计费资源数量，根据计费策略计算与计费资源数量对应的费用数据，将费用数据持久化存储到数据库中，作为对外提供数据的同时也作为收费历史。
本实施例中，废除小时级别的最小计费单位，将单位收费时间修改为分钟级别，实现对计费信息的迸发处理优化，并且可以保证展示计费数据的数据延迟时间小于单位收费时间。例如，计费信息的处理周期为每5分钟进行一次，则计费数据的展示存在小于5分钟的数据延迟。
本实施例中，可以在多个容器集群下，支持租户力度费用统计。各待计费容器集群中的应用状态变化通过接口的形式实时采集和记录，进而根据采集的信息确定集群使用的资源的数量变化，根据使用的资源数量实时调整该容器集 群的费用计算，生成新的费用数据。
步骤330、通过插件形式的Restful接口，将各待计费容器集群的费用数据发送至对应的前端系统。
本实施例中，计费信息和费用数据持久化存储的目的是为了对外提供数据服务，为了使得各待计费容器集群的费用数据可以分别展示在不同的前端系统，分别为各待计费容器集群配置对应的Restful接口，并将各Restful接口以插件形式直接挂载到PaaS平台的底层dashboard前端。当要对目标待计费容器集群的费用数据进行展示时，遵循HTTP协议，将JSON格式的集群的费用数据通过Restful接口形式对外提供，对接扣费模块可直接依据API调取计费接口获取应用费用信息。
本实施例中，为了便于租户进行费用支付，可以向租户提供H-Base1接口，通过H-Base1接口对待计费容器集群的费用进行支付，并将收费记录持久化存储到数据库中。
步骤340、通过前端系统对接收的待计费容器集群的费用数据进行展示。
本实施例中，支持在门户网站上对容器集群的费用数据进行展示。在PaaS平台的多集群面板中，将以前端插件形式将Restful接口插入前端门户网站，并将容器集群的计费信息、费用账单以及收费记录等相关费用数据汇总至门户网站做选择性展示，展示的数据至少包括总费用数据、详细费用数据、磁盘计费情况三个部分。
实施例四
图4是本申请实施例四中的一种容器平台的计费系统的结构示意图，本实施例可适用于对任务进行并发调度的情况。如图4所示，该系统包括：确定模 块410，预设数量的插件形式的数据采集器420，数据处理模块430以及对外接口440；
确定模块410，被配置为在容器平台中确定预设数量的待计费容器集群；
数据采集器420，被配置为获取目标待计费容器集群的管理节点提供的原生接口，并与原生接口对接，通过原生接口对目标待计费容器集群进行计费信息采集；
数据处理模块430，被配置为对采集的各待计费容器集群的计费信息进行计费处理，得到各待计费容器集群的费用数据；
对外接口440，被配置为将各待计费容器集群的费用数据发送至前端系统进行展示。
可选的，数据采集器420，可以被配置为：通过与当前数据采集器对接的目标待计费容器集群的管理节点的原生接口，实时从管理节点中获取目标待计费容器集群中的各工作节点反馈的服务操作记录；将存在操作更新的目标服务的操作记录作为目标待计费容器集群的计费信息。
可选的，数据处理模块430，可以被配置为：以单位收费时间为定时长，定时对当前待计费容器集群在当前单位收费时间内的计费信息进行归类处理，以将计费信息中的底层基础数据转换为业务数据；根据业务数据统计当前待计费容器集群在当前单位收费时间内使用的计费资源数量，根据计费策略计算与计费资源数量对应的费用增量数据；将费用增量数据与当前待计费容器集群的历史费用数据进行求和，得到当前待计费容器集群的费用数据。
可选的，还包括：支付模块，被配置为在得到待计费容器集群的费用数据之后，通过H-Base1接口对待计费容器集群的费用数据进行支付。
可选的，还包括：挂载模块，被配置为在通过对外接口将各待计费容器集 群的费用数据发送至前端系统进行展示之前，为各待计费容器集群配置对应的对外接口，并将各对外接口，分别以插件形式挂载到容器平台中的前端系统。
可选的，对外接口440，可以被配置为：通过与目标待计费容器集群对应的目标对外接口，将目标待计费容器集群的费用数据发送至目标对外接口所挂载的前端系统进行展示。
可选的，待计费容器集群的管理节点提供的原生接口包括Kubernetes接口。
可选的，对外接口为Restful接口。
可选的，容器平台包括多集群版本的PaaS平台。
本申请实施例的技术方案，通过在容器平台中确定预设数量的待计费容器集群；获取各待计费容器集群的管理节点提供的原生接口，分别为各原生接口对接插件形式的数据采集器，并通过数据采集器对各待计费容器集群进行计费信息采集；对采集的各待计费容器集群的计费信息进行计费处理，得到各待计费容器集群的费用数据；通过对外接口将各待计费容器集群的费用数据发送至前端系统进行展示，解决了相关技术中只能对一个容器集群中的各容器进行对应的数据采集和计费的问题，实现了对容器平台中的多个容器集群进行兼容性的多集群数据采集、计费以及费用展示。
本申请实施例的技术方案，通过在容器平台中确定预设数量的待计费容器集群；获取各待计费容器集群的管理节点提供的原生接口，分别为各原生接口对接插件形式的数据采集器，并通过数据采集器对各待计费容器集群进行计费信息采集；对采集的各待计费容器集群的计费信息进行计费处理，得到各待计费容器集群的费用数据；通过对外接口将各待计费容器集群的费用数据发送至前端系统进行展示，解决了相关技术中只能对一个容器集群中的各容器进行对 应的数据采集和计费的问题，实现了对容器平台中的多个容器集群进行兼容性的多集群数据采集、计费以及费用展示。

Claims (10)

  1. 一种容器平台的计费方法，包括：
    在容器平台中确定预设数量的待计费容器集群；
    获取每个待计费容器集群的管理节点提供的原生接口，分别为每个所述原生接口对接插件形式的数据采集器，并通过所述数据采集器对每个待计费容器集群进行计费信息采集；
    对采集的每个待计费容器集群的计费信息进行计费处理，得到每个待计费容器集群的费用数据；
    通过对外接口将每个待计费容器集群的费用数据发送至前端系统进行展示。
  2. 根据权利要求1所述的容器平台的计费方法，其中，通过所述数据采集器对每个待计费容器集群进行计费信息采集，包括：
    通过与当前数据采集器对接的目标待计费容器集群的管理节点的原生接口，实时从所述管理节点中获取所述目标待计费容器集群中的每个工作节点反馈的服务操作记录；
    将存在操作更新的目标服务的操作记录作为所述目标待计费容器集群的计费信息。
  3. 根据权利要求1所述的容器平台的计费方法，其中，对采集的每个待计费容器集群的计费信息进行计费处理，得到每个待计费容器集群的费用数据，包括：
    以单位收费时间为定时长，定时对当前待计费容器集群在当前单位收费时间内的计费信息进行归类处理，以将所述计费信息中的底层基础数据转换为业务数据；
    根据业务数据统计所述当前待计费容器集群在所述当前单位收费时间内使用的计费资源数量，根据计费策略计算与所述计费资源数量对应的费用增量数 据；
    将所述费用增量数据与所述当前待计费容器集群的历史费用数据进行求和，得到所述当前待计费容器集群的费用数据。
  4. 根据权利要求1所述的容器平台的计费方法，在得到每个待计费容器集群的费用数据之后，所述容器平台的计费方法还包括：
    通过H-Base1接口对所述待计费容器集群的费用数据进行支付。
  5. 根据权利要求1所述的容器平台的计费方法，在通过对外接口将每个待计费容器集群的费用数据发送至前端系统进行展示之前，所述容器平台的计费方法还包括：
    为每个待计费容器集群配置对应的对外接口，并将每个所述对外接口，分别以插件形式挂载到所述容器平台中的前端系统。
  6. 根据权利要求5所述的容器平台的计费方法，其中，通过对外接口将每个待计费容器集群的费用数据发送至前端系统进行展示，包括：
    通过与目标待计费容器集群对应的目标对外接口，将目标待计费容器集群的费用数据发送至目标对外接口所挂载的前端系统进行展示。
  7. 根据权利要求1所述的容器平台的计费方法，其中，所述待计费容器集群的管理节点提供的原生接口包括Kubernetes接口。
  8. 根据权利要求1所述的容器平台的计费方法，其中，所述对外接口为Restful接口。
  9. 根据权利要求1所述的容器平台的计费方法，其中，所述容器平台包括多集群版本的PaaS平台。
  10. 一种容器平台的计费系统，包括：确定模块，预设数量的插件形式的数据采集器，数据处理模块以及对外接口；
    所述确定模块，被配置为在容器平台中确定预设数量的待计费容器集群；
    所述数据采集器，被配置为获取目标待计费容器集群的管理节点提供的原生接口，并与所述原生接口对接，通过所述原生接口对所述目标待计费容器集群进行计费信息采集；
    所述数据处理模块，被配置为对采集的每个所述待计费容器集群的计费信息进行计费处理，得到每个所述待计费容器集群的费用数据；
    所述对外接口，被配置为将每个所述待计费容器集群的费用数据发送至前端系统进行展示。
PCT/CN2021/070294 2020-06-23 2021-01-05 容器平台计费方法及系统 WO2021258719A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010582466.2 2020-06-23
CN202010582466.2A CN113839974A (zh) 2020-06-23 2020-06-23 容器平台计费方法及系统

Publications (1)

Publication Number Publication Date
WO2021258719A1 true WO2021258719A1 (zh) 2021-12-30

Family

ID=78964199

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/070294 WO2021258719A1 (zh) 2020-06-23 2021-01-05 容器平台计费方法及系统

Country Status (2)

Country Link
CN (1) CN113839974A (zh)
WO (1) WO2021258719A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117273720A (zh) * 2023-11-21 2023-12-22 湖南兴盛优选网络科技有限公司 一种高性能的可扩展的计量计费服务平台

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107516199A (zh) * 2017-08-01 2017-12-26 携程旅游信息技术（上海）有限公司 云平台的容器计费方法、装置及系统、设备、存储介质
CN108512935A (zh) * 2018-04-16 2018-09-07 腾讯科技（深圳）有限公司 数据服务系统、方法、服务器和计算机可读存储介质
US10191778B1 (en) * 2015-11-16 2019-01-29 Turbonomic, Inc. Systems, apparatus and methods for management of software containers
CN109947537A (zh) * 2019-03-28 2019-06-28 山东浪潮云信息技术有限公司 创建云容器服务的系统及方法
US10346775B1 (en) * 2015-11-16 2019-07-09 Turbonomic, Inc. Systems, apparatus and methods for cost and performance-based movement of applications and workloads in a multiple-provider system
CN110531987A (zh) * 2019-07-30 2019-12-03 平安科技（深圳）有限公司 基于Kubernetes集群的管理方法、装置及计算机可读存储介质
CN110535831A (zh) * 2019-07-30 2019-12-03 平安科技（深圳）有限公司 基于Kubernetes和网络域的集群安全管理方法、装置及存储介质

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103152393B (zh) * 2013-02-05 2015-08-05 北京邮电大学 一种云计算的计费方法和计费系统
CN105049218B (zh) * 2015-06-24 2018-02-13 上海斐讯数据通信技术有限公司 PhiCloud云计费方法及系统
CN107241242B (zh) * 2017-07-19 2020-09-15 北京奇艺世纪科技有限公司 一种数据处理方法和装置
CN107508687A (zh) * 2017-09-08 2017-12-22 深圳市智物联网络有限公司 一种计费的方法、装置、物联网应用平台及计费服务器
WO2019104577A1 (zh) * 2017-11-30 2019-06-06 深圳市大疆创新科技有限公司 网站内容服务架构方法及系统
CN108512719B (zh) * 2018-03-02 2021-06-08 南京易捷思达软件科技有限公司 一种基于开源云平台的一体化资源监控系统
CN109067828B (zh) * 2018-06-22 2022-01-04 杭州才云科技有限公司 基于Kubernetes和OpenStack容器云平台多集群构建方法、介质、设备
CN109815430B (zh) * 2018-11-30 2020-07-31 北京金山云网络技术有限公司 请求处理方法、装置、数据处理服务器及可读存储介质
CN109934402A (zh) * 2019-03-11 2019-06-25 北京天润新能投资有限公司西北分公司 一种风电场集控中心集中风功率预测系统及其设计方法
CN110427181A (zh) * 2019-08-13 2019-11-08 山东浪潮商用系统有限公司 一种Web系统前后端分离方法
CN111061540B (zh) * 2019-11-27 2023-05-23 北京计算机技术及应用研究所 一种基于容器技术的应用虚拟化方法及系统
CN111273926A (zh) * 2020-01-14 2020-06-12 一飞智控(天津)科技有限公司 机场客户端远程升级管理方法、系统、存储介质、无人机

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10191778B1 (en) * 2015-11-16 2019-01-29 Turbonomic, Inc. Systems, apparatus and methods for management of software containers
US10346775B1 (en) * 2015-11-16 2019-07-09 Turbonomic, Inc. Systems, apparatus and methods for cost and performance-based movement of applications and workloads in a multiple-provider system
CN107516199A (zh) * 2017-08-01 2017-12-26 携程旅游信息技术（上海）有限公司 云平台的容器计费方法、装置及系统、设备、存储介质
CN108512935A (zh) * 2018-04-16 2018-09-07 腾讯科技（深圳）有限公司 数据服务系统、方法、服务器和计算机可读存储介质
CN109947537A (zh) * 2019-03-28 2019-06-28 山东浪潮云信息技术有限公司 创建云容器服务的系统及方法
CN110531987A (zh) * 2019-07-30 2019-12-03 平安科技（深圳）有限公司 基于Kubernetes集群的管理方法、装置及计算机可读存储介质
CN110535831A (zh) * 2019-07-30 2019-12-03 平安科技（深圳）有限公司 基于Kubernetes和网络域的集群安全管理方法、装置及存储介质

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117273720A (zh) * 2023-11-21 2023-12-22 湖南兴盛优选网络科技有限公司 一种高性能的可扩展的计量计费服务平台

Also Published As

Publication number Publication date
CN113839974A (zh) 2021-12-24

Similar Documents

Publication Publication Date Title
CN103414577B (zh) 用于Hadoop平台的计费系统及方法
US8347306B2 (en) Method and system for determining resource usage of each tenant in a multi-tenant architecture
JP6126099B2 (ja) タイムリーイベントデータ分配用マーケットプレイス
WO2020224022A1 (zh) 一种资源调度方法及系统
CN110418022B (zh) 为多个用户标识调整流量套餐的方法及装置
CN108090225B (zh) 数据库实例的运行方法、装置、系统及计算机可读存储介质
CN1509444A (zh) 用于监视服务提供商成绩的系统和方法
CN103067185A (zh) 云计算系统中的计费方法
US8174990B2 (en) Mechanism and system for programmable measurement of aggregate metrics from a dynamic set of nodes
JP7206698B2 (ja) 提供装置、処理システム及び通信方法
WO2021258719A1 (zh) 容器平台计费方法及系统
CN110348890A (zh) 一种计算停车费用的方法及设备
CN112311590A (zh) 云服务的租赁优化方法、装置、设备和介质
CN108833123A (zh) 基于按量的云主机计费方法及装置
CN106294708A (zh) 一种基于Torque的集群记账管理方法及系统
CN101252460B (zh) 用于收集按需服务的使用数据的方法和数据处理系统
CN108763065A (zh) 一种移动应用灰度发布系统及方法
CN112054912A (zh) OpenStack开源云平台的资源计费系统和方法
WO2015049515A1 (en) Improvements relating to distributed resource management in real-time systems
US11516033B1 (en) System and method for metering consumption
CN111488224A (zh) 一种分布式计量计费的方法及系统
CN112583609A (zh) 一种云计费方法、装置、云管理平台、系统及存储介质
CN110267717B (zh) 在多租户环境中按不同单独租户自动生成自动缩放呼叫规则的方法及装置
EP3331196B1 (en) Telecommunication system for monitoring and controlling of a network providing resource to a user
CN111861612B (zh) 一种资源分配方法、装置、设备及介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21829950

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21829950

Country of ref document: EP

Kind code of ref document: A1