WO2017161979A1 - 一种基于云平台管理服务器的方法及装置 - Google Patents

一种基于云平台管理服务器的方法及装置 Download PDF

Info

Publication number
WO2017161979A1
WO2017161979A1 PCT/CN2017/073748 CN2017073748W WO2017161979A1 WO 2017161979 A1 WO2017161979 A1 WO 2017161979A1 CN 2017073748 W CN2017073748 W CN 2017073748W WO 2017161979 A1 WO2017161979 A1 WO 2017161979A1
Authority
WO
WIPO (PCT)
Prior art keywords
server
primary
backup
feature value
servers
Prior art date
Application number
PCT/CN2017/073748
Other languages
English (en)
French (fr)
Inventor
张燕
翁栗
黄琳
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2017161979A1 publication Critical patent/WO2017161979A1/zh

Links

Images

Classifications

    • 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
    • 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/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/1008—Server selection for load balancing based on parameters of servers, e.g. available memory or workload
    • 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/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting

Definitions

  • This document relates to, but is not limited to, the field of communication technologies, and relates to a method and apparatus for managing a server based on a cloud platform.
  • SaaS Software-as-a-Service
  • the SaaS service provides a software model through the Internet.
  • the vendor deploys the application software on its own server.
  • the customer can order the required application software service to the manufacturer through the Internet according to his actual needs.
  • the number of servers will inevitably increase.
  • Servers that are active and standby are often fixed by racks and located in the same space. Due to physical location restrictions, they are not scalable.
  • the embodiment of the invention provides a method and a device for managing a server based on a cloud platform, which can completely control the server from the limitation of the physical location, thereby improving the disaster tolerance performance of the server and supporting the scalability of the server.
  • An embodiment of the present invention provides a method for managing a server based on a cloud platform, where the method includes: establishing a connection with a server accessing the cloud platform in advance and assigning a unique identifier to each server; receiving configuration parameters sent by the server, Determining, in the server, a primary server and a backup server based on the configuration parameter, wherein the number of the primary servers is one, and the number of the backup servers is one or more; when the primary server stops working And filtering out the first backup server from the backup server according to a preset rule, and determining the first backup server as a new primary server.
  • An embodiment of the present invention further provides an apparatus for managing a server based on a cloud platform, where the apparatus includes: an identifier allocation unit, configured to establish a connection with a server accessing the cloud platform in advance and assign a unique identifier to each server; a server determining unit, configured to receive a configuration parameter sent by the server, and determine a primary server and a backup server in the server according to the configuration parameter, where the number of the primary server is one, and the backup server The number of the switches is one or more; the switching unit is configured to: when the primary server stops working, filter the first backup server from the backup server according to a preset rule, and determine the first backup server as New primary server.
  • a method and device for managing a server based on a cloud platform can uniformly connect multiple servers by connecting a preset number of servers to the same platform and assigning different identifiers to different servers Manage.
  • the primary server and the backup server can be determined according to the current running state of the server, and when the primary server fails and stops working, a new primary server can be selected from the backup server.
  • the foregoing technical solution does not require the primary server and the backup server to be in the same physical location, and the unified management of the primary server and the backup server can avoid compatibility problems between different servers, thereby improving the disaster tolerance performance of the server. And support for server scalability.
  • the primary server and the backup server are divided for preset services, that is, multiple services can be simultaneously run in one server, thereby maximizing the capacity of each server, thereby saving The cost of the entire system.
  • Embodiments of the present invention further provide a computer readable storage medium having stored therein computer executable instructions, the computer executable instructions being implemented when implemented based on a cloud The method of platform management server.
  • FIG. 1 is a schematic structural diagram of a cloud platform management server according to an embodiment of the present disclosure
  • FIG. 2 is a flowchart of a method for managing a server based on a cloud platform according to an embodiment of the present invention
  • FIG. 3 is a schematic structural diagram of a primary server and a backup server related to a preset service A according to an embodiment of the present invention
  • FIG. 4 is a schematic structural diagram of an apparatus for managing a server based on a cloud platform according to an embodiment of the present invention.
  • FIG. 1 is a schematic structural diagram of a cloud platform management server according to an embodiment of the present invention.
  • multiple independent servers can be uniformly managed through the cloud platform.
  • Each of the servers in Figure 1 has separate functions and can also serve as a backup server for other servers.
  • server 0 can serve as the primary server of network service A
  • servers 1 to N can serve as backup servers for network service A.
  • both the primary server and the backup server can maintain two-way communication with the cloud platform, and the data can be synchronously updated between the primary server and the backup server.
  • the same server in order to ensure maximum utilization of the capacity of the server, can serve as a backup server for multiple network services.
  • the server 1 can serve as a backup server of the network service A.
  • the network service A can be allocated a certain amount of space in advance to store the data of the network service A.
  • it can also be a network service in the server 1.
  • B allocates a certain amount of space to back up the data of network service B.
  • the same server can act as a primary server for network services, and can also serve as a backup server for another or multiple other network services.
  • the functions of each server are relatively independent, and the primary server and the backup server are often divided by the network service.
  • FIG. 2 is a flowchart of a method for managing a server based on a cloud platform according to an embodiment of the present invention.
  • the processes described below include a plurality of operations occurring in a particular order, it should be clearly understood that the processes include more or fewer operations that can be performed sequentially or in parallel (eg, using a parallel processor or a multi-threaded environment). As shown in FIG. 2, the method includes:
  • Step S1 establishing a connection with a server accessing the cloud platform in advance and assigning a unique identifier to each server;
  • the cloud platform may establish a connection with a preset number of servers in advance.
  • the preset number of servers can access the cloud platform through a service router (SR), and the cloud platform performs unified management.
  • SR service router
  • the cloud platform may assign a unique identifier to each server to distinguish each server.
  • the identifier may be a series of digital codes generated according to the number of servers, for example, a total of 30 servers connected to the cloud platform, then consecutive digital codes 0 to 29 may be assigned to each server, such that each Each server has a different identity than the other servers.
  • the identifier may also be a network communication address allocated by the cloud platform for the server or a MAC address of each server itself, which is not limited in this application.
  • Step S2 receiving configuration parameters sent by the server, and determining a primary server and a backup server among the preset number of servers based on the configuration parameters;
  • the number of the primary servers is one, and the number of the backup servers is one or more.
  • the configuration parameter sent by the server may be received.
  • the configuration parameters may include various information related to the server.
  • the configuration parameters include a running state parameter of the server, a routing parameter, The length of normal operation and the amount of traffic that can accommodate the preset service.
  • the running state parameter may be assigned a value of 0 or 1 according to an operating state of the server. When the server is in the normal working state, its corresponding running state parameter may be 1; when the server is in the stopped working state, its corresponding running state parameter may be 0.
  • the operating state parameter may also be determined by the cloud platform.
  • the cloud platform can continuously receive the information sent by the server, and does not receive the abnormal signal sent by the server, the running state parameter corresponding to the server may be set to 1; when the cloud platform does not have the preset duration When receiving the information sent by the server or receiving the abnormal signal sent by the server, the running status parameter corresponding to the server may be set to 0.
  • the routing parameters of the server may be used to characterize the communication status between the server and the cloud platform.
  • the routing parameter may be a distance between the server and the cloud platform, or a hop of the TTL (Time To Live) of the data packet sent by the server.
  • the smaller the value of the routing parameter the better the communication status between the server and the cloud platform.
  • the duration of the normal operation of the server may be the duration between the current time of the server and the last time of stopping the work. The longer the normal operation of the server, the more stable the server is.
  • the service volume that the server can accommodate the preset service may indicate that the server can carry the preset service.
  • the greater the value of the service volume the more the server can carry the pre-load.
  • the more the service is set the more stable the operation of the preset service can be guaranteed.
  • the primary server running the preset service may be determined in the preset number of servers based on the configuration parameter, and the preset is determined. Set up a backup server for the business.
  • the feature value corresponding to each server may be calculated based on the configuration parameter.
  • the feature value may characterize the ability of the server to carry the preset service.
  • the feature value corresponding to the server may be calculated according to the following formula:
  • C represents the eigenvalue corresponding to the server
  • A represents the operating state parameter of the server, When the server works normally, A is 1, when the server stops working, A is 0; R represents the routing parameter of the server; t represents the duration of the normal operation of the server; D is the server can accommodate The amount of traffic of the preset service.
  • the server with the smaller feature value has the stronger ability to carry the preset service (except for the feature value of 0).
  • the server with the feature value of 0 may be removed from the preset number of servers, and the feature values are in descending order. , sort the remaining servers to form a server sequence.
  • the higher the ranking the stronger the ability to carry the preset service, and the more stable the operation of the preset service. Therefore, in this implementation, a server having the smallest feature value in the server sequence may be determined as a primary server, and a server other than the primary server in the server sequence may be determined as a backup server.
  • the method of selecting the primary server may be on a first-come, first-served basis, that is, the primary server that establishes a link with the cloud platform server at the earliest. Similarly, the same is true for selecting a backup server. If there are multiple backup servers with the same feature value, the backup connection is successful.
  • a service matrix table may be established in the cloud platform to perform real-time monitoring on the working state of the server.
  • Table 1 is a schematic diagram of a service matrix established in the cloud platform of the present embodiment.
  • A(N) represents a server associated with network service A, the identifier of which is N, and N is an integer greater than or equal to 1.
  • the type indicates whether the server is currently a primary server or a backup server.
  • the Master represents the primary server and the Slave represents the backup server.
  • the running status indicates whether the server is in a normal working state or in a stopped working state at the current time. When in the normal working state, the running state has a value of 1; when in the stopped working state, the running state has a value of 0.
  • the server can maintain a synchronized update of data with the corresponding backup server.
  • the running state of the server can be monitored in real time.
  • the server running the preset service may be adjusted according to the service rectangle table, and the service matrix table may be updated in real time according to the adjusted result.
  • FIG. 3 is a schematic structural diagram of a primary server and a backup server related to a preset service A according to an embodiment of the present invention.
  • the cloud platform when the preset service A is run, the cloud platform often specifies a primary server, and the primary server can perform real-time data interaction with the user to provide the user with the data of the preset service A.
  • the other server can be used as the backup server of the preset service A to perform disaster recovery backup on the primary server.
  • the Layer 2 device often closes the communication interface between the user and the backup server, and only retains the communication interface between the user and the primary server, thus avoiding confusion of business logic.
  • Step S3 When the primary server stops working, the first backup server is filtered out from the backup server according to a preset rule, and the first backup server is determined as a new primary server.
  • the first backup server may be filtered out from the backup server according to a preset rule, and the first The backup server is determined to be a new primary server to continue to provide data of the preset service to the user.
  • the cloud platform can monitor the running status of the primary server in real time.
  • the primary server may be determined to stop working; or when an abnormality is received from the primary server.
  • the command it can be judged that the main server has stopped working.
  • the backup server with the smallest feature value may be filtered out from the service matrix table, and the backup server with the smallest feature value is determined as the first backup server, and the first backup server may serve as the backup server.
  • a new primary server to continue to provide services to users.
  • the cloud platform may modify the type of the primary server in the service matrix table to be initialized, and the value of the running state corresponding to the primary server may also be modified to 0.
  • the corresponding backup server ID can also be set to null.
  • the type of the first backup server may be modified to be a master, so that the first backup server is used as a new primary server.
  • Table 2 is a schematic diagram of the service matrix of the primary server re-determining the cloud platform of the present embodiment.
  • the original primary server A(0) is changed to Initial because its operation is stopped, the running status value is changed to 0, and the corresponding backup server identifier is modified to null.
  • the backup server A(1) is selected as the first backup server because the feature value is the smallest among all the backup servers, and its corresponding type is modified to be the master as the new primary server.
  • an instruction to resume work may be sent to the cloud platform.
  • the cloud platform receives the instruction of the recovery work sent by the original primary server, it can be added as a backup server to the queue of the backup server.
  • the corresponding feature value is relatively large, because The server that recovers this work is often located at the end of the queue and has a lower priority. As the normal running time increases, its corresponding priority will gradually increase.
  • the cloud platform can re-determine a new primary server according to the above steps to keep the default service running normally.
  • a method for managing a server based on a cloud platform can uniformly manage multiple servers by connecting a preset number of servers to the same platform and assigning different identifiers to different servers. .
  • the primary server and the backup server can be determined according to the current running state of the server, and when the primary server fails and stops working, a new primary server can be selected from the backup server, thereby You can continue to provide users with normal business.
  • the method for managing a server based on the cloud platform provided by the embodiment of the present invention does not require the primary server and the backup server to be in the same physical location, and the unified management of the primary server and the backup server can avoid occurrence between different servers. Compatibility issues that can improve server disaster tolerance and support server scalability.
  • the primary server and the backup server are divided for preset services, that is, multiple services can be simultaneously run in one server, thereby maximizing the capacity of each server, thereby saving The cost of the entire system.
  • FIG. 4 is a functional block diagram of an apparatus for managing a server based on a cloud platform according to an embodiment of the present invention. As shown in FIG. 4, the device includes:
  • the identifier allocation unit 100 is configured to establish a connection with a server accessing the cloud platform in advance and assign a unique identifier to each server;
  • the primary backup server determining unit 200 is configured to receive configuration parameters sent by the server, and determine a primary server and a backup server in the server based on the configuration parameter, where the number of the primary servers is one.
  • the number of backup servers is one or more;
  • the switching unit 300 is configured to: when determining that the primary server stops working, filter the first backup server from the backup server according to a preset rule, and determine the first backup server Is the new primary server.
  • the primary backup server determining unit 200 includes:
  • the feature value calculation module 201 is configured to calculate a feature value corresponding to each server based on the configuration parameter;
  • the sorting module 202 is configured to remove the server whose feature value is 0 from the preset number of servers, and sort the remaining servers according to the order of the feature values from small to large to form a server sequence;
  • the determining module 203 is configured to determine a server having the smallest feature value in the server sequence as a primary server, and determine a server other than the primary server in the server sequence as a backup server.
  • the feature value calculation module 201 may calculate a feature value corresponding to each server according to the following formula:
  • C represents the characteristic value corresponding to the server
  • A represents the running state parameter of the server, when the server works normally, A is 1, when the server stops working, A is 0;
  • R represents the server The routing parameter;
  • t represents the duration of the normal operation of the server;
  • D is the amount of traffic that the server can accommodate the preset service;
  • the switching unit 300 includes:
  • the determining module 301 is configured to determine that the primary server stops working when the information fed back by the primary server is not received within a preset duration; or when the abnormal command sent by the primary server is received, determine the The primary server stops working;
  • the switching module 302 is configured to, when determining that the primary server stops working, use a server with the smallest feature value in the backup server as the first backup server, and determine the first backup server as the new primary server.
  • the primary backup server determining unit 200 is further configured to: after receiving the instruction for restoring work sent by the primary server, setting the primary server as a backup server.
  • the device for managing a server based on the cloud platform can uniformly manage multiple servers by connecting a preset number of servers to the same platform and assigning different identifiers to different servers. .
  • the primary server and the backup server can be determined according to the current running state of the server, and when the primary server fails and stops working, a new primary server can be selected from the backup server, thereby You can continue to provide users with normal business.
  • the device for managing a server based on the cloud platform provided by the embodiment of the present invention does not require the primary server and the backup server to be in the same physical location, and the unified management of the primary server and the backup server can avoid occurrence between different servers. Compatibility issues that can improve server disaster tolerance and support server scalability.
  • the primary server and the backup server are divided for preset services, that is, multiple services can be simultaneously run in one server, thereby maximizing the capacity of each server, thereby saving The cost of the entire system.
  • the embodiment of the present invention further provides a computer readable storage medium, where the computer readable storage medium stores computer executable instructions, and when the computer executable instructions are executed, implements a cloud platform management server based method.
  • the present application can be implemented by means of software plus a necessary general hardware platform. Based on such understanding, the technical solution of the present application may be embodied in the form of a software product in essence or in the form of a software product, which may be stored in a storage medium such as a ROM/RAM or a disk.
  • An optical disk, etc. includes instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present application or portions of the embodiments.
  • the above technical solutions can improve the disaster tolerance performance of the server and support the scalability of the server; at the same time, the capacity of each server can be maximized, and the cost of the entire system can be saved.

