US10572283B2 - Implementing requests on a model of a system prior to implementing on the system - Google Patents
Implementing requests on a model of a system prior to implementing on the system Download PDFInfo
- Publication number
- US10572283B2 US10572283B2 US15/815,216 US201715815216A US10572283B2 US 10572283 B2 US10572283 B2 US 10572283B2 US 201715815216 A US201715815216 A US 201715815216A US 10572283 B2 US10572283 B2 US 10572283B2
- Authority
- US
- United States
- Prior art keywords
- logged
- users
- component
- action
- computer
- 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.)
- Expired - Fee Related, expires
Links
- 230000009471 action Effects 0.000 claims abstract description 65
- 238000012545 processing Methods 0.000 claims description 54
- 238000000034 method Methods 0.000 claims description 24
- 238000004590 computer program Methods 0.000 claims description 18
- 238000004891 communication Methods 0.000 claims description 2
- 230000006870 function Effects 0.000 description 17
- 238000010586 diagram Methods 0.000 description 10
- 238000005192 partition Methods 0.000 description 10
- 230000008859 change Effects 0.000 description 6
- 238000007726 management method Methods 0.000 description 6
- 230000008901 benefit Effects 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 5
- 230000005540 biological transmission Effects 0.000 description 4
- 238000003491 array Methods 0.000 description 3
- 230000008520 organization Effects 0.000 description 3
- 230000002093 peripheral effect Effects 0.000 description 3
- 230000004044 response Effects 0.000 description 3
- 238000012360 testing method Methods 0.000 description 3
- 238000013519 translation Methods 0.000 description 3
- 230000003466 anti-cipated effect Effects 0.000 description 2
- 239000013256 coordination polymer Substances 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000006855 networking Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000001902 propagating effect Effects 0.000 description 2
- 230000002441 reversible effect Effects 0.000 description 2
- 238000012384 transportation and delivery Methods 0.000 description 2
- RYGMFSIKBFXOCR-UHFFFAOYSA-N Copper Chemical compound [Cu] RYGMFSIKBFXOCR-UHFFFAOYSA-N 0.000 description 1
- 230000003139 buffering effect Effects 0.000 description 1
- 230000009172 bursting Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 229910052802 copper Inorganic materials 0.000 description 1
- 239000010949 copper Substances 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000012517 data analytics Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000013439 planning Methods 0.000 description 1
- 229920001690 polydopamine Polymers 0.000 description 1
- 238000011176 pooling Methods 0.000 description 1
- 238000013468 resource allocation Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 210000003813 thumb Anatomy 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45545—Guest-host, i.e. hypervisor is an application program itself, e.g. VirtualBox
-
- 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/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- 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/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5061—Partitioning or combining of resources
- G06F9/5077—Logical partitioning of resources; Management or configuration of virtualized resources
-
- 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/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
Definitions
- One or more aspects relate, in general, to processing within a computing environment, and in particular, to facilitating such processing.
- a computing environment includes one or more computing systems, and a computing system typically includes hardware and computer programs that are managed by an operating system.
- the operating system performs a number of tasks including recognizing input, sending output, keeping track of files, controlling peripheral devices and providing security, as examples.
- Operating systems generally lack the ability to recognize and protect themselves from dangerous requests. Commands are accepted and loads are processed. It is typically the responsibility of a system administrator to take action to protect the system. For example, if operating system code is modified by, for instance, introducing an exit or other code or restarting a new version of the code, the system administrator is responsible for taking action if the change negatively affects the system.
- the computer program product includes a computer readable storage medium readable by a processing circuit and storing instructions for performing a method.
- the method includes, for instance, obtaining from one system, a request of an action to be implemented on another system.
- the other system is modeled based on the one system, and the action is to be implemented on the other system prior to being implemented on the one system.
- the action is performed by the other system, and an indication is sent to the one system specifying whether the one system is to implement the action.
- FIG. 1 depicts one example of a computing environment to incorporate and use one or more aspects of the present invention
- FIG. 2 depicts details of a first level system, in accordance with an aspect of the present invention
- FIG. 3 depicts one example of initialization logic used in accordance with an aspect of the present invention
- FIG. 4 depicts one example of processing performed by a watcher component, in accordance with an aspect of the present invention
- FIG. 5 depicts one example of processing performed by an anticipator component, in accordance with an aspect of the present invention
- FIG. 6 depicts one example of an implementer component processing requests received from various components, in accordance with an aspect of the present invention
- FIGS. 7A-7B depict one embodiment of facilitating processing within a computing environment, in accordance with an aspect of the present invention.
- FIG. 8A depicts another example of a computing environment to incorporate and use one or more aspects of the present invention.
- FIG. 8B depicts further details of the memory of FIG. 8A ;
- FIG. 9 depicts one embodiment of a cloud computing environment
- FIG. 10 depicts one example of abstraction model layers.
- a capability is provided to create a self-aware system, such as a self-aware operating system.
- aspects of one system are modeled on another system, referred to herein as a model.
- the model may change as the aspects of the one system change.
- actions to be implemented on the one system are initially implemented on the model. Then, if those actions are acceptable, they are implemented on the one system.
- One or more aspects of the capability enable the one system to become self-aware by dynamically determining actions to be tested on the model.
- the one system is a first level system
- the other system is a second level system.
- the first level system is a hypervisor (e.g., an operating system), which hosts guests, such as the second level system.
- the guests may be, e.g., guests that run operating systems or guests that run work other than operating systems.
- a guest of the first level system is referred to as a first level guest. If a guest of the first level system is running an operating system, then it may be referred to as a second level system.
- a second level system may also have guests which are referred to as second level guests, and so forth.
- the one system and the other system are separate systems coupled to one another (i.e., not host/guest).
- the one system may be in one logical partition and the other system, the model, may be in another logical partition communicatively coupled to the one logical partition.
- Other variations are also possible.
- the one system i.e., the system being modeled
- the one system is protected by not implementing unacceptable requests on the one system. This facilitates processing, and improves performance.
- FIG. 1 One embodiment of a computing environment to incorporate and use one or more aspects of the present invention is described with reference to FIG. 1 .
- the computing environment is based on the z/Architecture, offered by International Business Machines Corporation, Armonk, N.Y.
- One embodiment of the z/Architecture is described in “z/Architecture Principles of Operation,” IBM Publication No. SA22-7832-10, Mar. 2015, which is hereby incorporated herein by reference in its entirety.
- Z/ARCHITECTURE is a registered trademark of International Business Machines Corporation, Armonk, N.Y., USA.
- the computing environment is based on the Power Architecture, offered by International Business Machines Corporation, Armonk, N.Y.
- Power Architecture offered by International Business Machines Corporation, Armonk, N.Y.
- One embodiment of the Power Architecture is described in “Power ISATM Version 2.07B,” International Business Machines Corporation, Apr. 9, 2015, which is hereby incorporated herein by reference in its entirety.
- POWER ARCHITECTURE is a registered trademark of International Business Machines Corporation, Armonk, N.Y., USA.
- the computing environment may also be based on other architectures, including, but not limited to, the Intel x86 architectures. Other examples also exist.
- a computing environment 100 includes, for instance, a computer system 102 , such as a central processor complex, that may include, but is not limited to, one or more processors or processing units 104 (e.g., central processing units (CPUs)), a memory 106 (a.k.a., system memory, main memory, main storage, central storage or storage, as examples), and one or more input/output (I/O) interfaces 108 , coupled to one another via one or more buses and/or other connections 110 .
- processors or processing units 104 e.g., central processing units (CPUs)
- memory 106 a.k.a., system memory, main memory, main storage, central storage or storage, as examples
- I/O input/output
- Bus 110 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures.
- bus architectures include the Industry Standard Architecture (ISA), the Micro Channel Architecture (MCA), the Enhanced ISA (EISA), the Video Electronics Standards Association (VESA) local bus, and the Peripheral Component Interconnect (PCI).
- Memory 106 may include, for instance, one or more logical partitions 120 a . . . 120 n, one or more computer readable program instructions 122 , and processor firmware 124 .
- Computer readable program instructions 122 may be configured to carry out functions of embodiments of aspects of the invention.
- firmware includes, e.g., the microcode of the processor. It includes, for instance, the hardware-level instructions and/or data structures used in implementation of higher level machine code. In one embodiment, it includes, for instance, proprietary code that is typically delivered as microcode that includes trusted software or microcode specific to the underlying hardware and controls operating system access to the system hardware.
- At least one logical partition such as logical partition 120 a, includes a hypervisor 126 , such as z/VM offered by International Business Machines Corporation, Armonk, N.Y.
- hypervisor 126 is referred to as a host.
- hypervisor 126 is referred to as a first level system.
- Computer system 102 may also communicate via, e.g., I/O interfaces 108 with one or more external devices 140 , one or more network interfaces 142 , and/or one or more data storage devices 144 .
- Example external devices include a user terminal, a tape drive, a pointing device, a display, etc.
- Network interface 142 enables computer system 102 to communicate with one or more networks, such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet), providing communication with other computing devices or systems.
- LAN local area network
- WAN wide area network
- public network e.g., the Internet
- Data storage device 144 may store one or more programs 146 , one or more computer readable program instructions 148 , and/or data, etc.
- the computer readable program instructions may be configured to carry out functions of embodiments of aspects of the invention.
- I/O interfaces 108 include an I/O subsystem that directs the flow of information between input/output control units (not shown), devices 140 , and memory 106 .
- the control units are coupled between memory 106 and devices 140 .
- Computer system 102 may include and/or be coupled to removable/non-removable, volatile/non-volatile computer system storage media.
- it may include and/or be coupled to a non-removable, non-volatile magnetic media (typically called a “hard drive”), a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”), and/or an optical disk drive for reading from or writing to a removable, non-volatile optical disk, such as a CD-ROM, DVD-ROM or other optical media.
- a non-removable, non-volatile magnetic media typically called a “hard drive”
- a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”).
- an optical disk drive for reading from or writing to a removable, non-volatile optical disk, such as a CD-ROM, DVD-ROM or other optical media.
- Computer system 102 may be operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with computer system 102 include, but are not limited to, personal computer (PC) systems, server computer systems, thin clients, thick clients, handheld or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputer systems, mainframe computer systems, and distributed cloud computing environments that include any of the above systems or devices, and the like.
- PC personal computer
- server computer systems thin clients, thick clients, handheld or laptop devices
- multiprocessor systems microprocessor-based systems
- set top boxes set top boxes
- programmable consumer electronics network PCs
- minicomputer systems minicomputer systems
- mainframe computer systems mainframe computer systems
- distributed cloud computing environments that include any of the above systems or devices, and the like.
- a logical partition such as logical partition 120 a, includes a first level system, which is a hypervisor or host operating system, such as z/VM.
- This first level system can initiate guests, which run on the first level system. When these guests are running operating systems they may be referred to as second level systems. Further details regarding first and second level systems are described with reference to FIG. 2 .
- a first level system 200 runs in a logical partition, such as logical partition 120 a.
- This first level system is a hypervisor, e.g., z/VM, which may host one or more guests 202 , which may be other operating systems, such as z/VM, Linux, z/OS, etc.
- the first level system in accordance with an aspect of the present invention, starts a second level system 204 (e.g., z/VM), which is to model selected aspects of first level system 200 .
- the first level system logs on a first level guest which will run the second level system.
- the guest is not running an operating system, but instead, is running a user environment, such as CMS (Conversational Monitoring System).
- CMS Conversational Monitoring System
- a program is run that performs selected set-up and then starts the operating system, e.g., z/VM.
- the guest and the second level system which it starts have read access to the system configuration file and files containing the operating system code (e.g., on z/VM, CPLOAD and any CP exits) of the first level system.
- the first level guest is not given, in this example, any other special privileges.
- Second level system 204 may log on other guests 206 , which may run an operating system. For instance, on second level system 204 , a guest, which is automatically logged on, e.g., such as OPERATOR on z/VM, runs a program which causes other guests to be started (to be logged on). As an example, on z/VM, the guest may issue the XAUTOLOG command to direct the operating system to log on another specified guest. Further, in one example, second level system 204 logs on another guest 208 , referred to as a request receiver/implementer (RRI). Guest 208 runs a user environment, such as CMS, instead of a guest operating system. Guest 208 runs a program that sits and waits to receive commands from the first level system.
- a guest which is automatically logged on, e.g., such as OPERATOR on z/VM, runs a program which causes other guests to be started (to be logged on).
- the guest may issue the XAUTOLOG command to direct the operating
- first level watcher 220 of the first level system receives commands from a first level watcher 220 of the first level system and/or a first level anticipator 222 of the first level system, as described in further detail below.
- First level watcher and first level anticipator are, for instance, guests of the first level system.
- the watcher and anticipator are components of the one system being modeled.
- First level watcher 220 and second level system 204 are coupled to storage 230 .
- Storage 230 is used for a number of tasks, including, but not limited to, paging, and communicating between the second level system and the first level system, as examples.
- first level watcher 220 and first level anticipator 222 are described with reference to FIG. 3 .
- first level system e.g., z/VM
- certain guests also referred to herein as users
- Those guests can autolog other users, such as, for instance, first level anticipator 222 , STEP 300 .
- Guest autologging other guests is accomplished, for example, using, for instance, the XAUTOLOG command if on z/VM, as described herein.
- first level watcher 220 is autologged and builds a configuration file that includes an indication of the configuration of the first level system (e.g., IPL (initial program load) parameters, pages allocated, etc.), STEP 302 . Additionally, the first level watcher identifies the operating system load file (e.g., CPLOAD) of the first level system, STEP 304 , and the first level watcher begins update mode, STEP 306 .
- IPL initial program load
- second level system 204 begins, STEP 308 , including request receiver/implementer 208 , STEP 310 .
- the guest running second level system 204 has, e.g., read-only access to various disks that include files used to bring up and run the second level system. These disks may be defined as virtual disks in storage, which the host supplies from memory, instead of permanent storage, in one example.
- a guest of the first level system in starting the second level system, is caused to be logged on.
- the guest of the first level system starts a bring-up program.
- the bring-up program causes the first level watcher to be logged on if it is not already on.
- the first level watcher performs initial queries and writes results to a data file accessible by the original guest.
- the data in the file as obtained from the initial queries, guide the defining of an initial configuration for the second level operating system. The selection of the initial queries depends on the chosen detail and type of modeling.
- the first level watcher then enters a loop, periodically issuing, e.g., QUERY NAMES to determine the users logged on to the first level system (and/or possibly other queries), and writing results to another data file accessible by the second level system.
- the bring-up program running in the first level guest builds the system configuration file which the second level system is to employ by using a prototype, copying entries from the system configuration file of the first level system other than those overridden by entries in the prototype, and adjusting the configuration file to current conditions, as reflected by the queries of the watcher.
- the CPOWNed list is made to match the current situation, which may be different from what is specified in the first level system configuration file. Such differences may occur, for example, due to dynamic changes made since IPL of the first level system.
- the bring-up program also builds a user directory using its prototype base and adding as user entries any logged-on first level guests identified by the first level watcher which are not already in the prototype directory.
- the bring-up program uses other information from the first level watcher (e.g., QUERY ALLOC PAGE, QUERY ALLOC SPOOL) and pre-defined attributes to define, format and initialize the virtual disks to be used. Having created configuration files and positioned files as needed, the bring-up program ends by IPLing the second level operating system.
- first level watcher e.g., QUERY ALLOC PAGE, QUERY ALLOC SPOOL
- first level watcher 220 is a guest of first level system 200 , and in one example, runs a user environment, such as CMS. It performs system queries and supplies the data to the second level system. It is given privileges to the extent needed for the queries. As one particular example, it periodically runs queries of the first level system to determine various aspects of the first level system, including, for instance, a current configuration of the first level system—e.g., the users (also known as guests) logged on to the first level system, and/or other aspects of the first level system, such as the processing load (e.g., on z/VM, the output of the INDICATE command), as examples. Further details of the first level watcher are described with reference to FIG. 4 .
- first level watcher 220 queries the users (i.e., the guests running on the system, such as, for instance, virtual machines) of the first level system to determine which users are logged on, STEP 400 . Based on the responses to the queries, it creates a user list (e.g., a list of guests) that is provided to request receiver/implementer 208 , STEP 402 . First level watcher 220 awaits acknowledgment of receipt of the user list from request receiver/implementer 208 , STEP 404 . Based on receiving the acknowledgment, it performs another query of the users, STEP 406 .
- users i.e., the guests running on the system, such as, for instance, virtual machines
- first level watcher 220 determines whether there is a change in the user configuration, INQUIRY 408 . If there is a change in the user configuration, then processing continues with STEP 402 , in which an updated user list is provided to request receiver/implementer 208 . However, if the user configuration has not changed, then the first level watcher waits a specified time (e.g., an amount of time (e.g., 2 minutes), a number of cycles, etc.), STEP 410 . Based on that specified time expiring, processing continues with INQUIRY 408 .
- a specified time e.g., an amount of time (e.g., 2 minutes), a number of cycles, etc.
- the watcher may perform more or different queries, according to the first level system aspects which are being modeled.
- first level anticipator 222 supplies data and/or requests to the second level system, but this data and/or requests are in anticipation of being provided or implemented on the first level system. No special privileges are provided to the first level anticipator, in one example.
- First level anticipator 222 is used to indicate to the second level system (the model) that a particular action is to be performed by the second level system.
- the second level system performs the action, and if there does not appear to be a problem with the action, then that action may be implemented on the first level system.
- the action is implemented on the second level system first, and if it appears to be an acceptable action, then that action is implemented on the first level system. Further details regarding processing associated with the first level anticipator are described with reference to FIG. 5 .
- first level anticipator 222 waits to obtain from the first level system (e.g., z/VM) a command request specifying an action to be performed by the second level system to test the action before being released onto the first level system, STEP 500 .
- Example actions include a re-IPL with a CP load, create a virtual switch, perform a query, delete, copy, etc.
- first level anticipator sends the request to request receiver/implementer 208 , STEP 502 .
- Anticipator 222 waits a specified amount of time depending on the action to be performed, STEP 504 .
- a SHUTDOWN REIPL request asks for the second level system to restart, which would be expected to take on the order of 30 seconds.
- the anticipator might wait, e.g., 3 minutes or some other predefined amount of time or processing cycles, etc. after this request.
- the anticipator then sends a query to request receiver/implementer 208 requesting status of the action; i.e., requesting status as to whether the request is acceptable or is causing any problems with the second level system, STEP 506 .
- the action has negatively affected the second level system; or for another request, the question may be whether the system is running too slowly; etc. If the response indicates that the action is not acceptable, then anticipator 222 sends a back-out request to request receiver/implementer 208 to back-out the action, STEP 514 , and processing continues to STEP 500 . Otherwise, the action is invoked on the first level system, STEP 516 , and processing continues to STEP 500 .
- the request receiver/implementer receives, e.g., commands and data from a next lower level (e.g., level 1) watcher and anticipator, and uses the information to change the operating system, or its environment, or its users (guests). It is to have corresponding privileges to perform the actions. It can also provide information regarding the second level system, including status and performance information, to, e.g., the anticipator.
- a next lower level e.g., level 1
- level 1 e.g., level 1
- guests users
- It can also provide information regarding the second level system, including status and performance information, to, e.g., the anticipator.
- a request e.g., a list of users currently logged on first level
- the request receiver/implementer uses e.g., the X
- request receiver/implementer waits for a request, STEP 616 , and processing continues to INQUIRY 600 .
- request from the watcher relates to the users being logged on
- other requests from the watcher may be processed by the request receiver/implementer.
- the second level system runs an operating system that models the first level system, at least in certain aspects.
- the second level system has prototype versions of the configuration file and a user directory of the first level system.
- the bring-up program which is setting up the second level system, uses information provided by, e.g., the first level watcher, to fill out the files.
- the watcher watches the first level system and attempts to have the second level system match the first level system, in terms of configuration and/or user information, as examples.
- the anticipator anticipates selected changes to the first level system, and attempts to have the second level system match the anticipated changes.
- the request receiver/implementer serves as a conduit for the requests of the watcher and anticipator, and makes feedback available.
- the model is to be implemented as a fraction (e.g., on a z/VM first level system with 300 G of memory storage, the model is implemented as, e.g., a 5G second level system; many other examples are possible) of the size of the modeled system.
- the model may include a model of itself, and so forth. If the model includes a model of itself, this third-level system would then be sized at a fraction of a fraction, and similarly for any higher level models. Since there is a minimum viable size for an operating system, the number of such levels is finite, and one consideration is to provide for automatic pass of tests when there is no model available to perform the test.
- Scaling of the model becomes a consideration as one tries to account for more effects.
- a list of reversible commands and their inverse may be generated.
- the second level system is tested by invoking the command, invoking its inverse, then invoking again. This would have the potential not only to discover problems with the command, but also problems undoing it in case that was desired.
- actions e.g., changes
- the actions are first performed on a second level system, and if acceptable, then the actions are implemented on the first level system.
- the second level system is a guest of the first level system; however, in another example, the second level system may not be a guest of the first level system.
- One or more aspects of the present invention are inextricably tied to computer technology and facilitate processing within a computer, improving performance thereof. Further details of one embodiment of facilitating processing within a computing environment, as it relates to one or more aspects of the present invention, are described with reference to FIGS. 7A-7B .
- a request is obtained from one system, and the request specifies an action to be implemented on another system ( 700 ).
- the other system is modeled based on the one system ( 702 ), and the action is to be implemented on the other system prior to being implemented on the one system ( 704 ).
- the action is performed by the other system ( 706 ), and an indication is sent to the one system specifying whether the one system is to implement the action ( 708 ).
- the one system is a first level host system of the other system
- the other system is a guest of the first level host system ( 710 ).
- the one system includes an anticipator component ( 712 ), and the obtaining includes determining, by the other system, that the request is being received from the anticipator component ( 714 ). Based on determining that the request is being received from the anticipator component, the action is performed ( 716 ).
- the anticipator component is a guest of the first level host system ( 718 ).
- the sending includes sending a result of the action to the one system ( 720 ).
- the other system is configured based on the one system and includes a processing load based on the one system ( 722 ).
- the one system includes a watcher component ( 724 ), and a configuration update for the other system is obtained by the other system from the watcher component ( 726 ).
- the configuration update includes, for instance, one or more new users logged on to the one system ( 728 ).
- the other system includes an implementer component ( 730 ), and a determination is made by the implementer component that the configuration update has been obtained from the watcher component ( 732 ). Based on determining that the configuration update has been obtained, one or more actions are performed by the implementer component ( 734 ). The one or more actions include autologging one or more users specified in the configuration update ( 736 ).
- a computing environment 20 includes, for instance, a native central processing unit (CPU) 22 , a memory 24 , and one or more input/output devices and/or interfaces 26 coupled to one another via, for example, one or more buses 28 and/or other connections.
- computing environment 20 may include a PowerPC processor or a pSeries server offered by International Business Machines Corporation, Armonk, N.Y.; and/or other machines based on architectures offered by International Business Machines Corporation, Intel, or other companies.
- Native central processing unit 22 includes one or more native registers 30 , such as one or more general purpose registers and/or one or more special purpose registers used during processing within the environment. These registers include information that represents the state of the environment at any particular point in time.
- native central processing unit 22 executes instructions and code that are stored in memory 24 .
- the central processing unit executes emulator code 32 stored in memory 24 .
- This code enables the computing environment configured in one architecture to emulate another architecture.
- emulator code 32 allows machines based on architectures other than the z/Architecture, such as PowerPC processors, pSeries servers, or other servers or processors, to emulate the z/Architecture and to execute software and instructions developed based on the z/Architecture.
- Guest instructions 40 stored in memory 24 comprise software instructions (e.g., correlating to machine instructions) that were developed to be executed in an architecture other than that of native CPU 22 .
- guest instructions 40 may have been designed to execute on a z/Architecture processor, but instead, are being emulated on native CPU 22 , which may be, for example, an Intel processor.
- emulator code 32 includes an instruction fetching routine 42 to obtain one or more guest instructions 40 from memory 24 , and to optionally provide local buffering for the instructions obtained. It also includes an instruction translation routine 44 to determine the type of guest instruction that has been obtained and to translate the guest instruction into one or more corresponding native instructions 46 . This translation includes, for instance, identifying the function to be performed by the guest instruction and choosing the native instruction(s) to perform that function.
- emulator code 32 includes an emulation control routine 48 to cause the native instructions to be executed.
- Emulation control routine 48 may cause native CPU 22 to execute a routine of native instructions that emulate one or more previously obtained guest instructions and, at the conclusion of such execution, return control to the instruction fetch routine to emulate the obtaining of the next guest instruction or a group of guest instructions.
- Execution of native instructions 46 may include loading data into a register from memory 24 ; storing data back to memory from a register; or performing some type of arithmetic or logic operation, as determined by the translation routine.
- Each routine is, for instance, implemented in software, which is stored in memory and executed by native central processing unit 22 .
- one or more of the routines or operations are implemented in firmware, hardware, software or some combination thereof.
- the registers of the emulated processor may be emulated using registers 30 of the native CPU or by using locations in memory 24 .
- guest instructions 40 , native instructions 46 and emulator code 32 may reside in the same memory or may be disbursed among different memory devices.
- One or more aspects may relate to cloud computing.
- Cloud computing is a model of service delivery for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g. networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services) that can be rapidly provisioned and released with minimal management effort or interaction with a provider of the service.
- This cloud model may include at least five characteristics, at least three service models, and at least four deployment models.
- On-demand self-service a cloud consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with the service's provider.
- Resource pooling the provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to demand. There is a sense of location independence in that the consumer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter).
- Rapid elasticity capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out and rapidly released to quickly scale in. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time.
- Measured service cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported providing transparency for both the provider and consumer of the utilized service.
- level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts).
- SaaS Software as a Service: the capability provided to the consumer is to use the provider's applications running on a cloud infrastructure.
- the applications are accessible from various client devices through a thin client interface such as a web browser (e.g., web-based email).
- a web browser e.g., web-based email.
- the consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.
- PaaS Platform as a Service
- the consumer does not manage or control the underlying cloud infrastructure including networks, servers, operating systems, or storage, but has control over the deployed applications and possibly application hosting environment configurations.
- IaaS Infrastructure as a Service
- the consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, deployed applications, and possibly limited control of select networking components (e.g., host firewalls).
- Private cloud the cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on-premises or off-premises.
- Public cloud the cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services.
- Hybrid cloud the cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for loadbalancing between clouds).
- a cloud computing environment is service oriented with a focus on statelessness, low coupling, modularity, and semantic interoperability.
- An infrastructure comprising a network of interconnected nodes.
- cloud computing environment 50 comprises one or more cloud computing nodes 10 with which local computing devices used by cloud consumers, such as, for example, personal digital assistant (PDA) or cellular telephone 54 A, desktop computer 54 B, laptop computer 54 C, and/or automobile computer system 54 N may communicate.
- Nodes 10 may communicate with one another. They may be grouped (not shown) physically or virtually, in one or more networks, such as Private, Community, Public, or Hybrid clouds as described hereinabove, or a combination thereof.
- This allows cloud computing environment 50 to offer infrastructure, platforms and/or software as services for which a cloud consumer does not need to maintain resources on a local computing device.
- computing devices 54 A-N shown in FIG. 8 are intended to be illustrative only and that computing nodes 10 and cloud computing environment 50 can communicate with any type of computerized device over any type of network and/or network addressable connection (e.g., using a web browser).
- FIG. 10 a set of functional abstraction layers provided by cloud computing environment 50 ( FIG. 9 ) is shown. It should be understood in advance that the components, layers, and functions shown in FIG. 10 are intended to be illustrative only and embodiments of the invention are not limited thereto. As depicted, the following layers and corresponding functions are provided:
- Hardware and software layer 60 includes hardware and software components.
- hardware components include mainframes 61 ; RISC (Reduced Instruction Set Computer) architecture based servers 62 ; servers 63 ; blade servers 64 ; storage devices 65 ; and networks and networking components 66 .
- software components include network application server software 67 and database software 68 .
- Virtualization layer 70 provides an abstraction layer from which the following examples of virtual entities may be provided: virtual servers 71 ; virtual storage 72 ; virtual networks 73 , including virtual private networks; virtual applications and operating systems 74 ; virtual clients 75 ; and self-aware operating system processing 76 .
- management layer 80 may provide the functions described below.
- Resource provisioning 81 provides dynamic procurement of computing resources and other resources that are utilized to perform tasks within the cloud computing environment.
- Metering and Pricing 82 provide cost tracking as resources are utilized within the cloud computing environment, and billing or invoicing for consumption of these resources. In one example, these resources may comprise application software licenses.
- Security provides identity verification for cloud consumers and tasks, as well as protection for data and other resources.
- User portal 83 provides access to the cloud computing environment for consumers and system administrators.
- Service level management 84 provides cloud computing resource allocation and management such that required service levels are met.
- Service Level Agreement (SLA) planning and fulfillment 85 provide pre-arrangement for, and procurement of, cloud computing resources for which a future requirement is anticipated in accordance with an SLA.
- SLA Service Level Agreement
- Workloads layer 90 provides examples of functionality for which the cloud computing environment may be utilized. Examples of workloads and functions which may be provided from this layer include: mapping and navigation 91 ; software development and lifecycle management 92 ; virtual classroom education delivery 93 ; data analytics processing 94 ; and transaction processing 95 .
- the present invention may be a system, a method, and/or a computer program product at any possible technical detail level of integration
- the computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention
- the computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device.
- the computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing.
- a non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing.
- RAM random access memory
- ROM read-only memory
- EPROM or Flash memory erasable programmable read-only memory
- SRAM static random access memory
- CD-ROM compact disc read-only memory
- DVD digital versatile disk
- memory stick a floppy disk
- a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon
- a computer readable storage medium is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
- Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network.
- the network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers.
- a network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
- Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++, or the like, and procedural programming languages, such as the “C” programming language or similar programming languages.
- the computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
- the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
- electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.
- These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
- These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
- the computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
- each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s).
- the functions noted in the block may occur out of the order noted in the figures.
- two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
- one or more aspects may be provided, offered, deployed, managed, serviced, etc. by a service provider who offers management of customer environments.
- the service provider can create, maintain, support, etc. computer code and/or a computer infrastructure that performs one or more aspects for one or more customers.
- the service provider may receive payment from the customer under a subscription and/or fee agreement, as examples. Additionally or alternatively, the service provider may receive payment from the sale of advertising content to one or more third parties.
- an application may be deployed for performing one or more embodiments.
- the deploying of an application comprises providing computer infrastructure operable to perform one or more embodiments.
- a computing infrastructure may be deployed comprising integrating computer readable code into a computing system, in which the code in combination with the computing system is capable of performing one or more embodiments.
- a process for integrating computing infrastructure comprising integrating computer readable code into a computer system
- the computer system comprises a computer readable medium, in which the computer medium comprises one or more embodiments.
- the code in combination with the computer system is capable of performing one or more embodiments.
- a data processing system suitable for storing and/or executing program code includes at least two processors coupled directly or indirectly to memory elements through a system bus.
- the memory elements include, for instance, local memory employed during actual execution of the program code, bulk storage, and cache memory which provide temporary storage of at least some program code in order to reduce the number of times code must be retrieved from bulk storage during execution.
- I/O devices can be coupled to the system either directly or through intervening I/O controllers.
- Network adapters may also be coupled to the system to enable the data processing system to become coupled to other data processing systems or remote printers or storage devices through intervening private or public networks. Modems, cable modems, and Ethernet cards are just a few of the available types of network adapters.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
- Stored Programmes (AREA)
Abstract
Description
Claims (20)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15/815,216 US10572283B2 (en) | 2017-11-16 | 2017-11-16 | Implementing requests on a model of a system prior to implementing on the system |
US16/743,169 US11163595B2 (en) | 2017-11-16 | 2020-01-15 | Implementing requests on a model of a system prior to implementing on the system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15/815,216 US10572283B2 (en) | 2017-11-16 | 2017-11-16 | Implementing requests on a model of a system prior to implementing on the system |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/743,169 Continuation US11163595B2 (en) | 2017-11-16 | 2020-01-15 | Implementing requests on a model of a system prior to implementing on the system |
Publications (2)
Publication Number | Publication Date |
---|---|
US20190146819A1 US20190146819A1 (en) | 2019-05-16 |
US10572283B2 true US10572283B2 (en) | 2020-02-25 |
Family
ID=66432049
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/815,216 Expired - Fee Related US10572283B2 (en) | 2017-11-16 | 2017-11-16 | Implementing requests on a model of a system prior to implementing on the system |
US16/743,169 Active 2037-12-03 US11163595B2 (en) | 2017-11-16 | 2020-01-15 | Implementing requests on a model of a system prior to implementing on the system |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/743,169 Active 2037-12-03 US11163595B2 (en) | 2017-11-16 | 2020-01-15 | Implementing requests on a model of a system prior to implementing on the system |
Country Status (1)
Country | Link |
---|---|
US (2) | US10572283B2 (en) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10572283B2 (en) | 2017-11-16 | 2020-02-25 | International Business Machines Corporation | Implementing requests on a model of a system prior to implementing on the system |
Citations (42)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050260973A1 (en) * | 2004-05-24 | 2005-11-24 | Van De Groenendaal Joannes G | Wireless manager and method for managing wireless devices |
US20060021029A1 (en) * | 2004-06-29 | 2006-01-26 | Brickell Ernie F | Method of improving computer security through sandboxing |
US20070143591A1 (en) * | 2007-02-23 | 2007-06-21 | Richard Dellacona | Method for non-destructive restoration of a corrupted operating system |
US20070294707A1 (en) * | 2006-06-15 | 2007-12-20 | Microsoft Corporation | Enhancing or replacing host operating system functionality by leveraging guest operating system functionality |
US20080235764A1 (en) * | 2007-03-22 | 2008-09-25 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Resource authorizations dependent on emulation environment isolation policies |
US20080235000A1 (en) * | 2007-03-22 | 2008-09-25 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Implementing security control practice omission decisions from service emulation indications |
US20080235002A1 (en) * | 2007-03-22 | 2008-09-25 | Searete Llc | Implementing performance-dependent transfer or execution decisions from service emulation indications |
US20080235756A1 (en) * | 2007-03-22 | 2008-09-25 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Resource authorizations dependent on emulation environment isolation policies |
US20080235001A1 (en) * | 2007-03-22 | 2008-09-25 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Implementing emulation decisions in response to software evaluations or the like |
US20080234999A1 (en) * | 2007-03-22 | 2008-09-25 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Implementing performance-dependent transfer or execution decisions from service emulation indications |
US20080234998A1 (en) * | 2007-03-22 | 2008-09-25 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Coordinating instances of a thread or other service in emulation |
US20080235711A1 (en) * | 2007-03-22 | 2008-09-25 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Coordinating instances of a thread or other service in emulation |
US20090313358A1 (en) * | 2008-06-12 | 2009-12-17 | Shepherd's Pie Productions, Inc. | System and Method for Managing Network-Based Services |
US20100083248A1 (en) * | 2008-09-30 | 2010-04-01 | Wood Timothy W | Optimizing a prediction of resource usage of multiple applications in a virtual environment |
US20110023029A1 (en) * | 2009-07-22 | 2011-01-27 | Wael Diab | Method and system for abstracting virtual machines in a network |
US20110209218A1 (en) * | 2010-02-19 | 2011-08-25 | International Business Machines Corporation | Environmental imaging |
US8099596B1 (en) * | 2011-06-30 | 2012-01-17 | Kaspersky Lab Zao | System and method for malware protection using virtualization |
US20120016778A1 (en) * | 2009-07-28 | 2012-01-19 | Mathias Salle | Controlling cloud services |
US20120060167A1 (en) * | 2010-09-08 | 2012-03-08 | Salsburg Michael A | Method and system of simulating a data center |
US20120311106A1 (en) * | 2011-05-31 | 2012-12-06 | Morgan Christopher Edwin | Systems and methods for self-moving operating system installation in cloud-based network |
US20130019242A1 (en) * | 2011-07-13 | 2013-01-17 | Institute For Information Industry | Cloud-Based Test System and Method and Computer-Readable Storage Medium with Computer Program to Execute the Method |
US20130167157A1 (en) * | 2009-08-25 | 2013-06-27 | Adobe Systems Incorporated | Embedded Application Communication |
US20130326508A1 (en) * | 2012-05-30 | 2013-12-05 | Red Hat Israel, Ltd. | Display power management for virtual machines |
US20140108774A1 (en) * | 2012-10-16 | 2014-04-17 | International Business Machines Corporation | Dynamically recommending changes to an association between an operating system image and an update group |
US20140195853A1 (en) * | 2013-01-09 | 2014-07-10 | Microsoft Corporation | Cloud management using a component health model |
US20140273965A1 (en) * | 2009-01-28 | 2014-09-18 | Headwater Partners I Llc | Automated credential porting for mobile devices |
US20140317392A1 (en) | 2013-04-22 | 2014-10-23 | Lenovo (Singapore) Pte, Ltd. | Operating system management of second operating system |
US20150052092A1 (en) | 2013-08-16 | 2015-02-19 | Transoft (Shanghai), Inc. | Methods and systems of brain-like computing virtualization |
US20150089479A1 (en) * | 2013-09-23 | 2015-03-26 | Institute For Information Industry | Method for pre-testing software compatibility and system thereof |
US9052935B1 (en) * | 2012-11-27 | 2015-06-09 | Symantec Corporation | Systems and methods for managing affinity rules in virtual-machine environments |
US9075410B2 (en) * | 2011-02-15 | 2015-07-07 | International Business Machines Corporation | Abnormality detection for isolating a control system |
US20150339475A1 (en) * | 2014-05-23 | 2015-11-26 | Vmware, Inc. | Application whitelisting using user identification |
US20160026488A1 (en) | 2011-05-16 | 2016-01-28 | Microsoft Technology Licensing, Llc | Instruction set emulation for guest operating systems |
US20160125059A1 (en) * | 2014-11-04 | 2016-05-05 | Rubrik, Inc. | Hybrid cloud data management system |
US20160132420A1 (en) * | 2014-11-10 | 2016-05-12 | Institute For Information Industry | Backup method, pre-testing method for environment updating and system thereof |
KR20160071682A (en) | 2014-12-12 | 2016-06-22 | 국민대학교산학협력단 | Method of analyzing virtual operating system performance, virtual operating system performance analysis apparatus performing the same and storage medium storing the same |
US20160292420A1 (en) * | 2015-03-31 | 2016-10-06 | Juniper Networks, Inc. | Configuring a sandbox environment for malware testing |
US20160364261A1 (en) | 2015-06-15 | 2016-12-15 | Electronics And Telecommunications Research Institute | Apparatus and method for providing adaptive virtual desktop operating system service |
US9585085B1 (en) * | 2016-06-06 | 2017-02-28 | LotusFlare, Inc. | Managing network data consumption of applications on cellular computer networks on one or more client computers |
US20170080346A1 (en) * | 2014-05-01 | 2017-03-23 | Mohamad Abbas | Methods and systems relating to personalized evolving avatars |
US20170168918A1 (en) * | 2015-12-09 | 2017-06-15 | Sap Se | Sandboxing for Custom Logic |
US20180006872A1 (en) * | 2016-06-30 | 2018-01-04 | Microsoft Technology Licensing, Llc. | Data Plane API in a Distributed Computing Network |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8464250B1 (en) * | 2004-09-23 | 2013-06-11 | Transcontinental Events, Llc | System and method for on-demand cloning of virtual machines |
US9609044B2 (en) * | 2010-11-05 | 2017-03-28 | The Trustees Of Columbia University In The City Of New York | Methods, systems, and media for stored content distribution and access |
US10572283B2 (en) | 2017-11-16 | 2020-02-25 | International Business Machines Corporation | Implementing requests on a model of a system prior to implementing on the system |
-
2017
- 2017-11-16 US US15/815,216 patent/US10572283B2/en not_active Expired - Fee Related
-
2020
- 2020-01-15 US US16/743,169 patent/US11163595B2/en active Active
Patent Citations (42)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050260973A1 (en) * | 2004-05-24 | 2005-11-24 | Van De Groenendaal Joannes G | Wireless manager and method for managing wireless devices |
US20060021029A1 (en) * | 2004-06-29 | 2006-01-26 | Brickell Ernie F | Method of improving computer security through sandboxing |
US20070294707A1 (en) * | 2006-06-15 | 2007-12-20 | Microsoft Corporation | Enhancing or replacing host operating system functionality by leveraging guest operating system functionality |
US20070143591A1 (en) * | 2007-02-23 | 2007-06-21 | Richard Dellacona | Method for non-destructive restoration of a corrupted operating system |
US20080234998A1 (en) * | 2007-03-22 | 2008-09-25 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Coordinating instances of a thread or other service in emulation |
US20080235711A1 (en) * | 2007-03-22 | 2008-09-25 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Coordinating instances of a thread or other service in emulation |
US20080235002A1 (en) * | 2007-03-22 | 2008-09-25 | Searete Llc | Implementing performance-dependent transfer or execution decisions from service emulation indications |
US20080235756A1 (en) * | 2007-03-22 | 2008-09-25 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Resource authorizations dependent on emulation environment isolation policies |
US20080235001A1 (en) * | 2007-03-22 | 2008-09-25 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Implementing emulation decisions in response to software evaluations or the like |
US20080234999A1 (en) * | 2007-03-22 | 2008-09-25 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Implementing performance-dependent transfer or execution decisions from service emulation indications |
US20080235764A1 (en) * | 2007-03-22 | 2008-09-25 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Resource authorizations dependent on emulation environment isolation policies |
US20080235000A1 (en) * | 2007-03-22 | 2008-09-25 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Implementing security control practice omission decisions from service emulation indications |
US20090313358A1 (en) * | 2008-06-12 | 2009-12-17 | Shepherd's Pie Productions, Inc. | System and Method for Managing Network-Based Services |
US20100083248A1 (en) * | 2008-09-30 | 2010-04-01 | Wood Timothy W | Optimizing a prediction of resource usage of multiple applications in a virtual environment |
US20140273965A1 (en) * | 2009-01-28 | 2014-09-18 | Headwater Partners I Llc | Automated credential porting for mobile devices |
US20110023029A1 (en) * | 2009-07-22 | 2011-01-27 | Wael Diab | Method and system for abstracting virtual machines in a network |
US20120016778A1 (en) * | 2009-07-28 | 2012-01-19 | Mathias Salle | Controlling cloud services |
US20130167157A1 (en) * | 2009-08-25 | 2013-06-27 | Adobe Systems Incorporated | Embedded Application Communication |
US20110209218A1 (en) * | 2010-02-19 | 2011-08-25 | International Business Machines Corporation | Environmental imaging |
US20120060167A1 (en) * | 2010-09-08 | 2012-03-08 | Salsburg Michael A | Method and system of simulating a data center |
US9075410B2 (en) * | 2011-02-15 | 2015-07-07 | International Business Machines Corporation | Abnormality detection for isolating a control system |
US20160026488A1 (en) | 2011-05-16 | 2016-01-28 | Microsoft Technology Licensing, Llc | Instruction set emulation for guest operating systems |
US20120311106A1 (en) * | 2011-05-31 | 2012-12-06 | Morgan Christopher Edwin | Systems and methods for self-moving operating system installation in cloud-based network |
US8099596B1 (en) * | 2011-06-30 | 2012-01-17 | Kaspersky Lab Zao | System and method for malware protection using virtualization |
US20130019242A1 (en) * | 2011-07-13 | 2013-01-17 | Institute For Information Industry | Cloud-Based Test System and Method and Computer-Readable Storage Medium with Computer Program to Execute the Method |
US20130326508A1 (en) * | 2012-05-30 | 2013-12-05 | Red Hat Israel, Ltd. | Display power management for virtual machines |
US20140108774A1 (en) * | 2012-10-16 | 2014-04-17 | International Business Machines Corporation | Dynamically recommending changes to an association between an operating system image and an update group |
US9052935B1 (en) * | 2012-11-27 | 2015-06-09 | Symantec Corporation | Systems and methods for managing affinity rules in virtual-machine environments |
US20140195853A1 (en) * | 2013-01-09 | 2014-07-10 | Microsoft Corporation | Cloud management using a component health model |
US20140317392A1 (en) | 2013-04-22 | 2014-10-23 | Lenovo (Singapore) Pte, Ltd. | Operating system management of second operating system |
US20150052092A1 (en) | 2013-08-16 | 2015-02-19 | Transoft (Shanghai), Inc. | Methods and systems of brain-like computing virtualization |
US20150089479A1 (en) * | 2013-09-23 | 2015-03-26 | Institute For Information Industry | Method for pre-testing software compatibility and system thereof |
US20170080346A1 (en) * | 2014-05-01 | 2017-03-23 | Mohamad Abbas | Methods and systems relating to personalized evolving avatars |
US20150339475A1 (en) * | 2014-05-23 | 2015-11-26 | Vmware, Inc. | Application whitelisting using user identification |
US20160125059A1 (en) * | 2014-11-04 | 2016-05-05 | Rubrik, Inc. | Hybrid cloud data management system |
US20160132420A1 (en) * | 2014-11-10 | 2016-05-12 | Institute For Information Industry | Backup method, pre-testing method for environment updating and system thereof |
KR20160071682A (en) | 2014-12-12 | 2016-06-22 | 국민대학교산학협력단 | Method of analyzing virtual operating system performance, virtual operating system performance analysis apparatus performing the same and storage medium storing the same |
US20160292420A1 (en) * | 2015-03-31 | 2016-10-06 | Juniper Networks, Inc. | Configuring a sandbox environment for malware testing |
US20160364261A1 (en) | 2015-06-15 | 2016-12-15 | Electronics And Telecommunications Research Institute | Apparatus and method for providing adaptive virtual desktop operating system service |
US20170168918A1 (en) * | 2015-12-09 | 2017-06-15 | Sap Se | Sandboxing for Custom Logic |
US9585085B1 (en) * | 2016-06-06 | 2017-02-28 | LotusFlare, Inc. | Managing network data consumption of applications on cellular computer networks on one or more client computers |
US20180006872A1 (en) * | 2016-06-30 | 2018-01-04 | Microsoft Technology Licensing, Llc. | Data Plane API in a Distributed Computing Network |
Non-Patent Citations (5)
Title |
---|
IBM, "Power ISA-V2.07B," Apr. 9, 2015, pp. 1-1527. |
IBM, "z/Architecture-Principles of Operation," IBM Publication No. SA22-7832-10, Eleventh Edition, Mar. 2015, pp. 1-1732. |
IBM, "Power ISA—V2.07B," Apr. 9, 2015, pp. 1-1527. |
IBM, "z/Architecture—Principles of Operation," IBM Publication No. SA22-7832-10, Eleventh Edition, Mar. 2015, pp. 1-1732. |
Mel, Peter and Tim Grance, "The NIST Definition of Cloud Computing," National Institute of Standards and Technology, Information Technology Laboratory, Special Publication 800-145, Sep. 2011, pp. 1-7. |
Also Published As
Publication number | Publication date |
---|---|
US20190146819A1 (en) | 2019-05-16 |
US20200150988A1 (en) | 2020-05-14 |
US11163595B2 (en) | 2021-11-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11061709B2 (en) | Storage management for deployment of virtual machine | |
US10831583B2 (en) | Reporting errors to a data storage device | |
US10977167B2 (en) | Application monitoring with a decoupled monitoring tool | |
US10394971B2 (en) | Hybrid simulation of a computing solution in a cloud computing environment with a simplified computing solution and a simulation model | |
US10223218B2 (en) | Disaster recovery of managed systems | |
US20180239611A1 (en) | Running a kernel-dependent application in a container | |
AU2020426828B2 (en) | Reserving one or more security modules for secure guest | |
US9800518B2 (en) | Managing application, middleware, and virtual mechanism density in a cloud | |
AU2021278382B2 (en) | Proactively performing tasks based on estimating hardware reconfiguration times | |
US11163595B2 (en) | Implementing requests on a model of a system prior to implementing on the system | |
US10565056B2 (en) | Parallel data collection and recovery for failing virtual computer processing system | |
US11086807B2 (en) | Allocating address space | |
US20160191320A1 (en) | Relocating an embedded cloud for fast configuration of a cloud computing environment | |
JP7479378B2 (en) | Suppression of instruction interruption for overflow exception | |
US11068565B2 (en) | System obtains software features information of another system | |
US10831571B2 (en) | Communicating between systems using a coupling facility list structure |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:GREER, TIMOTHY D.;REEL/FRAME:044155/0018 Effective date: 20171116 Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW YORK Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:GREER, TIMOTHY D.;REEL/FRAME:044155/0018 Effective date: 20171116 |
|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20240225 |