OpenStack Bare Metal Node High Availability via Control Node Failover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
OpenStack lacks complete availability, as services running on bare metal nodes are not automatically saved if the underlying node experiences issues, leading to service disruptions.
Innovation Solution
Implementing a method using a control node to set up a main and backup bare metal node, where the control node manages the installation of an operating system image file, monitors node status, and automatically switches to the backup node if the main node fails, ensuring continuous service execution through power control and IP address management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If OpenStack is used as a cloud computing management platform, then it provides simple, scalable, and standardized management, but it lacks complete availability and services are not automatically saved when bare metal nodes fail
Solution Approach 1:
The patent implements preliminary action by pre-configuring backup bare metal nodes with the same operating system image files before failures occur. When a main bare metal node fails, the system can immediately activate a backup node without needing to perform installation or configuration at that moment, thus ensuring service continuity while maintaining system reliability.
Solution Approach 2:
The patent applies copying by creating duplicate operating system image files on both main and backup bare metal nodes. The backup nodes contain identical copies of the OS images, allowing immediate substitution when a main node fails. This copying mechanism enables automatic service preservation without requiring complex data recovery processes.
2Reliability
If backup bare metal nodes are configured to ensure high availability, then service continuity is improved, but the complexity of node management and image file distribution increases
Solution Approach 1:
The patent implements universality by designing a control node with multi-functional capabilities. The control node can simultaneously manage multiple bare metal nodes, distribute operating system image files to both main and backup nodes, monitor node status, and perform failover operations. This consolidates multiple management functions into a single universal controller, reducing overall system complexity despite having backup nodes.
Solution Approach 2:
The patent applies feedback by implementing a status monitoring mechanism where the control node continuously receives status information from bare metal nodes. When a node's status changes (e.g., from normal to abnormal), the system receives feedback and automatically triggers the appropriate response (activating a backup node). This automated feedback loop simplifies management by eliminating manual intervention while ensuring service continuity.
3Reliability
If automatic failover to backup nodes is implemented, then service disruption is prevented, but the complexity of monitoring and switching mechanisms increases
Solution Approach 1:
The patent implements self-service by enabling the system to automatically detect node failures and activate backup nodes without human intervention. The control node monitors the status of main bare metal nodes, and when a failure is detected, the system automatically switches to a backup node and activates the appropriate operating system image. This automated self-service mechanism prevents service disruptions while keeping the monitoring and switching logic centralized and manageable.
Data Source
AI summary
A method for implementing high availability of bare metal node based on OpenStack utilizes a control node communicating through a power control network with a main bare metal node and a backup bare metal node. The control node turns on a power supply to activate an operating system image file installed in the main bare metal node. Information as to status is sent to the control node by the main bare metal node, and if the status information ceases, the control node, switches off the power supply to the main bare metal node. The control node turns on a power supply to the backup bare metal node to activate the operating system image file therein and selects as subsequent backup a further bare metal node and installs activate the operating system image file therein.