Predefined IBM LPAR parameters
If you created an IBM LPAR Virtual Guest Package (VGP) with BMC Service Automation, BMC Cloud Lifecycle Management provides predefined LPAR parameters that you can use with your service blueprint.
The following figure illustrates parameters from the VGP that you can add to the service blueprint to override the default VGP values. 
For example, the BmcLparSharedCpuMaxProcUnits of 1.5 overrides the VGP's .5 default. These parameters are created and applied in the service deployment definition at the time when the service blueprint is created. If you enable User Entry, these parameters are then displayed to end-users in the requestable offering.
You can also configure the IBM VGP package with service catalog option choices so that end-users can modify, for example, the Desired, Min, or Max Processing Units when they provision the VM. For more information, see:
- Service-Catalog-options-and-option-choices
- Configuring-end-user-Option-Choices-in-service-blueprints
- Configuring optional parameters
Parameter name | Label | Description | Datatype | Possible | Remarks |
|---|---|---|---|---|---|
BmcLparCpuMode | CPU mode (shared / dedicated) | Used to specify processor type. | String | shared / dedicated | BmcLparCpuMode is mandatory if you use an IBM LPAR VGP in your service blueprint. |
BmcLparCpuMinProcs | Minimum processors | Applicable for both shared and dedicated processors. | Numeric |
| Optional |
BmcLparCpuMaxProcs | Maximum processors | Applicable for both shared and dedicated processors. | Numeric |
| Optional |
BmcLparSharedCpuMinProcUnits | Shared CPU minimum processing units | Applicable for shared processors only. | Numeric | 0.5 | Optional |
BmcLparSharedCpuMaxProcUnits | Shared CPU maximum processor units | Applicable for shared processors only. | Numeric | 1.5 | Optional |
BmcLparSharedCpuDesiredProcUnits | Shared CPU desired processor units | Applicable for shared processors only. | Numeric | 1.0 | Optional |
BmcLparMemoryMode | Memory mode | Used to specify memory type. | String | shared / dedicated | BmcLparMemoryMode is mandatory if you use an IBM LPAR VGP in your service blueprint. |
BmcLparMinMemory | Minimum memory | Applicable for both shared and dedicated memory. | Numeric |
| Optional |
BmcLparMaxMemory | Maximum memory | Applicable for both shared and dedicated memory. | Numeric |
| Optional |
BmcLparSharedMemoryIOEntitiledMemory | IO entitled memory | Applicable for shared memory only. | Numeric |
| Optional |
BmcLparSharedMemoryWeight | Shared memory weight | Applicable for shared memory only. | Numeric |
| Optional |
BmcLparDesiredMemory Note: This parameter was added in version 3.1 SP1 Hotfix 5 | Desired memory | Applicable for shared memory only. Sets the guaranteed amount of memory for each LPAR. | Integer (in MB) |
| Optional |
BmcLparCpuDesiredProcs Note: This parameter was added in version 3.1 SP1 Hotfix 5 | Desired CPU processors | Applicable for shared processors only. Sets the guaranteed amount of processor cycles for each LPAR. | Interger |
| Optional |
BmcLparSharedCpuUncappedWeight Note: This parameter was added in version 3.1 SP1 Hotfix 5 | Shared CPU uncapped weight | Applicable for shared processors only. Number that indicates how to distribute shared processing power relative to other uncapped systems. | Numeric (between 0 and 255) |
| Optional If you specify this parameter, the Uncapped checkbox is selected in the VGP and the corresponding Uncapped weight field is set. |
Where to go from here