Landscapes

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

Abstract

一种基于云平台管理服务器的方法及装置，其中，所述方法包括：预先与服务器建立连接并为每个服务器分配唯一的标识；接收所述服务器发来的配置参数，并基于所述配置参数在所述服务器中确定主服务器和备份服务器；当所述主服务器停止工作时，按照预设规则从所述备份服务器中筛选出第一备份服务器，并将所述第一备份服务器确定为新主服务器。上述技术方案能够摆脱物理位置的限制，统一地对服务器进行控制，从而提高服务器的容灾性能以及支持服务器的可扩展性。

Description

一种基于云平台管理服务器的方法及装置 技术领域
本文涉及但不限于通信技术领域，涉及一种基于云平台管理服务器的方法及装置。
背景技术
随着互联网技术的不断发展，以及SaaS(Software-as-a-Service，软件即服务)业务的不断推广，互联网中服务器的数量在不断增长。SaaS业务通过互联网提供软件的模式，厂商将应用软件统一部署在自己的服务器上，客户可以根据自己的实际需求，通过互联网向厂商定购所需的应用软件服务。这样，随着应用软件数量以及用户数量的增多，不可避免地会造成服务器数量的增多。在服务器数量不断增多的同时，用户对于服务器的稳定性和可靠性的需求也在不断提升。为了保证能够为用户提供持续的服务，往往可以为运行业务的主服务器添置备用服务器以进行容灾备份。这样，当运行业务的主服务器出现故障时，可以由备用服务器继续为用户提供服务，以保证用户的业务不受影响。
然而，相关的容灾备份技术往往具有以下缺陷：
1、一些厂商的主服务器只能与该厂商的备用服务器之间进行数据互通，无法兼容其他厂商的服务器；
2、互为主备的服务器往往由机架固定并且位于同一空间中，由于受物理位置的限制，不具备可扩展性。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本发明实施例提供一种基于云平台管理服务器的方法及装置，可以摆脱物理位置的限制，统一地对服务器进行控制，从而提高服务器的容灾性能以及支持服务器的可扩展性。
本发明实施例提供一种基于云平台管理服务器的方法，所述方法包括：预先与接入云平台的服务器建立连接并为每个服务器分配唯一的标识；接收所述服务器发来的配置参数，并基于所述配置参数在所述服务器中确定主服务器和备份服务器，其中，所述主服务器的数量为1个，所述备份服务器的数量为1个或多个；当所述主服务器停止工作时，按照预设规则从所述备份服务器中筛选出第一备份服务器，并将所述第一备份服务器确定为新主服务器。
本发明实施例还提供的一种基于云平台管理服务器的装置，所述装置包括：标识分配单元，设置为预先与接入云平台的服务器建立连接并为每个服务器分配唯一的标识；主备份服务器确定单元，设置为接收所述服务器发来的配置参数，并基于所述配置参数在所述服务器中确定主服务器和备份服务器，其中，所述主服务器的数量为1个，所述备份服务器的数量为1个或多个；切换单元，设置为当所述主服务器停止工作时，按照预设规则从所述备份服务器中筛选出第一备份服务器，并将所述第一备份服务器确定为新主服务器。
本发明实施例提供的一种基于云平台管理服务器的方法及装置，通过将预设数量的服务器连接至同一个平台上，并且为不同的服务器分配不同的标识，从而可以统一地对多个服务器进行管理。根据不同服务器发至平台的配置参数，从而可以根据服务器当前的运行状态，确定主服务器和备份服务器，并且当主服务器发生故障而停止工作时，可以从备份服务器中挑选出一个新的主服务器，以继续为用户提供正常的业务。上述技术方案不需要主服务器和备份服务器处于同样的物理位置中，并且通过对主服务器和备份服务器进行统一管理，可以避免不同的服务器之间出现兼容性的问题，从而可以提高服务器的容灾性能以及支持服务器的可扩展性。另外，所述的主服务器和备份服务器是针对预设业务而进行划分的，也就是说，一台服务器中可以同时运行多个业务，这样能够最大化地利用每台服务器的容量，从而节省了整个系统的成本。
本发明实施例还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机可执行指令，所述计算机可执行指令被执行时实现基于云 平台管理服务器的方法。
在阅读并理解了附图和详细描述后，可以明白其它方面。
附图说明
图1为本发明实施例提供的基于云平台管理服务器的架构示意图；
图2为本发明实施例提供的一种基于云平台管理服务器的方法流程图；
图3为本发明实施例中与预设业务A相关的主服务器和备份服务器的架构示意图；
图4为本发明实施例提供的一种基于云平台管理服务器的装置的结构示意图。
具体实施方式
下文中将结合附图对本申请的实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行。并且，虽然在流程图中示出了逻辑顺序，但是在一些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
图1为本发明实施例提供的基于云平台管理服务器的架构示意图。如图1所示，在本发明实施例中，可以通过云平台统一管理多个独立的服务器。图1中的每个服务器具备独立的功能，同时还可以作为其它服务器的备份服务器。例如，服务器0可以作为网络业务A的主服务器，服务器1至N可以作为网络业务A的备份服务器。在本发明实施例中，主服务器和备份服务器均可以与云平台保持双向通信，并且主服务器和备份服务器之间可以保持数据的同步更新。
另外，在本发明实施例中，为了保证最大化地利用服务器的容量，同一台服务器可以作为多个网络业务的备份服务器。例如，服务器1可以作为网络业务A的备份服务器，在服务器1中可以预先给网络业务A分配一定容量的空间，以存储网络业务A的数据。同时，在服务器1中还可以为网络业务 B分配一定容量的空间，以备份网络业务B的数据。
此外，同一台服务器可以作为一个网络业务的主服务器，还可以同时作为另一个或者另外多个网络业务的备份服务器。在本发明实施例中，每个服务器的功能相对独立，往往是通过网络业务对主服务器和备份服务器进行划分。
图2为本发明实施例提供的一种基于云平台管理服务器的方法流程图。虽然下文描述流程包括以特定顺序出现的多个操作，但是应该清楚了解，这些过程包括更多或更少的操作，这些操作可以顺序执行或并行执行(例如使用并行处理器或多线程环境)。如图2所示，所述方法包括：
步骤S1：预先与接入云平台的服务器建立连接并为每个服务器分配唯一的标识；
在本实施例中，云平台可以预先与预设数量的服务器建立连接。所述预设数量的服务器可以通过全业务路由器(Service Router，SR)接入所述云平台，由所述云平台进行统一管理。
在本实施例中，在与所述预设数量的服务器建立连接后，所述云平台可以为每个服务器分配唯一的标识，以将每个服务器进行区分。所述标识可以为根据服务器的数量生成的一系列数字编码，例如，与所述云平台建立连接的服务器共计30台，那么可以将连续的数字编码0至29分别分配给每个服务器，这样每个服务器便具备与其它服务器不同的标识。当然，在实际应用场景中，所述标识还可以为云平台为服务器分配的网络通信地址或者每个服务器自身的MAC地址，本申请对此并不做限定。
步骤S2：接收所述服务器发来的配置参数，并基于所述配置参数在所述预设数量的服务器中确定主服务器和备份服务器；
在本实施方式中，所述主服务器的数量为1个，所述备份服务器的数量为1个或者更多个。
在本实施例中，当云平台与服务器建立连接并为该服务器分配唯一的标识后，可以接收服务器发来的配置参数。所述配置参数可以包括与服务器相关的各种信息。例如，所述配置参数包括服务器的运行状态参数、路由参数、 正常运行的时长以及可容纳所述预设业务的业务量。其中，所述运行状态参数可以根据服务器的运行状态赋值为0或者1。当服务器处于正常工作状态时，其对应的运行状态参数可以为1；当服务器处于停止工作状态时，其对应的运行状态参数可以为0。
在本实施例中，所述运行状态参数还可以由云平台确定。可选地，当云平台能够持续接收服务器发来的信息，并且没有收到服务器发来的异常信号时，可以将该服务器对应的运行状态参数设置为1；当云平台在预设时长内没有接收到服务器发来的信息，或者接收到服务器发来的异常信号时，可以将该服务器对应的运行状态参数设置为0。
在本实施例中，所述服务器的路由参数可以用来表征服务器与云平台之间的通信状况。例如，所述路由参数可以为服务器与云平台之间的距离，或者为服务器发出的数据包的TTL(Time To Live，生存时间值)的跳数。在本实施例中，所述路由参数的值越小，说明服务器与云平台之间的通信状况越好。
在本实施例中，所述服务器的正常运行的时长可以为服务器当前时刻距离上一次停止工作时刻之间的时长。所述服务器的正常运行的时长越长，则表示该服务器越稳定。
在本实施例中，所述服务器可容纳所述预设业务的业务量可以表示该服务器能够承载所述预设业务的能力，业务量的值越大，则表明该服务器越能够承载所述预设业务，越能保证运行所述预设业务的稳定性。
在本实施例中，当云平台接收到服务器发来的配置参数时，可以基于所述配置参数，在所述预设数量的服务器中确定运行所述预设业务的主服务器以及确定所述预设业务的备份服务器。
在本实施例中，可以基于所述配置参数，计算每个服务器对应的特征值。所述特征值可以表征服务器能够承载所述预设业务的能力。
在本实施例中，可以按照下述公式来计算服务器对应的特征值：
Figure PCTCN2017073748-appb-000001
其中，C代表服务器对应的特征值；A代表所述服务器的运行状态参数， 当所述服务器正常工作时，A为1，当所述服务器停止工作时，A为0；R代表所述服务器的路由参数；t代表所述服务器正常运行的时长；D为所述服务器可容纳所述预设业务的业务量。e代表自然对数的底，e＝2.7182818。
由上述公式可以发现，当所述服务器在正常工作时，该服务器对应的特征值不为0，而当服务器停止工作时，其对应的特征值为0。此外，当所述服务器的路由参数越小(服务器到云平台的距离越小或者服务器发出的数据包的TTL跳数越小)或者正常运行的时长越长以及可容纳所述预设业务的业务量越大时，所述服务器对应的特征值则越小。R以及e的-t次方相乘的结果越小，特征值越小，比如R相同的情况下，t运行时间越长，特征值就越小；时间相同的情况下，R越小，特征值就越小。R与c成正比，t与c成反比。由此可见，在本实施例中，特征值越小的服务器，其对应的承载所述预设业务的能力越强(特征值为0除外)。
因此，在本实施例中，在计算出每个服务器对应的特征值后，可以将特征值为0的服务器从所述预设数量的服务器中去除，并按照所述特征值从小到大的顺序，对剩余的服务器进行排序，形成服务器序列。在所述服务器序列中，排名越靠前，则表明承载所述预设业务的能力越强，越能保证所述预设业务的稳定运行。因此，在本实施中，可以将所述服务器序列中特征值最小的个服务器确定为主服务器，将所述服务器序列中除所述主服务器之外的服务器确定为备份服务器。当存在多个特征值相同的服务器时情况时，则选择主服务器的方式可以采用先到先得原则，即最早与云平台服务器建立链接的为主服务器。同样，在选择备份服务器方面也是如此，如果存在多个特征值相同的备份服务器，则最早连接成功的为备份服务器。
在本实施例中，在确定了所述预设业务的主服务器和备份服务器之后，可以在云平台中建立业务矩阵表，以对服务器的工作状态进行实时监控。表1为本实施方式的云平台中建立的业务矩阵示意表。
Figure PCTCN2017073748-appb-000002
Figure PCTCN2017073748-appb-000003
表1
在表1中，A(N)代表与网络业务A相关的服务器，该服务器的标识为N，N为大于或等于1的整数。类型表示该服务器当前是主服务器还是备份服务器，其中，Master代表主服务器，Slave代表备份服务器。运行状态表示当前时刻服务器是处于正常工作状态还是处于停止工作状态，当处于正常工作状态时，运行状态的值为1；当处于停止工作状态时，运行状态的值为0。服务器可以与对应的备份服务器之间保持数据的同步更新。
在本实施例中，当云平台建立了所述业务矩阵表后，可以实时监控服务器的运行状态。当服务器运行出现故障时，可以根据所述业务矩形表及时对运行所述预设业务的服务器进行调整，并根据调整后的结果，实时更新所述业务矩阵表。
图3为本发明实施例中与预设业务A相关的主服务器和备份服务器的架构示意图。如图3所示，在运行预设业务A时，云平台往往指定一个主服务器，该主服务器可以与用户进行实时的数据交互，以向用户提供预设业务A的数据。其它的服务器则可以作为预设业务A的备份服务器，以对主服务器进行容灾备份。在主服务器正常工作时，二层设备往往关闭用户与备份服务器之间的通信接口，而仅保留用户与主服务器之间的通信接口，这样可以避免造成混乱的业务逻辑。
步骤S3：当所述主服务器停止工作时，按照预设规则从所述备份服务器中筛选出第一备份服务器，并将所述第一备份服务器确定为新主服务器。
在本实施例中，当主服务器停止工作时，为保证预设业务不被中断，可以按照预设规则从所述备份服务器中筛选出第一备份服务器，并将所述第一 备份服务器确定为新的主服务器，以向用户继续提供所述预设业务的数据。
在本实施例中，云平台可以实时监控主服务器的运行状态，当在预设时长内未接收到主服务器反馈的信息时，可以判定主服务器停止工作；或者当接收到主服务器发来的异常指令时，可以判断主服务器停止工作。在判定主服务器停止工作时，可以从所述业务矩阵表中筛选出特征值最小的备份服务器，并将所述特征值最小的备份服务器确定为第一备份服务器，该第一备份服务器即可以作为新的主服务器，从而向用户继续提供服务。
在本实施例中，当主服务器停止工作时，云平台可以将业务矩阵表中主服务器的类型修改为初始化(Initial)，此时所述主服务器对应的运行状态的值也可以修改为0，其对应的备份服务器标识也可以设置为空(null)。在确定了第一备份服务器后，可以将所述第一备份服务器的类型修改为Master，以使得所述第一备份服务器作为新的主服务器。表2为本实施方式的云平台重新确定主服务器的业务矩阵示意表。
Figure PCTCN2017073748-appb-000004
表2
由表2可见，原先的主服务器A(0)由于停止工作，其对应的类型被修改为Initial，运行状态的值被修改为0，对应的备份服务器标识被修改为null。而备份服务器A(1)由于特征值在所有的备份服务器中最小，因此被选为第一备份服务器，其对应的类型被修改为Master，以作为新的主服务器。
在本实施例中，当停止工作的主服务器重新恢复工作时，可以向云平台发送恢复工作的指令。这样，当云平台接收到所述原先的主服务器发来的恢复工作的指令后，可以将其作为备份服务器，加入备份服务器的队列。此时，由于恢复工作的服务器正常运行的时长较短，其对应的特征值也比较大，因 此恢复工作的服务器往往位于队列的末端，具备较低的优先级，随着正常运行时长的增加，其对应的优先级则会逐步提高。
如果重新确定的主服务器再次停止工作，那么云平台可以按照上述的步骤，再重新确定一个新的主服务器，以保持预设业务的正常运行。
本发明实施例提供的一种基于云平台管理服务器的方法，通过将预设数量的服务器连接至同一个平台上，并且为不同的服务器分配不同的标识，从而可以统一地对多个服务器进行管理。根据不同服务器发至平台的配置参数，从而可以根据服务器当前的运行状态，确定主服务器和备份服务器，并且当主服务器发生故障而停止工作时，可以从备份服务器中挑选出一个新的主服务器，从而可以继续为用户提供正常的业务。
本发明实施例提供的一种基于云平台管理服务器的方法，不需要主服务器和备份服务器处于同样的物理位置中，并且通过对主服务器和备份服务器进行统一管理，可以避免不同的服务器之间出现兼容性的问题，从而可以提高服务器的容灾性能以及支持服务器的可扩展性。另外，所述的主服务器和备份服务器是针对预设业务而进行划分的，也就是说，一台服务器中可以同时运行多个业务，这样能够最大化地利用每台服务器的容量，从而节省了整个系统的成本。
本发明实施例还提供一种基于云平台管理服务器的装置。图4为本发明实施例提供的一种基于云平台管理服务器的装置的功能模块图。如图4所示，所述装置包括：
标识分配单元100，设置为预先与接入云平台的服务器建立连接并为每个服务器分配唯一的标识；
主备份服务器确定单元200，设置为接收所述服务器发来的配置参数，并基于所述配置参数在所述服务器中确定主服务器和备份服务器，其中，所述主服务器的数量为1个，所述备份服务器的数量为1个或者多个；
切换单元300，设置为当判定所述主服务器停止工作时，按照预设规则从所述备份服务器中筛选出第一备份服务器，并将所述第一备份服务器确定 为新主服务器。
可选地，所述主备份服务器确定单元200包括：
特征值计算模块201，设置为基于所述配置参数，计算每个服务器对应的特征值；
排序模块202，设置为将特征值为0的服务器从所述预设数量的服务器中去除，并按照所述特征值从小到大的顺序，对剩余的服务器进行排序，形成服务器序列；
确定模块203，设置为将所述服务器序列中特征值最小的服务器确定为主服务器，将所述服务器序列中除所述主服务器之外的服务器确定为备份服务器。
可选地，所述特征值计算模块201可以按照下述公式计算每个服务器对应的特征值：
Figure PCTCN2017073748-appb-000005
其中，C代表服务器对应的特征值；A代表所述服务器的运行状态参数，当所述服务器正常工作时，A为1，当所述服务器停止工作时，A为0；R代表所述服务器的路由参数；t代表所述服务器正常运行的时长；D为所述服务器可容纳所述预设业务的业务量；e代表自然对数的底，e＝2.7182818。
可选地，所述切换单元300包括：
判定模块301，设置为当在预设时长内未接收到所述主服务器反馈的信息时，判定所述主服务器停止工作；或者当接收到所述主服务器发来的异常指令时，判定所述主服务器停止工作；
切换模块302，设置为当判定所述主服务器停止工作时，将所述备份服务器中特征值最小的服务器作为第一备份服务器，并将所述第一备份服务器确定为新主服务器。
可选地，所述主备份服务器确定单元200还设置为：当接收到所述主服务器发来的恢复工作的指令后，将所述主服务器设置为备份服务器。
需要说明的是，上述功能模块的实现方式均与步骤S1至S3中的描述一致，这里便不再赘述。
本发明实施例提供的一种基于云平台管理服务器的装置，通过将预设数量的服务器连接至同一个平台上，并且为不同的服务器分配不同的标识，从而可以统一地对多个服务器进行管理。根据不同服务器发至平台的配置参数，从而可以根据服务器当前的运行状态，确定主服务器和备份服务器，并且当主服务器发生故障而停止工作时，可以从备份服务器中挑选出一个新的主服务器，从而可以继续为用户提供正常的业务。
本发明实施方式提供的一种基于云平台管理服务器的装置，不需要主服务器和备份服务器处于同样的物理位置中，并且通过对主服务器和备份服务器进行统一管理，可以避免不同的服务器之间出现兼容性的问题，从而可以提高服务器的容灾性能以及支持服务器的可扩展性。另外，所述的主服务器和备份服务器是针对预设业务而进行划分的，也就是说，一台服务器中可以同时运行多个业务，这样能够最大化地利用每台服务器的容量，从而节省了整个系统的成本。
本发明实施例还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机可执行指令，所述计算机可执行指令被执行时实现基于云平台管理服务器的方法。
通过以上的实施方式的描述可知，本领域的技术人员可以清楚地了解到本申请可借助软件加必需的通用硬件平台的方式来实现。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品可以存储在存储介质中，如ROM/RAM、磁碟、光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施方式或者实施方式的某些部分所述的方法。
虽然通过实施方式描绘了本申请，本领域普通技术人员知道，本申请有许多变形和变化而不脱离本申请的精神，希望所附的权利要求包括这些变形和变化而不脱离本申请的精神。
工业实用性
上述技术方案能够提高服务器的容灾性能以及支持服务器的可扩展性；同时能够最大化地利用每台服务器的容量，节省整个系统的成本。

