CN109491764A - A kind of virtual-machine fail management method based on openstack - Google Patents
A kind of virtual-machine fail management method based on openstack Download PDFInfo
- Publication number
- CN109491764A CN109491764A CN201811383753.XA CN201811383753A CN109491764A CN 109491764 A CN109491764 A CN 109491764A CN 201811383753 A CN201811383753 A CN 201811383753A CN 109491764 A CN109491764 A CN 109491764A
- Authority
- CN
- China
- Prior art keywords
- virtual
- machine
- virtual machine
- physical host
- openstack
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
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
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/301—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is a virtual computing platform, e.g. logically partitioned systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
-
- 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/45575—Starting, stopping, suspending or resuming virtual machine instances
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Quality & Reliability (AREA)
- Mathematical Physics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The virtual-machine fail management method based on openstack that the present invention provides a kind of, it is characterized in that including the following steps: 1) to carry out failure monitoring to virtual machine；2) when listening to virtual-machine fail, where checking virtual machine 3) state of physical host enters step if physical host state is normal, if physical host is abnormal, issues and alarms to administrator；3) heartbeat message for detecting virtual machine, judging virtual machine according to heartbeat message, whether failure if virtual-machine fail restarts virtual machine.When this method permission can encounter failure in use, it timely feedbacks to administrator and solves, the use feeling of user not only can be improved, it can also find, position faster and prevent some problems, the ease for use of entire environment is improved, it can also be to there is one clearly to record the problem of encountering in environment.
Description
Technical field
The virtual-machine fail management method based on openstack that the present invention relates to a kind of.
Background technique
In the prior art, well known technology is with the growth of information explosion formula, and cloud platform has obtained more and more
Concern, OpenStack manage platform as the cloud computing of a open source, the favor of many companies are obtained, in the use of virtual machine
In the process, if virtual machine damages or more serious failure occurs, administrator can check and handle on interface, but
If the problem of user encounters in use, but the horizon page, the state of virtual machine is still normal, and administrator is
It has no idea to find such problems, it is therefore desirable to which a kind of failure management method can quickly handle virtual-machine fail, and energy
Notify administrator.This is existing deficiencies in the technology.
Summary of the invention
The purpose of the present invention is to deficiencies of the prior art, and provide a kind of void based on openstack
Quasi- machine failure management method is timely feedbacked to administrator and is solved, in this way when this method permission can encounter failure in use
The use feeling of user not only can be improved, can also find, position and prevent some problems faster, improve entire environment
Ease for use, can also be to there is one clearly to record the problem of encountering in environment.
This programme is achieved by the following technical measures: a kind of virtual-machine fail manager based on openstack
Method includes the following steps: 1) to carry out failure monitoring to virtual machine；2) it when listening to virtual-machine fail, checks where virtual machine
3) state of physical host enters step if physical host state is normal, if physical host is abnormal, to administrator
Issue alarm；3) heartbeat message for detecting virtual machine, according to heartbeat message judge virtual machine whether failure, if virtual machine is former
Barrier, then restart virtual machine.First determine whether in this way physical host whether failure, rather than directly restart virtual machine, can give in this way
User preferably experiences, and avoids restarting virtual machine without reason.
Where checking virtual machine in the step 2) when the state of physical host, physical host where judging virtual machine
Current resource service condition, if cpu or memory usage are 100%, physical host is abnormal, if cpu utilization rate * 0.5+
Memory usage * 0.5 is greater than the set value, and the setting value is 90%, then physical host is abnormal.It may determine that so virtual
Whether machine is abnormal, handles convenient for administrator.
When physical host exception, virtual machine is restarted, and check physical host state again, if still physical host is different
Often, then virtual machine is restarted again, when restarting number and reaching n times, closes fictitious host computer, and issue and alarm and record to administrator
Failure, wherein n≤5.Whether be the operation of virtual machine influence physical host, and set and restart number if may determine that in this way,
Avoid it is unconfined restart, improve the usage experience of user.
In the step 1) when carrying out failure monitoring to virtual machine, mirror image is carried out to virtual machine in real time and is deposited
Storage.When thus being avoided that failure, the case where loss of data, and after mirror image, use can be direct plungeed into.
When detecting virtual machine heartbeat message, cycle T is set, if being used to update to listen to virtual machine in cycle T
Heartbeat message when, then judge virtual-machine fail.In step 3), after restarting virtual machine, restart if repeating step 3) virtual machine
Number is more than n, then notifies administrator, and creates new virtual machine, before new virtual machine using restarting for the first time in step 3)
The mirror image of former virtual machine.It is able to confirm that whether be that the failure of virtual machine itself is saved without restarting for unlimited number in this way
Resource.After creating new virtual machine, the data disks of former virtual machine carry are formatted.Both can to avoid loss of data,
Can make the data disks of physical host will not be influenced by user before.
It can be seen that compared with prior art, the present invention implementing with substantive distinguishing features outstanding and significant progress
Beneficial effect be also obvious.
Detailed description of the invention
Fig. 1 is the flow chart of the specific embodiment of the invention.
Specific embodiment
In order to clarify the technical characteristics of the invention, below by a specific embodiment, and its attached drawing is combined, it is right
This programme is illustrated.
By attached drawing as can be seen that the virtual-machine fail management method based on openstack of this programme, including walk as follows
It is rapid: 1) failure monitoring to be carried out to virtual machine；Mirror image is carried out to virtual machine in real time and is stored；2) virtual-machine fail is being listened to
When, where checking virtual machine 3) state of physical host enters step if physical host state is normal, if physics master
Machine is abnormal, then issues and alarm to administrator；3) heartbeat message for detecting virtual machine judges whether virtual machine is former according to heartbeat message
Barrier, if virtual-machine fail, restarts virtual machine, when detecting virtual machine heartbeat message, cycle T is set, if in cycle T
For listen to virtual machine for update heartbeat message when, then judge virtual-machine fail.
Where checking virtual machine in step 2 when the state of physical host, the current money of physical host where judging virtual machine
Source service condition, if cpu or memory usage are 100%, physical host is abnormal, if cpu utilization rate * 0.5+ memory makes
It is greater than the set value with rate * 0.5, setting value 90%, then physical host is abnormal.When physical host exception, virtual machine is restarted, lay equal stress on
It newly checks physical host state, if still physical host is abnormal, restarts virtual machine again, when restarting number and reaching n times,
Fictitious host computer is closed, and is issued to administrator and alarms and records failure, wherein n≤5.
In step 3), after restarting virtual machine, if repeating step 3) virtual machine to restart number to be more than n, administrator is notified,
And new virtual machine is created, new virtual machine is created new using the mirror image of the former virtual machine before restarting for the first time in step 3)
After virtual machine, the data disks of former virtual machine carry are formatted.
The present invention is not limited in above-mentioned specific embodiment, and those of ordinary skill in the art are in essential scope of the invention
The variations, modifications, additions or substitutions inside made, also should belong to protection scope of the present invention.
Claims (8)
1. a kind of virtual-machine fail management method based on openstack, it is characterized in that including the following steps:
1) failure monitoring is carried out to virtual machine；
2) when listening to virtual-machine fail, the state of physical host where checking virtual machine, if physical host state is normal,
It then enters step 3), if physical host is abnormal, issues and alarm to administrator；
3) heartbeat message for detecting virtual machine judges whether failure weighs if virtual-machine fail virtual machine according to heartbeat message
Open virtual machine.
2. the virtual-machine fail management method according to claim 1 based on openstack, it is characterized in that: the step
It is rapid 2) in when checking the state of physical host where virtual machine, the Current resource of physical host uses feelings where judging virtual machine
Condition, if cpu or memory usage are 100%, physical host is abnormal, if cpu utilization rate * 0.5+ memory usage * 0.5
It is greater than the set value, then physical host is abnormal.
3. the virtual-machine fail management method according to claim 2 based on openstack, it is characterized in that: described sets
Definite value is 90%.
4. the virtual-machine fail management method according to claim 1 or 2 based on openstack, it is characterized in that: physics master
When machine exception, virtual machine is restarted, and check physical host state again, if still physical host is abnormal, restart void again
Quasi- machine closes fictitious host computer, and issue to administrator and alarm and record failure, wherein n≤5 when restarting number and reaching n times.
5. the virtual-machine fail management method according to claim 1 based on openstack, it is characterized in that: the step
It is rapid 1) in when carrying out failure monitoring to virtual machine, in real time virtual machine mirror image and store.
6. the virtual-machine fail management method according to claim 5 based on openstack, it is characterized in that: empty in detection
When quasi- movement hop-information, set cycle T, if in cycle T for listen to virtual machine for update heartbeat message when, sentence
Disconnected virtual-machine fail.
7. the virtual-machine fail management method according to claim 6 based on openstack, it is characterized in that: in step 3),
After restarting virtual machine, if repeating step 3) virtual machine to restart number to be more than n, administrator is notified, and create new virtual machine,
New virtual machine uses the mirror image of the former virtual machine before restarting for the first time in step 3).
8. the virtual-machine fail management method according to claim 7 based on openstack, it is characterized in that: creating newly
After virtual machine, the data disks of former virtual machine carry are formatted.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811383753.XA CN109491764A (en) | 2018-11-20 | 2018-11-20 | A kind of virtual-machine fail management method based on openstack |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811383753.XA CN109491764A (en) | 2018-11-20 | 2018-11-20 | A kind of virtual-machine fail management method based on openstack |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN109491764A true CN109491764A (en) | 2019-03-19 |
Family
ID=65696335
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811383753.XA Pending CN109491764A (en) | 2018-11-20 | 2018-11-20 | A kind of virtual-machine fail management method based on openstack |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109491764A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110264716A (en) * | 2019-06-25 | 2019-09-20 | 徐海连 | A kind of intelligent transportation system and application method based on Internet of Things |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102110071A (en) * | 2011-03-04 | 2011-06-29 | 浪潮(北京)电子信息产业有限公司 | Virtual machine cluster system and implementation method thereof |
| CN107734026A (en) * | 2017-10-11 | 2018-02-23 | 郑州云海信息技术有限公司 | A kind of design method, device and the equipment of network attached storage cluster |
| CN107885576A (en) * | 2017-10-16 | 2018-04-06 | 北京易讯通信息技术股份有限公司 | A kind of virtual machine HA method in private clound based on OpenStack |
| CN108108255A (en) * | 2016-11-25 | 2018-06-01 | 中兴通讯股份有限公司 | The detection of virtual-machine fail and restoration methods and device |
| CN108733454A (en) * | 2018-05-29 | 2018-11-02 | 郑州云海信息技术有限公司 | A kind of virtual-machine fail treating method and apparatus |
-
2018
- 2018-11-20 CN CN201811383753.XA patent/CN109491764A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102110071A (en) * | 2011-03-04 | 2011-06-29 | 浪潮(北京)电子信息产业有限公司 | Virtual machine cluster system and implementation method thereof |
| CN108108255A (en) * | 2016-11-25 | 2018-06-01 | 中兴通讯股份有限公司 | The detection of virtual-machine fail and restoration methods and device |
| CN107734026A (en) * | 2017-10-11 | 2018-02-23 | 郑州云海信息技术有限公司 | A kind of design method, device and the equipment of network attached storage cluster |
| CN107885576A (en) * | 2017-10-16 | 2018-04-06 | 北京易讯通信息技术股份有限公司 | A kind of virtual machine HA method in private clound based on OpenStack |
| CN108733454A (en) * | 2018-05-29 | 2018-11-02 | 郑州云海信息技术有限公司 | A kind of virtual-machine fail treating method and apparatus |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110264716A (en) * | 2019-06-25 | 2019-09-20 | 徐海连 | A kind of intelligent transportation system and application method based on Internet of Things |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| TWI746512B (en) | Physical machine fault classification processing method and device, and virtual machine recovery method and system | |
| US9110918B1 (en) | Systems and methods for measuring compliance with a recovery point objective for an application | |
| CN105024879B (en) | Virtual-machine fail detection, recovery system and virtual machine testing, recovery, start method | |
| US8996932B2 (en) | Cloud management using a component health model | |
| CN107248927A (en) | Generation method, Fault Locating Method and the device of fault location model | |
| US20150161025A1 (en) | Injecting Faults at Select Execution Points of Distributed Applications | |
| CN104685830A (en) | Fault management method, entity and system | |
| CN103440160A (en) | Virtual machine recovering method and virtual machine migration method , device and system | |
| Kc et al. | ELT: Efficient log-based troubleshooting system for cloud computing infrastructures | |
| CN105373899A (en) | Server asset management method and apparatus | |
| US9389942B2 (en) | Determine when an error log was created | |
| CN107656705B (en) | Computer storage medium and data migration method, device and system | |
| EP3178004B1 (en) | Recovering usability of cloud based service from system failure | |
| Mogul et al. | Thinking about availability in large service infrastructures | |
| CN107153571A (en) | A kind of dispositions method and device of virtual management node | |
| US8707107B1 (en) | Systems and methods for proactively facilitating restoration of potential data failures | |
| WO2015154517A1 (en) | Software failure locating method, apparatus and equipment | |
| CN109254922A (en) | A kind of automated testing method and device of server B MC Redfish function | |
| US11196624B2 (en) | Method and system for managing virtual datacenters | |
| CN108958965A (en) | A kind of BMC monitoring can restore the method, device and equipment of ECC error | |
| CA3172788A1 (en) | Endpoint security using an action prediction model | |
| CN108228308A (en) | The monitoring method and device of virtual machine | |
| CN114064217B (en) | OpenStack-based node virtual machine migration method and device | |
| CN109800052B (en) | Anomaly detection and positioning method and device applied to distributed container cloud platform | |
| CN109491764A (en) | A kind of virtual-machine fail management method based on openstack |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20190319 |