US20080028199A1 - Method for scheduling launch a computer system based upon a time of timed power-on partition of logical partitions - Google Patents
Method for scheduling launch a computer system based upon a time of timed power-on partition of logical partitions Download PDFInfo
- Publication number
- US20080028199A1 US20080028199A1 US11/869,855 US86985507A US2008028199A1 US 20080028199 A1 US20080028199 A1 US 20080028199A1 US 86985507 A US86985507 A US 86985507A US 2008028199 A1 US2008028199 A1 US 2008028199A1
- Authority
- US
- United States
- Prior art keywords
- partition
- launch
- time
- logical
- time period
- 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.)
- Abandoned
Links
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/4401—Bootstrapping
- G06F9/4406—Loading of operating system
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Power Sources (AREA)
- Computer And Data Communications (AREA)
Abstract
Methods, systems, and media for timed power-on in a logically partitioned environment are disclosed. Embodiments may disclose determining a time period based upon a time to launch a partition and a time of day associated with the next partition to launch. After determining the time period, a timer is set to boot the system based upon the time period. More specifically, embodiments allow the timed power-on (TPO) and time of day (TOD) of logical partitions to be modified by clients independently of other partitions by determining the system TPO based upon TPOs and TODs of logical partitions as well as the TOD of the system. Some embodiments include initiating a transaction like an interrupt in response to a change in a TPO or TOD of logical partition or the system. Several of such embodiments incorporate adjusting or re-calculating the system TPO in response to the transaction.
Description
- This is a continuation of co-pending U.S. patent application Ser. No. 10/418,348 filed Apr. 17, 2003, which is herein incorporated by reference.
- 1. Field of the Invention
- The present invention generally relates to the field of logically partitioned computer systems. More particularly, the present invention relates to methods, systems, and media for timed launching of logical partitions of computer systems.
- 2. Description of the Related Art
- Parallel processing generally refers to performing multiple computing tasks in parallel. Traditionally, parallel processing requires multiple computer systems with the resources of each computer system dedicated to a specific task or allocated to perform a portion of a common task. However, recent advances in computer hardware and software technologies have resulted in single computer systems capable of highly complex parallel processing by logically partitioning the system resources to different tasks. In a logically partitioned computer system, available system resources are allocated among multiple, logical partitions, each designed to appear to operate independently of the other. Management of the resources among logical partitions is typically accomplished via a layer of software components commonly referred to as a partition manager.
- An objective of the partition manager is to allow each logical partition to independently run software (e.g. operating systems and operating system specific applications) typically developed to run on a dedicated computer system, with little or no modification. For example, one logical partition may be running a first operating system such as IBMs OS/400, a second partition may be running and operating system such as IBMs AIX, while a third partition may be running a third operating system such as LINUX. By providing the ability to run multiple operating systems on the same computer system, a logically partitioned computer system may provide a user with a greater deal of freedom choosing application software best suited to the user's need with little or no regard to the operating system for which the application program was written.
- Logically partitioned systems, like other large computer systems, utilize a Timed Power On (TPO) function to power on the system at a specified time. An advantage of this approach, for example, is saving energy during prolonged periods of inactivity. Prolonged periods of inactivity may occur over weekends and holidays so the computer system may be powered down during the weekends and holidays and then powered on for the next workday, prior to the arrival of employees.
- Unlike other large computer systems, logically partitioned systems introduce complexities with regard to TPOs. In particular, a primary partition of a logically partitioned system is in charge of periodically checking memory locations associated with the TPOs for each logical partition to determine whether one or more of the logical partitions should be launched. Accordingly, the system administrator must launch the primary partition before the secondary, logical partitions can be launched.
- Current logically partitioned systems also offer a large, variable number of logical partitions, each logical partition servicing a different client with distinct periods of inactivity and working hours. Thus, the TPOs for all logical partitions of a computer system must either be manually coordinated with the launch of the primary partition by the system administrator, or logical partitions that are scheduled to launch prior to the launch of the primary partition will be delayed until the primary partition launches. Additionally, when servicing potentially hundreds of clients, manual coordination of the primary partition's TPO is cumbersome and prone to errors and the use of wide area networks (WANS) like the Internet further exacerbates these problems since the logical partitions can be used by clients of different entities located in different time zones.
- Therefore, there is a need for timed power-on in a logically partitioned environment.
- The problems identified above are in large part addressed by methods, systems, and media for timed power-on in a logically partitioned environment. One embodiment provides a method for launching at least one logical partition of a system. The method generally includes determining a time period based upon a time to launch a partition of the at least one logical partition and a time of day associated with the partition, the partition being the next partition to launch of the at least one logical partition; scheduling a launch for the system based upon the time period; and launching the system in response to the scheduled launch for the system.
- Another embodiment provides an apparatus for launching at least one logical partition of a system. The apparatus may include system hardware to partition; partition management circuitry to receive an event to indicate modification of a time to launch a logical partition of the at least one logical partition and determine a time period for the next scheduled launch associated with the at least one logical partition; and a timer coupled with the system hardware to boot the partition management circuitry based upon the time period.
- A further embodiment provides a computer readable medium containing a program which, when executed, performs an operation. The operation may include determining a time period based upon a time to launch a partition of at least one logical partition and a time of day associated with the partition, the partition being the next partition to launch of the at least one logical partition; scheduling a launch for the system based upon the time period; and launching the system in response to the scheduled launch for the system.
- So that the manner in which the above recited features, advantages and objects of the present invention are attained and can be understood in detail, a more particular description of the invention, briefly summarized above, may be had by reference to the embodiments thereof which are illustrated in the appended drawings.
- It is to be noted, however, that the appended drawings illustrate only typical embodiments of this invention and are therefore not to be considered limiting of its scope, for the invention may admit to other equally effective embodiments.
-
FIG. 1 is an embodiment of a computer system with one or more than one logical partition as part of the local network or wide area network. -
FIG. 2 is an embodiment of an apparatus including a server having hardware and firmware for implementing timed power-on in a logically partitioned environment. -
FIG. 3 depicts an embodiment of a method for timed power-on in a logically partitioned environment. - The following is a detailed description of example embodiments of the invention depicted in the accompanying drawings. The example embodiments are in such detail as to clearly communicate the invention. However, the amount of detail offered is not intended to limit the anticipated variations of embodiments, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the present invention as defined by the appended claims. The detailed descriptions below are designed to make such embodiments obvious to a person of ordinary skill in the art.
- Generally speaking, the invention contemplates methods, systems, and media for timed power-on in a logically partitioned environment. Embodiments may disclose determining a time period based upon a time to launch a partition and a time of day associated with the next partition to launch. After determining the time period, a timer is set to boot the system based upon the time period. More specifically, embodiments allow the timed power-on (TPO) and time of day (TOD) of logical partitions to be modified by clients independently of other partitions by determining the system TPO based upon TPOs and TODs of logical partitions as well as the TOD of the system. Some embodiments include initiating a transaction like an interrupt in response to a change in a TPO or TOD of logical partition or the system. Several of such embodiments incorporate adjusting or re-calculating the system TPO in response to the transaction.
- Turning now to the drawings,
FIG. 1 depicts an embodiment of asystem 100 for timed power-on in a logically partitioned environment.System 100 comprises aserver 110, a hardware management console (HMC) 130, a local area network/wide area network (LAN/WAN) 140, andclients Server 110 is a computer system having processing and storage capacity to serviceclients server 110 may include server software for multiple departments of an organization like a database system, allowing members of each department to access the database software vialogical partitions -
Server 110 includes hardware 112, apartition manager 114, andlogical partitions server 110 may be a symmetric multiprocessor (SMP) system including a plurality of processors such as an IBM RS/6000 or a multi-platform operating environment such as an IBM eServer iSeries that supports software like OS/400, Linux, WebSphere, Microsoft Windows and other e-business application environments on a single server for simplified management. Many such embodiments also support dynamic logical partitioning for allocation of resources and easy administration. - Hardware 112 includes a
timer 113 like a counter or a service processor that remains active whilepartition manager 114 andlogical partitions Timer 113 can automatically boot the system, i.e.,partition manager 114, when the time of day (TOD) associated withserver 110 reaches the timed power-on (TPO) set forpartition manager 114. However, in many embodiments, the automatic boot can be disabled or overridden. -
Partition manager 114 maintainslogical partitions partition manager 114 typically shuts down andtimer 113 of hardware 112boots partition manager 114 at the TPO set bypartition manager 114 prior to shutting down. - With regards to management of the logical partitions,
partition manager 114 may receive an event to indicate modification of a time to launch a logical partition oflogical partitions logical partitions partition manager 114 receives a new TPO forlogical partition 116 indicating that the client associated withlogical partition 116 wantslogical partition 116 to launch at 7:00 a.m. central standard time (CST) so that the services offered bylogical partition 116 are available for the employees that arrive at work at 8:00 a.m. CST.Partition manager 114 stores the modified partition TPO, recalculates the system TPO, stores the new TPO for the system and setstimer 113 to expire based upon the new TPO. - In some embodiments, setting the timer to expire may include storing a time in a memory location that is compared with the current TOD to determine when the timer expires. In other embodiments, setting the timer to expire may include storing a time count in a counter or in a memory location used as a counter. The time count is the difference between the new TPO and the current TOD for the corresponding partition. Accordingly, the timer expires upon reaching the time count.
-
Logical partitions server 110 forclients partition manager 114. The division allows the logical partitions to operate as independent logical systems, each having processing capacity, memory, storage capacity and I/O devices. For instance,partition manager 114 may divide hardware 112 between the threelogical partitions Partition manager 114 may also borrow processing capacity from the logical partitions and have access to a specified range of physical memory addresses to manage the logical partitions.Logical partitions partition manager 114 may enforce selections by the system operator(s) who logically partitioned the system, restricting the access oflogical partition 116 to one third of the processing capacity of one or more of the physical processors, a range of logical memory addresses, dynamically assigned to physical memory address via a look up table, and one third of the remaining data storage capacity by physically dividing address ranges or providing a range of logical addresses. Some embodiments are capable of supporting 254 or more logical partitions. -
Logical partitions server 110 and the system TPO is typically the TPO associated with bootingpartition manager 114. Sincepartition manager 114 divides the system resources and maintains the logical partitions, the system TPO is determined based upon the earliest launch of the logical partitions scheduled to be launched. In particular, the determination of the system TPO takes into account the TPOs of each logical partition and is used to facilitate bootingpartition manager 114, and, in some embodiments, powering on hardware 112 ofserver 110 in time to launch the next logical partition scheduled to be launched. The determination may also take into account the TODs of each logical partition so thatclients logical partitions -
HMC 130 is optional hardware that may provide access for a system operator for the server like a system administrator to create, manage, and remove logical partitions ofserver 110 such aslogical partitions HMC 130 provides access toserver 110 to adjust the system TOD and/or the system TPO. In many such embodiments,HMC 130 provides access to hardware 112 whenpartition manager 114 is not running. - In one embodiment,
HMC 130 is coupled directly withserver 110 via a dedicated Ethernet connection. In other embodiments,HMC 130 may couple withserver 110 via a network like local area network/wide area network (LAN/WAN) 140. - LAN/
WAN 140 is a network connection tocouple server 110 with clients such asclients WAN 140 may include a network in an office coupled with a cable modem, a direct subscriber line (DSL), a T1 line, a T3 line, or the like. In further embodiments, LAN/WAN 140 may include a network of temporary connections such as connections via a telephone system. In other embodiments, one or more clients likeclients server 110 directly. For example,server 110 operates as a web server allowing multiple businesses to connect to the web site independently via logical partitions for facilitating business-to-business (B2B) transactions. The client businesses can access their logical partition from anywhere in the world via the Internet and set the TPO for their logical partition based upon the next time they expect to accessserver 110.Partition manager 114 recognizes changes in the TPO for the each client and determines when the system should boot based upon those changes. -
Clients server 110 via LAN/WAN 140. - Referring now to
FIG. 2 , there is shown an embodiment of aserver 200 timed launching of logical partitions of the computer system.Server 200 includeshardware 210, a partition manager 220, andlogical partitions 270 through 290.Hardware 210 provides a computer system having one or more processors and memory that can be allocated to multiple logical computer systems to offer the advantage of multiple servers in terms of processing capabilities with the advantages of a single server in terms of maintenance and software management. For instance,hardware 210 can operate as one or more servers in one or more time zones, each having the capability of launching independently and each having the capability of running a different, independent operating system. -
Hardware 210 includes service processor (SP) 212,SP memory 214, processor(s) 222,memory 224, and input-output (I/O) 226.SP 212 acts as a timer that is coupled with the remainder ofhardware 210 to boot thepartition manager 230 based upon the TPO forserver 200. More specifically,SP 212 is a processor generally configured to power on and boot processor(s) 222,memory 224, and I/O 226 along withpartition manager 230 when the time of day associated with the system reaches the system TPO set to bootpartition manager 230.SP 212 also couples with processor(s) 222 via a processor bus and couples with dedicatedmemory SP memory 214. - When
server 200 is initially powered up,SP 212 uses the processor bus to interrogate the system (Host) processor(s) 222,memory 224, and I/O 226 to obtain an inventory and topology understanding ofserver 200.SP 212 then proceeds to load executable code and release processor(s) 222 for execution of the code. -
SP 212 maintainssystem TPO 216 andsystem TOD 218 to keep track of scheduled launches forpartition manager 230.SP 212 also maintains a system keylock 221 as an override to enable or disable automatic booting for the system. For example, customers coupled withlogical partitions 270 through 290 may setsystem TPO 216 to automatically “power on” or launch their partition early Monday morning, just in time for employees to start using theserver 110. Thus, thesystem TPO 216 is set for some time before the first logical partition is set to wake up. On the other hand, ifserver 230 or software thereon is being maintenanced or modified, system keylock 221 may be switched from “normal” to “manual” to preventpartition manager 230 from automatically booting in response to the expiration ofsystem TPO 216. In many such embodiments,system TPO 216 is set with a time count or time period that is the amount of time remaining until a user set time to power on the system or a TPO associated with a logical partition expires. - Processor(s) 222 include one or more system or host processors that provide the processing capacity for
server 200. Processor(s) 222 can be divided in accordance with logical processor units assigned to logical partitions by a system operator. For example, the system operator may provide a fraction of a processor to a logical partition. -
Memory 224 may include one or more memory devices having blocks of memory associated with physical addresses. As with processor(s) 222,memory 224 can be divided into physical blocks and associated with a logical partition or amounts of memory can assigned to logical partitions via logical blocks of addresses. The logical addresses can be assigned to physical addresses as data is stored at the logical addresses. - I/
O 224 includes I/O controllers, I/O busses and I/O adapters such as peripheral component interconnect (PCI) cards to coupleserver 210 with I/O equipment like tape drives, disk drives, compact disk (CD) drives, hard drives, optical drives, printers, scanners, telephone systems and networks. I/O equipment may also be physically and/or logically associated with logical partitions. -
Partition manager 230 comprises low-level encoded data, often referred to as partitioning licensed internal code (PLIC), to enforce logical partitioning ofhardware 210 forlogical partitions 270 through 290.Partition manager 230 enforces logical partitioning ofhardware 210 by presenting a partitioned view of hardware to task dispatchers of higher levels of code, such as code executed within the partitions. For instance, a client changes a time to launch a logical partition, initiating code to cause a perceived processor change a value at a memory location.Partition manager 230, however, receives the value, interprets the instruction to store the value as an event indicating modification of the time to launch, associates the memory location with a physical memory location, stores the modified time to launch in the physical memory location, utilizes code execution cycles of processor(s) 222 to determine a time period to the next scheduled launch associated withlogical partitions 270 through 290, and stores the new system TPO in value insystem TPO 216. -
Partition manager 230 comprises atime manager 240,virtual service processors 250 andvirtual keylocks 260.Time manager 240 manages and maintains TPOs and TODs for each of the logical partitions,virtual TODs 246 andvirtual TPOs 248, and for the system,system TOD 218 andsystem TPO 216.Time manager 240 manages the TPOs and TODs to allow each partition to independently set a TOD and TPO without concern regarding whether thepartition manager 240 will be available to launch the corresponding logical partition. For example, TPOs for logical partitions may default to a disabled state and TODs may default to the TOD associated withserver 200. When a client in a different time zone thanserver 200 accesseslogical partition 270, the client requests modification of the TOD of logical partition invirtual TODs 246 to match the client's time zone. The request to change the TOD is received bytime manager 240. In response,time manager 240 modifiesvirtual TODs 246 to reflect the requested change and communicates the modification tosystem VSP 252 of VSP's 250. - After modifying the TOD for
logical partition 270, the client may enable the TPO by requesting that the TPO be set to a time.Time manager 240 receives the request, modifies the corresponding TPO ofvirtual TPOs 248, and communicates the modifications tosystem VSP 252 of VSP's 250.System VSP 252 then sets a timer forlogical partition 270 insystem TPO 216. Upon expiration of the timer,partition manager 230 verifies that the keylock forlogical partition 270 is set to “normal,” or automatic, and launcheslogical partition 270. - VSP's 250 service processing requests from
logical partitions system VSP 252.System VSP 252 comprisessystem TPO determination 253 to determine a time period for settingsystem TPO 216.System TPO determination 253 is circuitry like a state machine or a processor executing instructions such as software or firmware, to determine the time period based upon a difference between a TPO for a logical partition and the logical partition's current TOD.System TPO determination 253 determinessystem TPO 216 the smallest time period of the logical partitions having enabled TPOs and setssystem TPO 216 based upon the smallest time period. In some embodiments,system TPO 216 is set to bootpartition manager 230 at a point in time before the expiration of the smallest time period. -
System TPO determination 253 recalculatessystem TPO 216 in response to an indication fromtime manager 240 that a TPO or TOD has been modified. Upon determining a new system TPO,system VSP 252sets system TPO 216 toboot partition manager 230. - Partitioning Licensed Internal Code (PLIC) 259 allocates processing capacity to
logical partitions 270 through 290 based upon a system operator's selections with regards to logically partitioningprocessors 222. For example, processing capacity ofprocessors 222 may be divided dynamically amonglogical partitions 270 through 290 according to time slices in response to the system operator's selections for the logical partitions. -
Virtual keylocks 260 include partition overrides for automatically launching logical partitions likelogical partitions 270 through 290.Virtual keylocks 260 operate in a similar manner as system keylock 221, allowing each client associated with a logical partition to override the automatic launching of the client's logical partition. For example, during a holiday, when employees are not usinglogical partition 270, the client associated withlogical partition 270 may set a corresponding virtual keylock ofvirtual keylocks 260 to override automatic launching oflogical partition 270, decouplinglogical partition 270 from the Internet for the holiday. Thus, the client can avoid unnecessary security risks involved with operatinglogical partition 270 during the holiday. -
Logical partitions 270 through 290 act like multiple servers although each has resources defined by a system operator ofserver 200 and enforced withpartition manager 230 rather than being defined physical limitations. Thus, resources of logical partitions can advantageously be modified via software rather than physically changing hardware. - In many embodiments, each logical partition operates independently from the other logical partitions. For example, one instance of the Advanced Interactive Executive (AIX) operating system,
OS 272, may be executing withinlogical partition 270, a second instance (image) of the AIX operating system,OS 282, may be executing withinlogical partition 280, and an OS/400 operating system,OS 292, may be operating withinlogical partition 290. -
OS 272 through 292 comprise time consoles 274 through 294 respectively. Time consoles 274 through 294 provide an interface between the client associated with the corresponding logical partition andtime manager 240 to allow the clients to modify the TODs and TPOs for each logical system. - In some embodiments,
partition manager 230 interfaces with a hardware management console (HMC) that includes a partition manager interface. The partition manager interface provides a system operator or administrator access to functions ofpartition manager 230 such as creating, modifying, and/or deleting logical partitions, and modifyingsystem TOD 218 and/orsystem TPO 216. For example, a system administrator accessesserver 200 from a remote location to updatesystem TOD 218. The partition manager interface offers the option of modifyingsystem TOD 218 and forwards the request totime manager 240. Upon receipt of the request,time manager 240 communicates the modification tosystem VSP 250 andsystem VSP 250 proceeds to recalculatesystem TPO 216 based upon the change tosystem TOD 218. -
FIG. 3 depicts anexample flow chart 300 of a method for launching logical partitions of a computer system. The computer system may have any number of logical partitions including the case of having just one partition. These logical partitions may or may not coincide with physical partitions of the system. Furthermore, the logical partitions may have been assigned fractional computing power of the processor(s), including fractional usage of other resources of the system and may be physically located anywhere in the world, and thus in any time zone. -
Flow chart 300 begins withelement 310 of storing the TODs and the corresponding time(s) for launching the partition(s) or TPOs for determining a time period, or time count, to launch the system. The logical partition operators or clients generally enter their own TODs and TPOs into the system. These TODs and TPOs are then available to the server for determining which partition needs to be launched next. - In
element 315, the server determines the next scheduled time to launch a logical partition, and sets up a timer for the system such that the system is booted prior in time to launch the logical partition. In some embodiments, the logical partition is launched after the system is booted. In other embodiments, a second timer is set for the corresponding logical partition to demark the time to launch that logical partition. For example, the first logical partition is the earliest logical partition scheduled to launch and the second logical partition is scheduled to launch after the first partition. The first logical partition may be associated with the system launch and launched immediately after the system launch or may have a separate timer configured to launch the first logical partition at some point after the system is launched. - Determining the time for launching the system is based upon differences between the time to launch each logical partition and the corresponding current time of day for each logical partition. In one aspect the time to launch the system may be determined by the following equation:
System TPO=System TOD+MIN(TPO1−TOD1,TPO2−TOD2, . . . TPOi−TODi, . . . , TPOn−TODn).
wherein the subscript i=1, 2, . . . , n designates the ith partition of partitions that have enabled, unexpired TPO values; the system TPO is TPO of the system, or the partition manager; and the system TOD is the TOD associated with the server. - For example, the system may have three logical partitions having enabled TPOs: a partition one, partition two and partition three. The client corresponding to partition one may reside in California and may set partition one's TPO, TPO1, to 8:00 a.m. pacific standard time (PST). The client corresponding to partition two may reside in Texas and may set partition two's TPO, TPO2, to 8:00 a.m. central standard time (CST). And the client corresponding to partition three may reside in New York and may set partition three's TPO, TPO3, to 8:00 a.m. eastern standard time (EST). The system may reside in Texas and the current system TOD may be 5:00 p.m. CST. VSP may determine that the difference between the current TOD1 and TPO1 is 17 hours, between the current TOD2 and TPO2 is 15 hours, and between the current TOD3 and TPO3 is 14 hours. Since 14 hours is the smallest time period, VSP may set the system TPO to power on and launch the system in 13 hours so that the system is operating when TPO3 expires. Then, the system will launch partition two when TPO2 expires, or matches TOD2, and partition one when TPO1 expires, or matches TOD1.
- Further, when all partition TPO values are either expired or disabled, the system TPO is disabled. Alternatively, any suitable function may be used that determines when the system should boot to facilitate the time of launch of the logical partitions, taking into account differences in time zones, if applicable.
-
Element 320, in many embodiments, determines whether an interrupt or a transaction was received to indicate that a logical partition's TPO was disabled. In some embodiments, the partition's TPO may be in one of three possible states. First, the TPO can have a binary value of zero, in which case the TPO is considered disabled. Second, the TPO can have a value such that the TPO is greater than zero but less than or equal the TOD associated with the logical partition. In that case the TPO is considered enabled but expired. Third, in the case of TOD less than TPO, the TPO is considered enabled but not yet expired. In many embodiments, the determination of the system TPO considers enabled TPOs. In further embodiments, the determination of the system TPO considers enabled TPOs that have not expired. - In
element 320, determining the time count for thesystem TPO 315 is performed whenever a partition disables its TPO since the change may affect the resulting system TPO. More specifically, disabled TPO values are ignored when determining the system TPO. Likewise, inelement 325, determining the system TPO is performed whenever any partition enables a new TPO. - In
element 330, determining the time count for thesystem TPO 315 is performed whenever a partition changes its TOD and/or its TPO. Since the TPO and TOD are persistently maintained by the time manager within the partition manager there will be a new event sent to the VSP in the partition manager whenever a client changes a logical partition's TOD and/or TPO, or disables TPO. The VSP also re-calculates the system TPO and sets a timer associated with the service processor. - In
element 335, the partition manager checks to determine whether the changed TPO or TOD resulted in an expired TPO for that logical partition. If the TPO is expired as a result of changing the TOD for the partition, the partition manager generates an error message, inelement 340 indicating that the partition has already been launched. Otherwise, the partition manager waits to receive an indication for another change related to a TOD and/or TPO, and/or the expiration of a timer associated with launching a logical partition. - Similarly, in
element 345, the partition manager may receive an indication that the system TOD has changed. In such situations, the time manager recalculates the system TPO inelement 315. When the TODs for each partition is independently maintained, the time manager also recalculates each partition TOD such that no net time TOD/TPO change is apparent from a partition perspective. The partition TOD/TPO is the same before and after the system TOD/TPO change is made. Alternatively, inelement 350, if the time count has expired, the system or the corresponding logical partition should be launched. -
Element 355 corresponds to implementing the keylock rules for the system and logical partitions. Inelement 355, if the keylock is set to normal when a TPO expires, then the partition manager will boot or the corresponding logical partition will launch automatically (element 365). On the other hand, when the keylock is set to manual, no automatic launching of the partition occurs and the partition manager waits for the next change related to a TOD and/or TPO, and/or the expiration of a time count. - One embodiment of the invention is implemented as a program product for use with a computer system such as, for example, the
system 100 shown inFIG. 1 and described below. The program(s) of the program product defines functions of the embodiments (including the methods described herein) and can be contained on a variety of signal-bearing media. Illustrative signal-bearing media include, but are not limited to: (i) information permanently stored on non-writable storage media (e.g., read-only memory devices within a computer such as CD-ROM disks readable by a CD-ROM drive); (ii) alterable information stored on writable storage media (e.g., floppy disks within a diskette drive or hard-disk drive); and (iii) information conveyed to a computer by a communications medium, such as through a computer or telephone network, including wireless communications. The latter embodiment specifically includes information downloaded from the Internet and other networks. Such signal-bearing media, when carrying computer-readable instructions that direct the functions of the present invention, represent embodiments of the present invention. - In general, the routines executed to implement the embodiments of the invention, may be part of an operating system or a specific application, component, program, module, object, or sequence of instructions. The computer program of the present invention typically is comprised of a multitude of instructions that will be translated by the native computer into a machine-readable format and hence executable instructions. Also, programs are comprised of variables and data structures that either reside locally to the program or are found in memory or on storage devices. In addition, various programs described hereinafter may be identified based upon the application for which they are implemented in a specific embodiment of the invention. However, it should be appreciated that any particular program nomenclature that follows is used merely for convenience, and thus the invention should not be limited to use solely in any specific application identified and/or implied by such nomenclature.
- While the foregoing is directed to embodiments of the present invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof, and the scope thereof is determined by the claims that follow.
Claims (25)
1. A method for launching at least one logical partition of a system, the method comprising:
determining a time period based upon a time to launch a partition of the at least one logical partition and a time of day associated with the partition, the partition being the next partition to launch of the at least one logical partition;
scheduling a launch for the system based upon the time period; and
launching the system in response to the scheduled launch for the system.
2. The method of claim 1 , further comprising receiving an indication that the time of day associated with the partition was modified and calculating a new time period for the partition.
3. The method of claim 1 , further comprising receiving an indication that the time to launch the partition was modified.
4. The method of claim 3 , wherein receiving the indication comprises receiving a value indicating a new time to launch the partition.
5. The method of claim 1 , further comprising changing the scheduled launch for the system when a subsequent time period is determined to be shorter than the time period, wherein the scheduled launch for the system is a system timed power-on.
6. The method of claim 1 , further comprising scheduling a launch for the partition based upon the time period, wherein the scheduled launch for the partition is after the scheduled launch for the system.
7. The method of claim 6 , further comprising launching the partition unless the scheduled launch for the partition is overridden.
8. The method of claim 1 , wherein determining the time period comprises calculating the difference between a timed power-on associated with the partition and the time of day associated with the partition.
9. The method of claim 8 , wherein scheduling the launch for the system comprises setting a timer based upon an enabled timed power-on.
10. The method of claim 1 , wherein launching the system comprises powering on hardware of the system and booting partition management code.
11. An apparatus for launching at least one logical partition of a system, the apparatus comprising:
system hardware to partition;
partition management circuitry to receive an event to indicate modification of a time to launch a logical partition of the at least one logical partition and determine a time period for the next scheduled launch associated with the at least one logical partition; and
a timer coupled with the system hardware to boot the partition management circuitry based upon the time period.
12. The apparatus of claim 11 , further comprising a client coupled with the logical partition to generate the event.
13. The apparatus of claim 11 , wherein the system hardware comprises at least one processor coupled with memory.
14. The apparatus of claim 11 , wherein the partition management circuitry comprises allocation circuitry to allocate processing capacity to the at least one logical partition.
15. The apparatus of claim 14 , wherein the allocation circuitry allocates a fraction of the processing capacity of a processor to the logical partition.
16. The apparatus of claim 14 , wherein the allocation circuitry comprises circuitry to determine the time period based upon a difference between a timed power-on and a time of day, the timed power-on and the time of day being associated with the logical partition.
17. The apparatus of claim 11 , wherein the partition management circuitry comprises time management circuitry to maintain a timed power-on and a time of day for the logical partition.
18. The apparatus of claim 11 , wherein partition management circuitry comprises time management circuitry to initiate a transaction to indicate a change related to the time period.
19. The apparatus of claim 11 , wherein the timer comprises a service processor to boot the system when the time of day associated with the system reaches the timed power-on set for the system.
20. A computer readable medium containing a program which, when executed, performs an operation, comprising:
determining a time period based upon a time to launch a partition of at least one logical partition and a time of day associated with the partition, the partition being the next partition to launch of the at least one logical partition;
scheduling a launch for the system based upon the time period; and
launching the system in response to the scheduled launch for the system.
21. The computer readable medium of claim 20 , wherein the operation further comprises receiving an indication that the time of day associated with the partition was modified and calculating a new time period for the partition.
22. The computer readable medium of claim 20 , wherein the operation further comprises receiving an indication that the time to launch the partition was modified.
23. The computer readable medium of claim 20 , wherein the operation further comprises changing the scheduled launch for the system when a subsequent time period is determined to be shorter than the time period.
24. The computer readable medium of claim 20 , wherein the operation further comprises scheduling a launch for the partition based upon the time period, wherein the scheduled launch for the partition is after the scheduled launch for the system.
25. The computer readable medium of claim 20 , wherein determining the time period comprises calculating the difference between a timed power-on associated with the partition and the time of day.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/869,855 US20080028199A1 (en) | 2003-04-17 | 2007-10-10 | Method for scheduling launch a computer system based upon a time of timed power-on partition of logical partitions |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/418,348 US7290125B2 (en) | 2003-04-17 | 2003-04-17 | Method for scheduling launch a computer system based upon a time of timed power-on partition of logical partitions |
US11/869,855 US20080028199A1 (en) | 2003-04-17 | 2007-10-10 | Method for scheduling launch a computer system based upon a time of timed power-on partition of logical partitions |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/418,348 Continuation US7290125B2 (en) | 2003-04-17 | 2003-04-17 | Method for scheduling launch a computer system based upon a time of timed power-on partition of logical partitions |
Publications (1)
Publication Number | Publication Date |
---|---|
US20080028199A1 true US20080028199A1 (en) | 2008-01-31 |
Family
ID=33159088
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/418,348 Active 2026-01-17 US7290125B2 (en) | 2003-04-17 | 2003-04-17 | Method for scheduling launch a computer system based upon a time of timed power-on partition of logical partitions |
US11/869,855 Abandoned US20080028199A1 (en) | 2003-04-17 | 2007-10-10 | Method for scheduling launch a computer system based upon a time of timed power-on partition of logical partitions |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/418,348 Active 2026-01-17 US7290125B2 (en) | 2003-04-17 | 2003-04-17 | Method for scheduling launch a computer system based upon a time of timed power-on partition of logical partitions |
Country Status (1)
Country | Link |
---|---|
US (2) | US7290125B2 (en) |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020120854A1 (en) * | 2000-09-22 | 2002-08-29 | Levine Richard B. | Systems and methods for preventing unauthorized use of digital content |
US20060212729A1 (en) * | 2005-03-18 | 2006-09-21 | Fujitsu Limited | Information processing device, operating system switchover method and recording medium |
US20070199074A1 (en) * | 2000-09-22 | 2007-08-23 | Ecd Systems | Systems and methods for preventing unauthorized use of digital content |
US20090049110A1 (en) * | 2005-12-20 | 2009-02-19 | International Business Machines Corporation | Apparatus and system for reorganizing a set of database partitions |
US20090138529A1 (en) * | 2007-11-22 | 2009-05-28 | Canon Kabushiki Kaisha | Method and device for coding and decoding information |
US8117667B2 (en) | 2001-05-09 | 2012-02-14 | Sca Ipla Holdings Inc. | Systems and methods for the prevention of unauthorized use and manipulation of digital content |
US20130185375A1 (en) * | 2012-01-17 | 2013-07-18 | International Business Machines Corporation | Configuring compute nodes in a parallel computer using remote direct memory access ('rdma') |
US20140201513A1 (en) * | 2013-01-16 | 2014-07-17 | Wistron Corp. | Power management circuit, server, and power management method thereof |
Families Citing this family (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB0004088D0 (en) * | 2000-02-21 | 2000-04-12 | Nokia Networks Oy | Packet data services in a telecommunications system |
US7290125B2 (en) * | 2003-04-17 | 2007-10-30 | International Business Corporation | Method for scheduling launch a computer system based upon a time of timed power-on partition of logical partitions |
US7099977B2 (en) * | 2004-01-12 | 2006-08-29 | Hewlett-Packard Development Company, L.P. | Processor interrupt filtering |
US7757033B1 (en) | 2004-02-13 | 2010-07-13 | Habanero Holdings, Inc. | Data exchanges among SMP physical partitions and I/O interfaces enterprise servers |
US7873693B1 (en) | 2004-02-13 | 2011-01-18 | Habanero Holdings, Inc. | Multi-chassis fabric-backplane enterprise servers |
US8868790B2 (en) | 2004-02-13 | 2014-10-21 | Oracle International Corporation | Processor-memory module performance acceleration in fabric-backplane enterprise servers |
US7953903B1 (en) | 2004-02-13 | 2011-05-31 | Habanero Holdings, Inc. | Real time detection of changed resources for provisioning and management of fabric-backplane enterprise servers |
US8145785B1 (en) | 2004-02-13 | 2012-03-27 | Habanero Holdings, Inc. | Unused resource recognition in real time for provisioning and management of fabric-backplane enterprise servers |
US7843907B1 (en) | 2004-02-13 | 2010-11-30 | Habanero Holdings, Inc. | Storage gateway target for fabric-backplane enterprise servers |
US7685281B1 (en) | 2004-02-13 | 2010-03-23 | Habanero Holdings, Inc. | Programmatic instantiation, provisioning and management of fabric-backplane enterprise servers |
US7633955B1 (en) | 2004-02-13 | 2009-12-15 | Habanero Holdings, Inc. | SCSI transport for fabric-backplane enterprise servers |
US7843906B1 (en) | 2004-02-13 | 2010-11-30 | Habanero Holdings, Inc. | Storage gateway initiator for fabric-backplane enterprise servers |
US8713295B2 (en) | 2004-07-12 | 2014-04-29 | Oracle International Corporation | Fabric-backplane enterprise servers with pluggable I/O sub-system |
US8578385B2 (en) * | 2005-04-21 | 2013-11-05 | Microsoft Corporation | Method and system for virtual service isolation |
JP2007128492A (en) * | 2005-10-07 | 2007-05-24 | Toshiba Corp | Information processing apparatus and power on control method |
WO2007099624A1 (en) * | 2006-03-01 | 2007-09-07 | Fujitsu Limited | Method for managing and controlling time of computer system and computer system |
US7853949B2 (en) * | 2006-03-13 | 2010-12-14 | International Business Machines Corporation | Method and apparatus for assigning fractional processing nodes to work in a stream-oriented computer system |
US20110252252A1 (en) * | 2010-04-12 | 2011-10-13 | Xerox Corporation | System and method for identifying and reducing power consumption based on an inactivity period |
US20130152081A1 (en) * | 2011-12-13 | 2013-06-13 | International Business Machines Corporation | Selectable event reporting for highly virtualized partitioned systems |
Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5426775A (en) * | 1992-05-25 | 1995-06-20 | Hewlett-Packard Company | Method and a device for booting a computer at a programmed time |
US5802354A (en) * | 1997-06-09 | 1998-09-01 | International Business Machines Corporation | Method and apparatus for synchronizing selected logical partitions of a partitioned information handling system to a test datesource |
US6421777B1 (en) * | 1999-04-26 | 2002-07-16 | International Business Machines Corporation | Method and apparatus for managing boot images in a distributed data processing system |
US6421786B1 (en) * | 1998-03-13 | 2002-07-16 | Nec Corporation | Virtual system time management system utilizing a time storage area and time converting mechanism |
US20020124165A1 (en) * | 2001-03-01 | 2002-09-05 | International Business Machines Corporation | Method and system for timed partition power-on in a logical partition environment |
US6687820B2 (en) * | 2000-12-07 | 2004-02-03 | International Business Machines Corporation | System includes a selection manager for remotely managing the selection of an operating system for a target computer |
US6691146B1 (en) * | 1999-05-19 | 2004-02-10 | International Business Machines Corporation | Logical partition manager and method |
US20050015581A1 (en) * | 2003-07-18 | 2005-01-20 | Hung-Ping Chen | [selectable booting method by bios with multi-partition in the disk on a single computer platform] |
US7065761B2 (en) * | 2001-03-01 | 2006-06-20 | International Business Machines Corporation | Nonvolatile logical partition system data management |
US7290125B2 (en) * | 2003-04-17 | 2007-10-30 | International Business Corporation | Method for scheduling launch a computer system based upon a time of timed power-on partition of logical partitions |
-
2003
- 2003-04-17 US US10/418,348 patent/US7290125B2/en active Active
-
2007
- 2007-10-10 US US11/869,855 patent/US20080028199A1/en not_active Abandoned
Patent Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5426775A (en) * | 1992-05-25 | 1995-06-20 | Hewlett-Packard Company | Method and a device for booting a computer at a programmed time |
US5802354A (en) * | 1997-06-09 | 1998-09-01 | International Business Machines Corporation | Method and apparatus for synchronizing selected logical partitions of a partitioned information handling system to a test datesource |
US6421786B1 (en) * | 1998-03-13 | 2002-07-16 | Nec Corporation | Virtual system time management system utilizing a time storage area and time converting mechanism |
US6421777B1 (en) * | 1999-04-26 | 2002-07-16 | International Business Machines Corporation | Method and apparatus for managing boot images in a distributed data processing system |
US6691146B1 (en) * | 1999-05-19 | 2004-02-10 | International Business Machines Corporation | Logical partition manager and method |
US6687820B2 (en) * | 2000-12-07 | 2004-02-03 | International Business Machines Corporation | System includes a selection manager for remotely managing the selection of an operating system for a target computer |
US20020124165A1 (en) * | 2001-03-01 | 2002-09-05 | International Business Machines Corporation | Method and system for timed partition power-on in a logical partition environment |
US6829714B2 (en) * | 2001-03-01 | 2004-12-07 | International Business Machines Corporation | Method for timed booting of logical partitions in a computer system in accordance with a preset schedule stored in nonvolatile memory |
US7065761B2 (en) * | 2001-03-01 | 2006-06-20 | International Business Machines Corporation | Nonvolatile logical partition system data management |
US7290125B2 (en) * | 2003-04-17 | 2007-10-30 | International Business Corporation | Method for scheduling launch a computer system based upon a time of timed power-on partition of logical partitions |
US20050015581A1 (en) * | 2003-07-18 | 2005-01-20 | Hung-Ping Chen | [selectable booting method by bios with multi-partition in the disk on a single computer platform] |
Cited By (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070199074A1 (en) * | 2000-09-22 | 2007-08-23 | Ecd Systems | Systems and methods for preventing unauthorized use of digital content |
US20020120854A1 (en) * | 2000-09-22 | 2002-08-29 | Levine Richard B. | Systems and methods for preventing unauthorized use of digital content |
US7565697B2 (en) * | 2000-09-22 | 2009-07-21 | Ecd Systems, Inc. | Systems and methods for preventing unauthorized use of digital content |
US20100306552A1 (en) * | 2000-09-22 | 2010-12-02 | Sca Ipla Holdings Inc. | Systems and methods for preventing unauthorized use of digital content |
US8261359B2 (en) | 2000-09-22 | 2012-09-04 | Sca Ipla Holdings Inc. | Systems and methods for preventing unauthorized use of digital content |
US8844048B2 (en) | 2001-05-09 | 2014-09-23 | Sca Ipla Holdings Inc. | Systems and methods for the prevention of unauthorized use and manipulation of digital content |
US8117667B2 (en) | 2001-05-09 | 2012-02-14 | Sca Ipla Holdings Inc. | Systems and methods for the prevention of unauthorized use and manipulation of digital content |
US20060212729A1 (en) * | 2005-03-18 | 2006-09-21 | Fujitsu Limited | Information processing device, operating system switchover method and recording medium |
US20090049110A1 (en) * | 2005-12-20 | 2009-02-19 | International Business Machines Corporation | Apparatus and system for reorganizing a set of database partitions |
US8086576B2 (en) * | 2005-12-20 | 2011-12-27 | International Business Machines Corporation | Apparatus and system for reorganizing a set of database partitions |
US20090138529A1 (en) * | 2007-11-22 | 2009-05-28 | Canon Kabushiki Kaisha | Method and device for coding and decoding information |
US8533172B2 (en) * | 2007-11-22 | 2013-09-10 | Canon Kabushiki Kaisha | Method and device for coding and decoding information |
US20130185381A1 (en) * | 2012-01-17 | 2013-07-18 | International Business Machines Corporation | Configuring Compute Nodes In A Parallel Computer Using Remote Direct Memory Access ('RDMA') |
US20130185375A1 (en) * | 2012-01-17 | 2013-07-18 | International Business Machines Corporation | Configuring compute nodes in a parallel computer using remote direct memory access ('rdma') |
US20140201513A1 (en) * | 2013-01-16 | 2014-07-17 | Wistron Corp. | Power management circuit, server, and power management method thereof |
US9170618B2 (en) * | 2013-01-16 | 2015-10-27 | Wistron Corp. | Power management circuit, server, and power management method thereof |
Also Published As
Publication number | Publication date |
---|---|
US7290125B2 (en) | 2007-10-30 |
US20040210705A1 (en) | 2004-10-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7290125B2 (en) | Method for scheduling launch a computer system based upon a time of timed power-on partition of logical partitions | |
US11681562B2 (en) | Resource manager for managing the sharing of resources among multiple workloads in a distributed computing environment | |
US7720957B2 (en) | Auto-configuration of an internal VLAN network interface | |
US7720972B2 (en) | System for transferring standby resource entitlement | |
US8429660B2 (en) | Systems and methods to allocate application tasks to a pool of processing machines | |
EP3469478B1 (en) | Server computer management system for supporting highly available virtual desktops of multiple different tenants | |
US7849221B2 (en) | Online instance deletion in a multi-instance computer system | |
JP3978199B2 (en) | Resource utilization and application performance monitoring system and monitoring method | |
US7447896B2 (en) | OS mini-boot for running multiple environments | |
US8074225B2 (en) | Assuring recovery of temporary resources in a logically partitioned computer system | |
US8327370B2 (en) | Dynamic policy manager method, system, and computer program product for optimizing fractional resource allocation | |
CN102214117B (en) | Virtual machine management method, system and server | |
US20060136913A1 (en) | Method, system and computer program product for an automatic resource management of a virtual machine | |
EP1693754A2 (en) | System and method for creating and managing virtual servers | |
US20050251538A1 (en) | Unique ID management in disconnected database replication | |
US20080082665A1 (en) | Method and apparatus for deploying servers | |
US11470144B1 (en) | Optimization-based pool protection for a cloud provider network | |
US7716433B2 (en) | Dynamically determining and managing a set of target volumes for snapshot operation | |
US9088569B2 (en) | Managing access to a shared resource using client access credentials | |
US11483205B1 (en) | Defragmentation of licensed resources in a provider network | |
US20080276060A1 (en) | Pre-Configured Partitions With Use-Rights Limitations | |
US11868448B1 (en) | Shared dedicated host resource groups in a provider network | |
US8386391B1 (en) | Resource-type weighting of use rights | |
Planning | Workload Management | |
CN114489932A (en) | Cloud computing management method for cloud desktop system server |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |