-
Notifications
You must be signed in to change notification settings - Fork 52
New HPOVScope
Create new Scope.
New-HPOVScope [-Name] <String>[ [-Description] <String>][ [-ApplianceConnection] <Object>] [<CommonParameters>]A scope is a grouping of resources that can be used to restrict the range of an operation or action. For example, you can create scopes based on:
* Organizations (Marketing, Research and Development, Finance)
* Usage (Production, Development, Testing)
* Skills (Linux, Windows)
The resources are arranged by categories. All the resources in these categories can be added to or removed from a scope:
* Enclosures
* Server Hardware
* Networks (Ethernet, FC, and FCoE)
* Network Sets
* Interconnects, excluding SAS resources
* Logical Interconnects, excluding SAS resources
* Logical Interconnect Groups, excluding SAS resources
* Switches
* Logical Switches
* Logical Switch Groups
NOTE: Resources in other categories are considered to be included in all scopes, and they cannot be removed.
When scopes are defined and resources assigned to them, you can:
* Restrict your view of the user interface (UI) to the resources in the scope.
* Filter email notifications for alerts based on the scope of the associated resources.
Minimum required privileges: Infrastructure administrator
-ApplianceConnection <Object>
Aliases [-Appliance]
Specify one or more HPOneView.Appliance.Connection object(s) or Name property value(s).
Default Value: ${Global:ConnectedSessions} | ? Default
| Aliases | Appliance |
| Required? | false |
| Position? | named |
| Default value | (${Global:ConnectedSessions} | ? Default) |
| Accept pipeline input? | false |
| Accept wildcard characters? | False |
-Description <String>
Administrator account of the target iLO.
| Aliases | None |
| Required? | false |
| Position? | named |
| Default value | |
| Accept pipeline input? | false |
| Accept wildcard characters? | False |
-Name <String>
Name of the scope to create.
| Aliases | None |
| Required? | true |
| Position? | named |
| Default value | |
| Accept pipeline input? | false |
| Accept wildcard characters? | False |
<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)
None. You cannot pipe objects to this cmdlet.
HPOneView.Appliance.Scope [System.Management.Automation.PSCustomObject]
Appliance Scope resource object.
-------------------------- EXAMPLE 1 --------------------------New-HPOVScope -Name MyFinanceScope
Create a "MyFinanceScope" for the default appliance connection.
-------------------------- EXAMPLE 2 --------------------------New-HPOVScope -Name MyFinanceScope -Descrition "Finance Scope of resources"
Create a "MyFinanceScope" with a descrition for the default appliance connection.
-------------------------- EXAMPLE 3 --------------------------New-HPOVScope -Name MyFinanceScope -Descrition "Finance Scope of resources" -ApplianceConnection $ConnectedSessions
Create a "MyFinanceScope" with a descrition for all appliance connections.
Create new Scope.
New-HPOVScope [-Name] <String>[ [-Description] <String>][ [-ApplianceConnection] <Object>] [<CommonParameters>]A scope is a grouping of resources that can be used to restrict the range of an operation or action. For example, you can create scopes based on:
* Organizations (Marketing, Research and Development, Finance)
* Usage (Production, Development, Testing)
* Skills (Linux, Windows)
The resources are arranged by categories. All the resources in these categories can be added to or removed from a scope:
* Enclosures
* Server Hardware
* Networks (Ethernet, FC, and FCoE)
* Network Sets
* Interconnects, excluding SAS resources
* Logical Interconnects, excluding SAS resources
* Logical Interconnect Groups, excluding SAS resources
* Switches
* Logical Switches
* Logical Switch Groups
NOTE: Resources in other categories are considered to be included in all scopes, and they cannot be removed.
When scopes are defined and resources assigned to them, you can:
* Restrict your view of the user interface (UI) to the resources in the scope.
* Filter email notifications for alerts based on the scope of the associated resources.
Minimum required privileges: Infrastructure administrator
-ApplianceConnection <Object>
Aliases [-Appliance]
Specify one or more HPOneView.Appliance.Connection object(s) or Name property value(s).
Default Value: ${Global:ConnectedSessions} | ? Default
| Aliases | Appliance |
| Required? | false |
| Position? | named |
| Default value | (${Global:ConnectedSessions} | ? Default) |
| Accept pipeline input? | false |
| Accept wildcard characters? | False |
-Description <String>
Administrator account of the target iLO.
| Aliases | None |
| Required? | false |
| Position? | named |
| Default value | |
| Accept pipeline input? | false |
| Accept wildcard characters? | False |
-Name <String>
Name of the scope to create.
| Aliases | None |
| Required? | true |
| Position? | named |
| Default value | |
| Accept pipeline input? | false |
| Accept wildcard characters? | False |
<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)
None. You cannot pipe objects to this cmdlet.
HPOneView.Appliance.Scope [System.Management.Automation.PSCustomObject]
Appliance Scope resource object.
-------------------------- EXAMPLE 1 --------------------------New-HPOVScope -Name MyFinanceScope
Create a 'MyFinanceScope' for the default appliance connection.
-------------------------- EXAMPLE 2 --------------------------New-HPOVScope -Name MyFinanceScope -Descrition 'Finance Scope of resources'
Create a 'MyFinanceScope' with a descrition for the default appliance connection.
-------------------------- EXAMPLE 3 --------------------------New-HPOVScope -Name MyFinanceScope -Descrition 'Finance Scope of resources' -ApplianceConnection $ConnectedSessions
Create a 'MyFinanceScope' with a descrition for all appliance connections.