Abstract: Disclosed embodiments provide systems and methods for analyzing and optimizing access policies. Access policies are analyzed by an access policy optimization system. In cases where large numbers of users have similar access privileges, the number of overall policies can be significantly reduced. An access control health metric is computed on an original set of access data as a measure of the current state of the access policies. It can be used as an indication that optimization of the access policies is warranted. The access data can include access policies and/or access groups. A policy subgroup mapping process is performed to identify subgroups of access policies. Subgroups with a number of entries exceeding a predetermined value are converted to access groups, the users that have those policies are added to the corresponding access groups, and the individual access policies are deleted. Duplicative and/or redundant policies are identified and removed.

Abstract: Coordination of rate limiting calculations and updates, for multiple interrelated services, at a single computer at a single logical location on a computer network, instead of coordinating rate limit calculations by direct data communications among and between the various machines hosting the interrelated services that are subject to rate limiting. In some of these embodiments, advantages to doing this may include: (i) reducing the number and/or bandwidth consumption of data communications needed to perform rate limiting calculations and determinations; and/or (ii) setting appropriate rate limits for only the “highest level” services (that is, the services that are initially called by users, as opposed to the services that the highest level service call (directly or indirectly)).

Abstract: Coordination of rate limiting calculations and updates, for multiple interrelated services, at a single computer at a single logical location on a computer network, instead of coordinating rate limit calculations by direct data communications among and between the various machines hosting the interrelated services that are subject to rate limiting. In some of these embodiments, advantages to doing this may include: (i) reducing the number and/or bandwidth consumption of data communications needed to perform rate limiting calculations and determinations; and/or (ii) setting appropriate rate limits for only the “highest level” services (that is, the services that are initially called by users, as opposed to the services that the highest level service call (directly or indirectly)).

Abstract: Dynamically changing the aggressiveness of optimization of virtual machines on physical hosts allows more efficient and varied optimization. An aggressiveness policy mechanism periodically applies system conditions to the aggressiveness policies to create aggressiveness settings that are provided to an optimizer. The optimizer then uses the aggressiveness settings to dynamically adjust the aggressiveness of placement of virtual machines according to the aggressiveness settings and consistent with other optimization policies. The aggressiveness policy mechanism may allow a system administrator to create and/or select aggressiveness policies.

Abstract: Dynamically changing the aggressiveness of optimization of virtual machines on physical hosts allows more efficient and varied optimization. An aggressiveness policy mechanism periodically applies system conditions to the aggressiveness policies to create aggressiveness settings that are provided to an optimizer. The optimizer then uses the aggressiveness settings to dynamically adjust the aggressiveness of placement of virtual machines according to the aggressiveness settings and consistent with other optimization policies. The aggressiveness policy mechanism may allow a system administrator to create and/or select aggressiveness policies.

Abstract: Dynamically changing the aggressiveness of optimization of virtual machines on physical hosts allows more efficient and varied optimization. An aggressiveness policy mechanism periodically applies system conditions to the aggressiveness policies to create aggressiveness settings that are provided to an optimizer. The optimizer then uses the aggressiveness settings to dynamically adjust the aggressiveness of placement of virtual machines according to the aggressiveness settings and consistent with other optimization policies. The aggressiveness policy mechanism may allow a system administrator to create and/or select aggressiveness policies.

Abstract: Dynamically changing the aggressiveness of optimization of virtual machines on physical hosts allows more efficient and varied optimization. An aggressiveness policy mechanism periodically applies system conditions to the aggressiveness policies to create aggressiveness settings that are provided to an optimizer. The optimizer then uses the aggressiveness settings to dynamically adjust the aggressiveness of placement of virtual machines according to the aggressiveness settings and consistent with other optimization policies. The aggressiveness policy mechanism may allow a system administrator to create and/or select aggressiveness policies.

Abstract: Dynamically changing the aggressiveness of optimization of virtual machines on physical hosts allows more efficient and varied optimization. An aggressiveness policy mechanism periodically applies system conditions to the aggressiveness policies to create aggressiveness settings that are provided to an optimizer. The optimizer then uses the aggressiveness settings to dynamically adjust the aggressiveness of placement of virtual machines according to the aggressiveness settings and consistent with other optimization policies. The aggressiveness policy mechanism may allow a system administrator to create and/or select aggressiveness policies.

Abstract: Dynamically changing the aggressiveness of optimization of virtual machines on physical hosts allows more efficient and varied optimization. An aggressiveness policy mechanism periodically applies system conditions to the aggressiveness policies to create aggressiveness settings that are provided to an optimizer. The optimizer then uses the aggressiveness settings to dynamically adjust the aggressiveness of placement of virtual machines according to the aggressiveness settings and consistent with other optimization policies. The aggressiveness policy mechanism may allow a system administrator to create and/or select aggressiveness policies.

