WO2018205325A1 - 在异构资源上构建内容分发网络平台的方法和系统 - Google Patents

在异构资源上构建内容分发网络平台的方法和系统 Download PDF

Info

Publication number
WO2018205325A1
WO2018205325A1 PCT/CN2017/086770 CN2017086770W WO2018205325A1 WO 2018205325 A1 WO2018205325 A1 WO 2018205325A1 CN 2017086770 W CN2017086770 W CN 2017086770W WO 2018205325 A1 WO2018205325 A1 WO 2018205325A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
resource
information
layer
basic
Prior art date
Application number
PCT/CN2017/086770
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 网宿科技股份有限公司
Priority to EP17909038.6A priority Critical patent/EP3554010B1/en
Priority to US16/463,937 priority patent/US11102089B2/en
Publication of WO2018205325A1 publication Critical patent/WO2018205325A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04—Network management architectures or arrangements
    • H04L41/044—Network management architectures or arrangements comprising hierarchical management structures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/14—Network analysis or design
    • H04L41/145—Network analysis or design involving simulating, designing, planning or modelling of a network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/508—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement
    • H04L41/509—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement wherein the managed service relates to media content delivery, e.g. audio, video or TV
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications

Definitions

  • the present invention relates to the field of content distribution network technologies, and in particular, to a method and system for constructing a content distribution network platform on heterogeneous resources.
  • the Content Delivery Network is built on the network and relies on the distributed edge servers deployed in the local area. Through the load balancing, content distribution and scheduling functions of the central platform, users can obtain the required content and reduce network congestion. Improve user access response speed and hit rate.
  • the existing technical solutions are mainly the integration within each system, such as the management integration of private clouds and public clouds, but there is no A unified management system spanning physical servers, virtual servers, virtual hosts, and containers.
  • OpenStack has implemented a set of integration solutions with Docker. However, this solution is based on the integration of Platform as a Service (PaaS) based on OpenStack, and the actual effect is not good.
  • PaaS Platform as a Service
  • Some advanced features of Docker are not supported because the Nova API is an abstraction to the machine, while the Docker API contains an abstraction of the process/application.
  • embodiments of the present invention provide a method and system for constructing a content distribution network platform on heterogeneous resources.
  • the technical solution is as follows:
  • a method for constructing a content distribution network platform on a heterogeneous resource includes a logical application layer and a basic resource layer, and the construction method includes the following steps:
  • the logic application layer determines the actual resource configuration requirement information and resource type information of the application according to the creation request, and then sends the actual resource configuration requirement information and the resource type information to the basic resource layer;
  • the basic resource layer receives the actual resource configuration requirement information and the resource type information, and creates an application basic resource environment according to the actual resource configuration requirement information and the resource type information.
  • the step of the logical application layer after receiving the application creation request, determining the actual resource configuration requirement information and the resource type information of the application according to the creation request, and then sending the actual resource configuration requirement information and the resource type information to the basic resource layer is specifically:
  • the application information is registered on the logical application layer, and then the application basic information in the creation request is verified. After the verification is passed, the actual resource configuration requirement information of the application is determined according to the application capability requirement information in the creation request, and then the actual resource configuration requirement is determined. Information and resource type information is sent to the underlying resource layer.
  • the application creation request includes at least application basic information and application capability requirement information, and Includes resource type information;
  • the application basic information includes: one or several of an application name, a network protocol address, and a deployment area;
  • Application capability requirement information includes: one or more of API (Application Programming Interface) responsiveness, bandwidth capability, high availability (HA) capability, and input/output (IO) capability. ;
  • API Application Programming Interface
  • HA high availability
  • IO input/output
  • the resource type information includes one or more of a physical machine, a virtual machine, and a container.
  • the specific steps of the logic application layer determining the actual resource configuration requirement information and the resource type information of the application according to the creation request after receiving the application creation request, and then sending the creation information and the resource type information to the basic resource layer include:
  • the logic application layer After receiving the application creation request, the logic application layer queries the registration information of the application, and compares with the information in the application creation request to perform verification;
  • the logic application layer queries the usage and remaining conditions of the application capability, and converts the application capability requirement information into actual resource configuration requirement information according to the query result;
  • the logic application layer sends the resource type information and the actual resource configuration requirement information in the application creation request to the basic resource layer;
  • the logical application layer queries the configured automatic creation policy, determines the resource type information of the deployed application according to the actual resource configuration requirement and the automatic creation policy, and then sets the resource type information and the actual resource configuration requirement. Information is sent to the underlying resource layer.
  • the automatic creation policy includes the current resource surplus situation, the existing resource allocation situation, and the application's own optimal resource type.
  • the specific steps of the basic resource layer to create the basic resource environment of the application according to the actual resource configuration requirement information and the resource type information include:
  • the basic resource layer uniformly abstracts the same technology into a resource type, finds the corresponding resource type according to the resource type information, and then finds the corresponding driver according to the resource type and the actual resource configuration requirement information, and finally configures the demand information by using the driver in combination with the actual resource. Create an application's underlying resource environment.
  • a system for building a content distribution network platform on heterogeneous resources comprising:
  • a logical application layer configured to determine an actual resource configuration requirement information and resource type information of the application according to the creation request after receiving the application creation request, and then send the actual resource configuration requirement information and the resource type information to the basic resource layer;
  • the basic resource layer is used to create an application basic resource environment according to actual resource configuration requirement information and resource type information.
  • the logical application layer includes:
  • the service function module is configured to register the application information, and the application basic information in the creation request is verified by the logic application management API module, and the actual resource configuration requirement information of the application is determined according to the application capability requirement information in the creation request after the verification.
  • logic application management API module includes:
  • the application cycle management API is used to provide an application creation request, including application lookup, deletion, addition, modification, and migration recovery.
  • Application capability management API for querying and counting usage and remaining of application capabilities
  • Application information management API for querying basic information of the application
  • business function module includes:
  • the application information management sub-module is configured to register application basic information, application capability information, and application resource type information, and receive an application creation request sent by the application cycle management API, and then query the application registration information through the application information management API, and create an application. The information in the request is compared and verified;
  • the application capability management sub-module is configured to query the application capability and the remaining situation of the application capability management API statistics through the application capability management API after the verification is passed, and then convert the application capability requirement information into actual resource configuration requirements according to the query result. information;
  • the application creation policy sub-module is used to query the configured automatic creation policy by applying the policy management API when the application creation request has no resource type information, and determine the resource type information of the deployment application according to the automatic creation policy and the actual resource configuration requirement.
  • the basic resource layer includes:
  • the basic resource layer includes:
  • the technical abstraction layer is used to uniformly abstract the same technology into a resource type, and according to the resource type information, find a corresponding resource type through the unified resource management API module;
  • the technology driver layer is configured to find a corresponding driver according to the resource type of the technology abstraction layer and the actual resource configuration requirement information, and then the driver creates the application basic resource environment through the unified resource management API module by combining the actual resource configuration requirement information.
  • the unified resource management API module includes:
  • the resource cycle management API is used to manage the life cycle of the basic resource, including querying, deleting, adding, and modifying.
  • the driver combines the actual resource configuration requirement information to create an application basic resource environment through the resource cycle management API;
  • the resource inventory management API is used to query and count different types of resource usage and remaining conditions, and find corresponding resource types in the technical abstraction layer according to the query result and the resource type information.
  • resource types of the technology abstraction layer include: physical machines, virtual machines, and containers.
  • the technical driver layer specifically includes: one of a physical machine management system driver, a private cloud management system driver, a cloud host management system driver, and a Kubernetes management system driver.
  • the technical solution provided by the embodiments of the present invention provides the following advantages:
  • the present invention provides a method and system for constructing a content distribution network platform on heterogeneous resources, and implements a capability modeling method based on a custom logic application model.
  • the services built by various heterogeneous technical solutions such as physical machines, virtual machines, and containers are managed in a unified manner.
  • Use a heterogeneous technology such as physical servers, virtual machines, public cloud hosts, and containers to build a content distribution network, and separate application management services (service planes) from the resource architecture (technical plane), but still maintain the unique value of various resource technologies. , features and intelligence.
  • the basic resource layer adopts a two-layer abstract-driven model to manage resources in a unified manner, which can quickly accept new technical solutions without changing the original structure. Layered management is used to simplify operation and maintenance. Upper-level business can customize business Capability model and creation strategy, complete automation deployment under multiple technology platforms, different applications can be shared or independently configured, and configuration is flexible.
  • FIG. 1 is a flow chart of an embodiment of a method for constructing a content distribution network platform on heterogeneous resources provided by the present invention
  • FIG. 2 is a specific flow chart of step S101 of Figure 1;
  • FIG. 3 is a specific flow chart of step S102 of Figure 1;
  • FIG. 4 is a structural diagram of an embodiment of a system 1 for constructing a content distribution network platform on heterogeneous resources according to the present invention.
  • FIG. 5 is a specific structural diagram of a system 1 for constructing a content distribution network platform on a heterogeneous resource in FIG. 4;
  • FIG. 6 is a detailed structural diagram of the logic application layer 100 of FIG. 5;
  • FIG. 7 is a detailed structural diagram of the basic resource layer 200 of FIG. 5.
  • the present invention provides an implementation manner of a method for constructing a content distribution network platform on a heterogeneous resource.
  • the content distribution network platform includes a logical application layer (Application Layer) and a basic resource layer (Resource Layer), and the construction method is as shown in FIG. 1 . Includes the following steps:
  • the logic application layer determines actual resource configuration requirement information and resource type information of the application according to the creation request, and then sends the actual resource configuration requirement information and the resource type information to the basic resource layer.
  • the present invention proposes a unified abstract management method based on a logical application model, and uniformly models the applications built on different technical solutions in an application capability manner to realize unified management of the upper management.
  • the logical application model is the basic unit of application management abstracted by the present invention, and each logical application entity is composed of a business function program and a resource environment program.
  • the A application is deployed on a physical machine, and the entity of the A application includes the function program of the A application itself and the physical machine entity and the system and software environment that the function program is running.
  • the method of the present invention divides the content distribution network platform into a logical application layer and a basic resource layer. After receiving the application creation request, the logical application layer determines the actual resource configuration requirement information and resource type information of the application according to the creation request, and then configures the actual resource. The demand information and resource type information are sent to the base resource layer.
  • the application creation request includes at least application basic information and application capability requirement information, and may also include resource type information, and the resource type information is optional information.
  • the creation request may not include the information, and if the information is not included, the creation process may be
  • the logic application layer makes its own decisions based on needs.
  • the basic information of the application includes: application name, Internet Protocol (IP) address, and deployment area. It is mainly used to describe the basic information of the application.
  • IP Internet Protocol
  • the required information can be arbitrarily defined according to requirements. The above is only given by way of example.
  • the application basic information may also have other information such as an application account (Identity, ID), which is not specifically limited in the present invention.
  • Application capability requirements information includes: Application Programming Interface (API) responsiveness, bandwidth capability, High Availability (HA) capability, and Input/Output (IO) capabilities, which can be arbitrarily defined according to requirements.
  • API Application Programming Interface
  • HA High Availability
  • IO Input/Output
  • the resource type information includes: physical machine, Instance, and container (Docker).
  • the basic resource layer receives the actual resource configuration requirement information and the resource type information, and creates an application basic resource environment according to the actual resource configuration requirement information and the resource type information.
  • the invention is based on a custom logic application model, and implements unified management of services built by various heterogeneous technical solutions such as physical machines, virtual machines, and containers in a capability modeling manner.
  • Use a heterogeneous technology such as physical servers, virtual machines, public cloud hosts, and containers to build a content distribution network, and separate application management services (service planes) from the resource architecture (technical plane) while still maintaining various resource technologies.
  • service planes application management services
  • step S101 in FIG. 1 are:
  • Step S201 registering application basic information, application capability information, and application resource type information on the logic application layer.
  • the registered content includes application basic information, application capability information, and application resource type information, such as application virtual machine A, in logical application.
  • Layer registration application name virtual machine A, network protocol address: 192.168.1.10; subnet mask: 255.255.0.0; deployment area: Shandong Telecom; application account: admin001; virtual network card connection: bridge; processing performance: 8 core processing Memory; 16G; storage performance: 480G; resource type information: virtual machine and other content.
  • Registration information can be compared with the application information in the creation request during the creation process to verify the creation request and decide whether to create the application on the system.
  • Step S202 After receiving the application creation request, the logic application layer queries the registration information of the application, compares with the information in the application creation request, and performs verification.
  • the logical application layer After receiving the request for creating an application, the logical application layer queries the registration information pre-registered by the application to be created on the logical application layer, and the information such as the application account, application name, network protocol address, and deployment area registered in the above step, and creation. The information in the request is compared. If the information is consistent and the verification is passed, the application can be continuously created on the system. If the information is inconsistent, the verification fails, and the application creation process is stopped.
  • Step S203 After the verification, the logic application layer queries the usage and remaining conditions of the application capability, and converts the application capability requirement information into actual resource configuration requirement information according to the query result.
  • the logic application layer queries the application capability of the existing application in the current system and the remaining application capabilities. According to the result of the query, it is known how many application capabilities are available in the current system, combined with the application capability in the creation request.
  • Demand information application capability requirements information such as virtual network card connection: bridging; processing performance: 8-core processor; memory: 16G; storage performance: 480G, etc. converted to actual resource configuration requirements information.
  • the application ability to avoid creating application requirements in the request is greater than the remaining application capabilities in the system, and the system has an error in the creation process due to insufficient application capability.
  • Step S204 when the application creation request includes resource type information, the logic application layer applies the application.
  • the resource type information and the actual resource configuration requirement information in the request are sent to the basic resource layer.
  • the logical application layer directly sends the actual resource configuration requirement obtained in step S203 and the resource type information in the creation request to the basic resource layer, and the basic resource The layer can complete the subsequent resource configuration process.
  • step S205 when there is no resource type information in the application creation request, the logical application layer queries the configured automatic creation policy, determines the resource type information of the deployed application according to the actual resource configuration requirement and the automatic creation policy, and then the resource type information and the actual The resource configuration requirement information is sent to the basic resource layer.
  • the logical application layer is configured with an automatic creation policy.
  • the automatic creation policy can determine the resource type information of the deployed application according to the current resource redundancy, the existing resource allocation, and the application's own optimal resource type.
  • the logical application layer queries the automatically created policy that is configured in advance, and determines the resource type information of the deployed application in combination with the actual resource configuration requirement, and then the actual resource.
  • the configuration requirements and resource type information are sent to the basic resource layer, and the subsequent resource configuration process is completed by the basic resource layer.
  • the logical application layer of the present invention can customize the business capability model and create a policy, and complete the automatic deployment under multiple technical platforms. Different applications can be shared or independently configured, and the configuration mode is flexible.
  • step S102 in FIG. 1 the specific steps of step S102 in FIG. 1 are as follows:
  • the basic resource layer uniformly abstracts the same technology into a resource type.
  • each resource type includes different drivers, such as a physical server management system driver (Real Server Manager), and a private cloud management system driver (Private). Cloud), cloud host management system driver (EC2) and Kubernetes management system driver, etc., the present invention will not be enumerated here.
  • Step S302 Find a corresponding resource type according to the resource type information.
  • the basic resource layer After receiving the actual resource configuration requirement information and the resource type information, the basic resource layer finds the corresponding resource type in the basic resource according to the resource type information.
  • Step S303 finding a corresponding driver according to the resource type and the actual resource configuration requirement information.
  • Step S304 the basic resource environment of the application is created by the driver in combination with the actual resource configuration requirement information.
  • the invention adopts hierarchical management to simplify operation and maintenance, and only needs to maintain the resources of the internal service to ensure the good operation and surplus of the resources. There is no need to pay too much attention to the specific application content and application functions of the operation.
  • the present invention also provides an implementation manner of a system 1 for constructing a content distribution network platform on a heterogeneous resource. As shown in FIG. 4, the present invention includes: a logical application layer 100 and a basic resource layer 200.
  • the logical application layer 100 is configured to determine actual resource configuration requirement information and resource type information of the application according to the creation request after receiving the application creation request, and then send the actual resource configuration requirement information and the resource type information to the basic resource layer 200.
  • the basic resource layer 200 is configured to create an application basic resource environment according to actual resource configuration requirement information and resource type information.
  • the application creation request received by the logic application layer 100 includes at least application basic information and application capability requirement information, and may also include resource type information.
  • the application basic information includes: one or more of an application name, a network protocol address, and a deployment area; and the application capability requirement information includes one or more of an API response capability, a bandwidth capability, a high availability capability, and an input/output capability;
  • the resource type information includes one or more of a physical machine, a virtual machine, and a container.
  • the logic application layer 100 verifies the application basic information in the creation request, and after the verification is passed, converts the application capability information in the creation request into actual resource configuration requirement information, and then configures the actual resource configuration requirement information and resources.
  • the type information is sent to the base resource layer 200.
  • the basic resource layer 200 abstracts the same technology into a resource type, and each resource type specifically includes different drivers.
  • the basic resource layer 200 finds the corresponding resource type according to the received resource type information, and then determines a suitable driver according to the actual resource configuration requirement under the corresponding resource type, and finally creates a logical application basis according to the actual resource configuration requirement information by the driver.
  • the resource environment completes the deployment and configuration of the application according to the application needs.
  • the logical application layer 100 includes a logical application management API module 101 and a business function module 102.
  • the basic resource layer 200 includes a unified resource management API module 201, a technology abstraction layer 202, and a technology driver layer 203.
  • the logic application management API module 101 is configured to manage the service function module; the service function module 102 is configured to register the application information, and the application basic information in the creation request is verified by the logic application management API module, and the verification is performed according to the creation request.
  • the application capability requirement information determines the actual resource configuration requirement information of the application.
  • the unified resource management API module 201 is configured to manage the technology abstraction layer and the technology driver layer; the technology abstraction layer 202 is used to uniformly abstract the same technology into a resource type, and according to the resource type information, find the corresponding resource type through the unified resource management API module; The technology driver layer 203 is configured to find a corresponding driver according to the resource type of the technology abstraction layer and the actual resource configuration requirement information, and then the driver creates the application basic resource environment through the unified resource management API module in combination with the actual resource configuration requirement information.
  • the invention adopts hierarchical management to simplify operation and maintenance, and only needs to maintain the resources of the internal service to ensure the good operation and surplus of the resources. There is no need to pay too much attention to the specific application content and application functions of the operation.
  • FIG. 6 shows a specific structure of the logic application layer 100 in FIG. 5.
  • the logical application management API module 101 includes an application life management API 1011, an application capability management API 1012, an application information management API 1013, and an application policy management API 1014.
  • the service function module 102 includes an application information management sub-module (App Manager) 1021, an application capability management sub-module (App Ability Mapper) 1022, and an application creation policy sub-assembly (Creation Strategy) 1023.
  • App Manager application information management sub-module
  • App Ability Mapper application capability management sub-module
  • Application Creation Strategy application creation policy sub-assembly
  • the application cycle management API 1011 is configured to provide an application creation request, which includes: searching, deleting, adding, modifying, and migrating recovery of the application; the application capability management API 1012 is used for querying and counting usage and remaining conditions of the application capability; and the application information management API 1013 is used to query application basic information; application policy management API 1014 is used for configuring and querying automatic creation policies.
  • the application information management sub-module 1021 is configured to register application basic information, application capability information, and application resource type information, and receive an application creation request sent by the application cycle management API 1011, and then query the application registration information through the application information management API 1013, and The information in the application creation request is compared and verified; the application capability management sub-module 1022 is configured to pass the application capability management API after the verification is passed. 1012 queries the usage and remaining conditions of the application capability of the application capability management API 1012, and then converts the application capability requirement information into actual resource configuration requirement information according to the query result; the application creation policy sub-module 1023 is configured to have no resources in the application creation request. The type information is used to query the configured automatic creation policy by applying the policy management API 1014, and the resource type information of the deployed application is determined according to the automatic creation policy and the actual resource configuration requirement.
  • the application basic information, the application capability information, and the application resource type information are first registered on the logical application layer 100 by the application information management sub-module 1021 before the application is created.
  • the application information management sub-module 1021 queries the registration information of the application through the application information management API 1013, and compares with the information in the application creation request to perform verification. If the information is inconsistent, the verification fails, and the application creation process is stopped. If the information is consistent and the verification is passed, the application capability management sub-module 1022 queries the usage capability of the application capability management API 1012 by using the application capability management API 1012 and the remaining situation.
  • the application capability requirement information is converted into actual resource configuration requirement information;
  • the application creation policy sub-module 1023 queries the configured automatic creation policy by applying the policy management API 1014, according to the automatic The creation policy and actual resource configuration requirements determine the resource type information of the deployed application.
  • the invention can customize the business capability model and create the strategy at the logic application layer, and complete the automatic deployment under various technical platforms. Different applications can be shared or independently configured, and the configuration mode is flexible.
  • FIG. 7 shows a specific structure of the basic resource layer 200 in FIG.
  • the unified resource management API module 201 includes: a resource life management API (Resource Lifecycle) 2011 and a resource inventory management API (Resource Inventory) 2012.
  • the resource cycle management API 2011 is used to manage the life cycle of the basic resources, including query, deletion, addition and modification.
  • the driver combines the actual resource configuration requirement information to create the basic resource environment of the application through the resource cycle management API; the resource inventory management API 2012 To query and count different types of resource usage and remaining conditions, find the corresponding resource type in the technical abstraction layer according to the query result and resource type information.
  • the resource types of the technology abstraction layer 202 include a physical machine 2021, a virtual machine 2022, and a container 2023.
  • the technology driver layer 203 specifically includes: a physical machine management system driver 2031, a private cloud management system driver 2032, a cloud host management system driver 2033, and a Kubernetes management system driver 2034.
  • the basic resource layer 200 After receiving the actual resource configuration requirement information and resource type information, the basic resource layer 200 passes the resources.
  • the inventory management API 2012 queries and counts different types of resource usage and remaining conditions in the technology abstraction layer 202, and finds corresponding resource types in the technology abstraction layer according to the query result and the resource type information. Then, according to the actual resource configuration requirements, the appropriate driver is determined according to the actual resource configuration requirement. The driver completes the application basic resource environment through the resource cycle management API 2011 according to the actual resource configuration requirement information, and completes the application deployment according to the application requirement. Configuration.
  • the invention adopts a two-layer abstract driving mode in the basic resource layer to uniformly manage resources, and can realize new technical solutions such as physical machines and virtual machines quickly without changing the original structure. It is only necessary to complete the functional docking in the technology driver layer of the resource, which can be incorporated into the system management and can quickly introduce a new technical architecture.
  • the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment. Those of ordinary skill in the art can understand and implement without deliberate labor.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Information Transfer Between Computers (AREA)
  • Stored Programmes (AREA)