Claims (10)

  1. 一种基于云平台管理服务器的方法，所述方法包括：
    预先与接入云平台的服务器建立连接并为每个服务器分配唯一的标识；
    接收所述服务器发来的配置参数，并基于所述配置参数在所述服务器中确定主服务器和备份服务器，其中，所述主服务器的数量为1个，所述备份服务器的数量为1个或多个；
    当所述主服务器停止工作时，按照预设规则从所述备份服务器中筛选出第一备份服务器，并将所述第一备份服务器确定为新主服务器。
  2. 根据权利要求1所述的方法，其中，基于所述配置参数在所述服务器中确定主服务器和备份服务器，包括：
    基于所述配置参数，计算每个服务器对应的特征值；
    将特征值为0的服务器从所述服务器中去除，并按照所述特征值对剩余的服务器进行排序，形成服务器序列；
    将所述服务器序列中特征值最小的服务器确定为主服务器，将所述服务器序列中除所述主服务器之外的服务器确定为备份服务器。
  3. 根据权利要求2所述的方法，其中：所述配置参数包括所述服务器的运行状态参数、路由参数、正常运行的时长和可容纳业务的业务量；
    所述计算每个服务器对应的特征值的公式为：
    Figure PCTCN2017073748-appb-100001
    其中，C代表服务器对应的特征值；
    A代表所述服务器的运行状态参数，当所述服务器正常工作时，A为1，当所述服务器停止工作时，A为0；
    R代表所述服务器的路由参数；
    t代表所述服务器正常运行的时长；
    D为所述服务器可容纳业务的业务量；
    e代表自然对数的底，e＝2.7182818。
  4. 根据权利要求3所述的方法，其中，所述当所述主服务器停止工作时，按照预设规则从所述备份服务器中筛选出第一备份服务器，包括：
    当在预设时长内未接收到所述主服务器反馈的信息时，判定所述主服务器停止工作，或者，当接收到所述主服务器发来的异常指令时，判定所述主服务器停止工作；
    当判定所述主服务器停止工作时，从所述备份服务器中筛选出特征值最小的服务器，并将筛选出的备份服务器确定为第一备份服务器。
  5. 根据权利要求1所述的方法，在将所述第一备份服务器确定为新主服务器之后，所述方法还包括：
    当接收到所述主服务器发来的恢复工作的指令后，将所述主服务器设置为备份服务器。
  6. 一种基于云平台管理服务器的装置，所述装置包括：
    标识分配单元，设置为预先与接入云平台的服务器建立连接并为每个服务器分配唯一的标识；
    主备份服务器确定单元，设置为接收所述服务器发来的配置参数，并基于所述配置参数在所述服务器中确定主服务器和备份服务器，其中，所述主服务器的数量为1个，所述备份服务器的数量为1个或多个；
    切换单元，设置为当所述主服务器停止工作时，按照预设规则从所述备份服务器中筛选出第一备份服务器，并将所述第一备份服务器确定为新主服务器。
  7. 根据权利要求6所述的装置，其中，所述主备份服务器确定单元包括：
    特征值计算模块，设置为基于所述配置参数，计算每个服务器对应的特征值；
    排序模块，设置为将特征值为0的服务器从所述服务器中去除，并根据所述特征值对剩余的服务器进行排序，形成服务器序列；
    确定模块，设置为将所述服务器序列中特征值最小的服务器确定为主服务器，将所述服务器序列中除所述主服务器之外的服务器确定为备份服务器。
  8. 根据权利要求7所述的装置，其中：所述配置参数包括所述服务器的运行状态参数、路由参数、正常运行的时长和可容纳业务的业务量；
    所述特征值计算模块根据下述公式计算每个服务器对应的特征值：
    Figure PCTCN2017073748-appb-100002
    其中，C代表服务器对应的特征值；
    A代表所述服务器的运行状态参数，当所述服务器正常工作时，A为1，当所述服务器停止工作时，A为0；
    R代表所述服务器的路由参数；
    t代表所述服务器正常运行的时长；
    D为所述服务器可容纳所述预设业务的业务量；
    e代表自然对数的底，e＝2.7182818。
  9. 根据权利要求8所述的装置，其中，所述切换单元包括：
    判定模块，设置为当在预设时长内未接收到所述主服务器反馈的信息时，判定所述主服务器停止工作；或者当接收到所述主服务器发来的异常指令时，判定所述主服务器停止工作；
    切换模块，设置为当判定所述主服务器停止工作时，将所述备份服务器中特征值最小的服务器作为第一备份服务器，并将所述第一备份服务器确定为新主服务器。
  10. 根据权利要求6所述的装置，其中，所述主备份服务器确定单元还设置为：
    当接收到所述主服务器发来的恢复工作的指令后，将所述主服务器设置为备份服务器。
