WO2020113668A1 - 防脑裂的OpenStack虚拟机高可用管理端装置及管理方法 - Google Patents
防脑裂的OpenStack虚拟机高可用管理端装置及管理方法 Download PDFInfo
- Publication number
- WO2020113668A1 WO2020113668A1 PCT/CN2018/121648 CN2018121648W WO2020113668A1 WO 2020113668 A1 WO2020113668 A1 WO 2020113668A1 CN 2018121648 W CN2018121648 W CN 2018121648W WO 2020113668 A1 WO2020113668 A1 WO 2020113668A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- management
- computing node
- node device
- abnormal
- virtual machine
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45587—Isolation or security of virtual machine instances
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
Definitions
- At least two management devices can communicate through the management network to form a management cluster
- Each management device includes:
- High-availability module for high-availability management of all computing node devices
- the method of high availability module running high availability management includes the following operations:
- Operation A-3 according to the abnormal status reported by each computing node device through the management network, determine whether processing is needed one by one. If no processing is required, the abnormal processing of the computing node device ends, and go back to the previous operation A-2; otherwise Go to the next operation A-4;
- the high availability module After the management device sends a shutdown request to the connected computing node device with the shared storage device in a normal state, the high availability module also runs the following operations:
- Operation B-3 check the network status reported by each computing node device through the management network, if it is normal, this round of inspection is terminated, otherwise go to operation B-4;
- Operation B-6 for a scenario where there is no need to shut down, issue a shutdown stop request to the corresponding computing node device;
- Operation B-7 for the scene that needs to be shut down, a shutdown request is issued to the corresponding computing node device.
- the cloud computing virtual machine VM management process includes Nova-api, Nova-conductor or Nova-scheduler.
- the management network plane is used to connect the management terminal device and provide management services
- the service network plane is used to connect computing node devices and provide access services for cloud computing virtual machine VMs.
- Operation A-3 according to the abnormal status reported by each of the computing node devices through the management network, determine whether processing is needed one by one. If no processing is required, the abnormal processing of the computing node device ends, and go back to the previous operation A-2; Otherwise go to the next operation A-4;
- Operation A-4 for the computing node device that needs to be processed in an abnormal state, check the status of the shared storage device connected to it, and when the shared storage device is abnormal, control all the nodes running on the computing node device through the Nova module
- the cloud computing virtual machine VM program does not run and ends, otherwise, go to the next operation A-5;
- Operation A-5 issuing an isolation request to the computing node device with the connected shared storage device in a normal state
- Operation B-5 For the computing node device that needs to be processed in an abnormal state, check the status of the shared storage device connected to it. When the shared storage device is abnormal, there is no need to isolate and go to operation B-6 and end, otherwise , Go to operation B-7;
- Nova module 101 namely Nova controller in the figure, includes Nova's native virtual machine VM management process, which is used to manage the life cycle of the virtual machine VM.
- the Libvirt management module 303 namely Libvirt in the figure, is used to provide a management process of a standard Hypervisor API interface on the KVM.
- Nova-compute a native Nova process
- Nova-computer computer module 302 is run by Nova-computer computer module 302, and is set in computing node device 300 to respond to each management process of the control node. It is a real executor of virtual machine life cycle management operations and is directly responsible for Hypervisor carries out various communications.
- Libvirt set in the computing node device 300, is run by the Libvirt management module 303, and provides a standard Hypervisor API management process on top of the virtual machine VM.
- the shared storage system is run by the shared storage device 400.
- the software programs used include CephFS and NFS, which provide shared file system storage.
- HaStack continuously monitors the Fencing event reported by HaStack-agent, and once the message is received, it proceeds to operation B-2.
- HaStack checks whether the cluster status is normal, if it is abnormal, it triggers a cluster abnormal alarm, and ends this round of inspection; if it is normal, go to operation B-3.
- HaStack processes the nodes with exceptions one by one, according to the specific interrupt type of each node, compares the HA strategy matrix to determine the subsequent Fencing processing strategy; if no processing is required, go to operation B-6; otherwise if subsequent processing is required, go to operation B -5.
- Operation B-6 for scenarios where Fencing is not required, issue a stop Fencing request to the corresponding computing node device.
- Operation B-7 for the scenario that requires Fencing, issue a Fencing request to the corresponding computing node device.
- HaStack issues a Fencing request to HaStack-agent.
- Embodiment 1 On the basis of Embodiment 1, as shown in FIG. 4, due to the storage failure of the underlying shared storage device 400, the lock heartbeat of Lock cannot be written on time. At this time, it is necessary to confirm whether to perform Fencing between HaStack-agent and HaStack At this time, the high-availability computing node module needs to run a method including the following operations:
- Operation C-1 When the cloud computing virtual machine VM continues to update and store the lock heartbeat, no processing is required if the write is normal, otherwise, once the lock heartbeat write is abnormal, go to operation C-2.
- Lock notifies HaStack-agent, reports the underlying storage abnormal event to HaStack, and waits for HaStack to provide the processing result.
- Operation C-3 If the management device returns the processing result within the specified time, go to operation C-5, otherwise go to operation C-4.
- HaStack returns the processing opinion within the predetermined time, then go to operation C-5; otherwise, go to operation C-4.
- the Lock management module performs a Fencing operation, that is, kills the VM program of the cloud computing virtual machine of the computing node device.
- Lock performs the Fencing operation according to the default setting, that is, kills all virtual machine VMs running on the computing node.
- the Lock management module determines whether Fencing is required according to the processing result returned by the management device.
- the recovery process includes the following operations:
- Operation D-1 When the Libvirt management module is started, register and obtain the lock heartbeat through the Lock management module. If the registration fails, go to operation D-2.
- Libvirt registers with Lock and acquires the lock heartbeat when it starts, and if it fails, it proceeds to operation D-2.
- Operation D-2 once the lock heartbeat registration fails, kill closes the cloud computing virtual machine VM program of the computing node device.
- the Libvirt management module records all the computing node devices that have been shut down by the VM program of the cloud computing virtual machine that was killed, and records them in the Fencing log isolation log file.
- Operate D-4 regularly check the Fencing log file, and if there is an update, go to operation D-5.
- HaStack-agent regularly checks the Fencing log on the node, and once it finds an update, it moves to operation D-5.
- Operation D-5 report the Fencing log files of all computing node devices to the management device. If the report fails, the processing is ended and the next report is required; otherwise, after reporting to the management device, the management device will issue an instruction to proceed restore.
- the HaStack-agent reports all Fencing logs to HaStack. If the report fails, the processing ends and the next report is required.
- HaStack receives the Fencing log reported by the agent, and determines whether to perform automatic processing according to the processing switch configured in advance: if the automatic processing is turned to D-8, if the automatic processing is not required, to D-7.
- the Qga in the VM GuestOS and the HaStack-agent of the computing node continue to maintain a heartbeat. Once the blue screen in the virtual machine is stuck or stuck, go to operation E-2.
- HaStack-agent when HaStack-agent receives an abnormal event, it will immediately report it to HaStack.
- HaStack after receiving an abnormal event inside the VM of the virtual machine, HaStack directly issues an HA command to Nova to trigger HA recovery.
- Operation A-3 according to the abnormal status reported by each computing node device through the management network, determine whether processing is needed one by one. If no processing is required, the abnormal processing of the computing node device ends, and go back to the previous operation A-2; otherwise Go to the next operation A-4;
- Operation A-4 for the computing node device that needs to be processed in an abnormal state, check the status of the shared storage device connected to it, and when the shared storage device is abnormal, control the cloud computing virtual machine VM running on the computing node device through the Nova module The program does not run and ends, otherwise, go to the next operation A-5;
- Operation B-5 For the computing node device that needs to be processed in an abnormal state, check the status of the shared storage device connected to it. When the shared storage device is abnormal, go to operation B-6 without Fencing and end, otherwise, go to To operation B-7;
- Operation B-7 for the scenario that requires Fencing, issue a Fencing request to the corresponding computing node device.
- the Lock management module determines whether Fencing is required according to the processing result returned by the management device.
- Operation D-2 once the lock heartbeat registration fails, kill closes the cloud computing virtual machine VM program of the computing node device;
- the Libvirt management module records all the computing node devices that have been shut down by killing the VM program of the cloud computing virtual machine, and records them in the Fencing log file;
- Operate D-4 regularly check the Fencing log files, and if there is an update, go to operation D-5;
- the management device After receiving the report of the abnormal event, the management device directly calls the Nova interface to control the cloud computing virtual machine VM program to resume operation again.
- the invention has been secondary developed based on the original OpenStack version.
- a set of independent high-availability systems for OpenStack virtual machines with anti-brain split are independently developed on the periphery of OpenStack. Get rid of the dependence on the IPMI plane detection/hardware dog in the traditional HA solution, and realize the complete virtual machine high availability (HA) technical side of carrier-class reliability.
- the present invention provides an improved OpenStack anti-brain split
- the high-availability management terminal device and management method of the virtual machine are used to realize high availability of the management terminal device, that is, a control node serving as a server.
- split-brain refers to a highly available (HA) system.
- HA highly available
- two connected control nodes or computing nodes are disconnected, they are originally a whole system and split into Two independent nodes. At this time, the two nodes begin to compete for shared resources. As a result, the system will be chaotic and data will be corrupted.
- the improved anti-brain split OpenStack virtual machine high availability management terminal device and management method provided by the improvement of the present invention That can solve this problem.
- the high-availability management terminal device of the split-proof OpenStack virtual machine since it has a high-availability module, it can run the high-availability management method, and through a series of operations from A-1 to A-6, detect the connected The status of the computing node device and the shared storage device, according to the type of abnormal state learned: the abnormality of the computing node device or the shared storage device, specifically which part of the management network plane, storage network plane, and service network plane in the management network And determine whether to perform Fencing operation to shut down the cloud computing virtual machine VM program corresponding to the abnormal computing node device, so as to ensure the high availability of the cloud computing virtual machine VM program of the computing node device in the system.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
- Hardware Redundancy (AREA)
Abstract
Description
Claims (10)
- 一种防脑裂的OpenStack虚拟机高可用管理端装置,通过管理网络和连接有共享存储装置的计算节点装置连接,该计算节点装置安装有云计算虚拟机VM程序,其特征在于:至少两个所述管理端装置之间能通过管理网络进行通信而组成管理集群,每个管理端装置包括:Nova模块,包括Nova原生的虚拟机VM管理进程,用于对虚拟机VM的生命周期进行管理操作;集群管理模块,用于收集所述集群的运行状况信息;以及高可用模块,用于对所有的所述计算节点装置进行高可用管理,其中,所述高可用模块运行高可用管理的方法,该方法包括以下操作:操作A-1,通过所述集群管理模块收集的运行状况信息检查集群状态是否正常,如果异常,则触发集群异常告警并结束,如果正常,则转到操作A-2;操作A-2,检查各个所述计算节点装置通过管理网络上报的状态,如果正常,则此轮检查终止,否则转到下一步操作A-3;操作A-3,根据每个所述计算节点装置通过管理网络上报的异常状态,逐个判断是否需要进行处理,如果无需处理,则该计算节点装置异常处理结束,转回上一步操作A-2;否则转到下一步操作A-4;操作A-4,对于需要处理的异常状态的所述计算节点装置,检查与之连接的共享存储装置的状态,当共享存储装置异常时,通过所述 Nova模块控制该计算节点装置上运行的所述云计算虚拟机VM程序不运行,并结束,否则,转到下一步操作A-5;操作A-5,向所连接的共享存储装置状态正常的所述计算节点装置下发隔离请求;操作A-6,向所述Nova模块下发命令,触发该计算节点装置上运行的所述云计算虚拟机VM程序运行。
- 根据权利要求1所述的管理端装置,其特征在于:其中,当管理端装置向所连接的共享存储装置状态正常的所述计算节点装置下发隔离请求后,所述高可用模块还运行以下操作:操作B-1,持续监听所述计算节点装置上报的隔离事件,一旦收到消息则转到操作B-2;操作B-2,通过所述集群管理模块收集的运行状况信息检查集群状态是否正常,如果异常,则触发集群异常告警并结束,如果正常,则转到操作B-3;操作B-3,检查各个所述计算节点装置通过管理网络上报的网络状态,如果正常,则此轮检查终止,否则转到操作B-4;操作B-4,根据每个所述计算节点装置通过管理网络上报的异常状态,判断是否需要进行处理,如果无需处理,则进行操作B-6;否则转到操作B-5;操作B-5,对于需要处理的异常状态的所述计算节点装置,检查与之连接的共享存储装置的状态,当共享存储装置异常时,无需隔离 并转到操作B-6,并结束,否则,转到操作B-7;操作B-6,针对无需隔离的场景,向对应的所述计算节点装置下发停止隔离请求;操作B-7,针对需要隔离的场景,向对应的所述计算节点装置下发执行隔离请求。
- 根据权利要求1所述的管理端装置,其特征在于:其中,所述虚拟机VM管理进程包括Nova-api、Nova-conductor或Nova-scheduler。
- 根据权利要求1所述的管理端装置,其特征在于:其中,所述集群管理模块包括Etcd或Consul。
- 根据权利要求1所述的管理端装置,其特征在于:其中,所述共享存储装置为CephFS或NFS文件管理程序管理运行。
- 根据权利要求1所述的管理端装置,其特征在于:其中,所述管理网络包括:管理网络平面,用于对接所述管理端装置,用于提供管理服务;存储网络平面,用于对接后端的所述共享存储装置,用于提供存储服务;业务网络平面,用于对接所述计算节点装置,用于提供云计算虚拟机VM的访问服务。
- 根据权利要求6所述的管理端装置,其特征在于:其中,当所述管理网络的管理网络平面、存储网络平面以及业务网络平面均正常时,操作A-2中所述计算节点装置通过管理网络上报的网络状态才判断为正常,否则根据异常的所述计算节点装置的具体中断类型是管理网络平面、存储网络平面以及业务网络平面中的哪一种或几种进行相应的处理。
- 根据权利要求2所述的管理端装置,其特征在于:其中,其中,所述管理网络包括:管理网络平面,用于对接所述管理端装置,用于提供管理服务;存储网络平面,用于对接后端的所述共享存储装置,用于提供存储服务;业务网络平面,用于对接所述计算节点装置,用于提供虚拟机VM的访问服务,对应的,当所述管理网络的管理网络平面、存储网络平面以及业务网络平面均正常时,操作B-3中所述计算节点装置通过管理网络上报的网络状态才判断为正常,否则根据异常的所述计算节点装置的具体中断类型是管理网络平面、存储网络平面以及业务网络平面中的哪一种或几种进行相应的隔离处理。
- 防脑裂的OpenStack虚拟机高可用的管理端装置的管理方法,包括以下操作:操作A-1,通过收集的运行状况信息检查集群状态是否正常,如果异常,则触发集群异常告警并结束,如果正常,则转到操作A-2;操作A-2,检查各个所述计算节点装置通过管理网络上报的状态,如果正常,则此轮检查终止,否则转到下一步操作A-3;操作A-3,根据每个所述计算节点装置通过管理网络上报的异常状态,逐个判断是否需要进行处理,如果无需处理,则该计算节点装置异常处理结束,转回上一步操作A-2;否则转到下一步操作A-4;操作A-4,对于需要处理的异常状态的所述计算节点装置,检查与之连接的共享存储装置的状态,当共享存储装置异常时,通过所述Nova模块控制该计算节点装置上运行的所述云计算虚拟机VM程序不运行,并结束,否则,转到下一步操作A-5;操作A-5,向所连接的共享存储装置状态正常的所述计算节点装置下发隔离请求;操作A-6,向所述Nova模块下发命令,触发该计算节点装置上运行的所述云计算虚拟机VM程序运行。
- 根据权利要求9所述的管理方法,其特征在于:其中,向所连接的共享存储装置状态正常的所述计算节点装置下发隔离请求后,还运行以下操作:操作B-1,持续监听所述计算节点装置上报的隔离事件,一旦收到消息则转到操作B-2;操作B-2,通过收集的运行状况信息检查集群状态是否正常,如果异常,则触发集群异常告警并结束,如果正常,则转到操作B-3;操作B-3,检查各个所述计算节点装置通过管理网络上报的网络状态,如果正常,则此轮检查终止,否则转到操作B-4;操作B-4,根据每个所述计算节点装置通过管理网络上报的异常状态,判断是否需要进行处理,如果无需处理,则进行操作B-6;否则转到操作B-5;操作B-5,对于需要处理的异常状态的所述计算节点装置,检查与之连接的共享存储装置的状态,当共享存储装置异常时,无需隔离并转到操作B-6,并结束,否则,转到操作B-7;操作B-6,针对无需隔离的场景,向对应的所述计算节点装置下发停止隔离请求;操作B-7,针对需要隔离的场景,向对应的所述计算节点装置下发执行隔离请求。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
BR112020004404-0A BR112020004404A2 (pt) | 2018-12-04 | 2018-12-18 | dispositivo terminal de gerenciamento de alta disponibilidade, e, método de gerenciamento de um dispositivo terminal de gerenciamento. |
PH12020550049A PH12020550049A1 (en) | 2018-12-04 | 2020-02-07 | High-availability management end device and management method of OpenStack virtual machine for preventing split-brain |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201811475904.4A CN109634716B (zh) | 2018-12-04 | 2018-12-04 | 防脑裂的OpenStack虚拟机高可用管理端装置及管理方法 |
CN201811475904.4 | 2018-12-04 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2020113668A1 true WO2020113668A1 (zh) | 2020-06-11 |
Family
ID=66071111
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2018/121648 WO2020113668A1 (zh) | 2018-12-04 | 2018-12-18 | 防脑裂的OpenStack虚拟机高可用管理端装置及管理方法 |
Country Status (4)
Country | Link |
---|---|
CN (1) | CN109634716B (zh) |
BR (1) | BR112020004404A2 (zh) |
PH (1) | PH12020550049A1 (zh) |
WO (1) | WO2020113668A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113535336A (zh) * | 2021-09-16 | 2021-10-22 | 深圳创新科技术有限公司 | 一种Cloudstack在国产服务器的部署运行方法及装置 |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110134518B (zh) * | 2019-05-21 | 2023-09-01 | 浪潮软件集团有限公司 | 一种提高大数据集群多节点应用高可用性的方法及系统 |
CN110297690A (zh) * | 2019-06-28 | 2019-10-01 | 深圳前海微众银行股份有限公司 | 基于云计算的虚拟机使用方法、装置、设备及可读存储介质 |
CN112398668B (zh) * | 2019-08-14 | 2022-08-23 | 北京东土科技股份有限公司 | 一种基于IaaS集群的云平台和节点的切换方法 |
CN110825487B (zh) * | 2019-09-19 | 2022-07-15 | 烽火通信科技股份有限公司 | 一种虚拟机防脑裂的管理方法及主服务器 |
CN111212127A (zh) * | 2019-12-29 | 2020-05-29 | 浪潮电子信息产业股份有限公司 | 一种存储集群及业务数据的维护方法、装置和存储介质 |
CN111240895A (zh) * | 2019-12-31 | 2020-06-05 | 深圳证券通信有限公司 | 一种面向OpenStack的节点批量备份系统的方法 |
CN114090184B (zh) * | 2021-11-26 | 2022-11-29 | 中电信数智科技有限公司 | 一种虚拟化集群高可用性的实现方法和设备 |
CN115811461B (zh) * | 2023-02-08 | 2023-04-28 | 湖南国科亿存信息科技有限公司 | San共享存储集群脑裂预防处理方法、装置及电子设备 |
CN116382850B (zh) * | 2023-04-10 | 2023-11-07 | 北京志凌海纳科技有限公司 | 一种利用多存储心跳检测的虚拟机高可用管理装置及系统 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103684941A (zh) * | 2013-11-23 | 2014-03-26 | 广东新支点技术服务有限公司 | 基于仲裁服务器的集群裂脑预防方法和装置 |
US8874954B1 (en) * | 2012-10-19 | 2014-10-28 | Symantec Corporation | Compatibility of high availability clusters supporting application failover with shared storage in a virtualization environment without sacrificing on virtualization features |
CN107239383A (zh) * | 2017-06-28 | 2017-10-10 | 郑州云海信息技术有限公司 | 一种OpenStack虚拟机的故障监控方法及装置 |
CN107885576A (zh) * | 2017-10-16 | 2018-04-06 | 北京易讯通信息技术股份有限公司 | 一种基于OpenStack的私有云中虚拟机HA的方法 |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104253860B (zh) * | 2014-09-11 | 2017-08-08 | 武汉噢易云计算股份有限公司 | 一种基于共享存储消息队列的虚拟机高可用实现方法 |
-
2018
- 2018-12-04 CN CN201811475904.4A patent/CN109634716B/zh active Active
- 2018-12-18 WO PCT/CN2018/121648 patent/WO2020113668A1/zh active Application Filing
- 2018-12-18 BR BR112020004404-0A patent/BR112020004404A2/pt not_active IP Right Cessation
-
2020
- 2020-02-07 PH PH12020550049A patent/PH12020550049A1/en unknown
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8874954B1 (en) * | 2012-10-19 | 2014-10-28 | Symantec Corporation | Compatibility of high availability clusters supporting application failover with shared storage in a virtualization environment without sacrificing on virtualization features |
CN103684941A (zh) * | 2013-11-23 | 2014-03-26 | 广东新支点技术服务有限公司 | 基于仲裁服务器的集群裂脑预防方法和装置 |
CN107239383A (zh) * | 2017-06-28 | 2017-10-10 | 郑州云海信息技术有限公司 | 一种OpenStack虚拟机的故障监控方法及装置 |
CN107885576A (zh) * | 2017-10-16 | 2018-04-06 | 北京易讯通信息技术股份有限公司 | 一种基于OpenStack的私有云中虚拟机HA的方法 |
Non-Patent Citations (1)
Title |
---|
WU, JIANG: "A Better VM HA Solution: Split-brain Solving & Host Network Fault Awareness", OPEN INFRASTRUCTURE SUMMIT, 14 November 2018 (2018-11-14), DOI: 20190816195942A * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113535336A (zh) * | 2021-09-16 | 2021-10-22 | 深圳创新科技术有限公司 | 一种Cloudstack在国产服务器的部署运行方法及装置 |
Also Published As
Publication number | Publication date |
---|---|
PH12020550049A1 (en) | 2020-10-12 |
CN109634716B (zh) | 2021-02-09 |
BR112020004404A2 (pt) | 2021-06-22 |
CN109634716A (zh) | 2019-04-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2020113668A1 (zh) | 防脑裂的OpenStack虚拟机高可用管理端装置及管理方法 | |
WO2020113669A1 (zh) | 防脑裂的OpenStack虚拟机高可用计算节点装置及管理方法 | |
WO2020113670A1 (zh) | 防脑裂的OpenStack虚拟机高可用系统 | |
US10621005B2 (en) | Systems and methods for providing zero down time and scalability in orchestration cloud services | |
US9720757B2 (en) | Securing crash dump files | |
US9684545B2 (en) | Distributed and continuous computing in a fabric environment | |
US8458422B1 (en) | Policy based creation of export sets and backup media | |
US9652326B1 (en) | Instance migration for rapid recovery from correlated failures | |
US20130185716A1 (en) | System and method for providing a virtualized replication and high availability environment | |
US9703651B2 (en) | Providing availability of an agent virtual computing instance during a storage failure | |
US20140173329A1 (en) | Cascading failover of blade servers in a data center | |
US20220269414A1 (en) | Snapshotting a containerized application | |
Glider et al. | The software architecture of a san storage control system | |
US11119872B1 (en) | Log management for a multi-node data processing system | |
US7467324B1 (en) | Method and apparatus for continuing to provide processing on disk outages | |
JP3467750B2 (ja) | 分散オブジェクト処理システム | |
WO2022108914A1 (en) | Live migrating virtual machines to a target host upon fatal memory errors | |
US8533331B1 (en) | Method and apparatus for preventing concurrency violation among resources | |
Lee et al. | NCU-HA: A lightweight HA system for kernel-based virtual machine | |
US11977431B2 (en) | Memory error prevention by proactive memory poison recovery | |
US20240202072A1 (en) | Hardware Memory Error Tolerant Software System | |
US20240134961A1 (en) | Methods and systems that monitor system-call-integrity | |
JP2022007301A (ja) | 復旧制御装置及び復旧制御方法 | |
Sultan et al. | Using remote memory communication for self-healing systems | |
Vallath et al. | Testing for Availability |
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: 18942217 Country of ref document: EP Kind code of ref document: A1 |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112020004404 Country of ref document: BR |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 112020004404 Country of ref document: BR Kind code of ref document: A2 Effective date: 20200304 |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 18942217 Country of ref document: EP Kind code of ref document: A1 |