Abstract

本发明公开了一种在异构资源上构建内容分发网络平台的方法和系统，内容分发网络平台包括逻辑应用层和基础资源层，构建方法包括以下步骤：逻辑应用层在收到应用创建请求后根据创建请求确定应用的实际资源配置需求信息和资源类型信息，然后将实际资源配置需求信息和资源类型信息发送给基础资源层；基础资源层根据接收到的实际资源配置需求信息和资源类型信息创建应用的基础资源环境。本发明基于自定义逻辑应用模型，以能力建模的方式实现对物理机、虚拟机、容器等多种异构技术方案构建的服务进行统一管理。利用异构技术构建内容分发网络，将应用管理服务从资源架构里剥离出来，但仍然保持各种资源技术的独特价值、特点和智能。

Description

在异构资源上构建内容分发网络平台的方法和系统 技术领域
本发明涉及内容分发网络技术领域，特别涉及一种在异构资源上构建内容分发网络平台的方法和系统。
背景技术
内容分发网络(Content Delivery Network，CDN)构建在网络之上，依靠部署在各地的边缘服务器，通过中心平台的负载均衡、内容分发、调度等功能模块，使用户就近获取所需内容，降低网络拥塞，提高用户访问响应速度和命中率。
随着网络的发展，传统超文本传输协议(Hyper Text Transfer Protocol，HTTP)和下载使网络数据量飞速上升，网络游戏产业逐渐成熟，特别是网络视频等需要高带宽的内容，对服务器和网络带宽的压力更大，对内容分发网络服务需求迫切。网站的内容类型不断增加和丰富，在新的需求下，流媒体、Flash、视频和下载等网站内容及业务成了新的主要应用对象。为了给软件下载、视频流媒体、企业网页(Web)应用、企业对企业(Business-to-Business，B2B)交易和第二代互联网(Web 2.0)互动等各种服务加速，传统的内容分发网络技术之上又增加了压缩、流量整形、智能路由和网络优化等技术。随着内容分发网络能够提供加速的内容类型不断丰富，其提供的服务也已从单纯的内容加速拓展到应用和服务的加速。再加上直播的兴起，给内容分发网络带来新的爆发式增长。传统的服务器模式，已经不能很好的支撑日益增长的内容分发网络业务。
2010年开始的云计算风潮，以及2013年兴起的容器(Docker)等新兴虚拟化技术，给内容分发网络带来了新的技术风向。这些新的技术各有所长，可以部分改善传统物理服务器模式下的劣势，带来更高的灵活性及资源利用率，以及硬件故障下的高可用性，更高的运维效率等等。
然而因为新技术接口各不相同互不兼容，造成了巨大的管理挑战。现有的技术方案主要是各体系内的融合，比如私有云与公有云的管理融合，但是没有 横跨物理服务器、虚拟服务器、虚拟主机及容器的统一管理体系。OpenStack有实现一套与Docker的整合方案。但是该方案是基于OpenStack进行平台即服务(Platform as a Service，PaaS)这一层的整合，实际效果不好。不支持Docker的一些高级特性，因为Nova API是对机器的抽象，而Docker API包含了对进程/应用的抽象。
如何将新的技术快速融入到内容分发网络体系是一个亟待解决的技术难题，现有技术存在的问题有：(1)因为不同的系统管理差异较大，内容分发网络系统在引入新的子系统时往往需要投入大量的人力物力，才能将新子系统融入到内容分发网络系统之中。(2)不同子系统之间互相兼容性不高，对于垂直化管理造成了巨大的管理挑战。
发明内容
为了解决现有技术的问题，本发明实施例提供了一种在异构资源上构建内容分发网络平台的方法和系统。所述技术方案如下：
一方面，一种在异构资源上构建内容分发网络平台的方法，内容分发网络平台包括逻辑应用层和基础资源层，构建方法包括以下步骤：
逻辑应用层在收到应用创建请求后根据创建请求确定应用的实际资源配置需求信息和资源类型信息，然后将实际资源配置需求信息和资源类型信息发送给基础资源层；
基础资源层接收到实际资源配置需求信息和资源类型信息，根据实际资源配置需求信息和资源类型信息创建应用的基础资源环境。
进一步的，逻辑应用层在收到应用创建请求后根据创建请求确定应用的实际资源配置需求信息和资源类型信息，然后将实际资源配置需求信息和资源类型信息发送给基础资源层的步骤具体为：
在逻辑应用层上注册应用信息，然后对创建请求中的应用基本信息进行校验，校验通过后根据创建请求中的应用能力需求信息确定应用的实际资源配置需求信息，然后将实际资源配置需求信息和资源类型信息发送给基础资源层。
进一步的，应用创建请求至少包括应用基本信息和应用能力需求信息，还 包括资源类型信息；
应用基本信息包括：应用名称，网络协议地址和部署区域中的一种或几种；
应用能力需求信息包括：API(Application Programming Interface，应用程序编程接口)响应能力，带宽能力，高可用性(High Availability，HA)能力和输入输出(Input/Output，IO)能力中的一种或几种；
资源类型信息包括：物理机、虚拟机和容器中的一种或几种。
进一步的，逻辑应用层在收到应用创建请求后根据创建请求确定应用的实际资源配置需求信息和资源类型信息，然后将创建信息和资源类型信息发送给基础资源层的具体步骤包括：
在逻辑应用层上注册应用基本信息、应用能力信息和应用资源类型信息；
逻辑应用层收到应用创建请求后，查询应用的注册信息，与应用创建请求中的信息对比，进行校验；
校验通过后逻辑应用层查询应用能力的使用情况和剩余情况，根据查询结果将应用能力需求信息转换为实际资源配置需求信息；
当应用创建请求中包含资源类型信息时，逻辑应用层将应用创建请求中的资源类型信息和实际资源配置需求信息发送给基础资源层；
当应用创建请求中没有资源类型信息时，逻辑应用层查询配置好的自动创建策略，根据实际资源配置需求和自动创建策略决定部署应用的资源类型信息，然后再将资源类型信息和实际资源配置需求信息发送给基础资源层。
进一步的，自动创建策略包括当前资源富余情况、现有资源分配情况和应用自身最优资源类型。
进一步的，基础资源层根据实际资源配置需求信息和资源类型信息创建应用的基础资源环境的具体步骤包括：
基础资源层将同类技术统一抽象为一种资源类型，根据资源类型信息找到对应的资源类型，然后根据资源类型和实际资源配置需求信息找到对应的驱动程序，最后通过驱动程序结合实际资源配置需求信息创建应用的基础资源环境。
另一方面，一种在异构资源上构建内容分发网络平台的系统，包括：
逻辑应用层，用于在收到应用创建请求后根据创建请求确定应用的实际资源配置需求信息和资源类型信息，然后将实际资源配置需求信息和资源类型信息发送给基础资源层；
基础资源层，用于根据实际资源配置需求信息和资源类型信息创建应用的基础资源环境。
进一步的，逻辑应用层包括：
逻辑应用管理API模块，用于管理业务功能模块；
业务功能模块，用于注册应用信息，通过逻辑应用管理API模块对创建请求中的应用基本信息进行校验，校验通过后根据创建请求中的应用能力需求信息确定应用的实际资源配置需求信息。
进一步的，逻辑应用管理API模块包括：
应用周期管理API，用于提供应用创建请求，具体包括应用的查找、删除、增加、修改及迁移恢复；
应用能力管理API，用于查询和统计应用能力的使用情况及剩余情况；
应用信息管理API，用于查询应用基本信息；
应用策略管理API，用于配置和查询自动创建策略。
进一步的，业务功能模块包括：
应用信息管理子模块，用于注册应用基本信息、应用能力信息和应用资源类型信息，并接收应用周期管理API发来的应用创建请求，然后通过应用信息管理API查询应用的注册信息，与应用创建请求中的信息对比，进行校验；
应用能力管理子模块，用于在校验通过后，通过应用能力管理API查询应用能力管理API统计的应用能力的使用情况及剩余情况，然后根据查询结果将应用能力需求信息转换为实际资源配置需求信息；
应用创建策略子模块，用于当应用创建请求中没有资源类型信息时，通过应用策略管理API查询配置好的自动创建策略，根据自动创建策略和实际资源配置需求决定部署应用的资源类型信息。
进一步的，基础资源层包括：
基础资源层包括：
统一资源管理API模块，用于管理技术抽象层和技术驱动层；
技术抽象层，用于将同类技术统一抽象为一种资源类型，根据资源类型信息，通过统一资源管理API模块找到对应资源类型；
技术驱动层，用于根据技术抽象层的资源类型和实际资源配置需求信息找到对应的驱动程序，然后驱动程序结合实际资源配置需求信息通过统一资源管理API模块创建应用的基础资源环境。
进一步的，统一资源管理API模块包括：
资源周期管理API，用于管理基础资源的生命周期，包括查询、删减、增加和修改，驱动程序结合实际资源配置需求信息通过资源周期管理API创建应用的基础资源环境；
资源清单管理API，用于查询和统计不同类型的资源使用情况和剩余情况，根据查询结果和资源类型信息在技术抽象层找到对应的资源类型。
进一步的，技术抽象层的资源类型包括：物理机、虚拟机和容器。
进一步的，技术驱动层具体包括：物理机管理系统驱动，私有云管理系统驱动，云主机管理系统驱动和Kubernetes管理系统驱动中的一种或几种。
本发明实施例提供的技术方案带来的有益效果是：本发明提供一种在异构资源上构建内容分发网络平台的方法和系统，基于自定义逻辑应用模型，以能力建模的方式实现对物理机、虚拟机、容器等多种异构技术方案构建的服务进行统一管理。利用物理服务器、虚拟机、公有云主机、容器等异构技术构建内容分发网络，将应用管理服务(业务平面)从资源架构(技术平面)里剥离出来，但仍然保持各种资源技术的独特价值、特点和智能。基础资源层采用两层抽象驱动的模式对资源进行统一管理，可以实现在不变动原有结构的基础上，快速接纳新的技术方案。采用分层管理，简化运维。上层业务可以自定义业务 能力模型和创建策略，完成多种技术平台下的自动化部署，不同的应用之间可以共享或者独立配置，配置灵活。
附图说明
为了更清楚地说明本发明实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本发明提供的一种在异构资源上构建内容分发网络平台的方法的实施方式的流程图；
图2是图1中步骤S101的具体流程图；
图3是图1中步骤S102的具体流程图；
图4是本发明提供的一种在异构资源上构建内容分发网络平台的系统1的实施方式结构图。
图5是图4中在异构资源上构建内容分发网络平台的系统1的具体结构图；
图6是图5中逻辑应用层100的具体结构图；
图7是图5中基础资源层200的具体结构图。
具体实施方式
为使本发明的目的、技术方案和优点更加清楚，下面将结合附图对本发明实施方式作进一步地详细描述。
本发明提供一种在异构资源上构建内容分发网络平台的方法的实施方式，内容分发网络平台包括逻辑应用层(Application Layer)和基础资源层(Resource Layer)，构建方法如图1所示，包括以下步骤：
S101，逻辑应用层在收到应用创建请求后根据创建请求确定应用的实际资源配置需求信息和资源类型信息，然后将实际资源配置需求信息和资源类型信息发送给基础资源层。
因为不同技术方案管理差异较大，要将不同技术方案的新系统融入已有CND系统往往需要投入大量人力物力。同时由于不同技术方案之间的兼容性较 低，对于系统的垂直化管理造成了巨大挑战。为此本发明提出一种基于逻辑应用模型的统一抽象管理方法，通过将构建于不同技术方案之上的应用以应用能力的方式进行统一建模，实现上层管理对于应用的统一管理。
逻辑应用模型是本发明抽象出的应用管理基本单元，每个逻辑应用实体由业务功能程序和资源环境程序组成。例如A应用是部署在物理机上的，那么A应用的实体就包括A应用本身的功能程序及承载功能程序运行的物理机实体及系统和软件环境。
通过上述方法本发明将内容分发网络平台分成逻辑应用层和基础资源层，逻辑应用层在收到应用创建请求后根据创建请求确定应用的实际资源配置需求信息和资源类型信息，然后将实际资源配置需求信息和资源类型信息发送给基础资源层。
应用创建请求至少包括应用基本信息和应用能力需求信息，还可以包括资源类型信息，资源类型信息为可选信息，创建请求中可以不包含该信息，如果不包含该信息，可以在创建过程中由逻辑应用层根据需求自行判断选择。
应用基本信息包括：应用名称、网络协议(Internet Protocol，IP)地址和部署区域等，主要用于描述应用的基本信息，可以根据需求任意定义所需信息，上文只示例性给出了的几种应用基本信息，还可以有应用账号(Identity，ID)等其他信息，本发明对此不作具体限定。
应用能力需求信息包括：应用程序编程接口(Application Programming Interface，API)响应能力、带宽能力、高可用性(High Availability，HA)能力和输入输出(Input/Output，IO)能力等，可以根据需求任意定义所需的应用能力需求信息，上文只给出了几种示例性的应用能力需求信息，对于不同应用可以有其他应用能力需求信息，本发明对此不作具体限制。
资源类型信息包括：物理机(Physical)、虚拟机(Instance)和容器(Docker)。
S102，基础资源层接收到实际资源配置需求信息和资源类型信息，根据实际资源配置需求信息和资源类型信息创建应用的基础资源环境。
本发明基于自定义逻辑应用模型，以能力建模的方式实现对物理机、虚拟机、容器等多种异构技术方案构建的服务进行统一管理。利用物理服务器、虚拟机、公有云主机、容器等异构技术构建内容分发网络，将应用管理服务(业务平面)从资源架构(技术平面)里剥离出来，同时仍然保持各种资源技术的 独特价值、特点和智能。
具体的，如图2所示是图1中步骤S101的具体步骤：
步骤S201，在逻辑应用层上注册应用基本信息、应用能力信息和应用资源类型信息。
在创建应用前，首先需要在CDN系统的逻辑应用层上对各种应用预先进行注册，注册的内容包括应用基本信息、应用能力信息和应用资源类型信息等，比如应用虚拟机A，在逻辑应用层注册应用名称：虚拟机A，网络协议地址：192.168.1.10；子网掩码：255.255.0.0；部署区域：山东电信；应用账号：admin001；虚拟网卡连接方式：桥接；处理性能：8核处理器；内存：16G；存储性能：480G；资源类型信息：虚拟机等内容。
不同的应用在逻辑应用层上有不同的注册信息，这些注册信息可以在创建应该的过程中可以和创建请求中的应用信息进行对比，以验证创建请求，决定是否在系统上创建该应用。
步骤S202，逻辑应用层收到应用创建请求后，查询应用的注册信息，与应用创建请求中的信息对比，进行校验。
当逻辑应用层收到创建应用的请求后，查询要创建的应用在逻辑应用层上预先注册过的注册信息，如上一步注册的应用账号、应用名称、网络协议地址、部署区域等信息，与创建请求中的信息进行对比，如果信息一致，校验通过，可以在系统上继续创建该应用，如果信息不一致，校验失败，停止应用创建过程。
步骤S203，校验通过后逻辑应用层查询应用能力的使用情况和剩余情况，根据查询结果将应用能力需求信息转换为实际资源配置需求信息。
当校验通过后，逻辑应用层查询当前系统中现有应用的应用能力使用情况以及剩余的应用能力，根据查询的结果可知当前系统中还有多少可用的应用能力，结合创建请求中的应用能力需求信息，将应用能力需求信息如虚拟网卡连接方式：桥接；处理性能：8核处理器；内存：16G；存储性能：480G等转换为实际资源配置需求信息。以避免创建请求中应用需求的应用能力大于系统中剩余的应用能力，系统因应用能力不足创建过程出现错误的情况。
步骤S204，当应用创建请求中包含资源类型信息时，逻辑应用层将应用创 建请求中的资源类型信息和实际资源配置需求信息发送给基础资源层。
如果应用已经指定了所需的资源类型，即创建请求中包含资源类型信息，逻辑应用层直接将步骤S203得到的实际资源配置需求和创建请求中的资源类型信息发送给基础资源层，由基础资源层完成后续资源配置过程即可。
步骤S205，当应用创建请求中没有资源类型信息时，逻辑应用层查询配置好的自动创建策略，根据实际资源配置需求和自动创建策略决定部署应用的资源类型信息，然后再将资源类型信息和实际资源配置需求信息发送给基础资源层。
逻辑应用层事先配置有自动创建策略，自动创建策略能够根据当前资源富余情况、现有资源分配情况和应用自身最优资源类型等条件结合实际资源配置需求信息决定部署应用的资源类型信息。当创建请求中只有应用基本信息和应用能力需求信息，而没有资源类型信息时，逻辑应用层查询事先配置好的自动创建策略，结合实际资源配置需求确定部署应用的资源类型信息，然后将实际资源配置需求和资源类型信息发送给基础资源层，由基础资源层完成后续资源配置过程。
本发明的逻辑应用层可以自定义业务能力模型和创建策略，完成多种技术平台下的自动化部署，不同的应用之间可以共享或者独立配置，配置方式灵活。
具体的，如图3所示是图1中步骤S102的具体步骤：
步骤S301，基础资源层将同类技术统一抽象为一种资源类型。比如物理机(Physical)、虚拟机(Instance)或者容器(Docker)等，每种资源类型下具体又包括不同驱动程序，比如物理机管理系统驱动(Real Server Manager)，私有云管理系统驱动(Private Cloud)，云主机管理系统驱动(EC2)和Kubernetes管理系统驱动等，本发明在此不再一一列举。
步骤S302，根据资源类型信息找到对应的资源类型。
基础资源层收到实际资源配置需求信息和资源类型信息后根据资源类型信息在基础资源成找到对应的资源类型。
步骤S303，根据资源类型和实际资源配置需求信息找到对应的驱动程序。
在基础资源层找到对应资源类型后，在相应的资源类型下根据实际资源配置需求选择合适合的驱动程序。
步骤S304，通过驱动程序结合实际资源配置需求信息创建应用的基础资源环境。
本发明采用分层管理，简化运维，仅需要维护好内部服务的资源情况，保障资源运行良好及富余情况。而无需过多关注运行的具体应用内容及应用功能。
本发明还提供一种在异构资源上构建内容分发网络平台的系统1的实施方式，如图4所示，包括：逻辑应用层100和基础资源层200。
逻辑应用层100用于在收到应用创建请求后根据创建请求确定应用的实际资源配置需求信息和资源类型信息，然后将实际资源配置需求信息和资源类型信息发送给基础资源层200。
基础资源层200用于根据实际资源配置需求信息和资源类型信息创建应用的基础资源环境。
在创建应用前，首先需要在逻辑应用层100上对各种应用预先进行注册，注册的内容包括应用基本信息、应用能力信息和应用资源类型信息等。逻辑应用层100收到的应用创建请求中至少包括应用基本信息和应用能力需求信息，还可以包括资源类型信息。应用基本信息包括：应用名称，网络协议地址和部署区域中的一种或几种；应用能力需求信息包括：API响应能力，带宽能力，高可用性能力和输入输出能力中的一种或几种；资源类型信息包括：物理机、虚拟机和容器中的一种或几种。收到应用创建请求后，逻辑应用层100对创建请求中的应用基本信息进行验证，验证通过后将创建请求中的应用能力信息转换为实际资源配置需求信息，然后将实际资源配置需求信息和资源类型信息发送给基础资源层200。基础资源层200将同类技术抽象为一种资源类型，每种资源类型下具体又包括不同驱动程序。基础资源层200根据收到的资源类型信息找到对应资源类型，然后在对应的资源类型下根据实际资源配置需求确定合适的的驱动程序，最后通过驱动程序按照实际资源配置需求信息创建逻辑应用的基础资源环境，依据应用需要完成应用的部署与配置。
具体的，如图5所示是图4中在异构资源上构建内容分发网络平台的系统1的具体结构。
逻辑应用层100包括：逻辑应用管理API模块101和业务功能模块102。
基础资源层200包括：统一资源管理API模块201、技术抽象层202和技术驱动层203。
逻辑应用管理API模块101用于管理业务功能模块；业务功能模块102用于注册应用信息，通过逻辑应用管理API模块对创建请求中的应用基本信息进行校验，校验通过后根据创建请求中的应用能力需求信息确定应用的实际资源配置需求信息。
统一资源管理API模块201用于管理技术抽象层和技术驱动层；技术抽象层202用于将同类技术统一抽象为一种资源类型，根据资源类型信息，通过统一资源管理API模块找到对应资源类型；技术驱动层203用于根据技术抽象层的资源类型和实际资源配置需求信息找到对应的驱动程序，然后驱动程序结合实际资源配置需求信息通过统一资源管理API模块创建应用的基础资源环境。
本发明采用分层管理，简化运维，仅需要维护好内部服务的资源情况，保障资源运行良好及富余情况。而无需过多关注运行的具体应用内容及应用功能。
如图6所示是图5中逻辑应用层100的具体结构。
逻辑应用管理API模块101包括：应用周期管理API(Application Lifecycle)1011、应用能力管理API(Application Ability Inventory)1012、应用信息管理API(Application information)1013和应用策略管理API(Application Strategy)1014。
务功能模块102包括：应用信息管理子模块(App Manager)1021、应用能力管理子模块(App Ability Mapper)1022和应用创建策略子模块(Creation Strategy)1023。
应用周期管理API 1011用于提供应用创建请求，具体包括应用的查找、删除、增加、修改及迁移恢复；应用能力管理API 1012用于查询和统计应用能力的使用情况及剩余情况；应用信息管理API 1013用于查询应用基本信息；应用策略管理API 1014用于配置和查询自动创建策略。
应用信息管理子模块1021用于注册应用基本信息、应用能力信息和应用资源类型信息，并接收应用周期管理API 1011发来的应用创建请求，然后通过应用信息管理API 1013查询应用的注册信息，与应用创建请求中的信息对比，进行校验；应用能力管理子模块1022用于在校验通过后，通过应用能力管理API 1012查询应用能力管理API 1012统计的应用能力的使用情况及剩余情况，然后根据查询结果将应用能力需求信息转换为实际资源配置需求信息；应用创建策略子模块1023用于当应用创建请求中没有资源类型信息时，通过应用策略管理API 1014查询配置好的自动创建策略，根据自动创建策略和实际资源配置需求决定部署应用的资源类型信息。
创建应用前首先通过应用信息管理子模块1021在逻辑应用层100上注册应用基本信息、应用能力信息和应用资源类型信息。通过应用周期管理API 1011向应用信息管理子模块1021发送应用创建请求后，应用信息管理子模块1021通过应用信息管理API 1013查询应用的注册信息，与应用创建请求中的信息对比，进行校验。如果信息不一致，校验失败，停止应用创建过程；如果信息一致，校验通过，应用能力管理子模块1022通过应用能力管理API 1012查询应用能力管理API 1012自身统计的应用能力的使用情况及剩余情况，然后根据查询结果将应用能力需求信息转换为实际资源配置需求信息；当应用创建请求中没有资源类型信息时应用创建策略子模块1023通过应用策略管理API 1014查询配置好的自动创建策略，根据自动创建策略和实际资源配置需求决定部署应用的资源类型信息。
本发明在逻辑应用层可以自定义业务能力模型和创建策略，完成多种技术平台下的自动化部署，不同的应用之间可以共享或者独立配置，配置方式灵活。
如图7所示是图5中基础资源层200的具体结构。
统一资源管理API模块201包括：资源周期管理API(Resource Lifecycle)2011和资源清单管理API(Resource Inventory)2012。资源周期管理API 2011用于管理基础资源的生命周期，包括查询、删减、增加和修改，驱动程序结合实际资源配置需求信息通过资源周期管理API创建应用的基础资源环境；资源清单管理API 2012用于查询和统计不同类型的资源使用情况和剩余情况，根据查询结果和资源类型信息在技术抽象层找到对应的资源类型。
技术抽象层202的资源类型包括：物理机2021、虚拟机2022和容器2023。
技术驱动层203具体包括：物理机管理系统驱动2031，私有云管理系统驱动2032，云主机管理系统驱动2033和Kubernetes管理系统驱动2034。
基础资源层200收到实际资源配置需求信息和资源类型信息后，通过资源 清单管理API 2012查询和统计技术抽象层202中不同类型的资源使用情况和剩余情况，根据查询结果和资源类型信息在技术抽象层找到对应的资源类型。然后在对应的资源类型下根据实际资源配置需求确定合适的驱动程序，该驱动程序，按照实际资源配置需求信息通过资源周期管理API 2011完成应用基础资源环境的创建，依据应用需要完成应用的部署与配置。
本发明在基础资源层采用两层抽象驱动的模式对资源进行统一管理，可以实现在不变动原有结构的基础上，快速接纳物理机、虚拟机等新的技术方案。只需要在资源的技术驱动层中完成功能对接既可以纳入系统管理，能够快速引入新的技术架构。
上述本发明实施例序号仅仅为了描述，不代表实施例的优劣。
以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。本领域普通技术人员在不付出创造性的劳动的情况下，即可以理解并实施。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到各实施方式可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件。基于这样的理解，上述技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品可以存储在计算机可读存储介质中，如ROM/RAM、磁碟、光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行各个实施例或者实施例的某些部分所述的方法。
以上所述仅为本发明的较佳实施例，并不用以限制本发明，凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (14)

  1. 一种在异构资源上构建内容分发网络平台的方法，其特征在于，所述内容分发网络平台包括逻辑应用层和基础资源层，所述构建方法包括以下步骤：
    所述逻辑应用层在收到应用创建请求后根据所述创建请求确定所述应用的实际资源配置需求信息和资源类型信息，然后将所述实际资源配置需求信息和所述资源类型信息发送给基础资源层；
    所述基础资源层接收到所述实际资源配置需求信息和所述资源类型信息，根据所述实际资源配置需求信息和所述资源类型信息创建所述应用的基础资源环境。
  2. 如权利要求1所述的在异构资源上构建内容分发网络平台的方法，其特征在于，所述逻辑应用层在收到应用创建请求后根据所述创建请求确定所述应用的实际资源配置需求信息和资源类型信息，然后将所述实际资源配置需求信息和所述资源类型信息发送给基础资源层的步骤具体为：
    在所述逻辑应用层上注册应用信息，然后对所述创建请求中的应用基本信息进行校验，校验通过后根据所述创建请求中的应用能力需求信息确定所述应用的实际资源配置需求信息，然后将所述实际资源配置需求信息和所述资源类型信息发送给基础资源层。
  3. 如权利要求2所述的在异构资源上构建内容分发网络平台的方法，其特征在于所述应用创建请求至少包括应用基本信息和应用能力需求信息，还包括资源类型信息；
    所述应用基本信息包括：应用名称，网络协议地址和部署区域中的一种或几种；
    所述应用能力需求信息包括：API响应能力，带宽能力，高可用性能力和输入输出能力中的一种或几种；
    所述资源类型信息包括：物理机、虚拟机和容器中的一种或几种。
  4. 如权利要求3所述的在异构资源上构建内容分发网络平台的方法，其特 征在于，所述逻辑应用层在收到应用创建请求后根据所述创建请求确定所述应用的实际资源配置需求信息和资源类型信息，然后将所述创建信息和所述资源类型信息发送给基础资源层的具体步骤包括：
    在所述逻辑应用层上注册应用基本信息、应用能力信息和应用资源类型信息；
    所述逻辑应用层收到应用创建请求后，查询所述应用的注册信息，与所述应用创建请求中的信息对比，进行校验；
    校验通过后所述逻辑应用层查询应用能力的使用情况和剩余情况，根据查询结果将应用能力需求信息转换为实际资源配置需求信息；
    当所述应用创建请求中包含所述资源类型信息时，所述逻辑应用层将所述应用创建请求中的资源类型信息和所述实际资源配置需求信息发送给所述基础资源层；
    当所述应用创建请求中没有所述资源类型信息时，所述逻辑应用层查询配置好的自动创建策略，根据所述实际资源配置需求和自动创建策略决定部署所述应用的资源类型信息，然后再将所述资源类型信息和实际资源配置需求信息发送给所述基础资源层。
  5. 如权利要求4所述的在异构资源上构建内容分发网络平台的方法，其特征在于，所述自动创建策略包括当前资源富余情况、现有资源分配情况和应用自身最优资源类型。
  6. 如权利要求5所述的在异构资源上构建内容分发网络平台的方法，其特征在于，所述基础资源层根据所述实际资源配置需求信息和所述资源类型信息创建所述应用的基础资源环境的具体步骤包括：
    所述基础资源层将同类技术统一抽象为一种资源类型，根据所述资源类型信息找到对应的资源类型，然后根据所述资源类型和实际资源配置需求信息找到对应的驱动程序，最后通过所述驱动程序结合实际资源配置需求信息创建所述应用的基础资源环境。
  7. 一种在异构资源上构建内容分发网络平台的系统，其特征在于，包括：
    逻辑应用层，用于在收到应用创建请求后根据所述创建请求确定所述应用的实际资源配置需求信息和资源类型信息，然后将所述实际资源配置需求信息和所述资源类型信息发送给基础资源层；
    基础资源层，用于根据所述实际资源配置需求信息和所述资源类型信息创建应用的基础资源环境。
  8. 如权利要求7所述的在异构资源上构建内容分发网络平台的系统，其特征在于，所述逻辑应用层包括：
    逻辑应用管理API模块，用于管理业务功能模块；
    业务功能模块，用于注册应用信息，通过逻辑应用管理API模块对所述创建请求中的应用基本信息进行校验，校验通过后根据所述创建请求中的应用能力需求信息确定所述应用的实际资源配置需求信息。
  9. 如权利要求8所述的在异构资源上构建内容分发网络平台的系统，其特征在于，所述逻辑应用管理API模块包括：
    应用周期管理API，用于提供应用创建请求，具体包括应用的查找、删除、增加、修改及迁移恢复；
    应用能力管理API，用于查询和统计应用能力的使用情况及剩余情况；
    应用信息管理API，用于查询应用基本信息；
    应用策略管理API，用于配置和查询自动创建策略。
  10. 如权利要求9所述的在异构资源上构建内容分发网络平台的系统，其特征在于，所述业务功能模块包括：
    应用信息管理子模块，用于注册应用基本信息、应用能力信息和应用资源类型信息，并接收所述应用周期管理API发来的应用创建请求，然后通过所述应用信息管理API查询所述应用的注册信息，与所述应用创建请求中的信息对比，进行校验；
    应用能力管理子模块，用于在校验通过后，通过所述应用能力管理API查询所述应用能力管理API统计的应用能力的使用情况及剩余情况，然后根据查询结果将应用能力需求信息转换为实际资源配置需求信息；
    应用创建策略子模块，用于当所述应用创建请求中没有所述资源类型信息时，通过应用策略管理API查询配置好的自动创建策略，根据所述自动创建策略和所述实际资源配置需求决定部署所述应用的资源类型信息。
  11. 如权利要求10所述的在异构资源上构建内容分发网络平台的系统，其特征在于，所述基础资源层包括：
    统一资源管理API模块，用于管理技术抽象层和技术驱动层；
    技术抽象层，用于将同类技术统一抽象为一种资源类型，根据所述资源类型信息，通过统一资源管理API模块找到对应资源类型；
    技术驱动层，用于根据所述技术抽象层的资源类型和实际资源配置需求信息找到对应的驱动程序，然后所述驱动程序结合实际资源配置需求信息通过统一资源管理API模块创建所述应用的基础资源环境。
  12. 如权利要求11所述的在异构资源上构建内容分发网络平台的系统，其特征在于，所述统一资源管理API模块包括：
    资源周期管理API，用于管理基础资源的生命周期，包括查询、删减、增加和修改，所述驱动程序结合实际资源配置需求信息通过资源周期管理API创建所述应用的基础资源环境；
    资源清单管理API，用于查询和统计不同类型的资源使用情况和剩余情况，根据查询结果和资源类型信息在所述技术抽象层找到所述对应的资源类型。
  13. 如权利要求12所述的在异构资源上构建内容分发网络平台的系统，其特征在于，所述技术抽象层的资源类型包括：物理机、虚拟机和容器。
  14. 如权利要求11所述的在异构资源上构建内容分发网络平台的系统，其特征在于，所述技术驱动层具体包括：物理机管理系统驱动，私有云管理系统驱动，云主机管理系统驱动和Kubernetes管理系统驱动中的一种或几种。
