EP2871553B1 - Systèmes et procédés pour protéger des biens virtualisés - Google Patents

Systèmes et procédés pour protéger des biens virtualisés Download PDF

Info

Publication number
EP2871553B1
EP2871553B1 EP14192169.2A EP14192169A EP2871553B1 EP 2871553 B1 EP2871553 B1 EP 2871553B1 EP 14192169 A EP14192169 A EP 14192169A EP 2871553 B1 EP2871553 B1 EP 2871553B1
Authority
EP
European Patent Office
Prior art keywords
asset
assets
power supply
supply unit
actions
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.)
Active
Application number
EP14192169.2A
Other languages
German (de)
English (en)
Other versions
EP2871553A1 (fr
Inventor
David Grehan
Sarah Jane Hannon
Frederik Kamminga
Paula Porter
Amit Kumar Khator
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Schneider Electric IT Corp
Original Assignee
Schneider Electric IT Corp
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 Schneider Electric IT Corp filed Critical Schneider Electric IT Corp
Publication of EP2871553A1 publication Critical patent/EP2871553A1/fr
Application granted granted Critical
Publication of EP2871553B1 publication Critical patent/EP2871553B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/26—Power supply means, e.g. regulation thereof
    • G06F1/30—Means for acting in the event of power-supply failure or interruption, e.g. power-supply fluctuations
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/26—Power supply means, e.g. regulation thereof
    • G06F1/32—Means for saving power
    • G06F1/3203—Power management, i.e. event-based initiation of a power-saving mode
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G06F3/0482—Interaction with lists of selectable items, e.g. menus
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G06F3/0486—Drag-and-drop
    • 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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
    • G06F9/4856—Task life-cycle, e.g. stopping, restarting, resuming execution resumption being on a different machine, e.g. task migration, virtual machine migration
    • 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/22—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]
    • 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/4557—Distribution of virtual machine instances; Migration and load balancing

