Modifies the cloud capacity settings for a private cloud.
Description
The Set-SCCloudCapacity cmdlet modifies the cloud capacity settings for a private cloud in System Center Virtual Machine Manager (VMM). You can update the following cloud capacity dimensions:
- virtual machines
- virtual CPUs
- custom quota points
- storage (GB)
- memory (MB)
Alternatively, you can set any or all of the dimensions to use the maximum capacity.
For more information about Set-SCCloudCapacity, type: "Get-Help Set-SCCloudCapacity -online".
Parameters
CloudCapacity
Required?
false
Accept Pipeline Input?
false
Position?
named
Specifies a cloud capacity object.
Confirm
Required?
false
Accept Pipeline Input?
false
Position?
named
Prompts for confirmation before running the command.
CPUCount
Required?
false
Accept Pipeline Input?
false
Position?
named
Specifies the number of virtual CPUs for a user role quota or cloud capacity.
CustomQuotaCount
Required?
false
Accept Pipeline Input?
false
Position?
named
Specifies the number of custom quota points for a user role quota or cloud capacity.
JobVariable
Required?
false
Accept Pipeline Input?
false
Position?
named
Specifies that job progress is tracked and stored in the variable named by this parameter.
MemoryMB
Required?
false
Accept Pipeline Input?
false
Position?
named
Specifies the amount of memory in megabytes (MB) for a user role quota or cloud capacity.
PROTipID
Required?
false
Accept Pipeline Input?
false
Position?
named
Specifies the ID of the PRO tip that triggered this action. This allows for auditing of PRO tips.
RunAsynchronously
Required?
false
Accept Pipeline Input?
false
Position?
named
Indicates that the job runs asynchronously so that control returns to the command shell immediately.
StorageGB
Required?
false
Accept Pipeline Input?
false
Position?
named
Specifies the amount of storage in gigabytes (GB) for a user role quota or cloud capacity. This storage amount does not include library storage.
UseCPUCountMaximum
Required?
false
Accept Pipeline Input?
false
Position?
named
Indicates that the maximum number of virtual CPUs is allowed for a user role or cloud capacity. When this parameter is used, no quota is enforced for the virtual CPU dimension.
UseCustomQuotaCountMaximum
Required?
false
Accept Pipeline Input?
false
Position?
named
Indicates that the maximum number of custom quota points is allowed for a user role or cloud capacity. When this parameter is used, no quota is enforced for the custom quota dimension.
UseMemoryMBMaximum
Required?
false
Accept Pipeline Input?
false
Position?
named
Indicates that the maximum amount of memory, in megabytes (MB), is allowed for a user role or cloud capacity. When this parameter is used, no quota is enforced for the memory dimension.
UseStorageGBMaximum
Required?
false
Accept Pipeline Input?
false
Position?
named
Indicates that the maximum amount of storage, in gigabytes (GB), is allowed for a user role or cloud capacity. When this parameter is used, no quota is enforced for the storage dimension.
UseVMCountMaximum
Required?
false
Accept Pipeline Input?
false
Position?
named
Indicates that the maximum number of virtual machines is allowed for a user role or cloud capacity. When this parameter is used, no quota is enforced for the virtual machine dimension.
VMCount
Required?
false
Accept Pipeline Input?
false
Position?
named
Specifies the number of virtual machines for a user role quota or cloud capacity.
VMMServer
Required?
false
Accept Pipeline Input?
false
Position?
named
Specifies a VMM server object.
JobGroup
Required?
true
Accept Pipeline Input?
false
Position?
named
Specifies an identifier for a series of commands that will run as a set just before the final command that includes the same job group identifier runs.
Confirm
Required?
false
Accept Pipeline Input?
false
Position?
named
Prompts for confirmation before running the command.
CPUCount
Required?
false
Accept Pipeline Input?
false
Position?
named
Specifies the number of virtual CPUs for a user role quota or cloud capacity.
CustomQuotaCount
Required?
false
Accept Pipeline Input?
false
Position?
named
Specifies the number of custom quota points for a user role quota or cloud capacity.
JobVariable
Required?
false
Accept Pipeline Input?
false
Position?
named
Specifies that job progress is tracked and stored in the variable named by this parameter.
MemoryMB
Required?
false
Accept Pipeline Input?
false
Position?
named
Specifies the amount of memory in megabytes (MB) for a user role quota or cloud capacity.
PROTipID
Required?
false
Accept Pipeline Input?
false
Position?
named
Specifies the ID of the PRO tip that triggered this action. This allows for auditing of PRO tips.
RunAsynchronously
Required?
false
Accept Pipeline Input?
false
Position?
named
Indicates that the job runs asynchronously so that control returns to the command shell immediately.
StorageGB
Required?
false
Accept Pipeline Input?
false
Position?
named
Specifies the amount of storage in gigabytes (GB) for a user role quota or cloud capacity. This storage amount does not include library storage.
UseCPUCountMaximum
Required?
false
Accept Pipeline Input?
false
Position?
named
Indicates that the maximum number of virtual CPUs is allowed for a user role or cloud capacity. When this parameter is used, no quota is enforced for the virtual CPU dimension.
UseCustomQuotaCountMaximum
Required?
false
Accept Pipeline Input?
false
Position?
named
Indicates that the maximum number of custom quota points is allowed for a user role or cloud capacity. When this parameter is used, no quota is enforced for the custom quota dimension.
UseMemoryMBMaximum
Required?
false
Accept Pipeline Input?
false
Position?
named
Indicates that the maximum amount of memory, in megabytes (MB), is allowed for a user role or cloud capacity. When this parameter is used, no quota is enforced for the memory dimension.
UseStorageGBMaximum
Required?
false
Accept Pipeline Input?
false
Position?
named
Indicates that the maximum amount of storage, in gigabytes (GB), is allowed for a user role or cloud capacity. When this parameter is used, no quota is enforced for the storage dimension.
UseVMCountMaximum
Required?
false
Accept Pipeline Input?
false
Position?
named
Indicates that the maximum number of virtual machines is allowed for a user role or cloud capacity. When this parameter is used, no quota is enforced for the virtual machine dimension.
VMCount
Required?
false
Accept Pipeline Input?
false
Position?
named
Specifies the number of virtual machines for a user role quota or cloud capacity.
VMMServer
Required?
false
Accept Pipeline Input?
false
Position?
named
Specifies a VMM server object.
Examples
1: Change the cloud capacity
properties of a specified cloud.
The first command gets the private cloud object named Cloud01 and stores the object in the $Cloud variable.
The second command gets the cloud capacity for the private cloud stored in $Cloud and stores it in the $CloudCapacity variable.
The last command indicates that there should be a limit placed on the virtual CPU count for the cloud capacity stored in $CloudCapacity, and changes the virtual CPU count capacity to 20.
2: Change the cloud capacity
properties of a specific private cloud using a job group.
The first command creates a new GUID and stores it in the $Guid variable. Subsequent commands that include this GUID are collected into a single job group.
The second command gets the private cloud object named Cloud02 and stores the object in the $Cloud variable.
The third command gets the cloud capacity object for the private cloud stored in $cloud and stores the object in the $CloudCapacity variable.
The fourth command sets a limit of 50 virtual machines, 100 virtual CPUs and 500 GB of storage on the cloud capacity. Using the JobGroup parameter specifies tha this command will not run until just before the final command that includes the JobGroup with the same GUID.
The last command sets the capacity properties on the private cloud stored in $Cloud using the settings that were specified in the fourth command. This command uses the JobGroup parameter to run Set-SCCloudCapacity just before Set-SCCloud runs so that the settings will be assocated with the specified private cloud.