PCT/CN2017/086770 2017-05-08 2017-06-01 在异构资源上构建内容分发网络平台的方法和系统 WO2018205325A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP17909038.6A EP3554010B1 (en) 2017-05-08 2017-06-01 Method and system for use in constructing content delivery network platform on heterogeneous resources
US16/463,937 US11102089B2 (en) 2017-05-08 2017-06-01 Method and system for constructing content delivery network platform on heterogeneous resources

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710316602.1A CN107135103B (zh) 2017-05-08 2017-05-08 在异构资源上构建内容分发网络平台的方法和系统
CN201710316602.1 2017-05-08

Publications (1)

Publication Number Publication Date
WO2018205325A1 true WO2018205325A1 (zh) 2018-11-15

Family

ID=59732413

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/086770 WO2018205325A1 (zh) 2017-05-08 2017-06-01 在异构资源上构建内容分发网络平台的方法和系统

Country Status (4)

Country Link
US (1) US11102089B2 (zh)
EP (1) EP3554010B1 (zh)
CN (1) CN107135103B (zh)
WO (1) WO2018205325A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111327681A (zh) * 2020-01-21 2020-06-23 北京工业大学 一种基于Kubernetes的云计算数据平台构建方法
CN111813419A (zh) * 2020-07-09 2020-10-23 浪潮云信息技术股份公司 一种基于kubernetes声明式管理裸机生命周期的方法
CN112698924A (zh) * 2021-03-23 2021-04-23 杭州太美星程医药科技有限公司 一种临床试验电子数据采集系统及其运行方法
US11914755B2 (en) 2021-02-04 2024-02-27 International Business Machines Corporation Cluster resource signature verification

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109962940B (zh) * 2017-12-14 2023-10-03 绍兴数智科技有限公司 一种基于云平台的虚拟化实例调度系统及调度方法
TWI641279B (zh) * 2017-12-15 2018-11-11 財團法人工業技術研究院 行動邊緣平台伺服器及其使用者設備內容之遷移管理方法
CN109885377B (zh) * 2018-11-23 2023-04-28 中国银联股份有限公司 统一资源调度协调器及其创建虚拟机和/或容器的方法、统一资源调度系统
CN110430442B (zh) * 2019-08-08 2021-11-26 赛尔网络有限公司 播放方法、装置及系统
CN110619185B (zh) * 2019-09-25 2020-09-04 北京世冠金洋科技发展有限公司 一种数据处理方法、装置及电子设备
CN110955537B (zh) * 2019-11-25 2022-11-04 北京奇艺世纪科技有限公司 一种物理机纳管方法及装置
US11281607B2 (en) * 2020-01-30 2022-03-22 Red Hat, Inc. Paravirtualized cluster mode for legacy APICs
CN111708632A (zh) * 2020-05-19 2020-09-25 中国人民财产保险股份有限公司 一种云资源管理方法及装置
CN112015520B (zh) * 2020-09-14 2024-06-07 支付宝(杭州)信息技术有限公司 数据上传系统及方法
CN112181648B (zh) * 2020-09-22 2022-05-31 中国科学院软件研究所 一种配置驱动的轻量级混合基础设施平台及数据处理方法
CN113010410A (zh) * 2020-12-08 2021-06-22 云智慧（北京）科技有限公司 一种基于骨干网对cdn性能的监控和评测方法和系统
CN113312337A (zh) * 2021-06-24 2021-08-27 中国农业银行股份有限公司 应用配置模型的构建方法和装置
US11995420B2 (en) 2021-08-19 2024-05-28 Red Hat, Inc. Generating a build process for building software in a target environment
CN116016498A (zh) * 2021-10-21 2023-04-25 中兴通讯股份有限公司 Cdn网元容器配置方法、读写方法、装置、设备及存储介质
CN114389955B (zh) * 2022-03-02 2023-08-15 中国电子科技集团公司第十四研究所 嵌入式平台异构资源池化管理方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101388785A (zh) * 2007-09-11 2009-03-18 中国电信股份有限公司 内容分发网络的资源抽象方法和业务开通方法
CN101764810A (zh) * 2009-12-25 2010-06-30 中国科学院声学研究所 一种跨域业务提供的协商方法和系统
WO2012034397A1 (zh) * 2010-09-15 2012-03-22 中兴通讯股份有限公司 一种实现cdn互连的方法和系统
CN102624684A (zh) * 2011-02-01 2012-08-01 中兴通讯股份有限公司 一种业务集成与交付系统及方法

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7558864B2 (en) * 2004-01-27 2009-07-07 International Business Machines Corporation Method, system and product for identifying, reserving, and logically provisioning resources in provisioning data processing systems
US7840398B2 (en) * 2006-03-28 2010-11-23 Intel Corporation Techniques for unified management communication for virtualization systems
CN101340368B (zh) * 2008-08-12 2013-02-06 北京航空航天大学 基于WSDM的Web服务分布式管理系统和管理方法
CN102427473B (zh) * 2011-11-28 2014-03-05 中国联合网络通信集团有限公司 跨平台资源构建方法及系统
WO2013101217A1 (en) * 2011-12-30 2013-07-04 Intel Corporation Technology abstraction layer
CN102655532B (zh) * 2012-04-18 2014-10-22 上海和辰信息技术有限公司 分布式异构虚拟资源集成管理方法及系统
US8826316B2 (en) * 2012-10-22 2014-09-02 The Nielsen Company (Us), Llc Systems and methods for configuring media devices utilizing audio codes or signatures
CN103885833B (zh) * 2012-12-20 2017-06-20 中国移动通信集团公司 一种资源管理方法和系统
CN105094980A (zh) * 2014-05-23 2015-11-25 北京云巢动脉科技有限公司 一种虚拟机内存的动态调整系统
CN103970908A (zh) * 2014-05-28 2014-08-06 浪潮电子信息产业股份有限公司 一种虚拟机模板ivf存储方法
CN105577714B (zh) * 2014-10-13 2019-12-13 中兴通讯股份有限公司 基于软件定义网络实现内容分发网络的方法及系统
US10102108B2 (en) * 2015-01-15 2018-10-16 Mobilize.Net Corporation Injected instrumentation application monitoring and management
CN104657918A (zh) * 2015-01-21 2015-05-27 胡宝清 一种区域资源环境数据共享和综合服务平台
CN105578482B (zh) * 2015-12-22 2019-04-09 重庆邮电大学 一种蜂窝异构网络资源分配方法
CN106230889B (zh) * 2016-07-15 2019-12-17 福建天泉教育科技有限公司 移动应用业务组件资源管理方法及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101388785A (zh) * 2007-09-11 2009-03-18 中国电信股份有限公司 内容分发网络的资源抽象方法和业务开通方法
CN101764810A (zh) * 2009-12-25 2010-06-30 中国科学院声学研究所 一种跨域业务提供的协商方法和系统
WO2012034397A1 (zh) * 2010-09-15 2012-03-22 中兴通讯股份有限公司 一种实现cdn互连的方法和系统
CN102624684A (zh) * 2011-02-01 2012-08-01 中兴通讯股份有限公司 一种业务集成与交付系统及方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3554010A4 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111327681A (zh) * 2020-01-21 2020-06-23 北京工业大学 一种基于Kubernetes的云计算数据平台构建方法
CN111813419A (zh) * 2020-07-09 2020-10-23 浪潮云信息技术股份公司 一种基于kubernetes声明式管理裸机生命周期的方法
CN111813419B (zh) * 2020-07-09 2024-04-16 浪潮云信息技术股份公司 一种基于kubernetes声明式管理裸机生命周期的方法
US11914755B2 (en) 2021-02-04 2024-02-27 International Business Machines Corporation Cluster resource signature verification
CN112698924A (zh) * 2021-03-23 2021-04-23 杭州太美星程医药科技有限公司 一种临床试验电子数据采集系统及其运行方法