Abstract: Dynamically changing the aggressiveness of optimization of virtual machines on physical hosts allows more efficient and varied optimization. An aggressiveness policy mechanism periodically applies system conditions to the aggressiveness policies to create aggressiveness settings that are provided to an optimizer. The optimizer then uses the aggressiveness settings to dynamically adjust the aggressiveness of placement of virtual machines according to the aggressiveness settings and consistent with other optimization policies. The aggressiveness policy mechanism may allow a system administrator to create and/or select aggressiveness policies.

Abstract: Dynamically changing the aggressiveness of optimization of virtual machines on physical hosts allows more efficient and varied optimization. An aggressiveness policy mechanism periodically applies system conditions to the aggressiveness policies to create aggressiveness settings that are provided to an optimizer. The optimizer then uses the aggressiveness settings to dynamically adjust the aggressiveness of placement of virtual machines according to the aggressiveness settings and consistent with other optimization policies. The aggressiveness policy mechanism may allow a system administrator to create and/or select aggressiveness policies.

Abstract: A mechanism is provided for isolation of device namespace to allow duplicate or common names in root volume group workload partitions. The mechanism creates a scratch file system that contains enough information to create an execution environment for a workload partition and information about which physical volumes to use for the root volume group file systems. The mechanism then populates the root file systems on a disk in the global space. The mechanism boots the workload partition from the scratch file system and configures the devices to be exported to the workload partition based information in the scratch file system. The mechanism then renames the logical volume names to the traditional names. The mechanism then temporarily mounts the root volume group file system onto the scratch file system.

Abstract: Computer implemented methods, data processing systems and computer program products install deliverables into user-specified install locations. A user-specified install location is provided. Software virtual product data is extracted from a software bundle. Software virtual product data is stored within the user-specified install location.

Abstract: A method, system, and computer usable program product for isolating a workload partition space are provided in the illustrative embodiments. A boot process of a workload partition in a data processing system is started using a scratch file system, the scratch file system being in a global space. A portion of a storage device containing a file system for the workload partition is exported to the workload partition, the portion forming an exported disk. The partially booted up workload partition may discover the exported disk. The exporting causes an association between the global space and the exported disk to either not form, or sever. The exporting places the exported disk in a workload partition space associated with the workload partition. The boot process is transitioned to stop using the scratch file system and start using the data in the exported disk for continuing the boot process.

Abstract: A mechanism is provided for isolation of device namespace to allow duplicate or common names in root volume group workload partitions. The mechanism creates a scratch file system that contains enough information to create an execution environment for a workload partition and information about which physical volumes to use for the root volume group file systems. The mechanism then populates the root file systems on a disk in the global space. The mechanism boots the workload partition from the scratch file system and configures the devices to be exported to the workload partition based information in the scratch file system. The mechanism then renames the logical volume names to the traditional names. The mechanism then temporarily mounts the root volume group file system onto the scratch file system.

Abstract: In a computer system divided into multiple separate workload partitions, wherein at least one of the partitions contains multiple applications, and a loopback interface is made available to each partition, a method is provided for routing packets from one application to another application. In one embodiment of the invention, each packet to be routed from one application to another application in the same home partition comprises a first packet, and all other packets comprise second packets. The method comprises the steps of assigning the same pre-specified IP address to each of the first packets, and routing each of the first packets from its home partition to a loopback interface at the IP network processing layer. The method further includes marking the first packets to identify the home partition of each first packet, and directing the marked first packets to a mechanism configured to deliver each first packet only to its home partition, in response to the markings.

Abstract: A method, system, and computer usable program product for isolating a workload partition space are provided in the illustrative embodiments. A boot process of a workload partition in a data processing system is started using a scratch file system, the scratch file system being in a global space. A portion of a storage device containing a file system for the workload partition is exported to the workload partition, the portion forming an exported disk. The partially booted up workload partition may discover the exported disk. The exporting causes an association between the global space and the exported disk to either not form, or sever. The exporting places the exported disk in a workload partition space associated with the workload partition. The boot process is transitioned to stop using the scratch file system and start using the data in the exported disk for continuing the boot process.

Abstract: A system to improve a user-space environment may include a user-space configured to execute on an operating system-level virtualization. The system may also include a boot module configured to boot up the user-space on the operating system-level virtualization without disrupting the operating system-level virtualization even if the operating system-level virtualization is already running.

Abstract: Computer implemented methods, data processing systems and computer program products install deliverables into user-specified install locations. A user-specified install location is provided. Software virtual product data is extracted from a software bundle. Software virtual product data is stored within the user-specified install location.

Abstract: A method is disclosed to assign Priority to Processes based on Roles. The method calculates the process priority of the process using a scheduler running in the computer system, based on either a first weight of a first role, a second weight of a second role, or a calculated weight if both the first and second roles can unlock access to the process. The method then assigns a share of the computer system's time to the process, the share of time being based on the process priority calculated for the process.