WO2015109955A1 - 电信云中异常事件的处理方法及装置 - Google Patents

电信云中异常事件的处理方法及装置 Download PDF

Info

Publication number
WO2015109955A1
WO2015109955A1 PCT/CN2015/070455 CN2015070455W WO2015109955A1 WO 2015109955 A1 WO2015109955 A1 WO 2015109955A1 CN 2015070455 W CN2015070455 W CN 2015070455W WO 2015109955 A1 WO2015109955 A1 WO 2015109955A1
Authority
WO
WIPO (PCT)
Prior art keywords
iaas
application layer
proxy process
abnormal event
proxy
Prior art date
Application number
PCT/CN2015/070455
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 WO2015109955A1 publication Critical patent/WO2015109955A1/zh
Priority to US15/220,116 priority Critical patent/US10187181B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/06—Generation of reports
    • H04L43/065—Generation of reports related to network devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • 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/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Definitions

  • the present invention relates to the field of telecommunication cloud technologies, and in particular, to a method and an apparatus for processing an abnormal event in a telecommunication cloud.
  • a layered architecture in which the service application layer is separated and decoupled from the IaaS (Infrastructure as a Service) layer is widely applied to telecommunication systems.
  • the hardware device is managed by the IaaS layer and is transparent to the service application.
  • the service application is generally running in a VM (Virtual Machine), as shown in Figure 1.
  • VM1 runs the main service process and processes the service.
  • VM2 runs the standby service process and does not process the service.
  • the standby service process synchronizes the state and data from the main service process.
  • the management process deployed on the VM3 monitors the processes running on the system. If the management process detects that the service process on the VM1 is abnormal, the standby service process on the VM2 is notified to be converted into the main service process.
  • the business process is processed, and the main business process on VM1 is transformed into a standby business process, thereby realizing the recovery of the service, as shown in FIG. 2B.
  • the resource status of the IaaS layer changes, such as a hardware failure or a Host OS running the host operating system, the host operating system crashes. It is required to provide related notification capabilities at the IaaS layer, handle exception events, and perform service migration and fault isolation operations together with the IaaS layer to provide users with highly reliable telecommunication services.
  • the abnormal event notification processing when the abnormal event notification processing is performed, as shown in FIG. 3, when the IaaS proxy process detects that the VM has failed, the fault is reported to the IaaS management center node, and the IaaS management center node notifies the application layer management center node, and finally The application layer management center node notifies the application layer management process.
  • the channel path is relatively long, and the abnormal event cannot be timely.
  • the notification is sent to the application layer, and both the application layer management center node and the IaaS management center node are management maintenance nodes, and the management maintenance node is used as a failure notification channel, and the reliability is relatively low.
  • the embodiment of the invention provides a method and a device for processing an abnormal event in a telecommunication cloud, so as to shorten the notification path and increase the reliability.
  • the first aspect provides a method for processing an abnormal event in a telecommunications cloud, including:
  • the infrastructure as a service IaaS proxy process detects resource status
  • the resource status abnormal event detected by the IaaS proxy process is sent to the application layer proxy process by the fault notification channel between the IaaS proxy process and the application layer proxy process established in advance in the host Host, by the application layer.
  • the agent process requests the application layer management process to process the abnormal event according to the degree of influence of the resource status abnormal event on the actual service; and/or
  • the resource status abnormal event detected by the IaaS proxy process is sent to the application layer management process by the fault notification channel between the IaaS proxy process and the application layer management process, which is pre-established in the host Host, by the application layer.
  • the management process processes the abnormal event according to the degree of influence of the resource status abnormal event on the actual service.
  • the method before the IaaS proxy process detects the resource status, the method further includes:
  • the IaaS proxy process receives the abnormal event notification service request sent by the application layer management center node;
  • the IaaS proxy process notifies the service request according to the abnormal event, creates a fault notification channel, and starts an abnormal event notification service;
  • the IaaS proxy process feeds back the access address, the access channel type, and the exchange protocol type of the abnormal event notification service to the application layer management center node, and indicates the application layer proxy process or the application layer management process according to the access address. And the access channel type and the exchange protocol type access the abnormal event notification service.
  • the IaaS proxy process detects a resource status, including:
  • the IaaS proxy process receives a subscription request sent by an application layer proxy process or an application layer management process
  • the IaaS proxy process detects the resource status associated with the subscription request based on the subscription request.
  • the IaaS proxy process detects a resource status, including:
  • the IaaS proxy process receives a subscription request that is sent by the application layer management process and includes a subscription relationship, where the subscription relationship is used to indicate the virtual machine that the application layer management process wants to pay attention to and the resource state of the virtual machine to be concerned about;
  • the IaaS proxy process searches for the IaaS proxy process to which the virtual machine belongs, and obtains the IaaS proxy process to be followed;
  • the IaaS proxy process sends the subscription relationship to the IaaS proxy process to be followed, and instructs the IaaS proxy process to monitor the resource status of the virtual machine to be focused according to the subscription relationship.
  • the IaaS proxy process receives a subscription request that includes a subscription relationship that is sent by the application layer management process, and specifically includes:
  • the IaaS proxy process receives the subscription request through a fault notification channel between the IaaS proxy process and an application layer management process;
  • the IaaS proxy process receives the subscription request through a fault notification channel between an application layer management process, an application layer management center node, and an IaaS proxy process.
  • the second aspect provides a method for processing an abnormal event in a telecommunications cloud, including:
  • the application layer proxy process receives the resource status abnormal event delivered by the infrastructure as a service IaaS proxy process through the failure notification channel between the IaaS proxy process and the application layer proxy process pre-established in the host host;
  • the application layer proxy process When the degree of influence of the resource status abnormal event on the actual service reaches a set level, the application layer proxy process requests the application layer management process to process the abnormal event.
  • the method before the application layer proxy process receives the resource state exception event delivered by the IaaS proxy process, the method further includes:
  • the application layer proxy process receives an access indication sent by the application layer management center node, where the access indication includes an access address, an access channel type, and an exchange protocol type of the abnormal event notification service fed back by the IaaS proxy process. ;
  • the application layer proxy process accesses the abnormal event notification service according to the access address, the access channel type, and the exchange protocol type included in the access indication.
  • the method further includes:
  • the application layer proxy process sends a subscription request to the IaaS proxy process, requesting the IaaS proxy process to deliver a resource status related to the subscription request.
  • the third aspect provides a method for processing an abnormal event in a telecommunications cloud, including:
  • the application layer management process receives the resource status abnormal event delivered by the infrastructure as a service IaaS proxy process through the failure notification channel between the IaaS proxy process and the application layer management process pre-established in the host host;
  • the application layer management process processes the abnormal event.
  • the method before the application layer management process receives the resource status exception event delivered by the IaaS proxy process, the method further includes:
  • an access indication where the access indication includes an access address, an access channel type, and an exchange protocol type of the abnormal event notification service fed back by the IaaS proxy process;
  • the application layer management process accesses the abnormal event notification service according to the access address, the access channel type, and the exchange protocol type included in the access indication.
  • the method further includes:
  • the application layer management process sends a subscription request to the IaaS proxy process, requesting the IaaS proxy process to deliver a resource status related to the subscription request.
  • the application layer management process sends a subscription including a subscription relationship to the IaaS proxy process by using a fault notification channel between the IaaS proxy process and an application layer management process. And requesting, by the IaaS proxy process, the resource status of the virtual machine to be focused on, where the subscription relationship is used to indicate a virtual machine that the application layer management process wants to pay attention to and a resource state to be concerned about the virtual machine; or
  • the application layer management process sends a subscription request including a subscription relationship to the IaaS proxy process through the fault notification channel between the application layer management process, the application layer management center node, and the IaaS proxy process, and requests the IaaS proxy process to Sending the resource state of the virtual machine to be concerned, the subscription relationship is used to indicate the virtual machine that the application layer management process wants to pay attention to and the resource state of the virtual machine to be concerned about.
  • the fourth aspect provides a processing device for an abnormal event in a telecommunication cloud, including a detecting unit and a sending unit, where
  • the detecting unit is configured to detect a resource status
  • the sending unit is configured to send the resource status abnormal event detected by the detecting unit to a fault notification channel between the infrastructure IaaS proxy process and the application layer proxy process that is pre-established in the host Host To the application layer proxy process, the application layer proxy process requests the application layer management process to process the abnormal event according to the degree of influence of the resource state abnormal event on the actual service; and/or
  • the resource status abnormal event detected by the detecting unit is sent to the application layer management process by the fault notification channel between the IaaS proxy process and the application layer management process, which is pre-established in the host Host, and is managed by the application layer.
  • the process processes the abnormal event according to the degree of influence of the resource status abnormal event on the actual service.
  • the sending unit is further configured to:
  • an access address, an access channel type, and a switching protocol type of the abnormal event notification service indicating that the application layer proxy process or the application layer management process is configured according to the access address
  • the access channel type and the exchange protocol type access the abnormal event notification service.
  • the detecting unit is configured to:
  • a resource status associated with the subscription request is detected based on the subscription request.
  • the detecting unit is configured to:
  • a subscription request that includes a subscription relationship, where the subscription relationship is used to indicate a virtual machine that the application layer management process wants to pay attention to and a resource state that is to be followed by the virtual machine;
  • the detecting unit is specifically configured to:
  • the subscription request is received through a failure notification channel between an application layer management process, an application layer management center node, and an IaaS proxy process.
  • the fifth aspect provides a processing device for an abnormal event in a telecommunication cloud, including a receiving unit and a requesting unit, where
  • the receiving unit is configured to receive, by the infrastructure-as-a-service IaaS proxy process, a resource status abnormal event sent by the fault notification channel between the IaaS proxy process and the application layer proxy process that is pre-established in the host host;
  • the requesting unit is configured to request the application layer management process to process the abnormal event when the degree of influence of the resource status abnormal event on the actual service reaches a set level.
  • the receiving unit is further configured to:
  • the access indication includes an access address, an access channel type, and an exchange protocol type of the abnormal event notification service fed back by the IaaS proxy process, and according to the The access address, the access channel type, and the exchange protocol type included in the incoming indication access the abnormal event notification service.
  • the requesting unit is further configured to:
  • the sixth aspect provides a processing device for an abnormal event in a telecommunication cloud, including a receiving unit and a processing unit, where
  • the receiving unit is configured to receive, by the infrastructure-as-a-service IaaS proxy process, a resource status abnormal event delivered by a fault notification channel between the infrastructure-as-a-service IaaS proxy process and the application layer management process, which is pre-established in the host host;
  • the processing unit is configured to process the abnormal event when the impact of the resource status abnormal event on the actual service reaches a set level.
  • the receiving unit is further configured to:
  • an access indication sent by the node of the management center where the access indication includes an access address, an access channel type, and an exchange protocol type of the abnormal event notification service fed back by the IaaS proxy process, and according to the The access address, the access channel type, and the exchange protocol type included in the incoming indication access the abnormal event notification service.
  • the apparatus further includes a request unit, where
  • the requesting unit is configured to send a subscription request to the IaaS proxy process, and request the IaaS proxy process to deliver a resource status related to the subscription request, before receiving the resource state exception event sent by the IaaS proxy process.
  • the requesting unit is configured to:
  • the subscription relationship is used to indicate a virtual machine that the application layer management process wants to pay attention to and a resource state to be concerned about the virtual machine;
  • the resource status of the machine, the subscription relationship is used to indicate the virtual machine that the application layer management process wants to pay attention to and the resource state of the virtual machine to be concerned about.
  • the method and device for processing an abnormal event in the telecommunication cloud provided by the embodiment of the present invention, by using a fault notification channel between the IaaS proxy process and the application layer proxy process established in the Host, or between the IaaS proxy process and the application layer management process
  • the fault notification channel directly delivers the detected resource status abnormal event to the application layer proxy process or the application layer management process without shortening the notification path and enhancing the reliability without passing through the IaaS management center and the application layer management center node.
  • FIG. 1 is a schematic diagram showing the structure of a telecommunications cloud layered architecture in the prior art
  • 2A-2B are schematic diagrams showing a process of implementing a service process migration in the prior art
  • FIG. 3 is a schematic diagram of an abnormal event notification processing process in the prior art
  • FIG. 4 is a system architecture diagram of establishing a fault notification channel between a guest and a Host according to an embodiment of the present invention
  • FIG. 5 is a flowchart of an abnormal event notification process in a telecommunications cloud according to an embodiment of the present invention
  • 6A-6B are schematic diagrams of a fault notification circuit of an application layer management process according to an embodiment of the present invention.
  • FIGS. 7A-7B are flowcharts of an abnormal event notification process performed by an application layer proxy process according to an embodiment of the present invention.
  • 8A-8B are flowcharts of an abnormal event notification process performed by an application layer management process according to an embodiment of the present invention.
  • FIG. 9 is a schematic diagram of an abnormal event processing device in a telecommunication cloud provided by an IaaS proxy process according to an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of an abnormal event processing apparatus in a telecommunications cloud provided by an application layer proxy process according to an embodiment of the present invention
  • 11A-11B are schematic diagrams showing the structure of an abnormal event processing device in a telecommunication cloud provided by an application layer management process according to an embodiment of the present invention.
  • FIG. 12 is a schematic structural diagram of an abnormal event processing apparatus in a telecommunication cloud according to an embodiment of the present invention.
  • the method for processing a telecom cloud abnormal event is applied to the system architecture shown in FIG. 4, including an IaaS proxy process on the Host side, a service process, an agent process, and a management process on the Guest side.
  • the IaaS proxy process runs on the Host.
  • the business processes and management processes on one guest run on the VM VM2 created by the IaaS layer.
  • the business processes and agent processes on the other guest run on the VMs created by the IaaS layer.
  • a fault notification channel R is established between the guest and the host, and the fault notification channel is used to notify the abnormal event to shorten the notification path and improve reliability.
  • FIG. 5 is a flowchart of processing an abnormal event in the telecommunication cloud by the IaaS proxy process, as shown in FIG. 5, including:
  • S102 The resource status abnormal event detected by the IaaS proxy process is sent to the application layer proxy process through a fault notification channel between the IaaS proxy process and the application layer proxy process established in the Host, or pre-established in the Host.
  • the fault notification channel between the IaaS proxy process and the application layer management process is sent to the application layer management process.
  • the resource status abnormal event detected by the IaaS proxy process is sent to the application layer proxy process through the fault notification channel between the IaaS proxy process and the application layer proxy process pre-established in the host Host, and the application layer proxy
  • the process requests the application layer management process to perform processing such as pause or active/standby switchover on the abnormal event according to the impact of the current resource status abnormal event on the actual service.
  • the resource status exception event detected by the IaaS proxy process is sent to the application layer management process through the fault notification channel between the IaaS proxy process and the application layer management process pre-established in the host Host, and the application layer management process is based on the current The extent to which the resource status abnormal event affects the actual service, and pauses the abnormal event or performs the active/standby switchover.
  • the fault notification channel needs to be established in the Host and the abnormal event notification service is started.
  • the process of establishing the fault notification channel on the IaaS side may be as follows:
  • the IaaS proxy process receives the abnormal event notification service request sent by the application layer management center node, and notifies the service request according to the abnormal event, creates a fault notification channel, and starts the abnormal event notification service.
  • the IaaS proxy process feeds the access address, the access channel type, and the exchange protocol type of the abnormal event notification service to the application layer management center node, and the application layer management center node indicates the application layer proxy process or the application layer management process, according to the access.
  • the address, access channel type, and exchange protocol type are connected to the abnormal event notification service.
  • the fault notification channel established in the embodiment of the present invention may use different types and different protocol formats.
  • the interface of the fault notification channel may be defined as follows:
  • a virtio-serial serial channel
  • a virtio-serial serial channel
  • the business process in the guest can read the character device.
  • /dev/virtio-serial/port1 according to the JOSN format to resolve the resource status exception event sent by the IaaS proxy process, using the following program:
  • the embodiment of the present invention can expand other channels as a fault notification channel, for example, a UDP/TCP channel through a virtual network card, and other formats such as XML and TLV, which can be implemented as follows:
  • the process of the resource state detection by the IaaS proxy process may be as follows:
  • the IaaS proxy process receives the subscription request sent by the application layer proxy process or the application layer management process, and detects the resource status related to the subscription request according to the received subscription request.
  • the application layer proxy process or the application layer management process may subscribe to a result event related to hardware failure, performance detection, and/or reliability detection, and send a subscription request including the subscription content to the IaaS proxy process.
  • the IaaS proxy process detects a resource status related to the subscription request according to the subscription request, and sends a resource status exception event related to the subscription request to the application layer proxy process or the application layer management process, by the application layer proxy process or
  • the application layer management process processes the abnormal event according to a specific service, for example, receiving a subscription for detecting a sub-health state of a virtual machine such as an excessive hardware temperature and a multi-bit memory error sent by an application layer management process or an application layer proxy process. Request to complete business migration and fault isolation in the event of a sub-health state.
  • the IaaS proxy process may be implemented by defining a notification interface, and the notification interface may include the following information:
  • the resource identifier (which can be multiple objects), the notification type, the trigger event type (including faults, performance degradation, and reliability reduction), and can be implemented by, for example, the following program:
  • the IaaS proxy process receives a subscription request that is sent by the application layer management process and includes a subscription relationship, where the subscription relationship is used to indicate a virtual machine that the application layer management process wants to pay attention to and a resource state of the virtual machine to be focused on.
  • the IaaS proxy process After receiving the subscription request including the subscription relationship, the IaaS proxy process searches for the IaaS proxy process to which the virtual machine belongs, and obtains the IaaS proxy process to be concerned.
  • the IaaS proxy process sends the subscription relationship to the IaaS proxy process, and indicates that the IaaS proxy process is to monitor the resource status of the virtual machine to be focused on according to the subscription relationship.
  • the IaaS proxy process detects that the resource status of the virtual machine is abnormal
  • the resource status abnormal event is sent to the IaaS proxy process to which the application layer management process that sends the subscription request belongs, and is passed by the IaaS proxy process.
  • the subscription when receiving the subscription request including the subscription relationship sent by the application layer management process, the subscription may be received through a fault notification channel between the IaaS proxy process and the application layer management process established in the Host; Through the application layer management process, the application layer management center node and The fault notification channel between the IaaS proxy processes is received.
  • the channel M represents a fault notification channel between the IaaS proxy process and the application layer management process
  • the channel M′ represents the application layer management process and the application layer management center node. The channel between the failure notification channel and the IaaS agent process.
  • the record subscription relationship is local.
  • the resource status exception event is sent to the IaaS proxy process of the host to which the application layer management process belongs, and the IaaS proxy process is reported to the application layer management process, and the application layer management process processes the virtual machine resource state abnormal event, for example, can notify other virtual
  • the service process in the machine takes over the business process of the virtual machine, as shown in FIG. 6B, where L is the path of the resource status abnormal event notification when the virtual machine fails.
  • the application layer management process in VM2 simultaneously manages four virtual machines (VM1-VM4), which can subscribe to the failure notification events of the four virtual machines, and the IaaS proxy process 2 needs to perform VM4 virtual machines.
  • the IaaS proxy process 2 may feed back the resource status exception event to the IaaS proxy process 1, and the IaA proxy process 1 passes through it and the VM2.
  • the application layer management process pre-establishes a fault notification channel to quickly notify the application layer management process in the VM2, and the application layer management process in the VM2 switches the service process on the virtual machine VM4 to the normal virtual machine.
  • the method for processing the abnormal event is directly sent to the application layer proxy process or the application layer by using the fault notification channel between the IaaS proxy process and the application layer management process.
  • the management process eliminates the need for IaaS management centers and application layer management center nodes, shortens the notification path, and enhances reliability.
  • the method for processing an abnormal event in the telecommunication cloud by using an application layer proxy process is taken as an example. As shown in FIG. 7A, the method includes:
  • the application layer proxy process receives the resource status abnormal event sent by the IaaS proxy process through the fault notification channel between the IaaS proxy process and the application layer proxy process that is pre-established in the host.
  • the application layer proxy process needs to access the abnormal event notification service provided by the IaaS proxy process in advance before receiving the resource state exception event delivered by the IaaS proxy process, and is preferably implemented as follows:
  • the application layer management center node sends an abnormal event notification service request to the IaaS proxy process, and receives the access address, access channel type, and exchange protocol of the abnormal event notification service fed back by the IaaS proxy process to create the fault notification channel and start the abnormal event notification service.
  • the application layer management center node when the application layer management center node receives the access address, the access channel type, and the exchange protocol type of the abnormal event notification service fed back by the IaaS proxy process, sending an access indication to the application layer proxy process, where the access indication includes The access address, the access channel type, and the exchange protocol type of the abnormal event notification service fed back by the IaaS proxy process, when the application layer proxy process receives the access indication, according to the access address, the access channel type, and the access channel included in the access indication
  • the exchange protocol type accesses the abnormal event notification service.
  • the application layer proxy process may also send a subscription request to the IaaS proxy process, requesting the IaaS proxy process to deliver the resource status related to the subscription request sent by the IaaS proxy process.
  • the subscription interface which is mainly a subscription interface object type, may be implemented, for example, by using the following program:
  • the process of the exception event processing performed by the application layer proxy process in the embodiment of the present invention includes:
  • the application layer proxy process sends an access abnormal event notification service request to the IaaS proxy process, and accesses the abnormal event notification service.
  • the application layer proxy process may apply for an abnormal event notification service provided by the IaaS proxy process when applying for the virtual machine to the IaaS proxy process, and the application layer management center node initiates an application request to the IaaS proxy process.
  • the IaaS proxy process After the application is successful, the IaaS proxy process returns the access address, access channel type, and exchange protocol type of the abnormal event notification service, and the application layer proxy process accesses the abnormal event notification according to the access address, the access channel type, and the exchange protocol type. service.
  • the application layer proxy process After receiving the resource status abnormal event, the application layer proxy process requests the application layer management process to perform service switching according to the actual service impact degree of the resource status abnormal event.
  • S304 The application layer management process instructs the service process to perform the process of switching the service process.
  • the application layer proxy process performs the abnormal event processing method, and the detected resource status abnormal event is directly sent to the fault notification channel between the IaaS proxy process and the application layer proxy process.
  • the application layer proxy process shortens the notification path and enhances reliability without going through the IaaS management center node and the application layer management center node.
  • the method for processing an abnormal event in the telecommunication cloud by using an application layer management process is taken as an example. As shown in FIG. 8A, the method includes:
  • the application layer management process receives the failure notification channel between the IaaS proxy process and the application layer management process established in advance by the IaaS proxy process.
  • the application layer management process may determine whether to process the resource dependency according to the service status of the service, and the impact of the resource status abnormal event on the actual service. When the degree reaches the set level, the exception event is processed. For example, when storing a high-service application, the application layer management process sends the IaaS proxy process. During the RAID downgrade notification, the automatic switching process is triggered before the service process is not damaged. The service process is switched to the more reliable virtual machine to reduce the impact of RAID degradation on the service process.
  • the abnormal event notification service provided by the IaaS proxy process needs to be accessed in advance, and is preferably implemented as follows:
  • the application layer management center node sends an abnormal event notification service request to the IaaS proxy process, and receives the access address, access channel type, and exchange protocol of the abnormal event notification service fed back by the IaaS proxy process to create the fault notification channel and start the abnormal event notification service.
  • the application layer management center node when the application layer management center node receives the access address, the access channel type, and the exchange protocol type of the abnormal event notification service fed back by the IaaS proxy process, sending an access indication to the application layer management process, where the access indication includes The access address, the access channel type, and the exchange protocol type of the abnormal event notification service fed back by the IaaS proxy process, when the application layer management process receives the access indication, according to the access address, the access channel type, and the access channel included in the access indication
  • the exchange protocol type accesses the abnormal event notification service.
  • the application layer management process may send a subscription request to the IaaS proxy process, requesting the IaaS proxy process to deliver the resource status related to the subscription request.
  • the application layer management process when the application layer management process sends a subscription request to the IaaS proxy process, it may be implemented by subscribing to the interface object type in the same manner as the application layer proxy process, and details are not described herein.
  • the application layer management process may pass the fault notification channel between the IaaS proxy process and the application layer management process, or the fault notification channel between the application layer management process, the application layer management center node, and the IaaS proxy process.
  • the status can be further referred to Figures 6A-6B.
  • the application layer management process obtains a resource status abnormal event and performs processing by sending a subscription request including a subscription relationship to the IaaS proxy process, as shown in FIG. 8B.
  • the application layer management process obtains a resource status abnormal event and performs processing by sending a subscription request including a subscription relationship to the IaaS proxy process, as shown in FIG. 8B.
  • S501 The application layer management process subscribes to the IaaS proxy process for a request for attention to a virtual machine state change.
  • the IaaS proxy process sends the subscription relationship to the IaaS proxy process of the host where the virtual machine is located, and is recorded as an IaaS proxy process.
  • the IaaS proxy process sends a virtual machine fault event notification through a pre-established fault notification channel.
  • S506 The application layer management process instructs the service process to perform the process of switching the service process.
  • the subscription relationship of the application layer virtual machine failure event may be sent to the IaaS proxy process by using another channel, that is, the application layer management center node issues a subscription relationship to the IaaS management center node, and the IaaS management center node saves the subscription relationship.
  • the application layer management center node issues a subscription relationship to the IaaS management center node
  • the IaaS management center node saves the subscription relationship.
  • the application layer management process is used to process the abnormal event, and the detected resource status abnormal event is directly sent to the application layer management through the fault notification channel between the IaaS proxy process and the application layer management process. Processes, without the need for IaaS Management Center and Application Layer Management Center nodes, shorten the notification path and enhance reliability.
  • the embodiment of the present invention provides a processing device for an abnormal event in the telecommunication cloud.
  • the device includes a detecting unit 901 and a sending unit 902, where ,
  • the detecting unit 901 is configured to detect a resource status.
  • the sending unit 902 is configured to send the resource status abnormal event detected by the detecting unit 901 to the application layer proxy process by using a fault notification channel between the IaaS proxy process and the application layer proxy process that is pre-established in the host Host. And the fault notification channel between the IaaS proxy process and the application layer management process pre-established in the host Host is sent to the application layer management process.
  • the sending unit 902 detects the resource status abnormality detected by the detecting unit 901. And the fault notification channel between the IaaS proxy process and the application layer proxy process pre-established in the host Host is sent to the application layer proxy process, and the application layer proxy process influences the actual service according to the resource state abnormal event. Request the application layer management process to handle exception events.
  • the sending unit 902 sends the resource status abnormal event detected by the detecting unit 901 to the application layer management process through the fault notification channel between the IaaS proxy process and the application layer management process established in advance in the host Host, by the application layer.
  • the management process processes the abnormal event according to the degree of influence of the resource status abnormal event on the actual business.
  • the sending unit 902 is further configured to:
  • the fault notification channel is created according to the abnormal event notification service request, and the abnormal event notification service is started;
  • the access address, the access channel type, and the exchange protocol type of the abnormal event notification service are fed back to the application layer management center node, indicating the application layer proxy process or the application layer management process according to the access address, the access channel type, and the exchange protocol type. Access the abnormal event notification service.
  • the detecting unit 901 is configured to:
  • the detecting unit 901 is configured to:
  • a subscription request including a subscription relationship, where the subscription relationship is used to indicate a virtual machine that the application layer management process wants to pay attention to and a resource state to be concerned about the virtual machine;
  • the subscription relationship is sent to the IaaS proxy process, and the IaaS proxy process is instructed to monitor the resource status of the virtual machine to be focused on according to the subscription relationship.
  • the detecting unit 901 is specifically configured to: receive a subscription request by using a fault notification channel between the IaaS proxy process and the application layer management process; or
  • the notification channel receives the subscription request.
  • the processing device for performing an abnormal event in the telecommunication cloud based on the application layer proxy process provides a device for processing an abnormal event in the telecommunication cloud, as shown in FIG. 10, including a receiving unit 1001 and a requesting unit 1002, where
  • the receiving unit 1001 is configured to receive a resource status abnormal event sent by the IaaS proxy process through a fault notification channel between the IaaS proxy process and the application layer proxy process that is pre-established in the host host;
  • the requesting unit 1002 is configured to request the application layer management process to process the abnormal event when the degree of influence of the resource status abnormal event on the actual service reaches a set level.
  • the receiving unit 1001 is further configured to:
  • an access indication sent by the application layer management center node where the access indication includes an access address, an access channel type, and an exchange protocol type of the abnormal event notification service fed back by the IaaS proxy process, and according to the access included in the access indication
  • the inbound address, access channel type, and exchange protocol type are connected to the abnormal event notification service.
  • the requesting unit 1002 is further configured to:
  • the IaaS proxy process Before receiving the resource status exception event sent by the IaaS proxy process, the IaaS proxy process sends a subscription request to the IaaS proxy process to issue a resource status related to the subscription request.
  • the processing method for performing an abnormal event in the telecommunication cloud based on the application layer management process further provides a processing device for an abnormal event in the telecommunication cloud.
  • the device includes a receiving unit 1101 and a processing unit 1102, where ,
  • the receiving unit 1101 is configured to receive a resource status abnormal event sent by the IaaS proxy process through a fault notification channel between the IaaS proxy process and the application layer management process that is pre-established in the host host;
  • the processing unit 1102 is configured to process the abnormal event when the degree of influence of the resource status abnormal event on the actual service reaches a set level.
  • the receiving unit 1102 is further configured to:
  • an access indication sent by the application layer management center node where the access indication includes an access address, an access channel type, and an exchange protocol type of the abnormal event notification service fed back by the IaaS proxy process, and according to the access included in the access indication
  • the inbound address, access channel type, and exchange protocol type are connected to the abnormal event notification service.
  • the apparatus further includes a requesting unit 1103, as shown in FIG. 11B, requesting unit 1103, for:
  • the IaaS proxy process Before receiving the resource status exception event sent by the IaaS proxy process, the IaaS proxy process sends a subscription request to the IaaS proxy process to issue a resource status related to the subscription request.
  • the request unit 1103 is configured to:
  • the device for processing an abnormal event in the telecommunication cloud is provided.
  • the embodiment of the present invention further provides a device for processing an abnormal event in the telecommunication cloud.
  • the device includes: a transceiver 1201, a processor 1202, and a memory 1203. And a bus 1204, wherein the transceiver 1201, the processor 1202, and the memory 1203 are both connected to the bus 1204.
  • the processor 1202 is configured to detect a resource status, and send, by using the transceiver 1201, the detected resource status abnormal event to the application by using a fault notification channel between the IaaS proxy process and the application layer proxy process that is pre-established in the host Host.
  • the layer proxy process the application layer proxy process requests the application layer management process to process the abnormal event according to the degree of influence of the resource state abnormal event on the actual service; and/or, the detected resource state abnormal event passes through the sink Host Host internal pre-built
  • the fault notification channel between the IaaS proxy process and the application layer management process is sent to the application layer management process, and the application layer management process processes the abnormal event according to the degree of influence of the resource state abnormal event on the actual service.
  • the processor 1202 is further configured to receive, by the transceiver 1201, a resource status abnormal event sent by the IaaS proxy process through a fault notification channel between the IaaS proxy process and the application layer proxy process that is pre-established in the host Host; when the resource status is abnormal When the impact of the event on the actual service reaches a set level, the application layer management process is requested to process the abnormal event.
  • the processor 1202 is further configured to receive, by the transceiver 1201, a resource status abnormal event sent by the IaaS proxy process through a fault notification channel between the IaaS proxy process and the application layer management process that is pre-established in the host host; when the resource status is abnormal When an event affects the actual business to a set level, the abnormal event is processed.
  • the processor 1202 performs the above process generally by one or more software programs, the one or more software programs are stored in the memory 1203, and when the processor 1202 needs to perform the above process, the one or more software programs are The processor 1202 is loaded into the processor 1202 to complete the above process.
  • the processor 1202 can be implemented by using the hardware, which is not limited by the embodiment of the present invention.
  • the processing device for the abnormal event in the telecommunication cloud provided by the embodiment of the present invention may be used to execute the processing method of the abnormal event in the telecommunication cloud shown in FIG. 4-8B, and thus the abnormality in the telecommunication cloud involved in FIG. 9-12
  • the description of the processing device for the event is not exhaustive. Refer to the description of Figure 4-8B.
  • processing device for the abnormal event in the telecommunication cloud provided by the embodiment of the present invention may be an independent component, or may be integrated in the IaaS proxy process, the application layer management process, or the application layer proxy process. Not limited.
  • the device for processing an abnormal event in the telecommunication cloud passes the fault notification channel between the IaaS proxy process and the application layer proxy process established in the Host, or the fault between the IaaS proxy process and the application layer management process.
  • the notification channel directly sends the detected resource status abnormal event to the application layer agent process or the application layer management process without going through the IaaS management center and
  • the layer management center node shortens the notification path and enhances reliability.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Multimedia (AREA)
  • Debugging And Monitoring (AREA)
  • Telephonic Communication Services (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Hardware Redundancy (AREA)
  • Computer And Data Communications (AREA)

Abstract

本发明公开了一种电信云中异常事件的处理方法及装置，以缩短通知路径，增加可靠性。本发明中检测资源状态；将检测到的资源状态异常事件，通过在宿主机Host内部预先建立的基础设施即服务IaaS代理进程与应用层代理进程之间的故障通知通道下发给应用层代理进程，和/或通过在宿主机Host内部预先建立的IaaS代理进程与应用层管理进程之间的故障通知通道下发给应用层管理进程。通过本发明将检测到的资源状态异常事件直接下发给应用层代理进程或者应用层管理进程，无需经过IaaS管理中心节点以及应用层管理中心节点，缩短了通知路径，并增强了可靠性。

Description

电信云中异常事件的处理方法及装置 技术领域
本发明涉及电信云技术领域，尤其涉及一种电信云中异常事件的处理方法及装置。
背景技术
随着电信云概念的推广，业务应用层与IaaS(Infrastructure as a Service，基础设施即服务)层分离、解耦的分层架构被广泛应用到电信***。电信***中，硬件设备由IaaS层管理，对业务应用透明，业务应用一般运行在VM(Virtual Machine，虚拟机)中，如图1所示。
电信应用的一个典型特征是高可靠性，电信***通过进程间主备互助的方式，实现高可靠性。如图2A所示，VM1上运行的是主业务进程，进行业务的处理，VM2上运行的是备业务进程，不进行业务的处理，备业务进程从主业务进程同步状态和数据。运行过程中，由部署在VM3上的管理进程，对***中运行的进程进行监控，若管理进程监控到VM1上的业务进程出现了异常，则会通知VM2上的备业务进程转换为主业务进程进行业务的处理，而VM1上的主业务进程转变为备业务进程，从而实现业务的恢复，如图2B所示。
在分层架构下，为保证电信应用在云上的可靠性，若IaaS层的资源状态发生变化，例如硬件故障或者运行VM的Host OS(Host Operating System，运行在宿主机的操作***)崩溃，需要在IaaS层提供相关的通知能力，对异常事件进行处理，由IaaS层一起完成业务迁移和故障隔离等操作，向用户提供高可靠的电信业务。
一般的，进行异常事件通知处理时，如图3所示，当IaaS代理进程检测到VM发生故障时，将该故障上报到IaaS管理中心节点，IaaS管理中心节点再通知应用层管理中心节点，最后由应用层管理中心节点通知到应用层管理进程。
上述进行异常事件通知处理的过程，通道路径比较长，不能及时将异常事 件通知到应用层，并且应用层管理中心节点和IaaS管理中心节点都为管理维护节点，管理维护节点作为故障通知通道，可靠性比较低。
发明内容
本发明实施例提供一种电信云中异常事件的处理方法及装置，以缩短通知路径，增加可靠性。
第一方面，提供一种电信云中异常事件的处理方法，包括：
基础设施即服务IaaS代理进程检测资源状态；
所述IaaS代理进程将检测到的资源状态异常事件，通过在宿主机Host内部预先建立的IaaS代理进程与应用层代理进程之间的故障通知通道下发给应用层代理进程，由所述应用层代理进程根据所述资源状态异常事件对实际业务的影响程度，请求应用层管理进程对所述异常事件进行处理；和/或
所述IaaS代理进程将检测到的资源状态异常事件，通过在宿主机Host内部预先建立的IaaS代理进程与应用层管理进程之间的故障通知通道下发给应用层管理进程，由所述应用层管理进程根据所述资源状态异常事件对实际业务的影响程度，对所述异常事件进行处理。
结合第一方面，在第一种实现方式中，在IaaS代理进程检测资源状态之前，该方法还包括：
IaaS代理进程接收应用层管理中心节点发送的异常事件通知服务请求；
IaaS代理进程根据所述异常事件通知服务请求，创建故障通知通道并启动异常事件通知服务；
IaaS代理进程将所述异常事件通知服务的接入地址、接入通道类型和交换协议类型，反馈给所述应用层管理中心节点，指示应用层代理进程或者应用层管理进程根据所述接入地址、所述接入通道类型和所述交换协议类型接入所述异常事件通知服务。
结合第一方面，在第二种实现方式中，所述IaaS代理进程检测资源状态，包括：
IaaS代理进程接收应用层代理进程或应用层管理进程发送的订阅请求；
IaaS代理进程根据所述订阅请求，检测与所述订阅请求相关的资源状态。
结合第一方面，在第三种实现方式中，所述IaaS代理进程检测资源状态，包括：
IaaS代理进程接收应用层管理进程发送的包含有订阅关系的订阅请求，所述订阅关系用于表示所述应用层管理进程欲关注的虚拟机以及欲关注虚拟机的资源状态；
IaaS代理进程查找所述欲关注虚拟机所属的IaaS代理进程，得到欲关注IaaS代理进程；
IaaS代理进程将所述订阅关系发送给所述欲关注IaaS代理进程，并指示所述欲关注IaaS代理进程根据所述订阅关系监测所述欲关注虚拟机的资源状态。
结合第一方面的第三种实现方式，在第四种实现方式中，所述IaaS代理进程接收应用层管理进程发送的包含有订阅关系的订阅请求，具体包括：
所述IaaS代理进程通过所述IaaS代理进程与应用层管理进程之间的故障通知通道接收所述订阅请求；或者
所述IaaS代理进程通过应用层管理进程、应用层管理中心节点和IaaS代理进程之间的故障通知通道接收所述订阅请求。
第二方面，提供一种电信云中异常事件的处理方法，包括：
应用层代理进程接收基础设施即服务IaaS代理进程通过在宿主机Host内部预先建立的IaaS代理进程与应用层代理进程之间的故障通知通道下发的资源状态异常事件；
当所述资源状态异常事件对实际业务的影响程度达到设定级别时，所述应用层代理进程请求应用层管理进程对所述异常事件进行处理。
结合第二方面，在第一种实现方式中，所述应用层代理进程接收IaaS代理进程下发的资源状态异常事件之前，该方法还包括：
所述应用层代理进程接收应用层管理中心节点下发的接入指示，所述接入指示中包括所述IaaS代理进程反馈的异常事件通知服务的接入地址、接入通道类型和交换协议类型；
所述应用层代理进程根据所述接入指示中包括的所述接入地址、所述接入通道类型和所述交换协议类型接入所述异常事件通知服务。
结合第二方面，在第二种实现方式中，所述应用层代理进程接收IaaS代理进程下发的资源状态异常事件之前，该方法还包括：
所述应用层代理进程向所述IaaS代理进程发送订阅请求，请求所述IaaS代理进程下发与所述订阅请求相关的资源状态。
第三方面，提供一种电信云中异常事件的处理方法，包括：
应用层管理进程接收基础设施即服务IaaS代理进程通过在宿主机Host内部预先建立的IaaS代理进程与应用层管理进程之间的故障通知通道下发的资源状态异常事件；
当所述资源状态异常事件对实际业务的影响程度达到设定级别时，所述应用层管理进程对所述异常事件进行处理。
结合第三方面，在第一种实现方式中，所述应用层管理进程接收IaaS代理进程下发的资源状态异常事件之前，该方法还包括：
接收应用层管理中心节点下发的接入指示，所述接入指示包括所述IaaS代理进程反馈的异常事件通知服务的接入地址、接入通道类型和交换协议类型；
所述应用层管理进程根据所述接入指示中包括的所述接入地址、所述接入通道类型和所述交换协议类型接入所述异常事件通知服务。
结合第三方面，在第二种实现方式中所述应用层管理进程接收IaaS代理进程下发的资源状态异常事件之前，该方法还包括：
所述应用层管理进程向所述IaaS代理进程发送订阅请求，请求所述IaaS代理进程下发与所述订阅请求相关的资源状态。
结合第三方面，在第三种实现方式中，所述应用层管理进程通过所述IaaS代理进程与应用层管理进程之间的故障通知通道，向所述IaaS代理进程发送包含有订阅关系的订阅请求，请求所述IaaS代理进程下发所述欲关注虚拟机的资源状态，所述订阅关系用于表示所述应用层管理进程欲关注的虚拟机以及欲关注虚拟机的资源状态；或者
所述应用层管理进程通过应用层管理进程、应用层管理中心节点和IaaS代理进程之间的故障通知通道，向所述IaaS代理进程发送包含有订阅关系的订阅请求，请求所述IaaS代理进程下发所述欲关注虚拟机的资源状态，所述订阅关系用于表示所述应用层管理进程欲关注的虚拟机以及欲关注虚拟机的资源状态
第四方面，提供一种电信云中异常事件的处理装置，包括检测单元和下发单元，其中，
所述检测单元，用于检测资源状态；
所述下发单元，用于将所述检测单元检测到的资源状态异常事件，通过在宿主机Host内部预先建立的基础设施即服务IaaS代理进程与应用层代理进程之间的故障通知通道下发给应用层代理进程，由所述应用层代理进程根据所述资源状态异常事件对实际业务的影响程度，请求应用层管理进程对所述异常事件进行处理；和/或
将所述检测单元检测到的资源状态异常事件，通过在宿主机Host内部预先建立的IaaS代理进程与应用层管理进程之间的故障通知通道下发给应用层管理进程，由所述应用层管理进程根据所述资源状态异常事件对实际业务的影响程度，对所述异常事件进行处理。
结合第四方面，在第一种实现方式中，所述下发单元，还用于：
接收应用层管理中心节点发送的异常事件通知服务请求；
根据所述异常事件通知服务请求，创建故障通知通道并启动异常事件通知服务；
将所述异常事件通知服务的接入地址、接入通道类型和交换协议类型，反馈给所述应用层管理中心节点，指示应用层代理进程或者应用层管理进程根据所述接入地址、所述接入通道类型和所述交换协议类型接入所述异常事件通知服务。
结合第四方面，在第二种实现方式中，所述检测单元，用于：
接收应用层代理进程或应用层管理进程发送的订阅请求；
根据所述订阅请求，检测与所述订阅请求相关的资源状态。
结合第四方面，在第三种实现方式中，所述检测单元，用于：
接收应用层管理进程发送的包含有订阅关系的订阅请求，所述订阅关系用于表示所述应用层管理进程欲关注的虚拟机以及欲关注虚拟机的资源状态；
查找所述欲关注虚拟机所属的IaaS代理进程，得到欲关注IaaS代理进程；
将所述订阅关系发送给所述欲关注IaaS代理进程，并指示所述欲关注IaaS代理进程根据所述订阅关系监测所述欲关注虚拟机的资源状态。
结合第四方面的第三种实现方式，在第四种实现方式中，所述检测单元，具体用于：
通过所述IaaS代理进程与应用层管理进程之间的故障通知通道接收所述订阅请求；或者
通过应用层管理进程、应用层管理中心节点和IaaS代理进程之间的故障通知通道接收所述订阅请求。
第五方面，提供一种电信云中异常事件的处理装置，包括接收单元和请求单元，其中，
所述接收单元，用于接收基础设施即服务IaaS代理进程通过在宿主机Host内部预先建立的IaaS代理进程与应用层代理进程之间的故障通知通道下发的资源状态异常事件；
所述请求单元，用于当所述资源状态异常事件对实际业务的影响程度达到设定级别时，请求应用层管理进程对所述异常事件进行处理。
结合第五方面，在第一种实现方式中，所述接收单元，还用于：
接收应用层管理中心节点下发的接入指示，所述接入指示中包括所述IaaS代理进程反馈的异常事件通知服务的接入地址、接入通道类型和交换协议类型，并根据所述接入指示中包括的所述接入地址、所述接入通道类型和所述交换协议类型接入所述异常事件通知服务。
结合第五方面，在第二种实现方式中，所述请求单元，还用于：
接收IaaS代理进程下发的资源状态异常事件之前，向所述IaaS代理进程发送订阅请求，请求所述IaaS代理进程下发与所述订阅请求相关的资源状态。
第六方面，提供一种电信云中异常事件的处理装置，包括接收单元和处理单元，其中，
所述接收单元，用于接收基础设施即服务IaaS代理进程通过在宿主机Host内部预先建立的基础设施即服务IaaS代理进程与应用层管理进程之间的故障通知通道下发的资源状态异常事件；
所述处理单元，用于当所述资源状态异常事件对实际业务的影响程度达到设定级别时，对所述异常事件进行处理。
结合第六方面，在第一种实现方式中，所述接收单元，还用于：
接收接收应用层管理中心节点下发的接入指示，所述接入指示包括所述IaaS代理进程反馈的异常事件通知服务的接入地址、接入通道类型和交换协议类型，并根据所述接入指示中包括的所述接入地址、所述接入通道类型和所述交换协议类型接入所述异常事件通知服务。
结合第六方面，在第二种实现方式中，该装置还包括请求单元，其中，
所述请求单元，用于接收IaaS代理进程下发的资源状态异常事件之前，向所述IaaS代理进程发送订阅请求，请求所述IaaS代理进程下发与所述订阅请求相关的资源状态。
结合第六方面的第二种实现方式，在第三种实现方式中，所述请求单元，用于：
通过所述IaaS代理进程与应用层管理进程之间的故障通知通道，向所述IaaS代理进程发送包含有订阅关系的订阅请求，请求所述IaaS代理进程下发所述欲关注虚拟机的资源状态，所述订阅关系用于表示所述应用层管理进程欲关注的虚拟机以及欲关注虚拟机的资源状态；或者
通过应用层管理进程、应用层管理中心节点和IaaS代理进程之间的故障通知通道，向所述IaaS代理进程发送包含有订阅关系的订阅请求，请求所述IaaS代理进程下发所述欲关注虚拟机的资源状态，所述订阅关系用于表示所述应用层管理进程欲关注的虚拟机以及欲关注虚拟机的资源状态。
本发明实施例提供的电信云中异常事件的处理方法及装置，通过在Host内部预先建立的IaaS代理进程与应用层代理进程之间的故障通知通道，或IaaS代理进程与应用层管理进程之间的故障通知通道，将检测到的资源状态异常事件直接下发给应用层代理进程或者应用层管理进程，无需经过IaaS管理中心以及应用层管理中心节点，缩短了通知路径，并增强了可靠性。
附图说明
图1为现有技术***云分层架构构成示意图；
图2A-图2B为现有技术中实现业务进程迁移过程示意图；
图3为现有技术中异常事件通知处理过程示意图；
图4为本发明实施例提供的Guest和Host之间建立有故障通知通道的***架构图；
图5为本发明实施例提供的电信云中异常事件通知处理流程图；
图6A-图6B为本发明实施例提供的应用层管理进程故障通知线路示意图；
图7A-图7B为本发明实施例提供的应用层代理进程进行异常事件通知处理流程图；
图8A-图8B为本发明实施例提供的应用层管理进程进行异常事件通知处理流程图；
图9为本发明实施例基于IaaS代理进程提供的电信云中异常事件处理装置 构成示意图；
图10为本发明实施例基于应用层代理进程提供的电信云中异常事件处理装置构成示意图；
图11A-图11B为本发明实施例基于应用层管理进程提供的电信云中异常事件处理装置构成示意图；
图12为本发明实施例提供的电信云中异常事件处理装置构成示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分实施例，并不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例，都属于本发明保护的范围。
本发明实施例提供的电信云异常事件的处理方法，应用于图4所示的***架构，包括Host(宿主机)端的IaaS代理进程，Guest(客户机)端的业务进程、代理进程和管理进程，图4中IaaS代理进程运行在Host端，其中一个Guest上的业务进程和管理进程运行在IaaS层创建的虚拟机VM2上，另一个Guest上的业务进程和代理进程运行在IaaS层创建的虚拟机VM1上，本发明实施例在Guest和Host之间建立故障通知通道R，通过该故障通知通道进行异常事件的通知，以缩短通知路径，提高可靠性。
在一个实施例中，以IaaS代理进程执行电信云中异常事件的处理过程进行说明，图5所示为IaaS代理进程进行电信云中异常事件的处理流程图，如图5所示，包括：
S101：IaaS代理进程检测资源状态。
S102：IaaS代理进程将检测到的资源状态异常事件，通过在Host内部预先建立的IaaS代理进程与应用层代理进程之间的故障通知通道下发给应用层代理进程，或通过在Host内部预先建立的IaaS代理进程与应用层管理进程之间的故障通知通道下发给应用层管理进程。
具体的，IaaS代理进程将检测到的资源状态异常事件，通过在宿主机Host内部预先建立的IaaS代理进程与应用层代理进程之间的故障通知通道下发给应用层代理进程，由应用层代理进程根据当前资源状态异常事件对实际业务的影响程度，请求应用层管理进程对异常事件进行例如暂停或者主备倒换等处理。
IaaS代理进程将检测到的资源状态异常事件，通过在宿主机Host内部预先建立的IaaS代理进程与应用层管理进程之间的故障通知通道下发给应用层管理进程，由应用层管理进程根据当前资源状态异常事件对实际业务的影响程度，对异常事件进行暂停或者主备倒换等处理。
进一步的，本发明实施例中在执行S101检测资源状态之前，需要在Host内部预先建立故障通知通道并启动异常事件通知服务，IaaS侧建立故障通知通道的过程可优选如下方式：
IaaS代理进程接收应用层管理中心节点发送的异常事件通知服务请求，并根据异常事件通知服务请求，创建故障通知通道并启动异常事件通知服务。IaaS代理进程将异常事件通知服务的接入地址、接入通道类型和交换协议类型，反馈给应用层管理中心节点，由应用层管理中心节点指示应用层代理进程或者应用层管理进程，根据接入地址、接入通道类型和交换协议类型接入异常事件通知服务。
具体的，本发明实施例中建立的故障通知通道可以使用不同的类型，不同的协议格式，例如可采用如下方式定义故障通知通道的接口：
“directChannelType”:[string]通道类型，该通道类型可以是“Charter device，UDP或TCP”
“directChannelName”:[string]通道地址，该通道地址是IaaS代理进程提供的异常事件通知服务的接入地址。
“directChannelProtocol”:[string]通道消息协议，该通道消息协议可以是“JOSN，XML或TLV”。
例如：Host OS中KVM(Kernel-based Virtual Machine，基于内核的虚拟机)创建虚拟机时，提供virtio-serial(串口通道)给Guest中的业务进程，Guest中的业务进程可以读取字符设备“/dev/virtio-serial/port1”，按照JOSN格式去解析IaaS代理进程下发的资源状态异常事件，采用如下程序实现：
directChannelName＝/dev/virtio-serial/port1
directChannelType＝charter device
directChannelProtocol＝JOSN
当然，本发明实施例可以扩充其他通道，作为故障通知通道，例如通过虚拟网卡走UDP/TCP的通道，也支持其他格式例如XML和TLV，可采用如下方式实现：
directChannelName＝172.168.1.6:8990
directChannelType＝TCP
directChannelProtocol＝TLV。
进一步的，本发明实施例中IaaS代理进程进行资源状态检测的过程，可优选如下方式：
第一种优选的方式：IaaS代理进程接收应用层代理进程或应用层管理进程发送的订阅请求，根据接收到的订阅请求，检测与该订阅请求相关的资源状态。
具体的，本发明实施例中应用层代理进程或应用层管理进程可以订阅相关硬件故障、性能检测和/或可靠性检测的结果事件，并将包含该订阅内容的订阅请求发送给IaaS代理进程，IaaS代理进程根据该订阅请求检测与该订阅请求相关的资源状态，并当检测到的与该订阅请求相关的资源状态异常事件发送给应用层代理进程或应用层管理进程，由应用层代理进程或应用层管理进程根据具体的业务对该异常事件进行处理，例如可以接收应用层管理进程或应用层代理进程发送的对硬件温度过高及多比特的内存错误等虚拟机亚健康状态进行检测的订阅请求，以在发生亚健康状态时完成业务迁移及故障隔离。
具体的，IaaS代理进程接收到应用层代理进程或者应用层管理进程发送的订阅请求后，可通过定义通知接口实现，该通知接口可以包含如下信息：受影 响资源标识(可以是多个对象)，通知类型，触发事件类型(包含故障，性能下降，可靠性减低)，并可采用例如以下的程序方式实现：
Figure PCTCN2015070455-appb-000001
第二种优选的方式：
A：IaaS代理进程接收应用层管理进程发送的包含有订阅关系的订阅请求，该订阅关系用于表示应用层管理进程欲关注的虚拟机以及该欲关注虚拟机的资源状态。
B：IaaS代理进程接收到包含订阅关系的订阅请求后，查找欲关注虚拟机所属的IaaS代理进程，得到欲关注IaaS代理进程。
C：IaaS代理进程将订阅关系发送给欲关注IaaS代理进程，并指示欲关注IaaS代理进程根据该订阅关系监测欲关注虚拟机的资源状态。
具体的，当欲关注IaaS代理进程检测到欲关注虚拟机的资源状态发生异常时，将资源状态异常事件发送给该发送订阅请求的应用层管理进程所属的IaaS代理进程，并由IaaS代理进程通过在Host内部预先建立的IaaS代理进程与应用层管理进程之间的故障通知通道下发给应用层管理进程。
优选的，本发明实施例中接收应用层管理进程发送的包含有订阅关系的订阅请求时，可通过在Host内部预先建立的IaaS代理进程与应用层管理进程之间的故障通知通道接收；也可以通过应用层管理进程、应用层管理中心节点和 IaaS代理进程之间的故障通知通道接收，如图6A所示，通道M代表IaaS代理进程与应用层管理进程之间的故障通知通道，通道M’代表通过应用层管理进程、应用层管理中心节点和IaaS代理进程之间的故障通知通道接收的通道。
具体的，欲关注IaaS代理进程接收到订阅关系以后，记录订阅关系到本地，当检查到欲关注虚拟机资源状态发生异常时，或者需要对欲关注虚拟机进行故障操作时，根据订阅关系，将资源状态异常事件发送给应用层管理进程所属Host的IaaS代理进程，IaaS代理进程上报给应用层管理进程，由应用层管理进程对该欲关注虚拟机资源状态异常事件进行处理，例如可以通知其他虚拟机中的业务进程接管欲关注虚拟机的业务进程，如图6B所示，L为虚拟机故障时资源状态异常事件通知经过路径。
例如，图6B所示，VM2中的应用层管理进程同时管理4个虚拟机(VM1-VM4)，其可订阅这4个虚拟机的故障通知事件，当IaaS代理进程2需要对VM4虚拟机进行重启或关闭操作时，或者IaaS代理进程2直接检测到VM4发生故障时，则IaaS代理进程2可将该资源状态异常事件反馈给IaaS代理进程1，由I aaS代理进程1通过其与VM2中的应用层管理进程之间预先建立的故障通知通道，快速通知VM2中的应用层管理进程，由VM2中的应用层管理进程对虚拟机VM4上的业务进程倒换到正常的虚拟机上面。
本发明实施例中上述异常事件的处理方法，通过预先建立的IaaS代理进程与应用层管理进程之间的故障通知通道，将检测到的资源状态异常事件直接下发给应用层代理进程或者应用层管理进程，无需经过IaaS管理中心以及应用层管理中心节点，缩短了通知路径，并增强了可靠性。
在另一实施例中，以应用层代理进程执行电信云中异常事件的处理方法为例进行说明，如图7A所示，包括：
S201：应用层代理进程接收IaaS代理进程通过在Host内部预先建立的IaaS代理进程与应用层代理进程之间的故障通知通道下发的资源状态异常事件。
S202：当接收到的资源状态异常事件对实际业务的影响程度达到设定级别时，请求应用层管理进程对所述异常事件进行处理。
具体的，本发明实施例中应用层代理进程接收IaaS代理进程下发的资源状态异常事件之前，需要预先接入IaaS代理进程提供的异常事件通知服务，优选如下方式实现：
应用层管理中心节点向IaaS代理进程发送异常事件通知服务请求，并接收IaaS代理进程创建故障通知通道并启动异常事件通知服务后反馈的异常事件通知服务的接入地址、接入通道类型和交换协议类型，当应用层管理中心节点接收到IaaS代理进程反馈的异常事件通知服务的接入地址、接入通道类型和交换协议类型时，向应用层代理进程发送接入指示，该接入指示中包括IaaS代理进程反馈的异常事件通知服务的接入地址、接入通道类型和交换协议类型，应用层代理进程接收到接入指示时，根据接入指示中包括的接入地址、接入通道类型和交换协议类型接入异常事件通知服务。
进一步的，本发明实施例中应用层代理进程还可向IaaS代理进程发送订阅请求，请求IaaS代理进程下发与其发送的订阅请求相关的资源状态。
具体的，本发明实施例中应用层代理进程向IaaS代理进程发送订阅请求时，可通过订阅接口，主要是订阅接口对象类型实现，例如可采用如下程序实现：
Figure PCTCN2015070455-appb-000002
本发明实施例中应用层代理进程进行异常事件处理的过程，如图7B所示，包括：
S301：应用层代理进程向IaaS代理进程发送接入异常事件通知服务请求，并接入异常事件通知服务。
具体的，本发明实施例中应用层代理进程可在向IaaS代理进程申请虚拟机时，附带申请IaaS代理进程提供的异常事件通知服务，由应用层管理中心节点向IaaS代理进程发起申请请求，在申请成功后，由IaaS代理进程返回异常事件通知服务的接入地址、接入通道类型和交换协议类型，应用层代理进程根据该接入地址、接入通道类型和交换协议类型接入异常事件通知服务。
S302：IaaS代理进程检测到资源状态异常事件时，通过预先建立的IaaS代理进程与应用层代理进程之间的故障通知通道下发资源状态异常事件。
S303：应用层代理进程接收到资源状态异常事件后，根据资源状态异常事件对实际业务影响程度，请求应用层管理进程进行业务倒换。
S304：应用层管理进程指示业务进程，进行倒换业务进程处理。
本发明实施例中应用层代理进程进行异常事件的处理方法，通过在Host内部预先建立的IaaS代理进程与应用层代理进程之间的故障通知通道，将检测到的资源状态异常事件直接下发给应用层代理进程，无需经过IaaS管理中心节点以及应用层管理中心节点，缩短了通知路径，并增强了可靠性。
本发明的再一实施例中，以应用层管理进程执行电信云中异常事件的处理方法为例进行说明，如图8A所示，包括：
S401：应用层管理进程接收IaaS代理进程通过在Host内部预先建立的IaaS代理进程与应用层管理进程之间的故障通知通道。
S402：当资源状态异常事件对实际业务的影响程度达到设定级别时，应用层管理进程对异常事件进行处理。
具体的，本发明实施例中应用层管理进程接收到IaaS代理进程下发的资源状态异常事件后，可根据自身业务对该资源依赖情况决定是否进行处理，当资源状态异常事件对实际业务的影响程度达到设定级别时，对异常事件进行处理。例如，在存储高业务应用时，应用层管理进程在接收到IaaS代理进程下发 的RAID降级通知时，在业务进程还没有受损前，触发自动切换进程，将业务进程切换到可靠性更高的虚拟机上，降低RAID降级对业务进程的影响。
进一步的，本发明实施例中应用层管理进程接收IaaS代理进程下发的资源状态异常事件之前，需要预先接入IaaS代理进程提供的异常事件通知服务，优选如下方式实现：
应用层管理中心节点向IaaS代理进程发送异常事件通知服务请求，并接收IaaS代理进程创建故障通知通道并启动异常事件通知服务后反馈的异常事件通知服务的接入地址、接入通道类型和交换协议类型，当应用层管理中心节点接收到IaaS代理进程反馈的异常事件通知服务的接入地址、接入通道类型和交换协议类型时，向应用层管理进程发送接入指示，该接入指示中包括IaaS代理进程反馈的异常事件通知服务的接入地址、接入通道类型和交换协议类型，应用层管理进程接收到接入指示时，根据接入指示中包括的接入地址、接入通道类型和交换协议类型接入异常事件通知服务。
进一步的，应用层管理进程可以向IaaS代理进程发送订阅请求，请求IaaS代理进程下发与订阅请求相关的资源状态。
具体的，本发明实施例中应用层管理进程向IaaS代理进程发送订阅请求时，可采用与应用层代理进程相同的方式，通过订阅接口对象类型实现，具体不再赘述。
更进一步的，本发明实施例中应用层管理进程可通过IaaS代理进程与应用层管理进程之间的故障通知通道或者应用层管理进程、应用层管理中心节点和IaaS代理进程之间的故障通知通道，向IaaS代理进程发送包含有订阅关系的订阅请求，请求IaaS代理进程下发欲关注虚拟机的资源状态，该订阅关系用于表示应用层管理进程欲关注的虚拟机以及欲关注虚拟机的资源状态，可进一步参阅图6A-图6B。
具体的，本发明实施例中应用层管理进程通过发送包含订阅关系的订阅请求给IaaS代理进程，获取资源状态异常事件并进行处理的过程如图8B所示， 包括：
S501：应用层管理进程向IaaS代理进程订阅关注虚拟机状态变化的请求。
S502：IaaS代理进程将订阅关系发送给关注虚拟机所在Host的IaaS代理进程，记为欲关注IaaS代理进程。
S503：欲关注IaaS代理进程保存订阅关系。
S504：欲关注IaaS代理进程向IaaS代理进程发布虚拟机故障。
S505：IaaS代理进程通过预先建立的故障通知通道，下发虚拟机故障事件通知。
S506：应用层管理进程指示业务进程，进行倒换业务进程处理。
当然，上述应用层虚拟机故障事件的订阅关系可以使用另外一种通道下发给欲关注IaaS代理进程，即应用层管理中心节点下发订阅关系给IaaS管理中心节点，IaaS管理中心节点保存订阅关系到数据库中，欲关注IaaS代理进程启动时从IaaS管理中心节点获取订阅关系。
本发明实施例中应用层管理进程进行异常事件的处理方法，通过预先建立的IaaS代理进程与应用层管理进程之间的故障通知通道，将检测到的资源状态异常事件直接下发给应用层管理进程，无需经过IaaS管理中心以及应用层管理中心节点，缩短了通知路径，并增强了可靠性。
基于上述IaaS代理进程执行电信云中异常事件的处理方法，本发明实施例提供一种电信云中异常事件的处理装置，如图9所示，该装置包括检测单元901和下发单元902，其中，
检测单元901，用于检测资源状态。
下发单元902，用于将检测单元901检测到的资源状态异常事件，通过在宿主机Host内部预先建立的IaaS代理进程与应用层代理进程之间的故障通知通道下发给应用层代理进程，和/或通过在宿主机Host内部预先建立的IaaS代理进程与应用层管理进程之间的故障通知通道下发给应用层管理进程。
本发明实施例中，下发单元902将检测单元901检测到的资源状态异常事 件，通过在宿主机Host内部预先建立的IaaS代理进程与应用层代理进程之间的故障通知通道下发给应用层代理进程，由应用层代理进程根据资源状态异常事件对实际业务的影响程度，请求应用层管理进程对异常事件进行处理。
下发单元902将检测单元901检测到的资源状态异常事件，通过在宿主机Host内部预先建立的IaaS代理进程与应用层管理进程之间的故障通知通道下发给应用层管理进程，由应用层管理进程根据资源状态异常事件对实际业务的影响程度，对异常事件进行处理。
其中，在第一种实现方式中，下发单元902，还用于：
接收应用层管理中心节点发送的异常事件通知服务请求；
根据异常事件通知服务请求，创建故障通知通道并启动异常事件通知服务；
将异常事件通知服务的接入地址、接入通道类型和交换协议类型，反馈给应用层管理中心节点，指示应用层代理进程或者应用层管理进程根据接入地址、接入通道类型和交换协议类型接入异常事件通知服务。
在第二种实现方式中，检测单元901，用于：
接收应用层代理进程或应用层管理进程发送的订阅请求；
根据订阅请求，检测与该订阅请求相关的资源状态。
在第三种实现方式中，检测单元901，用于：
接收应用层管理进程发送的包含有订阅关系的订阅请求，其中，订阅关系用于表示应用层管理进程欲关注的虚拟机以及欲关注虚拟机的资源状态；
查找欲关注虚拟机所属的IaaS代理进程，得到欲关注IaaS代理进程；
将订阅关系发送给欲关注IaaS代理进程，并指示欲关注IaaS代理进程根据订阅关系监测欲关注虚拟机的资源状态。
在第四种实现方式中，检测单元901，具体用于：通过IaaS代理进程与应用层管理进程之间的故障通知通道接收订阅请求；或者
通过应用层管理进程、应用层管理中心节点和IaaS代理进程之间的故障 通知通道接收订阅请求。
基于应用层代理进程执行电信云中异常事件的处理方法，本发明实施例提供一种电信云中异常事件的处理装置，如图10所示，包括接收单元1001和请求单元1002，其中，
接收单元1001，用于接收IaaS代理进程通过在宿主机Host内部预先建立的IaaS代理进程与应用层代理进程之间的故障通知通道下发的资源状态异常事件；
请求单元1002，用于当资源状态异常事件对实际业务的影响程度达到设定级别时，请求应用层管理进程对异常事件进行处理。
在第一种实现方式中，接收单元1001，还用于：
接收应用层管理中心节点下发的接入指示，接入指示中包括IaaS代理进程反馈的异常事件通知服务的接入地址、接入通道类型和交换协议类型，并根据接入指示中包括的接入地址、接入通道类型和交换协议类型接入异常事件通知服务。
在第二种实现方式中，请求单元1002，还用于：
接收IaaS代理进程下发的资源状态异常事件之前，向IaaS代理进程发送订阅请求，请求IaaS代理进程下发与订阅请求相关的资源状态。
基于应用层管理进程执行电信云中异常事件的处理方法，本发明实施例还提供一种电信云中异常事件的处理装置，如图11A所示，该装置包括接收单元1101和处理单元1102，其中，
接收单元1101，用于接收IaaS代理进程通过在宿主机Host内部预先建立的IaaS代理进程与应用层管理进程之间的故障通知通道下发的资源状态异常事件；
处理单元1102，用于当资源状态异常事件对实际业务的影响程度达到设定级别时，对异常事件进行处理。
在第一种实现方式中，接收单元1102，还用于：
接收接收应用层管理中心节点下发的接入指示，接入指示包括IaaS代理进程反馈的异常事件通知服务的接入地址、接入通道类型和交换协议类型，并根据接入指示中包括的接入地址、接入通道类型和交换协议类型接入异常事件通知服务。
在第二种实现方式中，该装置还包括请求单元1103，如图11B所示，请求单元1103，用于：
接收IaaS代理进程下发的资源状态异常事件之前，向IaaS代理进程发送订阅请求，请求IaaS代理进程下发与订阅请求相关的资源状态。
在第三种实现方式中，请求单元1103，用于：
通过所述IaaS代理进程与应用层管理进程之间的故障通知通道，向IaaS代理进程发送包含有订阅关系的订阅请求，请求IaaS代理进程下发欲关注虚拟机的资源状态，订阅关系用于表示应用层管理进程欲关注的虚拟机以及欲关注虚拟机的资源状态；或者
通过应用层管理进程、应用层管理中心节点和IaaS代理进程之间的故障通知通道，向IaaS代理进程发送包含有订阅关系的订阅请求，请求IaaS代理进程下发欲关注虚拟机的资源状态，订阅关系用于表示应用层管理进程欲关注的虚拟机以及欲关注虚拟机的资源状态。
基于上述提供的电信云中异常事件的处理装置，本发明实施例还提供一种电信云中异常事件的处理装置，如图12所示，该装置包括：收发器1201，处理器1202，存储器1203和总线1204，其中，收发器1201，处理器1202和存储器1203均与总线1204连接。
处理器1202，用于检测资源状态；通过收发器1201将检测到的资源状态异常事件，通过在宿主机Host内部预先建立的IaaS代理进程与应用层代理进程之间的故障通知通道下发给应用层代理进程，由应用层代理进程根据资源状态异常事件对实际业务的影响程度，请求应用层管理进程对所述异常事件进行处理；和/或，将检测到的资源状态异常事件，通过在宿主机Host内部预先建 立的IaaS代理进程与应用层管理进程之间的故障通知通道下发给应用层管理进程，由应用层管理进程根据资源状态异常事件对实际业务的影响程度，对异常事件进行处理。
处理器1202，还用于通过收发器1201接收IaaS代理进程通过在宿主机Host内部预先建立的IaaS代理进程与应用层代理进程之间的故障通知通道下发的资源状态异常事件；当资源状态异常事件对实际业务的影响程度达到设定级别时，请求应用层管理进程对所述异常事件进行处理。
处理器1202，还用于通过收发器1201接收IaaS代理进程通过在宿主机Host内部预先建立的IaaS代理进程与应用层管理进程之间的故障通知通道下发的资源状态异常事件；当资源状态异常事件对实际业务的影响程度达到设定级别时，对异常事件进行处理。
其中，处理器1202执行上述过程通常由一个或多个软件程序控制完成，上述一个或多个软件程序存储于存储器1203中，当处理器1202需要执行上述过程时，将上述一个或多个软件程序调入处理器1202，由处理器1202控制完成上述过程。当然处理器1202执行上述过程也可通过硬件实现，本发明实施例不做限定。
本发明实施例提供的电信云中异常事件的处理装置，可以用来执行图4-图8B所示的电信云中异常事件的处理方法，因此对于图9-图12中涉及的电信云中异常事件的处理装置说明不够详尽的地方，可参阅图4-图8B的说明。
需要说明的是，本发明实施例提供的电信云中异常事件的处理装置可以是独立的部件，也可以是集成在IaaS代理进程、应用层管理进程或应用层代理进程之内，本发明实施例不做限定。
本发明实施例提供的电信云中异常事件的处理装置，通过在Host内部预先建立的IaaS代理进程与应用层代理进程之间的故障通知通道，或IaaS代理进程与应用层管理进程之间的故障通知通道，将检测到的资源状态异常事件直接下发给应用层代理进程或者应用层管理进程，无需经过IaaS管理中心以及应 用层管理中心节点，缩短了通知路径，并增强了可靠性。
显然，本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和范围。这样，倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。

Claims (24)

  1. 一种电信云中异常事件的处理方法，其特征在于，包括：
    基础设施即服务IaaS代理进程检测资源状态；
    所述IaaS代理进程将检测到的资源状态异常事件，通过在宿主机Host内部预先建立的IaaS代理进程与应用层代理进程之间的故障通知通道下发给应用层代理进程，由所述应用层代理进程根据所述资源状态异常事件对实际业务的影响程度，请求应用层管理进程对所述异常事件进行处理；和/或
    所述IaaS代理进程将检测到的资源状态异常事件，通过在宿主机Host内部预先建立的IaaS代理进程与应用层管理进程之间的故障通知通道下发给应用层管理进程，由所述应用层管理进程根据所述资源状态异常事件对实际业务的影响程度，对所述异常事件进行处理。
  2. 如权利要求1所述的方法，其特征在于，在IaaS代理进程检测资源状态之前，该方法还包括：
    IaaS代理进程接收应用层管理中心节点发送的异常事件通知服务请求；
    IaaS代理进程根据所述异常事件通知服务请求，创建故障通知通道并启动异常事件通知服务；
    IaaS代理进程将所述异常事件通知服务的接入地址、接入通道类型和交换协议类型，反馈给所述应用层管理中心节点，指示应用层代理进程或者应用层管理进程根据所述接入地址、所述接入通道类型和所述交换协议类型接入所述异常事件通知服务。
  3. 如权利要求1所述的方法，其特征在于，所述IaaS代理进程检测资源状态，包括：
    IaaS代理进程接收应用层代理进程或应用层管理进程发送的订阅请求；
    IaaS代理进程根据所述订阅请求，检测与所述订阅请求相关的资源状态。
  4. 如权利要求1所述的方法，其特征在于，所述IaaS代理进程检测资源 状态，包括：
    IaaS代理进程接收应用层管理进程发送的包含有订阅关系的订阅请求，所述订阅关系用于表示所述应用层管理进程欲关注的虚拟机以及欲关注虚拟机的资源状态；
    IaaS代理进程查找所述欲关注虚拟机所属的IaaS代理进程，得到欲关注IaaS代理进程；
    IaaS代理进程将所述订阅关系发送给所述欲关注IaaS代理进程，并指示所述欲关注IaaS代理进程根据所述订阅关系监测所述欲关注虚拟机的资源状态。
  5. 如权利要求4所述的方法，其特征在于，所述IaaS代理进程接收应用层管理进程发送的包含有订阅关系的订阅请求，具体包括：
    所述IaaS代理进程通过所述IaaS代理进程与应用层管理进程之间的故障通知通道接收所述订阅请求；或者
    所述IaaS代理进程通过应用层管理进程、应用层管理中心节点和IaaS代理进程之间的故障通知通道接收所述订阅请求。
  6. 一种电信云中异常事件的处理方法，其特征在于，包括：
    应用层代理进程接收基础设施即服务IaaS代理进程通过在宿主机Host内部预先建立的IaaS代理进程与应用层代理进程之间的故障通知通道下发的资源状态异常事件；
    当所述资源状态异常事件对实际业务的影响程度达到设定级别时，所述应用层代理进程请求应用层管理进程对所述异常事件进行处理。
  7. 如权利要求6所述的方法，其特征在于，所述应用层代理进程接收IaaS代理进程下发的资源状态异常事件之前，该方法还包括：
    所述应用层代理进程接收应用层管理中心节点下发的接入指示，所述接入指示中包括所述IaaS代理进程反馈的异常事件通知服务的接入地址、接入通道类型和交换协议类型；
    所述应用层代理进程根据所述接入指示中包括的所述接入地址、所述接入通道类型和所述交换协议类型接入所述异常事件通知服务。
  8. 如权利要求6所述的方法，其特征在于，所述应用层代理进程接收IaaS代理进程下发的资源状态异常事件之前，该方法还包括：
    所述应用层代理进程向所述IaaS代理进程发送订阅请求，请求所述IaaS代理进程下发与所述订阅请求相关的资源状态。
  9. 一种电信云中异常事件的处理方法，其特征在于，包括：
    应用层管理进程接收基础设施即服务IaaS代理进程通过在宿主机Host内部预先建立的IaaS代理进程与应用层管理进程之间的故障通知通道下发的资源状态异常事件；
    当所述资源状态异常事件对实际业务的影响程度达到设定级别时，所述应用层管理进程对所述异常事件进行处理。
  10. 如权利要求9所述的方法，其特征在于，所述应用层管理进程接收IaaS代理进程下发的资源状态异常事件之前，该方法还包括：
    接收应用层管理中心节点下发的接入指示，所述接入指示包括所述IaaS代理进程反馈的异常事件通知服务的接入地址、接入通道类型和交换协议类型；
    所述应用层管理进程根据所述接入指示中包括的所述接入地址、所述接入通道类型和所述交换协议类型接入所述异常事件通知服务。
  11. 如权利要求9所述的方法，其特征在于，所述应用层管理进程接收IaaS代理进程下发的资源状态异常事件之前，该方法还包括：
    所述应用层管理进程向所述IaaS代理进程发送订阅请求，请求所述IaaS代理进程下发与所述订阅请求相关的资源状态。
  12. 如权利要求11所述的方法，其特征在于，所述应用层管理进程向所述IaaS代理进程发送订阅请求，请求所述IaaS代理进程下发与所述订阅请求相关的资源状态，具体包括：
    所述应用层管理进程通过所述IaaS代理进程与应用层管理进程之间的故障通知通道，向所述IaaS代理进程发送包含有订阅关系的订阅请求，请求所述IaaS代理进程下发所述欲关注虚拟机的资源状态，所述订阅关系用于表示所述应用层管理进程欲关注的虚拟机以及欲关注虚拟机的资源状态；或者
    所述应用层管理进程通过应用层管理进程、应用层管理中心节点和IaaS代理进程之间的故障通知通道，向所述IaaS代理进程发送包含有订阅关系的订阅请求，请求所述IaaS代理进程下发所述欲关注虚拟机的资源状态，所述订阅关系用于表示所述应用层管理进程欲关注的虚拟机以及欲关注虚拟机的资源状态。
  13. 一种电信云中异常事件的处理装置，其特征在于，包括检测单元和下发单元，其中，
    所述检测单元，用于检测资源状态；
    所述下发单元，用于将所述检测单元检测到的资源状态异常事件，通过在宿主机Host内部预先建立的基础设施即服务IaaS代理进程与应用层代理进程之间的故障通知通道下发给应用层代理进程，由所述应用层代理进程根据所述资源状态异常事件对实际业务的影响程度，请求应用层管理进程对所述异常事件进行处理；和/或
    将所述检测单元检测到的资源状态异常事件，通过在宿主机Host内部预先建立的IaaS代理进程与应用层管理进程之间的故障通知通道下发给应用层管理进程，由所述应用层管理进程根据所述资源状态异常事件对实际业务的影响程度，对所述异常事件进行处理。
  14. 如权利要求13所述的装置，其特征在于，所述下发单元，还用于：
    接收应用层管理中心节点发送的异常事件通知服务请求；
    根据所述异常事件通知服务请求，创建故障通知通道并启动异常事件通知服务；
    将所述异常事件通知服务的接入地址、接入通道类型和交换协议类型，反 馈给所述应用层管理中心节点，指示应用层代理进程或者应用层管理进程根据所述接入地址、所述接入通道类型和所述交换协议类型接入所述异常事件通知服务。
  15. 如权利要求13所述的装置，其特征在于，所述检测单元，用于：
    接收应用层代理进程或应用层管理进程发送的订阅请求；
    根据所述订阅请求，检测与所述订阅请求相关的资源状态。
  16. 如权利要求15所述的装置，其特征在于，所述检测单元，用于：
    接收应用层管理进程发送的包含有订阅关系的订阅请求，所述订阅关系用于表示所述应用层管理进程欲关注的虚拟机以及欲关注虚拟机的资源状态；
    查找所述欲关注虚拟机所属的IaaS代理进程，得到欲关注IaaS代理进程；
    将所述订阅关系发送给所述欲关注IaaS代理进程，并指示所述欲关注IaaS代理进程根据所述订阅关系监测所述欲关注虚拟机的资源状态。
  17. 如权利要求16所述的装置，其特征在于，所述检测单元，具体用于：
    通过所述IaaS代理进程与应用层管理进程之间的故障通知通道接收所述订阅请求；或者
    通过应用层管理进程、应用层管理中心节点和IaaS代理进程之间的故障通知通道接收所述订阅请求。
  18. 一种电信云中异常事件的处理装置，其特征在于，包括接收单元和请求单元，其中，
    所述接收单元，用于接收基础设施即服务IaaS代理进程通过在宿主机Host内部预先建立的IaaS代理进程与应用层代理进程之间的故障通知通道下发的资源状态异常事件；
    所述请求单元，用于当所述资源状态异常事件对实际业务的影响程度达到设定级别时，请求应用层管理进程对所述异常事件进行处理。
  19. 如权利要求18所述的装置，其特征在于，所述接收单元，还用于：
    接收应用层管理中心节点下发的接入指示，所述接入指示中包括所述IaaS 代理进程反馈的异常事件通知服务的接入地址、接入通道类型和交换协议类型，并根据所述接入指示中包括的所述接入地址、所述接入通道类型和所述交换协议类型接入所述异常事件通知服务。
  20. 如权利要求18所述的装置，其特征在于，所述请求单元，还用于：
    接收IaaS代理进程下发的资源状态异常事件之前，向所述IaaS代理进程发送订阅请求，请求所述IaaS代理进程下发与所述订阅请求相关的资源状态。
  21. 一种电信云中异常事件的处理装置，其特征在于，包括接收单元和处理单元，其中，
    所述接收单元，用于接收基础设施即服务IaaS代理进程通过在宿主机Host内部预先建立的IaaS代理进程与应用层管理进程之间的故障通知通道下发的资源状态异常事件；
    所述处理单元，用于当所述资源状态异常事件对实际业务的影响程度达到设定级别时，对所述异常事件进行处理。
  22. 如权利要求21所述的装置，其特征在于，所述接收单元，还用于：
    接收接收应用层管理中心节点下发的接入指示，所述接入指示包括所述IaaS代理进程反馈的异常事件通知服务的接入地址、接入通道类型和交换协议类型，并根据所述接入指示中包括的所述接入地址、所述接入通道类型和所述交换协议类型接入所述异常事件通知服务。
  23. 如权利要求21所述的装置，其特征在于，该装置还包括请求单元，其中，
    所述请求单元，用于接收IaaS代理进程下发的资源状态异常事件之前，向所述IaaS代理进程发送订阅请求，请求所述IaaS代理进程下发与所述订阅请求相关的资源状态。
  24. 如权利要求23所述的装置，其特征在于，所述请求单元，用于：
    通过所述IaaS代理进程与应用层管理进程之间的故障通知通道，向所述IaaS代理进程发送包含有订阅关系的订阅请求，请求所述IaaS代理进程下发 所述欲关注虚拟机的资源状态，所述订阅关系用于表示所述应用层管理进程欲关注的虚拟机以及欲关注虚拟机的资源状态；或者
    通过应用层管理进程、应用层管理中心节点和IaaS代理进程之间的故障通知通道，向所述IaaS代理进程发送包含有订阅关系的订阅请求，请求所述IaaS代理进程下发所述欲关注虚拟机的资源状态，所述订阅关系用于表示所述应用层管理进程欲关注的虚拟机以及欲关注虚拟机的资源状态。
PCT/CN2015/070455 2014-01-27 2015-01-09 电信云中异常事件的处理方法及装置 WO2015109955A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US15/220,116 US10187181B2 (en) 2014-01-27 2016-07-26 Method and device for handling exception event in telecommunication cloud

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410040568.6A CN103746855B (zh) 2014-01-27 2014-01-27 电信云中异常事件的处理方法及装置
CN201410040568.6 2014-01-27

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/220,116 Continuation US10187181B2 (en) 2014-01-27 2016-07-26 Method and device for handling exception event in telecommunication cloud

Publications (1)

Publication Number Publication Date
WO2015109955A1 true WO2015109955A1 (zh) 2015-07-30

Family

ID=50503846

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/070455 WO2015109955A1 (zh) 2014-01-27 2015-01-09 电信云中异常事件的处理方法及装置

Country Status (3)

Country Link
US (1) US10187181B2 (zh)
CN (1) CN103746855B (zh)
WO (1) WO2015109955A1 (zh)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103746855B (zh) 2014-01-27 2017-09-12 华为技术有限公司 电信云中异常事件的处理方法及装置
CN105187482B (zh) * 2015-07-20 2018-09-28 深圳供电局有限公司 一种PaaS平台故障自愈实现的方法及消息服务器
CN106603498B (zh) * 2016-11-15 2020-01-10 华为技术有限公司 事件上报方法及装置
CN111316599B (zh) * 2017-11-09 2023-04-07 上海诺基亚贝尔股份有限公司 用于云环境中的持续可用性的方法、管理节点和处理节点
US10678630B2 (en) * 2017-12-15 2020-06-09 Wipro Limited Method and system for resolving error in open stack operating system
CN110839011A (zh) * 2018-08-17 2020-02-25 视联动力信息技术股份有限公司 监控资源信息的上报方法和装置
US11609776B1 (en) * 2019-12-23 2023-03-21 Cisco Technology, Inc. Elastic internet protocol (IP) address for hypervisor and virtual router management in a branch environment
CN112769605B (zh) * 2020-12-30 2022-08-09 杭州东方通信软件技术有限公司 一种异构多云的运维管理方法及混合云平台

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102984214A (zh) * 2012-11-08 2013-03-20 华为技术有限公司 一种实现电信云中业务迁移的方法及装置
US20130091282A1 (en) * 2011-10-06 2013-04-11 Channarong Tontiruttananon On-demand integrated capacity and reliability service level agreement licensing
CN103294540A (zh) * 2013-05-17 2013-09-11 北京航空航天大学 一种通过至强融核协处理器提升Erlang虚拟机性能的方法
CN103746855A (zh) * 2014-01-27 2014-04-23 华为技术有限公司 电信云中异常事件的处理方法及装置

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10037237B2 (en) * 2013-03-28 2018-07-31 Telefonaktiebolaget L M Ericsson (Publ) Method and arrangement for fault management in infrastructure as a service clouds

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130091282A1 (en) * 2011-10-06 2013-04-11 Channarong Tontiruttananon On-demand integrated capacity and reliability service level agreement licensing
CN102984214A (zh) * 2012-11-08 2013-03-20 华为技术有限公司 一种实现电信云中业务迁移的方法及装置
CN103294540A (zh) * 2013-05-17 2013-09-11 北京航空航天大学 一种通过至强融核协处理器提升Erlang虚拟机性能的方法
CN103746855A (zh) * 2014-01-27 2014-04-23 华为技术有限公司 电信云中异常事件的处理方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
YU , NAIBO: "Investigation of IaaS Mode", TELECOMMUNICATIONS SCIENCE, vol. 201110, no. 10A, pages 39 - 43 *

Also Published As

Publication number Publication date
US10187181B2 (en) 2019-01-22
CN103746855A (zh) 2014-04-23
US20160337084A1 (en) 2016-11-17
CN103746855B (zh) 2017-09-12

Similar Documents

Publication Publication Date Title
WO2015109955A1 (zh) 电信云中异常事件的处理方法及装置
KR102059251B1 (ko) 노드 시스템, 서버 장치, 스케일링 제어 방법 및 프로그램
US8910160B1 (en) Handling of virtual machine migration while performing clustering operations
US9448899B2 (en) Method, apparatus and system for switching over virtual application two-node cluster in cloud environment
US11330071B2 (en) Inter-process communication fault detection and recovery system
US10083098B1 (en) Network function virtualization (NFV) virtual network function (VNF) crash recovery
US20200042410A1 (en) Role designation in a high availability node
EP3014433B1 (en) Management of computing sessions
EP4083786A1 (en) Cloud operating system management method and apparatus, server, management system, and medium
WO2016165304A1 (zh) 一种实例节点管理的方法及管理设备
WO2015154246A1 (zh) 基于网络功能虚拟化的故障处理方法及装置、***
KR101840222B1 (ko) 컴퓨팅 세션의 관리
KR20180135124A (ko) 컴퓨팅 세션의 관리
US11995100B2 (en) System and method for highly available database service
US8566847B2 (en) Out-of-band host management via a management controller
US9571584B2 (en) Method for resuming process and information processing system
JP2008305070A (ja) 情報処理装置および情報処理装置システム
WO2013117081A1 (zh) 外接设备和虚拟设备的业务信息处理方法、装置和***
WO2017035737A1 (zh) 一种网络服务描述符上架方法及装置
US11341008B2 (en) System and method for reducing failover times in a redundant management module configuration
WO2024016624A1 (zh) 多集群访问方法和***
WO2018094686A1 (zh) 一种smb业务故障处理方法和存储设备
WO2020252724A1 (zh) 日志处理方法、设备及计算机可读存储介质
JP2013218449A (ja) クラウドコンピューティングシステム
TWM432075U (en) Monitoring device and monitoring system applicable to cloud algorithm

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15739818

Country of ref document: EP

Kind code of ref document: A1