Also Published As

Publication number Publication date
US20200389372A1 (en) 2020-12-10
CN107135103B (zh) 2021-03-19
EP3554010B1 (en) 2021-07-21
EP3554010A1 (en) 2019-10-16
CN107135103A (zh) 2017-09-05
EP3554010A4 (en) 2019-11-06
US11102089B2 (en) 2021-08-24

Similar Documents

Publication Publication Date Title
WO2018205325A1 (zh) 在异构资源上构建内容分发网络平台的方法和系统
US11429408B2 (en) System and method for network function virtualization resource management
WO2018024059A1 (zh) 一种虚拟化网络中业务部署的方法和装置
US10713071B2 (en) Method and apparatus for network function virtualization
CN106375176B (zh) 一种物理机接入云平台的方法
WO2017113201A1 (zh) 一种网络服务的生命周期管理方法及设备
WO2018149272A1 (zh) 基于sla的资源分配方法和nfvo
WO2018058579A1 (zh) 网络切片的管理方法及管理单元
WO2017080391A1 (zh) 一种网络服务部署方法和装置
US20190392150A1 (en) Network-accessible computing service for micro virtual machines
WO2018006676A1 (zh) 加速资源处理方法、装置及网络功能虚拟化系统
US20220004410A1 (en) Method For Deploying Virtual Machine And Container, And Related Apparatus
US9619429B1 (en) Storage tiering in cloud environment
CN103930873A (zh) 用于虚拟化环境的基于动态策略的接口配置
CN103957237A (zh) 一种弹性云的体系结构
WO2019174000A1 (zh) 用于业务管理的方法和装置
CN113900773B (zh) 一种基于国产平台虚拟机和容器的超融合调度方法
CN106134141A (zh) 一种更新网络服务描述器nsd的方法及装置
CN106209402A (zh) 一种虚拟网络功能的伸缩方法和设备
CN103685608A (zh) 一种自动配置安全虚拟机ip地址的方法及装置
WO2016183799A1 (zh) 一种硬件加速方法以及相关设备
CN112698838B (zh) 多云容器部署系统及其容器部署方法
WO2016183832A1 (zh) 一种网络业务实例化的方法及设备
US20220350637A1 (en) Virtual machine deployment method and related apparatus
WO2020181734A1 (zh) 一种管理网络地址转换nat网关的方法及服务器

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: 17909038

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2017909038

Country of ref document: EP

Effective date: 20190712

NENP Non-entry into the national phase

Ref country code: DE