Definitions

  • the technical field generally relates to power management within information technology (IT) environments, and more particularly, to systems and methods for managing and protecting virtualized assets.
  • IT information technology
  • a server may host multiple virtual machines and may be attached to one or more uninterruptable power supplies (UPSs) to insure continuous operation.
  • UPSs uninterruptable power supplies
  • a UPS may continue to power the server for some period of time.
  • it may be necessary to gracefully power-down the server in order to maintain the integrity of one or more virtual machines hosted on the server.
  • the specialized software may be configured to communicate with one or more UPSs (e.g., via a network) and process UPS events. For example, in the event of a power outage the specialized software may receive a UPS event indicating backup power is being supplied via the UPS. Additional events from the UPS may provide indications of power values including current load, remaining power, and estimated amount of power remaining. In some circumstances the specialized software may determine a shutdown of IT assets is appropriate. In these circumstances, the specialized software may execute shutdown commands (e.g., remote procedures) on one or more servers associated with a UPS that has indicated a fault. The one or more servers may perform an orderly shutdown of hosted virtual machines prior to turning off.
  • Documents US2012/036383 and WO2013/095505 disclose examples of power management methods and systems for protecting IT assets according to available prior art.
  • a power management system configured to protect a plurality of information technology (IT) assets is provided according to claims 1-8.
  • a non-transitory computer readable medium storing instructions for managing a plurality of IT assets is provided according to claims 14 and 15.
  • each server In a traditional IT environments (e.g., data centers, server rooms, IT closets, etc) each server typically hosts a single operating system (OS) which in turn may host one or more shared resources such as web servers, databases, and storage repositories.
  • virtualized environments include servers which are configured to host one or more virtual machines. These servers are commonly referred to as hosts or Hypervisors. Virtual machines may also be referred to as guest operating systems.
  • a Hypervisor presents the guest operating systems with a virtual operating platform and manages the execution of the guest operating systems. Multiple instances of a variety of operating systems may share the virtualized hardware resources.
  • a virtual machine as referred to herein, is a software implementation of a computer that executes programs like a physical machine.
  • FIG. 1 illustrates various types of Hypervisors generally indicated at 100.
  • the types 100 include a bare-metal type 102 and a hosted type 104.
  • the Hypervisor is executed directly on the host server's hardware. Guest operating systems on the bare-metal type 102 operate at what is considered two levels from the server hardware (e.g., the operating system and Hypervisor are interfaced).
  • the Hypervisor is hosted and executed by an OS (e.g., Linux, Windows Server, etc).
  • the virtual machine is executed by a Hypervisor application which is typically compatible with the operating system of the host.
  • VMware vSphere® offered by VMWare of Palo Alto, CA is one example of a hosted type 104 virtualization solution. Guest operating systems on the hosted type 104 operate at what is considered three levels from the server hardware.
  • Some IT environments may include a mix of virtualized technologies including servers configured as both the bare-metal type 102 and the hosted type 104.
  • Traditional power management includes specialized software which is executed by an OS. For this reason, the specialized software may be incompatible with the bare-metal type 102 as the specialized software requires compatible operating systems.
  • the hosted type 104 may be compatible with the specialized software; however, it may be impractical to install specialized software on each and every server.
  • Some aspects and embodiments disclosed herein are directed to a system and method for protecting virtualized assets within an IT environment without specialized power-protection software installed on each physical server.
  • migration and shutdown of virtual machines may be based on power-related events from power supply units (e.g., UPSs, PDUs, outlets, generators, electrical relays, etc.).
  • power supply units e.g., UPSs, PDUs, outlets, generators, electrical relays, etc.
  • relationships between clustered Hypervisors, virtual machines, and power supply units may be determined and advantageously used to migrate virtual machines in the event of power faults.
  • Virtualization technologies enable virtual machines to be moved amongst Hypervisors.
  • Systems and methods in accord with some examples may migrate a virtual machine from a Hypervisor experiencing a power fault to a Hypervisor which is coupled to a non-faulting power supply unit.
  • aspects and embodiments disclosed herein include examples directed to UPS devices, other power supply units may be utilized.
  • a system and method to order shut down and startup of Hypervisors and virtual machines is provided.
  • an ordered shutdown may be desirable.
  • Lower priority assets may be shut off first while higher priority assets may be shut off last.
  • critical assets like storage arrays and virtual asset power management systems (VAPMS) may be depended on by other assets to operate and should be shut down last.
  • VAPMS virtual asset power management systems
  • a particular order may be desirable. For example, a database server may need to be operational prior to any an application server coming online.
  • FIG. 2 is one example of an IT environment 200 including multiple Hypervisors and UPSs.
  • the IT environment 200 includes a network 202, a cluster 204, a storage array 206, a virtual asset power management system 208, a plurality of UPSs 210, a user 212, and a third-party virtualization management system 214.
  • the cluster 204 includes a first Hypervisor 216 and a second Hypervisor 218. Although the cluster 204 is shown as including only two Hypervisors, it should be understood that additional Hypervisors may be included in a cluster. Likewise, although in the example shown there is only one cluster, in other examples there may be multiple clusters.
  • the first Hypervisor 216 and the second Hypervisor 218 may host a plurality of virtual machines, such as the virtual machines 220.
  • the virtual machines 220 may host any number of shared resources such as databases, web servers and application servers, etc.
  • Migration of a virtual machine may include transferring an instance of a virtual machine hosted on one Hypervisor (e.g., the Hypervisor 216) and instructing a second Hypervisor (e.g., the Hypervisor 218) to host and execute the same virtual machine. This may be accomplished by centrally storing virtual machine images.
  • virtual machines such as the virtual machines 220 may be executed from a virtual machine image physically located on the storage array 206.
  • the Hypervisors 216 and 218 may launch one or more virtual machines 220 by retrieving and executing the virtual machine image located on the storage array 206.
  • migration of virtual machines includes the VAPMS 208 instructing a Hypervisor to launch one or more virtual machines via an application programming interface (API).
  • API application programming interface
  • the instruction may include a location (e.g., network path, physical path) of where the virtual machine image may be found and other execution parameters.
  • the instruction may include an IP address of the storage array 206 and a path to the virtual machine image.
  • the VAPMS 208 may instruct the third-party virtualization management system 214 to perform the migration by proxy.
  • the VAPMS 208 is implemented using one or more computer systems, such as the distributed computer system 900 discussed below with regard to FIG. 9 .
  • the VAPMS 208 may be configured to monitor and manage one or more assets of the IT environment 200.
  • the VAPMS 208 may be configured to communicate with the Hypervisors 216 and 218 of the cluster 204 via the network 202.
  • the VAPMS 208 may communicate with UPSs such as the UPSs 210 via the network 202.
  • examples of the VAPMS 208 include a variety of hardware and software components configured to perform the functions described herein and examples are not limited to a particular hardware component, software component, or particular combination thereof.
  • the network 202 may include any communication network through which computer systems send and receive information.
  • the network 202 may be a public network, such as the internet, and may include other public or private network such as LANs, WANs, extranets and internets.
  • the user 212 may utilize the network 202 to exchange data with the VAPMS 208.
  • the user 212 may access the VAPMS 208 using the network 202 from a remote computer system or from a mobile device such as a laptop or smart phone.
  • an application (or "app") may be executed on the computer system (or directly on the VAPMS 208) and may enable the user 212 to perform operations which configure, monitor and control the VAPMS 208.
  • the user 212 may access a webpage hosted by the VAPMS 208 in order to perform operations which configure, monitor and control the VAPMS 208.
  • one or more IT assets may be configured with network interfaces and host one or more web services.
  • the VAPMS 208 may communicate with a web service which is responsible for handling requests, such as requests made by the user 212 via the network 202.
  • the one or more IT assets may communicate machine-to-machine via web services.
  • a web service may be defined as a software system designed to support interoperable machine-to-machine interaction over a network.
  • An IT asset may be configured with one or more web services which include interfaces capable of generating and processing messages in a machine-processable format (e.g., Web Services Description Language (WSDL)).
  • WSDL Web Services Description Language
  • the one or more IT assets may interact with each other using web services configured to process Simple Object Access Protocol (SOAP) messages. These messages may be communicated using HTTP with an XML serialization or other Web-related standard.
  • SOAP Simple Object Access Protocol
  • a web service may be configured according to Web-related communication standards.
  • information may flow between the elements, components and subsystems described herein using a variety of techniques.
  • Such techniques include, for example, passing the information over the network 202 using standard protocols, such as TCP/IP, passing the information between modules in memory and passing the information by writing to a file, database, or some other non-volatile storage device.
  • pointers, identifiers, or other references to information may be transmitted and received in place of, or in addition to, copies of the information.
  • the information may be exchanged in place of, or in addition to, pointers, identifiers, or other references to the information.
  • Other techniques and protocols for communicating information may be used without departing from the scope of the examples disclosed herein.
  • the VAPMS may communicate with one or more IT assets via the network 202. This communication may include initially identifying assets and asset types.
  • the VAPMS may be configured to initiate a discovery request and receive responses from one or more IT assets in accordance with the process discussed below with reference to FIG. 10 .
  • the discovery process may first discover UPSs such as the UPSs 210 of FIG. 2 .
  • the discovery process may then discover other IT assets such as Hypervisors and third-party virtualization management systems.
  • identifiers of IT assets may be stored in a non-volatile storage area of the VAPMS 208. These identifiers may include asset name, asset type, hostname, and IP address.
  • the VAPMS 208 may communicate with the third-party virtualization management system 214 to identify virtual IT assets.
  • the third party virtualization management system 214 may provide a list of Hypervisors and virtual machines via an API call.
  • identifiers for UPSs, Hypervisors, and other IT assets may be manually defined by a user, such as the user 212.
  • the stored identifiers of IT assets may be subsequently displayed to a user to perform configuration and maintenance of the VAPMS 208.
  • FIG. 3 an example user interface screen 300 of the VAPMS 208 is illustrated.
  • the user interface screen 300 includes a navigation panel 302 and a content panel 334.
  • the navigation panel 302 includes one or more navigation options including a Hypervisor Protection option 308 and Power Supply Device options 310.
  • the VAPMS 208 may be configured to change the content of the content panel 334 by receiving a user selection from the navigation panel 302.
  • the Hypervisor Protection options 308 was selected by the user 212 initiating a mouse operation (e.g., a single-click or double-click) or a keystroke.
  • power-related assets e.g., UPSs, PDUs, etc
  • UPSs UPSs, PDUs, etc
  • the VAPMS 208 may receive one or more user selections to configure location (e.g., identifier of an IT environment), cluster, and Hypervisor to UPS relationships.
  • location e.g., identifier of an IT environment
  • selection of the Hypervisor Protection options 308 visualizes an inventory tree view 304 and a mapping tree view 306.
  • the VAPMS 208 visualizes clusters and associated devices in a tree hierarchy to allow a user, such as the user 212, to visually determine how an IT environment is presently configured and protected.
  • the inventory tree view 304 may be configured to display Hypervisor identifiers (e.g., leaves) under location and/or cluster nodes.
  • a location node 312 includes a cluster node 314 and IT asset nodes 316 and 318.
  • the cluster node 314 may represent the cluster 204 of FIG. 2 .
  • the IT asset nodes 316 and 318 may represent the Hypervisors 216 and 218 of FIG. 2 .
  • the VAPMS 208 may be hosted in a virtual machine, such as one of the virtual machines 220 of FIG. 2 .
  • a special icon such as the icon associated with the node 318 may indicate that the node (Hypervisor) includes an instance of the VAPMS 208, and thus, is a critical IT asset.
  • migration and shutdown of virtual machines may treat critical IT assets differently. For example, IT assets hosting an instance of the VAPMS 208 or the third-party virtualization management system 214 should only be migrated and/or shutdown last to avoid service interruptions. Likewise, some critical IT assets, such as the storage array 206, may need to be shutdown last and started up first.
  • Hypervisors may host and execute virtual machines based on virtual machines physically located on a storage array. For this reason, the VAPMS 208 may prioritize the startup and shutdown of these critical assets to avoid interruption of services.
  • the mapping tree view 306 is designed to allow a user, such as the user 212, to initiate the generation of associations between IT assets (e.g., Hypervisors 316 and 318) and one or more power supply units (e.g., UPSs 322, 324, and 326).
  • IT assets e.g., Hypervisors 316 and 3108
  • UPSs 322, 324, and 326 power supply units
  • the VAPMS 208 generates these associations, in part, via the user interface 300. These associations allow a user to determine if IT assets are protected and to make modifications as necessary. In addition, these associations allow the VAPMS 208 to receive and correlate power-related events from UPSs in order to make intelligent decisions based on which IT assets may be affected.
  • the mapping tree view 306 may be empty.
  • the mapping tree view 306 may include an existing list of UPSs and associations.
  • UPSs and associations between UPSs and IT assets may be automatically determined.
  • a user such as the user 212, may add, remove, and undo changes to UPS nodes in the mapping tree view 306 using the mapping operations 320. For example, a user may click the Add option of the mapping options 320 and be presented with a list (not shown) of available UPS assets to be added to the mapping tree view 306.
  • the mapping tree view 306 includes UPS nodes 322, 324 and 326.
  • the UPS node 326 may represent a UPS device which is configured with a switched outlet group. For example, in the example shown a main outlet group node 328 and a secondary outlet group node 330 is displayed. Each outlet group of the UPS node 326 represents a separately controllable outlet group of a physical UPS. As discussed further below with reference to the processes of FIGs. 10-12 , the order in which migration and shutdown of Hypervisors occurs may be determined based on the order in which the outlet groups appear under a UPS node, such as the UPS node 328.
  • the VAPMS 208 may generate one or more associations based on the mapping tree view 306.
  • the user 212 may interact with the user interface 200 to generate the association of one or more Hypervisor nodes with one or more UPS nodes in the mapping tree view 306.
  • the user 212 may use a mouse cursor 332 to initiate a drag-and-drop operation over the mapping tree view 306.
  • releasing the cursor 332 will then associate the Hypervisor node 318 with the main outlet group node 328.
  • a user may continue to map each Hypervisor within the cluster 314 until each IT asset is protected by an associated UPS.
  • the cluster 314 is grayed out (disabled) because each associated cluster asset has been associated with one or more UPSs in the mapping tree view 306.
  • one or more Hypervisor nodes may be associated with an outlet group (e.g., outlet groups 328 or 330) or with a UPS node (e.g., UPS nodes 322 and 324). It should be understood that in some IT environments a Hypervisor may be backed up by more than one UPS. Accordingly, the mapping tree view 306 may include a Hypervisor node being associated with more than one UPS node or outlet group node. As discussed further below, when a Hypervisor has at least one associated UPS that is not experiencing an interruption in power, the VAPMS 208 may determine migration and shutdown processes in accordance with FIGs. 10-12 is unnecessary. As discussed below with reference to the processes of FIGs. 10-12 , the order in which Hypervisors appear under UPS nodes, such as UPS nodes 322, 324 and 326, may determine the order in which migration and shutdown occurs.
  • UPS nodes 322, 324 and 326 UPS nodes
  • the VAPMS may receive the generated associations based on a user action (e.g., clicking an apply button) and store the associations in a non-volatile memory area.
  • FIG. 4 another example of a user interface of the VAPMS 208 is generally indicated at 400.
  • settings related to the Shutdown Settings options 402 is visualized in the content panel 334.
  • One or more global options related to shutdown and migration may be configured using the user interface 400.
  • the VAPMS 208 may use one or more of the global options as a default parameter.
  • settings may be defined with a high degree of granularity within the VAPMS 208 to provide fine grain control of migration and shutdown processes.
  • the Shutdown Settings options 402 displayed within the content panel 334 includes an expander control 404 with various settings categories.
  • the Virtual Machine Migration category 406 includes an Enable VM Migration check box 408 and a Duration entry box 410.
  • the selection of the check box 408 enables a default mode of attempting to migrate virtual machines in the event of a detected power condition (e.g., a fault).
  • the Duration entry box 410 determines the amount of time (in seconds) before the VAPMS 208 should exit out of the process of migrating virtual machines.
  • An apply button 412 causes the VAPMS 208 to apply any changes made to the settings while an undo button 414 will undo any changes made.
  • FIG. 5 another example of a user interface of the VAPMS 208 is generally indicated at 500.
  • settings related to the Shutdown Settings option 402 may be visualized in the content panel 334.
  • the Shutdown Settings option 402 within the content panel 334 includes an expander control 404 with various settings categories.
  • the Virtual Machine Shutdown/Startup category 502 has been expanded (e.g., made visible) and includes an VM Shutdown checkbox 504, a VM Shutdown Duration entry box 506, a VM Startup checkbox 508, and a VM startup duration entry box 510.
  • the VM shutdown checkbox 504 enables the option of shutting down virtual machines in the event of a power event detected by the VAPMS 208. As discussed below with reference to the process of FIGs. 10-12 , when the option of shutting down virtual machines is enabled the VAPMS 208 will attempt to migrate (if enabled) the virtual machines to another hypervisor first.
  • the VM Shutdown Duration checkbox 506 determines the amount of time (in seconds) the Hypervisor VAPMS should wait before continuing with the next action in a shut down process.
  • the VAPMS 208 may allow settings to be applied at a fine-grain level.
  • UPS assets 310 FIG. 3
  • FIG. 6 with additional reference to FIG. 3 is another example of a user interface of the VAPMS 208 is generally indicated at 600.
  • settings related to a UPS asset 602 may be visualized in the content panel 334.
  • the content panel 334 includes UPS details 604, a settings expander control 606, an apply button 608 and an undo button 610.
  • the settings expander control 606 includes a plurality of settings categories including Migration settings 612.
  • the Migration settings 612 include an Enable VM Migration check box 614 and a Duration entry box 616.
  • the VAPMS 208 may enable settings specific to each individual power-related asset.
  • the UPS details 604 may include information such as an IP address 618, a UPS model identifier 620 and a UPS configuration mode 622.
  • the Enable VM Migration check box 614 overrides a global migration setting, such as the global migration option enabled by the Enable VM Migration checkbox 408 of FIG. 4 .
  • the Duration entry box 616 overrides a duration setting defined by the Duration entry box 410 of FIG. 4 .
  • the extender control 606 includes a Virtual Machine Shutdown/Startup settings category 702.
  • the Virtual Machine Shutdown/Startup settings category 702 includes a VM Shutdown checkbox 704, a VM Shutdown Duration entry box 706, a VM Startup checkbox 708, and a VM Startup Duration entry box 710.
  • global settings of the VAPMS 208 may be overridden in regards to shut down settings. For example, virtual machine shutdown/startup may be disabled for a particular Hypervisor by unchecking the VM Shutdown checkbox 704 and the VM Startup checkbox 710.
  • the user interface 800 includes a Virtual Machine Migration checkbox 802, a Virtual Machine Migration Duration entry box 804, a Virtual Machine Shutdown checkbox 806, a Virtual Machine Shutdown duration entry box 808, a Virtual Machine Startup checkbox 810, and a Virtual Machine Startup entry box 812.
  • changes made to VAPMS 208 using the user interface 800 may override the default settings and asset-specific settings discussed above with reference to FIGs. 4-7 .
  • aspects and functions described herein may be implemented as specialized hardware or software components executing in one or more computer systems.
  • computer systems There are many examples of computer systems that are currently in use. These examples include, among others, network appliances, personal computers, workstations, mainframes, networked clients, servers, media servers, application servers, database servers and web servers.
  • Other examples of computer systems may include mobile computing devices, such as cellular phones and personal digital assistants, and network equipment, such as load balancers, routers and switches.
  • aspects may be located on a single computer system or may be distributed among a plurality of computer systems connected to one or more communications networks.
  • aspects and functions may be distributed among one or more computer systems configured to provide a service to one or more client computers, or to perform an overall task as part of a distributed system. Additionally, aspects may be performed on a client-server or multi-tier system that includes components distributed among one or more server systems that perform various functions. Consequently, examples are not limited to executing on any particular system or group of systems. Further, aspects and functions may be implemented in software, hardware or firmware, or any combination thereof. Thus, aspects and functions may be implemented within methods, acts, systems, system elements and components using a variety of hardware and software configurations, and examples are not limited to any particular distributed architecture, network, or communication protocol.
  • the distributed computer system 900 includes one or more computer systems that exchange information. More specifically, the distributed computer system 900 includes computer systems 902, 904 and 906. As shown, the computer systems 902, 904 and 906 are interconnected by, and may exchange data through, a communication network 908.
  • the network 908 may include any communication network through which computer systems may exchange data.
  • the computer systems 902, 904 and 906 and the network 908 may use various methods, protocols and standards, including, among others, Fibre Channel, Token Ring, Ethernet, Wireless Ethernet, Bluetooth, IP, IPV6, TCP/IP, UDP, DTN, HTTP, FTP, SNMP, SMS, MMS, SS7, JSON, SOAP, CORBA, REST and Web Services.
  • the computer systems 902, 904 and 906 may transmit data via the network 908 using a variety of security measures including, for example, TLS, SSL or VPN.
  • the distributed computer system 900 illustrates three networked computer systems, the distributed computer system 900 is not so limited and may include any number of computer systems and computing devices, networked using any medium and communication protocol.
  • the computer system 902 includes a processor 910, a memory 912, an interconnection element 914, an interface 916 and data storage element 918.
  • the processor 910 performs a series of instructions that result in manipulated data.
  • the processor 910 may be any type of processor, multiprocessor or controller. Some example processors include commercially available processors such as an Intel Xeon, Itanium, Core, Celeron, or Pentium processor, an AMD Opteron processor, an Apple A4 or A5 processor, a Sun UltraSPARC or IBM Power5+ processor and an IBM mainframe chip.
  • the processor 910 is connected to other system components, including one or more memory devices 912, by the interconnection element 914.
  • the memory 912 stores programs and data during operation of the computer system 902.
  • the memory 912 may be a relatively high performance, volatile, random access memory such as a dynamic random access memory (“DRAM”) or static memory (“SRAM").
  • the memory 912 may include any device for storing data, such as a disk drive or other nonvolatile storage device.
  • Various examples may organize the memory 912 into particularized and, in some cases, unique structures to perform the functions disclosed herein. These data structures may be sized and organized to store values for particular data and types of data.
  • the interconnection element 914 may include one or more physical busses, for example, busses between components that are integrated within a same machine, but may include any communication coupling between system elements including specialized or standard computing bus technologies such as IDE, SCSI, PCI and InfiniBand.
  • the interconnection element 914 enables communications, such as data and instructions, to be exchanged between system components of the computer system 902.
  • the computer system 902 also includes one or more interface devices 916 such as input devices, output devices and combination input/output devices.
  • Interface devices may receive input or provide output. More particularly, output devices may render information for external presentation. Input devices may accept information from external sources. Examples of interface devices include keyboards, mouse devices, trackballs, microphones, touch screens, printing devices, display screens, speakers, network interface cards, etc. Interface devices allow the computer system 902 to exchange information and to communicate with external entities, such as users and other systems.
  • the data storage element 918 includes a computer readable and writeable nonvolatile, or non-transitory, data storage medium in which instructions are stored that define a program or other object that is executed by the processor 910.
  • the data storage element 918 also may include information that is recorded, on or in, the medium, and that is processed by the processor 910 during execution of the program. More specifically, the information may be stored in one or more data structures specifically configured to conserve storage space or increase data exchange performance.
  • the instructions may be persistently stored as encoded signals, and the instructions may cause the processor 910 to perform any of the functions described herein.
  • the medium may, for example, be optical disk, magnetic disk or flash memory, among others.
  • the processor 910 or some other controller causes data to be read from the nonvolatile recording medium into another memory, such as the memory 912, that allows for faster access to the information by the processor 910 than does the storage medium included in the data storage element 918.
  • the memory may be located in the data storage element 918 or in the memory 912, however, the processor 910 manipulates the data within the memory, and then copies the data to the storage medium associated with the data storage element 918 after processing is completed.
  • a variety of components may manage data movement between the storage medium and other memory elements and examples are not limited to particular data management components. Further, examples are not limited to a particular memory system or data storage system.
  • the computer system 902 is shown by way of example as one type of computer system upon which various aspects and functions may be practiced, aspects and functions are not limited to being implemented on the computer system 902 as shown in FIG. 9 .
  • Various aspects and functions may be practiced on one or more computers having a different architectures or components than that shown in FIG. 9 .
  • the computer system 902 may include specially programmed, special-purpose hardware, such as an application-specific integrated circuit ("ASIC") tailored to perform a particular operation disclosed herein.
  • ASIC application-specific integrated circuit
  • another example may perform the same function using a grid of several general-purpose computing devices running MAC OS System X with Motorola PowerPC processors and several specialized computing devices running proprietary hardware and operating systems.
  • the computer system 902 may be a computer system including an operating system that manages at least a portion of the hardware elements included in the computer system 902.
  • a processor or controller such as the processor 910, executes an operating system.
  • Examples of a particular operating system that may be executed include a Windows-based operating system, such as, Windows NT, Windows 2000 (Windows ME), Windows XP, Windows Vista or Windows 7 operating systems, available from the Microsoft Corporation, a MAC OS System X operating system or an iOS operating system available from Apple Computer, one of many Linux-based operating system distributions, for example, the Enterprise Linux operating system available from Red Hat Inc., a Solaris operating system available from Sun Microsystems, or a UNIX operating systems available from various sources. Many other operating systems may be used, and examples are not limited to any particular operating system.
  • the processor 910 and operating system together define a computer platform for which application programs in high-level programming languages are written.
  • These component applications may be executable, intermediate, bytecode or interpreted code which communicates over a communication network, for example, the Internet, using a communication protocol, for example, TCP/IP.
  • aspects may be implemented using an object-oriented programming language, such as .Net, SmallTalk, Java, C++, Ada, C# (C-Sharp), Python, or JavaScript.
  • object-oriented programming languages such as .Net, SmallTalk, Java, C++, Ada, C# (C-Sharp), Python, or JavaScript.
  • Other object-oriented programming languages may also be used.
  • functional, scripting, or logical programming languages may be used.
  • various aspects and functions may be implemented in a non-programmed environment, for example, documents created in HTML, XML or other format that, when viewed in a window of a browser program, can render aspects of a graphical-user interface or perform other functions.
  • various examples may be implemented as programmed or non-programmed elements, or any combination thereof.
  • a web page may be implemented using HTML while a data object called from within the web page may be written in C++.
  • the examples are not limited to a specific programming language and any suitable programming language could be used.
  • the functional components disclosed herein may include a wide variety of elements, e.g. specialized hardware, executable code, data structures or objects, which are configured to perform the functions described herein.
  • the components disclosed herein may read parameters that affect the functions performed by the components. These parameters may be physically stored in any form of suitable memory including volatile memory (such as RAM) or nonvolatile memory (such as a magnetic hard drive). In addition, the parameters may be logically stored in a propriety data structure (such as a database or file defined by a user mode application) or in a commonly shared data structure (such as an application registry that is defined by an operating system). In addition, some examples provide for both system and user interfaces that allow external entities to modify the parameters and thereby configure the behavior of the components.
  • FIG. 10 One example of such a virtual asset power management process 950 is illustrated in FIG. 10 .
  • the process 950 includes acts of identifying IT assets, determining associations, and monitoring power-related events. The method begins in act 952.
  • a VAPMS such as the VAPMS 208 of FIG. 2 identifies one or more IT assets.
  • the VAPMS 208 may initially identify if one or UPSs are present within an IT environment.
  • the VAPMS 208 may initiate a discovery procedure via a network, such as the network 202 of FIG. 2 .
  • a UDP message may be broadcasted to a subnet of the network 202.
  • simple network management protocol SNMP
  • SNMP simple network management protocol
  • the VAPMS 208 may identify other assets of the IT environment including Hypervisors.
  • some Hypervisors may be configured to respond to discovery requests. In some circumstances it may be necessary to enter Hypervisor information manually.
  • the VAPMS 208 may provide a user interface or API which enables the manual creation of Hypervisor identifiers within the VAPMS 208.
  • the VAPMS 208 may communicate with a third-party virtualization management system, such as the third-party virtualization management system 214 of FIG. 2 to identify one or more Hypervisors and virtualized assets such as virtual machines.
  • the VAPMS 208 may communicate via a web-service hosted on the third-party virtualization management system 214 and may initiate one or more API calls to retrieve a list of Hypervisors and their associated virtual machines.
  • third-party virtualization management systems may be integrated with to advantageously control the operation of Hypervisors and their virtual machines.
  • the VAPMS 208 may communicate with one or more Hypervisors directly to identify what virtual machines are currently hosted.
  • the VAPMS may perform migration and shutdown of virtual machines directly.
  • identifiers of IT assets may be stored in a non-volatile memory area of the VAPMS 208.
  • the VAPMS 208 may generate one or more associations between IT assets determined in the act 954.
  • Hypervisors may be associated with one or more UPSs.
  • the associations may be manually defined by a user, such as the user 212, via the user interface 300.
  • the associations may be automatically determined when IT assets are initially determined in the act 954.
  • an IP address scheme may be used to determine a UPS device which is coupled to one or more Hypervisors.
  • an IP address assigned to the UPS device may have a particular octet set to a predefined constant. For instance, an IP address of 192.168.1.100 may be assigned to a UPS.
  • the VAPMS 208 may then associate any IT asset with an IP address of 192.168.1.101-254 as being associated with the UPS.
  • the VAPMS 208 may monitor power-related events from the one or UPSs identified in the act 954. As discussed below with reference to FIG. 10 , power-related events may be received and correlated based on the associations generated in the act 956.
  • Processes in accord with the virtual asset power management process 950 enable the identification and association of IT assets with one or more UPSs. According to these processes, an end user may easily determine which IT assets are protected and what power-related asset they are protected by.
  • some examples perform processes through which the VAPMS 208 monitors power-related events from one or more UPSs.
  • One example of such a monitoring of power-related events process is illustrated in FIG. 11 .
  • the process 970 includes acts of receiving power-related events, determining sequence of actions, and performing the sequence of actions. The process begins in act 972.
  • the VAPMS 208 receives an event via a network, such as the network 202 of FIG. 2 , from a UPS or other IT asset within the IT environment 200.
  • the event may be a power-related event and may indicate at least one of a power failure, current load, and a power restored event.
  • the VAPMS 208 may determine which UPS the event originated from (e.g., by IP address, Hostname, contents of the event, etc). Once the originating asset of the event is determined, the VAPMS 208 may determine the originating asset's relationship with other IT assets based on the associations generated in the act 956 of FIG. 10 .
  • the originating asset may be identified as the UPS 324 ( FIG. 3 ) which may be associated with one or more Hypervisors.
  • a sequence of actions may be determined based on the type of event, the identified originating asset of the power-related event, and IT assets potentially affected. For instance, if the type of event indicates a power failure then one or more associated IT assets may be affected.
  • the VAPMS 208 may determine a sequence of actions to perform including migrating virtual machines of affected IT assets to avoid service interruptions and maintain data integrity.
  • the UPS 324 FIG. 3
  • the UPS 324 initiates a power event indicating loss of main power
  • the VAPMS 208 may determine one or more virtual machines hosted by the Hypervisor 216 which may be migrated to avoid interruption of service. As discussed above with reference to FIG. 3 , some virtual machines may be hosting critical virtualized assets such as the VAPMS 208 and the third-party virtualization management system 214. The VAPMS 208 may determine that such critical virtualized assets should be migrated last.
  • the sequence in which virtual machines are migrated is based on the associations generated in the act 956 of FIG. 10 .
  • the order in which the IT asset nodes appear within the user interface 300 will govern the order in which migration occurs. For example, if the Hypervisor nodes 316 and 318 are associated with the UPS node 324, the order in which they appear below the UPS node 324 establishes the order of migration and/or shutdown. In some instances this order may be overridden based on whether an IT asset is a critical asset. For example, a Hypervisor hosting an instance of the VAPMS 208 would be migrated and/or shutdown last regardless of the Hypervisor's position below a UPS node.
  • an IT asset may be protected by more than one UPS.
  • a primary and secondary UPS may protect a group of related IT assets (e.g., in a cluster).
  • the VAPMS 208 may receive a power event indicating a power fault for one or more of the connected UPSs. The VAPMS 208 may then determine if at least one of the connected UPSs is operating normally. In one example, if at least one UPS is operating normally no migrations may be initiated.
  • the VAPMS 208 may be configured with global settings and asset-specific settings. The sequence of actions in response to a power event may be adapted based on these settings.
  • the global settings may include a global option to allow virtual machines migration. This setting may be adjusted in the VAPMS 208 using the Enable VM Migration checkbox 408 ( FIG. 4 ).
  • the global settings may include a global option to allow the startup and shutdown of Hypervisors and their virtual machines.
  • FIG. 5 includes an example of these settings that may be changed in the VAPMS 208 using the VM Shutdown checkbox 504 and the VM Startup checkbox 508.
  • these global settings may be overridden to provide a high degree of granularity and control by having distinct settings for each cluster, each IT asset within the clusters, and for each virtualized asset.
  • This fine-grain control is found above with reference to FIGS. 6-7 .
  • a UPS may include two or more outlet groups.
  • the sequence in which migration may occur may be based on the outlet groups. For example, Hypervisors associated with the Main Outlets group 328 of FIG. 3 may be migrated only after the Hypervisors associated with a secondary outlet group (e.g., the outlet group 330) are migrated first.
  • Hypervisors and their virtual machines
  • an available Hypervisor may have insufficient processing and/or power resources to host additional virtual machines.
  • the VAPMS 208 may query a Hypervisor for current CPU usage, current number or running virtual machines, and available memory.
  • suitability may be based on whether a Hypervisor is coupled to a non-faulting UPS.
  • migration of virtual machines may be limited to only Hypervisors within the same cluster. In these examples, the VAPMS 208 may not have a suitable Hypervisor in the cluster to migrate virtual machines to.
  • a power event may indicate that power has been restored.
  • a sequence similar to a sequence used to migrate virtual machines may be determined. However, during startup the order in which Hypervisors and other IT assets are started up is in reverse. For example, a Hypervisor hosting an instance of the third-party virtualization management system 214 may be migrated and/or shutdown last. During startup, however, the Hypervisor hosting an instance of the third-party virtualization management system 214 may be started up prior to other assets which depend on the third-party virtualization management system 214.
  • the VAPMS 208 executes a sequence of actions determined in the act 976.
  • the sequence of actions may be based on receiving an event, such as an event indicating a power fault or restoration of power.
  • the sequence of actions may include a list of affected IT assets and an order by which migration and/or shutdown may occur. The process ends in act 980.
  • Processes in accord with the virtual machine management process 970 enable the ability to correlate power-related events with an originating IT asset via associations within the VAPMS 208.
  • IT assets which may be affected by the power-related event may be identified along with a sequence of actions.
  • the sequence of actions may be executed to migrate and/or shutdown data center assets and virtual machines to avoid interruption of service and maintain data integrity.
  • the VAPMS 208 executes a sequence of actions determined in the act 976.
  • One example of the process of executing a sequence of actions is illustrated in FIG. 12 .
  • the process 990 includes acts of querying each Hypervisor, iterating through a list of virtual machines, communicating shutdown requests, and communicating startup requests.
  • the process 990 begins the act 992.
  • the sequence of actions may be performed by the VAPMS 208.
  • the sequence of actions may include a list of IT assets which may be affected by the power event and the action to be performed.
  • a list of Hypervisors may be included with the action being to migrate any virtual machines hosted therein.
  • the VAPMS 208 may query each Hypervisor directly for a list of currently running virtual machines.
  • the VAPMS 208 may integrate with a third-party virtualization management system, such as the third-party virtualization management system 214, and may be configured to request a list of currently running virtual machines from the third-party virtualization management system 214.
  • the VAPMS 208 may iterate through the list of currently running virtual machines and define the order in which the virtual machines should be shut down. For example, a virtual machine running an instance of the VAPMS 208, or other critical asset (e.g., third-party virtualization management system, storage array, etc) will be shutdown and migrated to a different Hypervisor last.
  • critical asset e.g., third-party virtualization management system, storage array, etc
  • the VAPMS 208 may initiate shutdown requests via a network, such as the network 202 in FIG. 2 , in the defined order.
  • the VAPMS 208 communicates with a Hypervisor directly to gracefully shutdown the virtual machines in the defined order.
  • the VAPMS 208 communicates with a third-party virtualization management system, such as the third-party virtualization management system 214, to shutdown the virtual machines in the defined order.
  • the VAPMS 208 may continue to shutdown virtual machines until each Hypervisor affected by the power event received in the step 974 has been shutdown. In one example, the VAPMS 208 may then communicate a shutdown command to each affected Hypervisor. In another example, the VAPMS 208 may communicate a shutdown command through a third-party virtualization management system to shutdown each affected Hypervisor.
  • the VAPMS 208 may communicate startup requests to migrate each virtual machine shutdown in the act 996 to another Hypervisor.
  • a suitable Hypervisor must be determined prior to migrating the virtual machines.
  • the communicated request may include a location of the virtual image stored on a storage array, such as the storage array 206 of FIG. 2 .
  • the shutdown requests of the act 998 and the startup requests of act 1000 may be performed sequentially.
  • the VAPMS may include a timer which determines the shutdown/startup request has exceeded a predefined period of time. As discussed above with reference to the FIG. 11 , the predefined amount of time may be determined based on settings defined within the VAPMS 208. These settings may be adjusted via the user interfaces of FIGs. 4-8 . When the predetermined amount of time has elapsed the VAPMS 208 may continue to the next virtual machine, Hypervisor, etc. In one example, the VAPMS 208 may attempt a number of retries until the predetermined amount of time has elapsed.
  • Processes 950, 970, and 990 each depict one particular sequence of acts in a particular example.
  • the acts included in these processes may be performed by, or using, one or more computer systems specially configured as discussed herein. Some acts are optional and, as such, may be omitted in accord with one or more examples. Additionally, the order of the acts can be altered, or other acts can be added, without departing from the scope of the examples described herein.
  • the acts are performed on particular, specially configured machines, namely a VAPMS configured according to the examples disclosed herein.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Power Sources (AREA)
  • Debugging And Monitoring (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Supply And Distribution Of Alternating Current (AREA)
  • Remote Monitoring And Control Of Power-Distribution Networks (AREA)

Claims (15)

  1. Un système de gestion de puissance configuré pour protéger une pluralité de biens de technologie de l'information (TI), le système comprenant :
    une mémoire (912) ;
    au moins un processeur (910) couplé à la mémoire ; et
    un composant de migration exécutable par l'au moins un processeur et configuré pour :
    identifier la pluralité de biens de TI, la pluralité de biens de TI incluant au moins un serveur hôte ;
    générer une association entre au moins un bien de TI et au moins une unité d'alimentation en puissance (210) ;
    recevoir un événement relatif à la puissance en provenance de l'au moins une unité d'alimentation en puissance (210) ;
    corréler l'événement relatif à la puissance avec au moins un bien de TI concerné sur la base de l'association générée ;
    déterminer une séquence d'actions, la séquence d'actions étant configurée pour faire migrer au moins une machine virtuelle de l'au moins un bien de TI concerné à un bien de TI non concerné, et la séquence d'actions incluant des actions identifiant la pluralité de machines virtuelles dans une liste ordonnée ; et
    exécuter la séquence d'actions ;
    caractérisé par le fait que la génération de l'association est effectuée automatiquement sur la base d'un mécanisme d'adresses IP,
    l'adresse IP attribuée à chaque unité d'alimentation en puissance ayant un dernier octet particulier réglé à une constante prédéfinie, toutes les adresses IP avec un masque de sous-réseau concordant et un dernier octet supérieur à ladite constante étant présumées être des biens de TI connectés à l'unité d'alimentation en puissance respective.
  2. Le système de la revendication 1, dans lequel l'au moins une unité d'alimentation en puissance est une alimentation en puissance sans interruption (ASI), dans lequel l'ASI inclut un groupe de prises primaire et un groupe de prises secondaire, et dans lequel l'au moins un serveur hôte est couplé à au moins un groupe parmi le groupe de prises primaire et le groupe de prises secondaire.
  3. Le système de la revendication 1, comprenant en outre une interface utilisateur configurée pour afficher un mappage de l'au moins une unité d'alimentation en puissance et de l'au moins un bien de TI associé à l'au moins une unité d'alimentation en puissance.
  4. Le système de la revendication 3, dans lequel l'association générée peut être modifiée par un utilisateur en glissant-déposant une représentation d'un bien de TI non associé de la pluralité de biens de TI sur le mappage.
  5. Le système de la revendication 4, dans lequel l'au moins un bien de TI concerné est identifié comme étant concerné par l'événement relatif à la puissance sur la base de l'association générée entre l'au moins une unité d'alimentation en puissance et un ou plusieurs biens de TI mappés associés à l'au moins une unité d'alimentation en puissance.
  6. Le système de la revendication 5, dans lequel le composant de migration est en outre configuré pour communiquer directement avec l'au moins un bien de TI concerné afin de déterminer une pluralité de machines virtuelles hébergées par l'au moins un bien de TI concerné.
  7. Le système de la revendication 6, dans lequel le composant de migration est en outre configuré pour communiquer indirectement avec l'au moins un bien de TI concerné afin de déterminer une pluralité de machines virtuelles hébergées par l'au moins un bien de TI concerné.
  8. Le système de la revendication 6, dans lequel le composant de migration est en outre configuré pour déterminer si au moins une des machines virtuelles est un bien de TI critique, dans lequel la liste ordonnée est ordonnée sur la base d'un ordre suivant lequel des biens de TI apparaissent dans le mappage, et dans lequel la séquence d'actions exécutée inclut une action pour faire migrer au moins un bien de TI critique en dernier.
  9. Un procédé de gestion d'une pluralité de biens de technologie de l'information (TI) à l'aide d'un système informatique incluant une mémoire (912), un dispositif d'affichage, et au moins un processeur (910) couplé à la mémoire et au dispositif d'affichage, le procédé comprenant :
    l'identification de la pluralité de biens de TI, la pluralité de biens de TI incluant au moins un serveur hôte ;
    la génération d'une association entre au moins un bien de TI et au moins une unité d'alimentation en puissance (210) ;
    la réception d'informations relatives à un événement relatif à la puissance en provenance de l'au moins une unité d'alimentation en puissance (210) ;
    la corrélation de l'événement relatif à la puissance avec au moins un bien de TI concerné sur la base de l'association générée ;
    la détermination d'une séquence d'actions, la séquence d'actions étant configurée pour faire migrer au moins une machine virtuelle d'au moins un bien de TI concerné, et la séquence d'actions incluant des actions identifiant la pluralité de machines virtuelles dans une liste ordonnée ; et
    l'exécution de la séquence d'actions ;
    caractérisé par le fait que la génération de l'association est effectuée automatiquement sur la base d'un mécanisme d'adresses IP,
    l'adresse IP attribuée à chaque unité d'alimentation en puissance ayant un dernier octet particulier réglé à une constante prédéfinie, toutes les adresses IP avec un masque de sous-réseau concordant et un dernier octet supérieur à ladite constante étant présumées être des biens de TI connectés à l'unité d'alimentation en puissance respective.
  10. Le procédé de la revendication 9, dans lequel l'acte de génération de l'association entre au moins un bien de TI et au moins une unité d'alimentation en puissance inclut la représentation visuelle sur le dispositif d'affichage d'un mappage de l'au moins une unité d'alimentation en puissance et de l'au moins un bien de TI associé à l'au moins une unité d'alimentation en puissance.
  11. Le procédé de la revendication 10, dans lequel la liste ordonnée inclut une pluralité de biens de TI et une pluralité de machines virtuelles associées à chaque bien de TI de la pluralité de biens de TI, et le procédé comprenant en outre l'identification d'au moins un bien de TI de la pluralité de biens de TI comme étant un bien de TI critique.
  12. Le procédé de la revendication 11, dans lequel l'acte d'exécution de la séquence d'actions inclut la communication directe avec chaque bien de TI sur la base de la liste ordonnée.
  13. Le procédé de la revendication 12, le procédé comprenant en outre la transmission d'une commande d'arrêt pour chaque machine virtuelle de la pluralité de machines virtuelles sur la base de la liste ordonnée et la détermination d'un ou de plusieurs biens de TI pour migration de la pluralité de machines virtuelles, dans lequel l'acte de transmission de la commande d'arrêt inclut en outre l'arrêt du bien de TI critique en dernier, et l'acte de détermination d'un ou de plusieurs biens de TI pour migration de la pluralité de machines virtuelles inclut la détermination quant à savoir si les un ou plusieurs biens de TI sont couplés à une unité d'alimentation en puissance ne subissant pas de panne de courant.
  14. Un support non transitoire lisible par ordinateur stockant des instructions pour la gestion d'une pluralité de biens de TI, les instructions étant exécutables par au moins un processeur d'un système informatique, les instructions étant configurées pour ordonner au système informatique :
    d'identifier la pluralité de biens de TI, la pluralité de biens de TI incluant au moins un serveur hôte ;
    de générer une association entre au moins un bien de TI et au moins une unité d'alimentation en puissance ;
    de recevoir un événement relatif à la puissance en provenance de l'au moins une unité d'alimentation en puissance ;
    de corréler l'événement relatif à la puissance avec au moins un bien de TI concerné sur la base de l'association générée ;
    de déterminer une séquence d'actions, la séquence d'actions étant configurée pour faire migrer au moins une machine virtuelle de l'au moins un bien de TI à un bien de TI non concerné, et la séquence d'actions incluant des actions identifiant la pluralité de machines virtuelles dans une liste ordonnée ; et
    d'exécuter la séquence d'actions ;
    caractérisé par le fait que la génération de l'association est effectuée automatiquement sur la base d'un mécanisme d'adresses IP,
    l'adresse IP attribuée à chaque unité d'alimentation en puissance ayant un dernier octet particulier réglé à une constante prédéfinie, toutes les adresses IP avec un masque de sous-réseau concordant et un dernier octet supérieur à ladite constante étant présumées être des biens de TI connectés à l'alimentation en puissance respective.
  15. Le support non transitoire lisible par ordinateur de la revendication 14, dans lequel les instructions sont en outre configurées pour générer un mappage de l'au moins une unité d'alimentation en puissance et de l'au moins un bien de TI associé à l'au moins une unité d'alimentation en puissance sur une interface utilisateur.
EP14192169.2A 2013-11-07 2014-11-06 Systèmes et procédés pour protéger des biens virtualisés Active EP2871553B1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
IN5013CH2013 IN2013CH05013A (fr) 2013-11-07 2013-11-07

Publications (2)

Publication Number Publication Date
EP2871553A1 EP2871553A1 (fr) 2015-05-13
EP2871553B1 true EP2871553B1 (fr) 2020-04-15

Family

ID=52003555

Family Applications (1)

Application Number Title Priority Date Filing Date
EP14192169.2A Active EP2871553B1 (fr) 2013-11-07 2014-11-06 Systèmes et procédés pour protéger des biens virtualisés

Country Status (5)

Country Link
US (1) US9791908B2 (fr)
EP (1) EP2871553B1 (fr)
CN (1) CN104635901B (fr)
AU (1) AU2014256371A1 (fr)
IN (1) IN2013CH05013A (fr)

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9778718B2 (en) 2009-02-13 2017-10-03 Schneider Electric It Corporation Power supply and data center control
AU2011384034A1 (en) 2011-12-22 2014-07-10 Schneider Electric It Corporation Systems and methods for reducing energy storage requirements in a data center
EP3063658A4 (fr) * 2013-10-30 2017-05-24 Hewlett-Packard Enterprise Development LP Base de données de gestion de système de topologies réalisées
US10284427B2 (en) 2013-10-30 2019-05-07 Hewlett Packard Enterprise Development Lp Managing the lifecycle of a cloud service modeled as topology decorated by a number of policies
WO2015065374A1 (fr) 2013-10-30 2015-05-07 Hewlett-Packard Development Company, L.P. Gestion du cycle de vie d'un service de nuage modélisé en tant que topologie
US10212051B2 (en) 2013-10-30 2019-02-19 Hewlett Packard Enterprise Development Lp Stitching an application model to an infrastructure template
US11245588B2 (en) 2013-10-30 2022-02-08 Micro Focus Llc Modifying realized topologies
WO2015065356A1 (fr) 2013-10-30 2015-05-07 Hewlett-Packard Development Company, L.P. Correction de topologie
EP3063660A4 (fr) 2013-10-30 2017-06-14 Hewlett-Packard Enterprise Development LP Exécution d'une topologie
US10230568B2 (en) 2013-10-30 2019-03-12 Hewlett Packard Enterprise Development Lp Monitoring a cloud service modeled as a topology
WO2015065392A1 (fr) 2013-10-30 2015-05-07 Hewlett-Packard Development Company, L.P. Facilitation de calcul autonome dans un service en nuage
IN2013CH05013A (fr) 2013-11-07 2015-05-08 Schneider Electric It Corp
GB201513039D0 (en) * 2015-07-23 2015-09-09 Eaton Ind France Sas Shutting down of a virtual system
EP3362897A1 (fr) 2015-10-13 2018-08-22 Schneider Electric Industries SAS Gestion centralisée d'un système d'automatisation défini par logiciel
CN105468407B (zh) * 2015-11-19 2018-11-06 国云科技股份有限公司 一种自动发现并按序运行启动类的方法
US20170308278A1 (en) 2016-04-21 2017-10-26 Schneider Electric Software, Llc Automated graphical user interface configuration
US10545777B2 (en) * 2016-11-08 2020-01-28 International Business Machines Corporation Generating a virtual machines relocation protocol
US10725810B2 (en) * 2017-06-01 2020-07-28 Vmware, Inc. Migrating virtualized computing instances that implement a logical multi-node application
US10496429B2 (en) * 2017-07-20 2019-12-03 Vmware, Inc. Managing virtual computing instances and physical servers
US10860078B2 (en) * 2018-10-25 2020-12-08 Dell Products, L.P. Managing power request during cluster operations
US11003478B2 (en) * 2018-12-11 2021-05-11 Schneider Electric It Corporation Systems and methods for protecting virtual machines running on software-defined storage
US11294772B2 (en) 2019-09-04 2022-04-05 EMC IP Holding Company LLC System and method to achieve virtual machine backup load balancing using machine learning
US10853190B1 (en) * 2019-09-04 2020-12-01 EMC IP Holding Company LLC System and method for a machine learning based smart restore mechanism

Family Cites Families (78)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4868832A (en) 1986-04-30 1989-09-19 Marrington S Paul Computer power system
US5845090A (en) 1994-02-14 1998-12-01 Platinium Technology, Inc. System for software distribution in a digital computer network
US5978594A (en) 1994-09-30 1999-11-02 Bmc Software, Inc. System for managing computer resources across a distributed computing environment by first reading discovery information about how to determine system resources presence
US6317775B1 (en) 1995-11-03 2001-11-13 Cisco Technology, Inc. System for distributing load over multiple servers at an internet site
US7197553B2 (en) 2002-04-19 2007-03-27 Nortel Networks Limited Network system having a virtual-service-module
US7072960B2 (en) 2002-06-10 2006-07-04 Hewlett-Packard Development Company, L.P. Generating automated mappings of service demands to server capacities in a distributed computer system
US7152100B2 (en) 2002-07-09 2006-12-19 Adtran, Inc. System and method for provisioning network access devices
US8131802B2 (en) 2007-10-05 2012-03-06 Sony Computer Entertainment America Llc Systems and methods for seamless host migration
JP3776880B2 (ja) 2002-12-10 2006-05-17 株式会社日立製作所 無停電電源装置
US7546475B2 (en) 2003-05-13 2009-06-09 Hewlett-Packard Development Company, L.P. Power-aware adaptation in a data center
US7458028B2 (en) * 2003-07-18 2008-11-25 Avinash Chidambaram Graphical interface for configuring a power supply controller
US7146353B2 (en) 2003-07-22 2006-12-05 Hewlett-Packard Development Company, L.P. Resource allocation for multiple applications
US7127625B2 (en) 2003-09-04 2006-10-24 Hewlett-Packard Development Company, L.P. Application management based on power consumption
EP1678617A4 (fr) 2003-10-08 2008-03-26 Unisys Corp Para-virtualisation d un systeme informatique utilisant un h yperviseur implemente dans une partition du systeme hote
US7451336B2 (en) 2003-10-16 2008-11-11 International Business Machines Corporation Automated load shedding of powered devices in a computer complex in the event of utility interruption
US7131012B2 (en) * 2003-10-16 2006-10-31 International Business Machines Corporation Method and apparatus for correlating an out-of-range condition to a particular power connection
JP4351517B2 (ja) 2003-11-14 2009-10-28 株式会社日立製作所 データセンタの装置管理方法、装置管理サーバ、データセンタの装置管理システム並びにプログラム
US7502333B2 (en) * 2004-03-23 2009-03-10 Hewlett-Packard Development Company, L.P. Pre-configured topology with connection management
US7197433B2 (en) 2004-04-09 2007-03-27 Hewlett-Packard Development Company, L.P. Workload placement among data centers based on thermal efficiency
US8156490B2 (en) 2004-05-08 2012-04-10 International Business Machines Corporation Dynamic migration of virtual machine computer programs upon satisfaction of conditions
US7514815B2 (en) 2004-09-28 2009-04-07 American Power Conversion Corporation System and method for allocating power to loads
US20060112286A1 (en) 2004-11-23 2006-05-25 Whalley Ian N Method for dynamically reprovisioning applications and other server resources in a computer center in response to power and heat dissipation requirements
US7389403B1 (en) 2005-08-10 2008-06-17 Sun Microsystems, Inc. Adaptive computing ensemble microprocessor architecture
US8429630B2 (en) 2005-09-15 2013-04-23 Ca, Inc. Globally distributed utility computing cloud
US20070150584A1 (en) 2005-12-28 2007-06-28 Deepa Srinivasan Apparatus, system, and method for determining server utilization in hosted computing infrastructure
US20070234077A1 (en) 2006-03-31 2007-10-04 Rothman Michael A Reducing power consumption by load imbalancing
JP4800837B2 (ja) 2006-05-22 2011-10-26 株式会社日立製作所 計算機システム、その消費電力低減方法、及びそのプログラム
CN101098075A (zh) 2006-06-30 2008-01-02 佛山市顺德区顺达电脑厂有限公司 保护系统以及方法
US8725886B1 (en) 2006-10-20 2014-05-13 Desktone, Inc. Provisioned virtual computing
US8296760B2 (en) 2006-10-27 2012-10-23 Hewlett-Packard Development Company, L.P. Migrating a virtual machine from a first physical machine in response to receiving a command to lower a power mode of the first physical machine
US7856549B2 (en) 2007-01-24 2010-12-21 Hewlett-Packard Development Company, L.P. Regulating power consumption
US8205205B2 (en) 2007-03-16 2012-06-19 Sap Ag Multi-objective allocation of computational jobs in client-server or hosting environments
JP5596343B2 (ja) 2007-04-13 2014-09-24 日本電気株式会社 仮想計算機システムおよびその最適化方法
US7886165B2 (en) 2007-05-24 2011-02-08 Broadcom Corporation Power management for Power-over-Ethernet-capable switch
US8468230B2 (en) 2007-10-18 2013-06-18 Fujitsu Limited Method, apparatus and recording medium for migrating a virtual machine
JP4902501B2 (ja) 2007-11-12 2012-03-21 株式会社日立製作所 電力制御方法、計算機システム、及びプログラム
US8447993B2 (en) 2008-01-23 2013-05-21 Palo Alto Research Center Incorporated Integrated energy savings and business operations in data centers
US20090189774A1 (en) * 2008-01-28 2009-07-30 Dell Products L.P. Power Topology Determination
US8996890B2 (en) 2008-02-07 2015-03-31 Dell Products L.P. Method for power conservation in virtualized environments
US7877323B2 (en) * 2008-03-28 2011-01-25 American Express Travel Related Services Company, Inc. Consumer behaviors at lender level
JP4924514B2 (ja) 2008-03-31 2012-04-25 富士通株式会社 仮想マシン管理プログラム、管理サーバ装置及び仮想マシン管理方法
WO2009126154A1 (fr) 2008-04-10 2009-10-15 Hewlett-Packard Development Company, L.P. Migration de machine virtuelle selon des données environnementales
JP5157717B2 (ja) 2008-07-28 2013-03-06 富士通株式会社 仮想バッテリを備えた仮想マシンシステムおよび仮想バッテリを備えた仮想マシンシステム用プログラム
NL2003139A1 (nl) 2008-07-31 2010-02-02 Asml Holding Nv Cooling of actuator coils.
GB0818174D0 (en) 2008-10-03 2008-11-12 Leaneco Aps Emergency power supply apparatus
US8467985B2 (en) 2008-10-31 2013-06-18 Schneider Electric Usa Inc. Automated synchronization of data between electrical grids
US8200370B2 (en) 2008-12-04 2012-06-12 American Power Conversion Corporation Energy reduction
US20100145884A1 (en) 2008-12-04 2010-06-10 American Power Conversion Corporation Energy savings aggregation
US8046468B2 (en) 2009-01-26 2011-10-25 Vmware, Inc. Process demand prediction for distributed power and resource management
US9519517B2 (en) 2009-02-13 2016-12-13 Schneider Electtic It Corporation Data center control
US9778718B2 (en) 2009-02-13 2017-10-03 Schneider Electric It Corporation Power supply and data center control
US8674823B1 (en) 2009-05-12 2014-03-18 Plug ID, LLC. Power management system
EP2457153B1 (fr) * 2009-07-20 2016-11-02 Schneider Electric IT Corporation Methode et systeme d' analyse de puissance
US8723362B2 (en) 2009-07-24 2014-05-13 Facebook, Inc. Direct tie-in of a backup power source to motherboards in a server system
US8458499B2 (en) 2009-08-07 2013-06-04 International Business Machines Corporation Method for reducing power state in a computer system out-of-band when a request for reducing the power state is not immediately serviceable in band according to a priority of the request
US8769535B2 (en) 2009-09-24 2014-07-01 Avaya Inc. Providing virtual machine high-availability and fault tolerance via solid-state backup drives
JP5378946B2 (ja) 2009-10-26 2013-12-25 株式会社日立製作所 サーバ管理装置およびサーバ管理方法
US20110202728A1 (en) 2010-02-17 2011-08-18 Lsi Corporation Methods and apparatus for managing cache persistence in a storage system using multiple virtual machines
US8495193B2 (en) * 2010-02-23 2013-07-23 Microsoft Corporation Centralized management tool for remote presentation session server farms
US8627123B2 (en) 2010-03-25 2014-01-07 Microsoft Corporation Managing power provisioning in distributed computing
US9207993B2 (en) 2010-05-13 2015-12-08 Microsoft Technology Licensing, Llc Dynamic application placement based on cost and availability of energy in datacenters
US9317314B2 (en) * 2010-06-29 2016-04-19 Microsoft Techology Licensing, Llc Techniques for migrating a virtual machine using shared storage
JP5206750B2 (ja) 2010-08-09 2013-06-12 サンケン電気株式会社 電源装置およびプログラム
US8952566B2 (en) 2010-10-26 2015-02-10 Microsoft Technology Licensing, Llc Chassis slots accepting battery modules and other module types
EP2458501A1 (fr) 2010-11-30 2012-05-30 France Telecom Procédé de fonctionnement d'un dispositif de communication et dispositif de communication apparenté
US20120137289A1 (en) 2010-11-30 2012-05-31 International Business Machines Corporation Protecting high priority workloads in a virtualized datacenter
US8612801B2 (en) 2011-01-25 2013-12-17 Dell Products, Lp System and method for extending system uptime while running on backup power
EP2690553A4 (fr) * 2011-03-22 2016-06-15 Fujitsu Ltd Appareil de gestion de migration, procédé de gestion de migration et programme de gestion de migration
US9608440B2 (en) * 2011-11-08 2017-03-28 Eaton Corporation Methods and apparatus for determining power distribution system topology using disturbance detection
AU2011384034A1 (en) 2011-12-22 2014-07-10 Schneider Electric It Corporation Systems and methods for reducing energy storage requirements in a data center
US9329888B2 (en) 2013-01-28 2016-05-03 International Business Machines Corporation Computing optimized virtual machine allocations using equivalence combinations
US9164810B2 (en) 2013-04-16 2015-10-20 Dell Products L.P. Allocating an application computation between a first and a second information handling system based on user's context, device battery state, and computational capabilities
US9665387B2 (en) 2013-05-08 2017-05-30 Amazon Technologies, Inc. User-influenced placement of virtual machine instances
US20140337833A1 (en) 2013-05-08 2014-11-13 Amazon Technologies, Inc. User-Influenced Placement of Virtual Machine Instances
US20140337834A1 (en) 2013-05-08 2014-11-13 Amazon Technologies, Inc. User-Influenced Placement of Virtual Machine Instances
US11245588B2 (en) * 2013-10-30 2022-02-08 Micro Focus Llc Modifying realized topologies
IN2013CH05013A (fr) 2013-11-07 2015-05-08 Schneider Electric It Corp
WO2015106039A1 (fr) 2014-01-09 2015-07-16 Nautilus Data Technologies, Inc. Système et des procédé permettant une gestion intelligente de l'énergie des centres de données et une reprise après sinistre du marché de l'énergie

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
EP2871553A1 (fr) 2015-05-13
CN104635901B (zh) 2019-11-08
US9791908B2 (en) 2017-10-17
AU2014256371A1 (en) 2015-05-21
IN2013CH05013A (fr) 2015-05-08
CN104635901A (zh) 2015-05-20
US20150128052A1 (en) 2015-05-07

Similar Documents

Publication Publication Date Title
EP2871553B1 (fr) Systèmes et procédés pour protéger des biens virtualisés
US10044550B2 (en) Secure cloud management agent
US9253157B2 (en) Dynamically defining rules for network access
JP6466003B2 (ja) Ｖｎｆフェイルオーバの方法及び装置
CN115442433A (zh) 用于经由云交换促进容器间通信的方法和系统
CN107534570A (zh) 虚拟化网络功能监控
US9792150B1 (en) Detecting site change for migrated virtual machines
US11805004B2 (en) Techniques and interfaces for troubleshooting datacenter networks
CN106462206B (zh) 用于监控具有不同冗余度等级的ups组的配置的系统和方法
US10120779B1 (en) Debugging of hosted computer programs
US10860375B1 (en) Singleton coordination in an actor-based system
US10425475B2 (en) Distributed data management
US20200120169A1 (en) Scalable message passing architecture a cloud environment
CN104158707A (zh) 一种检测并处理集群脑裂的方法和装置
US11397632B2 (en) Safely recovering workloads within a finite timeframe from unhealthy cluster nodes
CN114189425A (zh) 基于意图的分布式警报服务
US10440145B1 (en) SDK for reducing unnecessary polling of a network service
US20130185763A1 (en) Distributed processing system, distributed processing method and computer-readable recording medium
US9348672B1 (en) Singleton coordination in an actor-based system
US20210357239A1 (en) Methods and systems for managing computing virtual machine instances
US20210334001A1 (en) Host-aware discovery and backup configuration for storage assets within a data protection environment
US10860078B2 (en) Managing power request during cluster operations
US10860347B1 (en) Virtual machine with multiple content processes
US10305733B1 (en) Defining software infrastructure using a physical model
CN110278243B (zh) 负载均衡应用管理方法、装置、计算机设备及存储介质

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20141106

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

R17P Request for examination filed (corrected)

Effective date: 20151113

RBV Designated contracting states (corrected)

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20180706

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602014063731

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: G06F0001320000

Ipc: G06F0001320300

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: G06F 1/30 20060101ALI20191014BHEP

Ipc: G06F 1/3203 20190101AFI20191014BHEP

Ipc: G06F 9/455 20180101ALI20191014BHEP

INTG Intention to grant announced

Effective date: 20191112

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

RIN1 Information on inventor provided before grant (corrected)

Inventor name: HANNON, SARAH JANE

Inventor name: GREHAN, DAVID

Inventor name: PORTER, PAULA

Inventor name: KAMMINGA, FREDERIK

Inventor name: KHATOR, AMIT KUMAR

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602014063731

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1258072

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200515

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20200415

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200815

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200715

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200716

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200817

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1258072

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200415

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200715

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602014063731

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

26N No opposition filed

Effective date: 20210118

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201106

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20201130

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201130

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201130

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201106

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201130

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20231121

Year of fee payment: 10

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20231123

Year of fee payment: 10

Ref country code: DE

Payment date: 20231127

Year of fee payment: 10