PCT/CN2017/073748 2016-03-22 2017-02-16 一种基于云平台管理服务器的方法及装置 WO2017161979A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610167625.6A CN107222327A (zh) 2016-03-22 2016-03-22 一种基于云平台管理服务器的方法及装置
CN201610167625.6 2016-03-22

Publications (1)

Publication Number Publication Date
WO2017161979A1 true WO2017161979A1 (zh) 2017-09-28

Family

ID=59899362

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/073748 WO2017161979A1 (zh) 2016-03-22 2017-02-16 一种基于云平台管理服务器的方法及装置

Country Status (2)

Country Link
CN (1) CN107222327A (zh)
WO (1) WO2017161979A1 (zh)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110557650A (zh) * 2018-05-30 2019-12-10 视联动力信息技术股份有限公司 基于视联网的数据处理系统
US10887382B2 (en) 2018-12-18 2021-01-05 Storage Engine, Inc. Methods, apparatuses and systems for cloud-based disaster recovery
US10958720B2 (en) 2018-12-18 2021-03-23 Storage Engine, Inc. Methods, apparatuses and systems for cloud based disaster recovery
US10983886B2 (en) 2018-12-18 2021-04-20 Storage Engine, Inc. Methods, apparatuses and systems for cloud-based disaster recovery
US11176002B2 (en) 2018-12-18 2021-11-16 Storage Engine, Inc. Methods, apparatuses and systems for cloud-based disaster recovery
US11178221B2 (en) 2018-12-18 2021-11-16 Storage Engine, Inc. Methods, apparatuses and systems for cloud-based disaster recovery
US11252019B2 (en) 2018-12-18 2022-02-15 Storage Engine, Inc. Methods, apparatuses and systems for cloud-based disaster recovery
US11489730B2 (en) 2018-12-18 2022-11-01 Storage Engine, Inc. Methods, apparatuses and systems for configuring a network environment for a server

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110324375B (zh) 2018-03-29 2020-12-04 华为技术有限公司 一种信息备份方法及相关设备
CN109921942B (zh) * 2019-03-18 2020-04-21 无锡华云数据技术服务有限公司 云平台切换控制方法、装置、系统及电子设备
CN112527552A (zh) * 2019-09-18 2021-03-19 中兴通讯股份有限公司 容灾方法、装置、局点和存储介质

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101127632A (zh) * 2006-08-15 2008-02-20 腾讯科技（深圳）有限公司 一种服务器流量控制方法、系统以及重定向器
US20090259741A1 (en) * 2008-04-11 2009-10-15 Jinmei Shen Grid Computing Implementation
CN101662495A (zh) * 2009-09-16 2010-03-03 成都市华为赛门铁克科技有限公司 备份方法、主服务器、备份服务器以及备份系统
CN103312677A (zh) * 2012-03-15 2013-09-18 宇龙计算机通信科技(深圳)有限公司 终端、服务器和通信连接的建立方法
CN103560922A (zh) * 2013-11-18 2014-02-05 北京特立信电子技术股份有限公司 一种容灾方法及系统
CN104735088A (zh) * 2015-04-16 2015-06-24 北京金山安全软件有限公司 一种cdn网络中服务器节点调整方法及装置
WO2015107650A1 (ja) * 2014-01-16 2015-07-23 株式会社日立製作所 複数のサーバを有するサーバシステムの管理システム

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101127632A (zh) * 2006-08-15 2008-02-20 腾讯科技（深圳）有限公司 一种服务器流量控制方法、系统以及重定向器
US20090259741A1 (en) * 2008-04-11 2009-10-15 Jinmei Shen Grid Computing Implementation
CN101662495A (zh) * 2009-09-16 2010-03-03 成都市华为赛门铁克科技有限公司 备份方法、主服务器、备份服务器以及备份系统
CN103312677A (zh) * 2012-03-15 2013-09-18 宇龙计算机通信科技(深圳)有限公司 终端、服务器和通信连接的建立方法
CN103560922A (zh) * 2013-11-18 2014-02-05 北京特立信电子技术股份有限公司 一种容灾方法及系统
WO2015107650A1 (ja) * 2014-01-16 2015-07-23 株式会社日立製作所 複数のサーバを有するサーバシステムの管理システム
CN104735088A (zh) * 2015-04-16 2015-06-24 北京金山安全软件有限公司 一种cdn网络中服务器节点调整方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
WANG LIJUN: "A Fault -Tolerant Mechanism Based on Paxos Algorithm", COMPUTER APPLICATIONS AND SOFTWARE, vol. 28, no. 6, 30 June 2011 (2011-06-30) *

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110557650A (zh) * 2018-05-30 2019-12-10 视联动力信息技术股份有限公司 基于视联网的数据处理系统
CN110557650B (zh) * 2018-05-30 2022-04-05 视联动力信息技术股份有限公司 基于视联网的数据处理系统
US10887382B2 (en) 2018-12-18 2021-01-05 Storage Engine, Inc. Methods, apparatuses and systems for cloud-based disaster recovery
US10958720B2 (en) 2018-12-18 2021-03-23 Storage Engine, Inc. Methods, apparatuses and systems for cloud based disaster recovery
US10983886B2 (en) 2018-12-18 2021-04-20 Storage Engine, Inc. Methods, apparatuses and systems for cloud-based disaster recovery
US11176002B2 (en) 2018-12-18 2021-11-16 Storage Engine, Inc. Methods, apparatuses and systems for cloud-based disaster recovery
US11178221B2 (en) 2018-12-18 2021-11-16 Storage Engine, Inc. Methods, apparatuses and systems for cloud-based disaster recovery
US11252019B2 (en) 2018-12-18 2022-02-15 Storage Engine, Inc. Methods, apparatuses and systems for cloud-based disaster recovery
US11489730B2 (en) 2018-12-18 2022-11-01 Storage Engine, Inc. Methods, apparatuses and systems for configuring a network environment for a server

