WO2017067484A1 - Système et procédé de planification de centre de données de virtualisation - Google Patents

Système et procédé de planification de centre de données de virtualisation Download PDF

Info

Publication number
WO2017067484A1
WO2017067484A1 PCT/CN2016/102759 CN2016102759W WO2017067484A1 WO 2017067484 A1 WO2017067484 A1 WO 2017067484A1 CN 2016102759 W CN2016102759 W CN 2016102759W WO 2017067484 A1 WO2017067484 A1 WO 2017067484A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
node
resource
standby
primary
Prior art date
Application number
PCT/CN2016/102759
Other languages
English (en)
Chinese (zh)
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 WO2017067484A1 publication Critical patent/WO2017067484A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • 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/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • 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
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • 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/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources

Definitions

  • the present invention relates to the field of cloud computing and data center virtualization technologies, and more particularly to a virtualized data center scheduling system and method.
  • data center virtualization is the basic trend of service-oriented data centers, and virtualized data centers have unified servers. Operational flexibility, power savings, space savings, disaster recovery, high availability and many other advantages.
  • SFC Service Function Chaining
  • an embodiment of the present invention provides a virtualized data center scheduling system and method, which can maintain normal operation of a service node in a service function chain, thereby providing a high reliability service for a data center.
  • an embodiment of the present invention provides a virtualized data center scheduling system, including:
  • Service definition and orchestration modules Service definition and orchestration modules, data center management platforms, and network controllers;
  • the service definition and orchestration module is configured to provide a service interface, a resource template, and a reliability requirement level definition interface, and receive a service orchestration policy generation service function chain, where the service reliability requirement level includes an abnormal alarm, and a single service node automatically recovers Differentiated service active and standby nodes and equal service active and standby nodes;
  • the data center management platform is configured to allocate a resource node of the data center according to the defined service type and the resource template, and after determining that the service node is abnormal, scheduling resource recovery of the data center according to a service reliability requirement level.
  • the network controller is configured to formulate a packet forwarding path of the service node.
  • an embodiment of the present invention provides a virtualized data center scheduling method, where the method includes:
  • the service reliability requirement level includes an abnormal alarm, a single service node automatic recovery, a differentiated service active standby node, and an equalization Serving the active and standby nodes;
  • a packet forwarding path of the service node is formulated.
  • a virtualized data center scheduling system and method includes: a service definition and orchestration module, a data center management platform, and a network controller, and provides services through a service definition and orchestration module.
  • the data center management platform allocates a resource node of the data center according to the defined service type and the resource template, and after determining that the service node is abnormal, scheduling the resource of the data center according to the service reliability requirement level to restore the service.
  • the network controller formulates a packet forwarding path of the service node, so that when the service node is abnormal, the service node can be restored according to the service type, resource template, and service reliability requirement level defined by the user, thereby ensuring Service section of the functional service chain Normal operation, high reliability and improved service data center.
  • FIG. 1 is a functional block diagram of a virtualized data center scheduling system according to an embodiment of the present invention
  • FIG. 2 is a functional block diagram of a second embodiment of a virtualized data center scheduling system according to the present invention.
  • FIG. 3 is a functional block diagram of a third embodiment of a virtualized data center scheduling system according to the present invention.
  • FIG. 4 is a schematic flowchart of Embodiment 1 of a method for scheduling a virtualized data center according to the present invention.
  • the data center refers to transmitting, accelerating, displaying, calculating, and storing data information on the internet infrastructure based on virtualization, that is, multiple virtual machines can be run on one computer, or multiple Environments share the resources of this computer. Different virtual machines can run different operating systems and multiple applications on the same computer.
  • the system according to the embodiment of the present invention aims to solve the technical problem of how to maintain the normal operation of the service node of the service function chain to provide a highly reliable service for the data center in the prior art.
  • FIG. 1 is a functional block diagram of a virtualized data center scheduling system according to an embodiment of the present invention. As shown in FIG. 1, the system includes: a service definition and orchestration module 10, a data center management platform 20, and a network controller 30;
  • the service definition and orchestration module 10 is configured to provide a service interface, a resource template, and a reliability requirement level definition interface, and receive a service orchestration policy generation service function chain, where the service reliability requirement level includes an abnormal alarm, and a single service node automatically Recovery, differentiated service primary and secondary nodes and equal service active and standby nodes;
  • the service definition and orchestration module 10 accepts a tenant or a user to define an interface according to a service type, a resource template, and a reliability requirement level provided by the virtualized data center scheduling system, and customizes a service orchestration policy to determine a requirement.
  • the service reliability requirement level generates a service function chain, wherein the service reliability requirement level includes: an abnormal alarm, a single service node automatic recovery, a differentiated service active standby node, and an equal service active standby node.
  • the data center management platform 20 is configured to allocate a resource generation service node of the data center according to the defined service type and the resource template, and after determining that the service node is abnormal, scheduling the resource of the data center according to the service reliability requirement level. Recovering the service node;
  • the data center management platform 20 allocates a resource generating service node according to the defined service type and the resource template to provide a guarantee for the service node to process the service service, and after determining the abnormality of the service node, according to the service reliability.
  • the demand level schedules resources of the data center to recover the service node.
  • the network controller 30 is configured to formulate a packet forwarding path of the serving node.
  • the network of the virtualized data center scheduling system generally adopts a control plane and a forwarding plane separation scheme, and the network controller 30 uniformly controls the forwarding plane device to formulate a packet forwarding policy of the service node.
  • a virtualized data center scheduling system includes: a service definition and orchestration module, a data center management platform, and a network controller, and provides a service type, a resource template, and a reliability requirement level through a service definition and orchestration module.
  • the definition interface, the receiving service orchestration policy generates a service function chain, and the service reliability requirement level includes an abnormal alarm, a single service node automatic recovery, a differentiated service active standby node, and an equal service active standby node, and the data center management platform is defined according to the definition
  • the service type and the resource template are allocated to the resource generation service node of the data center.
  • the resource of the data center is scheduled to be restored according to the service reliability requirement level, and the network controller formulates the service.
  • the packet forwarding path of the node so that when the service node is abnormal, the service node can be restored according to the service type, resource template, and service reliability requirement level defined by the user, thereby ensuring the normal operation of the service node of the functional service chain. , increased the number High reliability and service center.
  • the data center management platform 20 includes: a device resource management platform 210 and a virtualization service management platform 220. among them,
  • the device resource management platform 210 is configured to allocate, according to the defined service type and the resource template, the hardware device resource of the data center, manage and maintain the hardware device resource, provide performance metric data of the hardware device resource, and determine the Whether the service node has an exception;
  • the virtualization service management platform 220 is configured to allocate a virtualized resource generation service node of the data center according to the defined service type and the resource template, and after determining that the service node is abnormal, scheduling the service according to the service reliability requirement level.
  • the virtualized resource of the data center recovers the service node
  • the data center management platform 20 includes: a device resource management platform 210 and a virtualization service management platform 220, wherein the device resource management platform 210 is configured to manage and maintain data center hardware device resources, and provide hardware device resource performance.
  • Metric data such as hardware performance indicators such as storage, calculation, and network of the computer or server corresponding to the service node. According to the performance metric data, the running status of the service node can be detected to determine whether the service node is abnormal, and the hardware device resource is abnormal. A fault alarm is provided.
  • the virtualization service management platform 220 is configured to allocate a virtualized resource generation service node of the data center according to the defined service type and the resource template, and after determining that the service node is abnormal, according to the service reliability requirement level,
  • the service node provides virtualized resource management and scheduling based on hardware device resources, including computing, storage, and network virtualization resources to recover the service node.
  • FIG. 3 is a functional block diagram of a third embodiment of a virtualized data center scheduling system according to the present invention. As shown in FIG. 3, the system further includes: a service detecting module 40;
  • the service detection module 40 is configured to detect, when the service service chain has a service primary node and a service standby node, consistency of service status of the service primary node and the service standby node, and timeliness of receiving data packets, Determining whether the service primary node and the service standby node are abnormal.
  • the service detecting module 40 records a mapping relationship between the service master node and the service standby node when the service function node has a service master node and a service standby node, and the mapping relationship may be a service master node.
  • the service master node and the service standby node together form a service set, and detect the consistency of service status of the active and standby service nodes of the service set. That is, whether the data processed by the service master node and the service standby node are consistent, so as to determine whether the service master node and the service standby node service need to be synchronized, and also detect the timeliness of receiving the data packet.
  • the service detection module 40 receives the service master at time T1.
  • Node data packet X receives the service standby node data packet X at time T2, only when the time difference between T1 and T2 is less than the limit When the value of the service node and the master node serving standby normal, abnormal and vice versa. It is determined whether there is a delay, so that it can be determined whether the service primary node and the service standby node are abnormal.
  • the service detecting module 40 is further configured to:
  • the service detecting module 40 determines that the service primary node is abnormal, in order to restore the service as soon as possible, the service The service detection module 40 is further configured to re-determine the relationship between the service master node and the service standby node.
  • the original service standby node may be the service master node, and the original service master node is the service standby node to ensure uninterrupted service.
  • the system further includes: a service backup module 50;
  • the service backup module 50 is configured to: if the service primary node and the service standby node have different service states, determine that the service standby node needs to synchronize with the service primary node, and synchronize the memory of the service primary node. And the image file to the service standby node.
  • the service detection module 40 detects that the service status of the service primary node and the service standby node is inconsistent, it is determined that the service standby node needs to synchronize with the service primary node, and the service detection module 40 triggers synchronization.
  • the request to the service backup module 50, the service backup module 50 synchronizes the primary node memory and the image file to the service standby node in an incremental manner, so that the service active and standby nodes synchronize to work non-periodically, saving data center resources and minimizing It affects the processing power of the service master node.
  • the service backup module 50 is further configured to create a snapshot storage according to a preset time interval. If a remote disaster recovery data center exists, the service standby node is synchronized according to a preset time interval. Mirror the file to the remote disaster recovery data center.
  • the service backup module 50 is further configured to create a snapshot storage according to a certain time interval, and the interval time may be specifically set according to the situation, and the image file of the standby node is synchronously synchronized to the disaster recovery data center to ensure data.
  • the data security and reliability of the center If there is a disaster recovery data center, the disaster recovery data center can perform health status monitoring and function switching on the data center. When a system stops working due to an accident (such as a fire, an earthquake, etc.), The entire system can be switched to another location so that the system functions can continue to function normally.
  • the virtualization service management platform 220 is configured to, after determining that the service node is abnormal, scheduling the virtualized resource of the data center to restore the service node according to a service reliability requirement level. ,Refers to:
  • the virtualization service management platform 220 is configured to generate an alarm prompt after determining that the service node is abnormal, when the service reliability requirement level is abnormal.
  • the service node When the service reliability requirement level is automatically restored by the single service node, after determining that the service node is abnormal, the service node is restored according to the single service node recovery policy;
  • the point and the service standby node After determining that the service standby node is abnormal, the point and the service standby node recover the service standby node according to the single service node recovery policy, and complete synchronization with the service primary node, and after determining that the service primary node is abnormal, switch
  • the original service standby node is the service primary node, and the original service primary node is the service standby node, and the original service primary node is restored according to the single service node recovery policy.
  • the virtualization service management platform 220 is configured to detect the service node by using the hardware performance metric data of the service node when the service reliability requirement level is abnormal, and generate an alarm prompt when the service is unavailable. An exception that can be handled manually by a system administrator or related user.
  • the virtualization service management platform 220 is configured to perform a restart on the service node according to the hardware device resource performance metric data provided by the device resource management platform 210 when the service reliability requirement level is automatically restored by the single service node. Migration or rebuild operation.
  • the virtualization service management platform 220 is configured to generate a service primary node and a service standby node for the service node when the service reliability requirement level is a differentiated or equal service primary standby node, after determining that the service standby node is abnormal Performing a restart, migration, or reconstruction operation on the service node according to the hardware device resource performance metric data provided by the device resource management platform 210 to restore the service standby node, and completing synchronization to the service primary node, in determining the After the service master node is abnormal, the original service standby node is the service master node, and the original service master node is the service standby node, and the service node is restarted and migrated according to the hardware device resource performance metric data provided by the device resource management platform 210. Or the rebuild operation restores the original service master node.
  • the single service node recovery strategy includes:
  • the service node storage resource is abnormal, causing the service node image file to use abnormality, if there is a snapshot resource, attempting to reconstruct the service node with the latest snapshot of the service node, or when there is no snapshot resource, then virtualizing The service management platform reconstructs the service node according to the virtual resource template of the service node.
  • the performance metric data may reflect a specific abnormality, such as a storage exception, a calculation abnormality, or a network abnormality.
  • a specific abnormality such as a storage exception, a calculation abnormality, or a network abnormality.
  • the virtualization service management platform 220 attempts to reconstruct the service node with the latest snapshot of the service node. If there is no snapshot resource, the virtualization service management platform 220 reconstructs the service node according to its virtual resource template.
  • the virtualization service management platform is configured to: when the service reliability requirement level is a difference or an equal service primary standby node, after the service primary node and the service standby node are generated for the service node, further configured to:
  • the service reliability requirement level is a differentiated service primary and secondary node
  • different virtual resources are allocated to the service primary node and the service standby node, and the virtual resources are distributed on different hardware devices;
  • the service reliability requirement level is an equal service primary and secondary node
  • the same virtual resource is allocated to the service primary node and the service standby node, and the virtual resources are distributed on different hardware devices.
  • the virtualization service management platform 220 allocates different virtual resources, which are different from the service primary node and the service standby node, and the service standby node
  • the virtual resources are thinned relative to the virtual resources of the service master node and distributed on different hardware devices.
  • the switching service in order to detect the abnormality of the main service, the switching service can be automatically automated to the standby node, and the service is not interrupted.
  • the virtualization service management platform 220 allocates the same virtual resource of the service primary node and the service standby node, and is distributed in different hardware.
  • the switch between the active and standby services can be more rapid, and the impact on the entire service chain is minimized.
  • the virtualization service management platform switches the service after determining that the service primary node is abnormal.
  • the service master node means:
  • the network controller is requested to change a service port chain, and the service master node is replaced by a service standby node to process a service service.
  • a request is sent to the network controller to change a service port chain, and the service standby node is replaced by the service standby node. Dealing with the service business can make the service uninterrupted and ensure the normal operation of the entire service function chain.
  • the method further includes:
  • the service standby node is online expanded with the virtualized resources equal to the service primary node.
  • the service reliability requirement level is a differentiated service primary and secondary node
  • the resources allocated by the virtualization service management platform to the service primary node and the service standby node are different, and an abnormality occurs in the service primary node.
  • the service primary node is switched to be a service standby node. Therefore, the service standby node needs to be expanded online, so that the service standby node and the abnormal service primary node have equal virtualized resources, so that the service is prepared.
  • the node has the ability to handle the business that was previously processed by the abnormal service master node.
  • the virtualized service management platform recovers the service primary node according to the single service node recovery policy, and further includes:
  • the virtualized resource equal to the original serving standby node is obtained when the service primary node is restored.
  • the service reliability requirement level is the differentiated service primary and secondary nodes
  • the virtualized resources allocated according to the original service standby node virtual resource specifications are used to enable the service to be processed.
  • the network controller 30 formulates the data forwarding policy of the service primary node and the service standby node when the service reliability requirement level is a difference or an equal service primary and secondary node, and the service primary node and the service standby node receive
  • the request of the upstream service node sends the data processed by the service master node and the service standby node to the downstream service node, and forwards the data to the service detection module, that is, in the process of performing the service, the service master node and the service standby node both Data processing is performed so that when the service master node is abnormal, the service standby node can continue to serve, thereby ensuring the normal operation of the service service function chain.
  • FIG. 4 is a schematic flowchart of Embodiment 1 of a method for scheduling a virtualized data center according to an embodiment of the present invention. As shown in FIG. 4, the method includes:
  • the interface for providing a service type, a resource template, and a reliability requirement level, and receiving a service orchestration policy to generate a service function chain, where the service reliability requirement level includes an abnormal alarm, a single service node automatic recovery, and a differentiated service active and standby node. And equal service primary and secondary nodes;
  • S102 Allocate a resource of the data center according to the defined service type and the resource template to generate a service node. After the service node is abnormal, scheduling the resource of the data center according to the service reliability requirement level to restore the service node;
  • a virtualized data center scheduling method provided by the embodiment of the present invention includes: providing a service interface type, a resource template, and a reliability requirement level definition interface, and receiving a service orchestration policy generation service function chain, where the service reliability requirement level includes An abnormal alarm, a single service node automatic recovery, a differentiated service primary standby node, and an equal service active standby node, and a data center resource generation service node is allocated according to the defined service type and resource template, and after determining the service node abnormality, according to The service reliability requirement level schedules the resources of the data center to recover the service node, and formulates a data packet forwarding path of the service node, so that when an abnormality occurs in the service node, the service type, resource template, and The service reliability requirement level is used to restore the service node, thereby ensuring the normal operation of the service node of the functional service chain and improving the high reliability service of the data center.
  • the service reliability requirement level includes An abnormal alarm, a single service node automatic recovery, a differentiated service primary stand
  • the foregoing S102 includes:
  • the method further includes:
  • the mapping relationship between the service primary node and the service standby node is recorded, and the service status of the service primary node and the service standby node is detected.
  • the timeliness of the data packet determines whether the service master node and the service standby node are abnormal.
  • the method further includes:
  • the method further includes:
  • the service master node and the service standby node have different service states, determine that the service standby node needs to synchronize with the service master node, and synchronize the memory and image files of the service master node to the service standby node.
  • the method further includes:
  • the snapshot storage is created at the preset interval. If the remote disaster recovery data center exists, the image of the standby node is synchronized to the remote disaster recovery data center.
  • the foregoing S102 is specifically:
  • the virtualization service management platform When the service reliability requirement level is an abnormal alarm, the virtualization service management platform generates an alarm prompt after determining that the service node is abnormal;
  • the virtualized service management platform recovers the service node according to the single service node recovery policy after determining that the service node is abnormal;
  • the virtualization service management platform When the service reliability requirement level is a differentiated or equal service primary and secondary node, the virtualization service management platform generates a service primary node and a service standby node for the service node, and after determining that the service standby node is abnormal, according to the single The service node recovery policy restores the service standby node, and completes synchronization with the service primary node. After determining that the service primary node is abnormal, the service primary node is switched, and the service primary node is restored according to a single service node recovery policy. .
  • the single service node recovery policy includes:
  • the service node storage resource is abnormal, causing the service node image file to use abnormality, if there is a snapshot resource, attempting to reconstruct the service node with the latest snapshot of the service node, or when there is no snapshot resource, then virtualizing The service management platform reconstructs the service node according to the virtual resource template of the service node.
  • generating a service primary node and a service standby node for the service node including:
  • the service reliability requirement level is a differentiated service primary and secondary node
  • different virtual resources are allocated to the service primary node and the service standby node, and the virtual resources are distributed on different hardware devices;
  • the service reliability requirement level is an equal service primary and secondary node
  • the same virtual resource is allocated to the service primary node and the service standby node, and the virtual resources are distributed on different hardware devices.
  • switching the service primary node includes:
  • the network controller is requested to change a service port chain, and the service master node is replaced by a service standby node to process a service service.
  • the method before the service primary node is replaced by the serving standby node to process the service service, the method further includes:
  • the service standby node is online expanded with the virtualized resources equal to the service primary node.
  • the method further includes:
  • the virtualized resource equal to the original service standby node is obtained when the service primary node is restored.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Hardware Redundancy (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un système et un procédé de planification de centre de données de virtualisation. Le système comprend : un module de définition et d'orchestration de services, une plateforme de gestion de centre de données et un contrôleur de réseau, des interfaces définies d'un type de service, un modèle de ressource et un niveau d'exigence de fiabilité étant prévus, une politique d'orchestration de services étant reçue pour générer une chaîne de fonctions de services et une ressource d'un centre de données étant attribuée selon le type de service défini et un modèle de ressource pour générer un nœud de service. Lors de la détermination d'une anomalie du nœud de service, une ressource du centre de données est planifiée selon le niveau d'exigence de fiabilité de service pour restaurer le nœud de service et un chemin d'acheminement de paquets de données du nœud de service est décidé. Ainsi, lorsqu'une anomalie d'un nœud de service survient, le nœud de service peut être restauré selon un type de service, un modèle de ressource et le niveau d'exigence de fiabilité de service défini par un utilisateur, ce qui garantit un fonctionnement normal du nœud de service dans une chaîne de fonctions de services et améliore le service du centre de données pour qu'il soit très fiable.
PCT/CN2016/102759 2015-10-23 2016-10-20 Système et procédé de planification de centre de données de virtualisation WO2017067484A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510698183.3A CN106612312A (zh) 2015-10-23 2015-10-23 一种虚拟化数据中心调度系统和方法
CN201510698183.3 2015-10-23

Publications (1)

Publication Number Publication Date
WO2017067484A1 true WO2017067484A1 (fr) 2017-04-27

Family

ID=58556643

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/102759 WO2017067484A1 (fr) 2015-10-23 2016-10-20 Système et procédé de planification de centre de données de virtualisation

Country Status (2)

Country Link
CN (1) CN106612312A (fr)
WO (1) WO2017067484A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108200211A (zh) * 2018-02-12 2018-06-22 华为技术有限公司 集群中镜像文件下载的方法、节点和查询服务器
CN111769992A (zh) * 2020-07-13 2020-10-13 迈普通信技术股份有限公司 一种网络数据的管理方法、云平台及存储介质
CN112269693A (zh) * 2020-10-23 2021-01-26 北京浪潮数据技术有限公司 一种节点自协调方法、装置和计算机可读存储介质

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107094098B (zh) * 2017-05-19 2019-12-17 西安交通大学苏州研究院 网络功能虚拟化中业务功能链的故障检测与定位方法
CN107070753A (zh) * 2017-06-15 2017-08-18 郑州云海信息技术有限公司 一种分布式集群系统的数据监控方法、装置及系统
CN107506405A (zh) * 2017-08-07 2017-12-22 北京小度信息科技有限公司 数据处理方法、装置、电子设备及计算机可读存储介质
CN108170507B (zh) * 2017-12-04 2022-02-22 上海市信息网络有限公司 虚拟应用管理方法/系统、计算机可读存储介质及服务端
CN108566308B (zh) * 2018-04-28 2020-11-06 电子科技大学 一种基于共享保护服务功能链的可靠性增强方法
CN109542338B (zh) * 2018-10-19 2022-02-18 郑州云海信息技术有限公司 一种实现分布式存储系统中节点信息一致性方法及装置
CN109981355A (zh) * 2019-03-11 2019-07-05 北京网御星云信息技术有限公司 用于云环境的安全防御方法及系统、计算机可读存储介质
CN109842526B (zh) * 2019-03-12 2021-12-07 中国联合网络通信集团有限公司 一种容灾方法和装置
CN110213075B (zh) * 2019-04-04 2020-01-31 特斯联（北京）科技有限公司 一种多重网络节点配置方法、装置、终端设备及介质
CN112073397B (zh) * 2020-08-27 2022-08-23 北京计算机技术及应用研究所 一种基于软件定义安全的混合资源管理系统
CN117149474A (zh) * 2022-05-23 2023-12-01 中兴通讯股份有限公司 一种异构加速资源异常处理方法、装置、存储介质及电子装置
CN115474079A (zh) * 2022-08-11 2022-12-13 中国电信股份有限公司 媒体流迁移方法、装置、电子设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104360924A (zh) * 2014-11-11 2015-02-18 上海天玑科技股份有限公司 一种在云数据中心环境下对虚拟机进行监控等级划分的方法
CN104639414A (zh) * 2015-01-30 2015-05-20 杭州华三通信技术有限公司 一种报文转发方法和设备
WO2015097359A1 (fr) * 2013-12-23 2015-07-02 Orange Procede de diagnostic de fonctions service dans un reseau ip

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015097359A1 (fr) * 2013-12-23 2015-07-02 Orange Procede de diagnostic de fonctions service dans un reseau ip
CN104360924A (zh) * 2014-11-11 2015-02-18 上海天玑科技股份有限公司 一种在云数据中心环境下对虚拟机进行监控等级划分的方法
CN104639414A (zh) * 2015-01-30 2015-05-20 杭州华三通信技术有限公司 一种报文转发方法和设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
GU, R. ET AL.: "Service Function Chain Extension Architecture draft-gu-sfc-extend-architecture-00", IETF INTERNET -DRAFT, 8 March 2015 (2015-03-08), XP015105284 *
HALPERN, J. ET AL.: "Service Function Chaining (SFC) Architecture draft-ietf-sfc-architecture-08", IETF INTERNET -DRAFT, 11 May 2015 (2015-05-11), XP055376621 *

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108200211A (zh) * 2018-02-12 2018-06-22 华为技术有限公司 集群中镜像文件下载的方法、节点和查询服务器
WO2019153880A1 (fr) * 2018-02-12 2019-08-15 华为技术有限公司 Procédé de téléchargement de fichier miroir dans un groupe, nœud et serveur d'interrogation
CN108200211B (zh) * 2018-02-12 2020-10-09 华为技术有限公司 集群中镜像文件下载的方法、节点和查询服务器
CN111769992A (zh) * 2020-07-13 2020-10-13 迈普通信技术股份有限公司 一种网络数据的管理方法、云平台及存储介质
CN111769992B (zh) * 2020-07-13 2022-06-21 迈普通信技术股份有限公司 一种网络数据的管理方法、云平台及存储介质
CN112269693A (zh) * 2020-10-23 2021-01-26 北京浪潮数据技术有限公司 一种节点自协调方法、装置和计算机可读存储介质
CN112269693B (zh) * 2020-10-23 2024-03-01 北京浪潮数据技术有限公司 一种节点自协调方法、装置和计算机可读存储介质

Also Published As

Publication number Publication date
CN106612312A (zh) 2017-05-03

Similar Documents

Publication Publication Date Title
WO2017067484A1 (fr) Système et procédé de planification de centre de données de virtualisation
US11249815B2 (en) Maintaining two-site configuration for workload availability between sites at unlimited distances for products and services
US10983880B2 (en) Role designation in a high availability node
US11307943B2 (en) Disaster recovery deployment method, apparatus, and system
US10609159B2 (en) Providing higher workload resiliency in clustered systems based on health heuristics
US10084858B2 (en) Managing continuous priority workload availability and general workload availability between sites at unlimited distances for products and services
TWI755417B (zh) 計算任務分配方法、流計算任務的執行方法、控制伺服器、流計算中心伺服器集群、流計算系統及異地多活系統
US10203992B2 (en) Worker node rebuild for parallel processing system
US7617411B2 (en) Cluster system and failover method for cluster system
US8615676B2 (en) Providing first field data capture in a virtual input/output server (VIOS) cluster environment with cluster-aware vioses
US20080052327A1 (en) Secondary Backup Replication Technique for Clusters
CN108270726B (zh) 应用实例部署方法及装置
US8726274B2 (en) Registration and initialization of cluster-aware virtual input/output server nodes
US10430217B2 (en) High availability using dynamic quorum-based arbitration
CN111460039A (zh) 关系型数据库处理系统、客户端、服务器及方法
CN102523257A (zh) 一种基于iaas云平台的虚拟机容错方法
US20130205108A1 (en) Managing reservation-control in a storage system
WO2015196692A1 (fr) Système informatique en nuage, et procédé et appareil de traitement pour un système informatique en nuage
CN105468446A (zh) 一种基于Linux的HPC作业调度实现高可用的方法
Jehl et al. Towards fast and efficient failure handling for paxos state machines
CN115549751A (zh) 遥感卫星地面站监控系统和方法
CN115098259A (zh) 一种资源管理方法、装置、云平台、设备及存储介质
CN114827148A (zh) 基于云容错技术的云安全计算方法和装置、存储介质
CN116166460A (zh) 应用于集群数据库系统的管理控制方法、管理控制器以及集群数据库系统
JP2012155540A (ja) クラスタシステム

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

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

Country of ref document: EP

Kind code of ref document: A1