Also Published As

Publication number Publication date
CN107222327A (zh) 2017-09-29

Similar Documents

Publication Publication Date Title
WO2017161979A1 (zh) 一种基于云平台管理服务器的方法及装置
US9999030B2 (en) Resource provisioning method
EP3281359B1 (en) Application driven and adaptive unified resource management for data centers with multi-resource schedulable unit (mrsu)
CN112532675B (zh) 一种网络边缘计算系统的创建方法、装置及介质
US9584369B2 (en) Methods of representing software defined networking-based multiple layer network topology views
US11669360B2 (en) Seamless virtual standard switch to virtual distributed switch migration for hyper-converged infrastructure
WO2021022985A1 (zh) 云服务处理方法及装置、云服务器、云服务系统及存储介质
CN113037794B (zh) 计算资源配置调度方法、装置及系统
US11463514B2 (en) Methods and apparatuses for balancing utilization of computer resources
EP3442201B1 (en) Cloud platform construction method and cloud platform
US20170063627A1 (en) Allocation of virtual clusters in a large-scale processing environment
JP2016116184A (ja) 網監視装置および仮想ネットワーク管理方法
US11863612B2 (en) Network edge computing and network edge computation scheduling method, device and medium
US10871997B2 (en) System and method for routing computing workloads based on proximity
CN110262893A (zh) 配置镜像内存的方法、装置及计算机存储介质
US11720460B2 (en) Enhanced configuration management of data processing clusters
CN102724104A (zh) 自动配置Java EE应用集群的装置和方法
CN106302075B (zh) 一种创建逻辑卷的方法及装置
US9110823B2 (en) Adaptive and prioritized replication scheduling in storage clusters
CN108259345B (zh) 端口生成方法和装置
CN112468458B (zh) 一种基于neutron分层机制的调度方法
WO2021057150A1 (zh) 端口共享方法及装置、存储介质、电子装置
CN111193607B (zh) 一种传输资源管理的方法、装置及存储介质
CN114827079A (zh) 网络地址转换网关的扩容方法、设备及存储介质
AU2018290375B2 (en) Resource allocation method and system

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

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

Ref document number: 17769256

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17769256

Country of ref document: EP

Kind code of ref document: A1