Bare Metal Server (BMS)

The Organizations service provides Service Control Policies (SCPs) to set access control policies.

SCPs do not actually grant any permissions to an entity. They only set the permissions boundary for the entity. When SCPs are attached to a member account or an organizational unit (OU), they do not directly grant permissions to that member account or OU. Instead, the SCPs just determine what permissions are available for that member account or the member accounts under that OU.

This section describes the elements used by Organizations SCPs. The elements include actions, resources, and conditions.

For details about how to use these elements to create a custom SCP, see Creating an SCP.

Actions

Actions are specific operations that are allowed or denied in an SCP.

The Access Level column describes how the action is classified (List, Read, or Write). This classification helps you understand the level of access that an action grants when you use it in an SCP.
The Resource Type column indicates whether the action supports resource-level permissions.
- You can use a wildcard (*) to indicate all resource types. If this column is empty (-), the action does not support resource-level permissions, and you must specify all resources ("*") in your SCP statements.
- If this column includes a resource type, you must specify the URN in the Resource element of your statements.
- Required resources are marked with asterisks (*) in the table. If you specify a resource in a statement using this action, then it must be of this type.
For details about the resource types defined by BMS, see Resources.
The Condition Key column contains keys that you can specify in the Condition element of an SCP statement.
- If the Resource Type column has values for an action, the condition key takes effect only for the listed resource types.
- If the Resource Type column is empty (-) for an action, the condition key takes effect for all resources that action supports.
- If the Condition Key column of an action is empty (-), the action does not support any condition keys.
For details about the condition keys defined by BMS, see Conditions.

The following table lists the actions that you can define in SCP statements for BMS.

**Table 1** Actions supported by BMS
Action	Description	Access Level	Resource Type (*: required)	Condition Key
bms:servers:updateBaremetalServer	Grants permission to modify BMSs.	write	instance*	g:EnterpriseProjectId g:ResourceTag/<tag-key>
bms:servers:showBaremetalServerInterfaceAttachments	Grants permission to query BMS NICs.	read	instance*	g:EnterpriseProjectId g:ResourceTag/<tag-key>
bms:servers:resetServerPwd	Grants permission to reset a BMS password with a few clicks.	write	instance*	g:EnterpriseProjectId g:ResourceTag/<tag-key>
bms:servers:showResetPasswordFlag	Grants permission to check whether BMS passwords can be reset with a few clicks.	read	instance*	g:EnterpriseProjectId g:ResourceTag/<tag-key>
bms:servers:showWindowsBaremetalServerPwd	Grants permission to obtain Windows BMS passwords.	read	instance*	g:EnterpriseProjectId g:ResourceTag/<tag-key>
bms:servers:deletePassword	Grants permission to delete Windows BMS passwords.	write	instance*	g:EnterpriseProjectId g:ResourceTag/<tag-key>
bms:servers:showBaremetalServerVolumeInfo	Grants permission to query EVS disks attached to a BMS.	read	instance*	g:EnterpriseProjectId g:ResourceTag/<tag-key>
bms:servers:create	Grants permission to create BMSs.	write	-	g:EnterpriseProjectId g:TagKeys g:RequestTag/<tag-key>
bms:servers:showBaremetalServer	Grants permission to query details about a BMS.	read	instance*	g:EnterpriseProjectId g:ResourceTag/<tag-key>
bms:servers:attachVolume	Grants permission to attach EVS disks to a BMS.	write	instance*	g:EnterpriseProjectId g:ResourceTag/<tag-key>
bms:servers:detachVolume	Grants permission to detach EVS disks from a BMS.	write	instance*	g:EnterpriseProjectId g:ResourceTag/<tag-key>
bms:servers:updateMetadata	Grants permission to update BMS metadata.	write	instance*	g:EnterpriseProjectId g:ResourceTag/<tag-key>
bms:servers:reInstallOS	Grants permission to reinstall a BMS OS.	write	instance*	g:EnterpriseProjectId g:ResourceTag/<tag-key>
bms:servers:showBaremetalServerTags	Grants permission to query BMS tags.	read	instance*	g:EnterpriseProjectId g:ResourceTag/<tag-key>
bms:servers:start	Grants permission to start BMSs in a batch.	write	instance*	g:EnterpriseProjectId g:ResourceTag/<tag-key>
bms:servers:reboot	Grants permission to restart BMSs in a batch.	write	instance*	g:EnterpriseProjectId g:ResourceTag/<tag-key>
bms:servers:stop	Grants permission to stop BMSs in a batch.	write	instance*	g:EnterpriseProjectId g:ResourceTag/<tag-key>
bms:servers:list	Grants permission to query BMS details.	list	-	g:EnterpriseProjectId
bms:serverFlavors:get	Grants permission to query flavor details and extended flavor information.	list	-	-
bms:serverQuotas:get	Grants permission to query tenant quotas.	read	-	-
bms:servers:batchCreateBaremetalServerTags	Grants permission to add tags in a batch.	write	instance*	g:RequestTag/<tag-key> g:TagKeys g:EnterpriseProjectId
bms:servers:batchDeleteBaremetalServerTags	Grants permission to delete tags in a batch.	write	instance*	g:RequestTag/<tag-key> g:TagKeys g:EnterpriseProjectId
bms:servers:addNics	Grants permission to bind NICs to a BMS.	write	instance*	g:EnterpriseProjectId g:ResourceTag/<tag-key>
bms:server:deleteNics	Grants permission to unbind NICs from a BMS.	write	instance*	g:EnterpriseProjectId g:ResourceTag/<tag-key>
bms:servers:serialConsole	Grants permission to obtain an address for remotely logging in to a BMS.	read	instance*	g:EnterpriseProjectId g:ResourceTag/<tag-key>
bms:server:updateInterface	Grants permission to modify BMS NICs.	write	instance*	g:EnterpriseProjectId g:ResourceTag/<tag-key>

Each API of BMS usually supports one or more actions. Table 2 lists the supported actions and dependencies.

**Table 2** Actions and dependencies supported by BMS APIs
API	Action	Dependencies
PUT /v1/{project_id}/baremetalservers/{server_id}	bms:servers:updateBaremetalServer	-
GET /v1/{project_id}/baremetalservers/{server_id}/os-interface	bms:servers:showBaremetalServerInterfaceAttachments	-
PUT /v1/{project_id}/baremetalservers/{server_id}/os-reset-password	bms:servers:resetServerPwd	-
GET /v1/{project_id}/baremetalservers/{server_id}/os-resetpwd-flag	bms:servers:showResetPasswordFlag	-
GET /v1/{project_id}/baremetalservers/{server_id}/os-server-password	bms:servers:showWindowsBaremetalServerPwd	-
DELETE /v1/{project_id}/baremetalservers/{server_id}/os-server-password	bms:servers:deletePassword	-
GET /v1/{project_id}/baremetalservers/{server_id}/os-volume_attachments	bms:servers:showBaremetalServerVolumeInfo	-
POST /v1/{project_id}/baremetalservers	bms:servers:create	-
GET /v1/{project_id}/baremetalservers/{server_id}	bms:servers:showBaremetalServer	-
POST /v1/{project_id}/baremetalservers/{server_id}/attachvolume	bms:servers:attachVolume	evs:volumes:use
DELETE /v1/{project_id}/baremetalservers/{server_id}/detachvolume/{attachment_id}	bms:servers:detachVolume	-
POST /v1/{project_id}/baremetalservers/{server_id}/metadata	bms:servers:updateMetadata	-
POST /v1/{project_id}/baremetalservers/{server_id}/reinstallos	bms:servers:reInstallOS	-
GET /v1/{project_id}/baremetalservers/{server_id}/tags	bms:servers:showBaremetalServerTags	-
POST /v1/{project_id}/baremetalservers/action	bms:servers:start	-
POST /v1/{project_id}/baremetalservers/action	bms:servers:reboot	-
POST /v1/{project_id}/baremetalservers/action	bms:servers:stop	-
GET /v1/{project_id}/baremetalservers/detail	bms:servers:list	-
GET /v1/{project_id}/baremetalservers/flavors	bms:serverFlavors:get	-
GET /v1/{project_id}/baremetalservers/limits	bms:serverQuotas:get	-
POST /v1/{project_id}/baremetalservers/{server_id}/tags/action	bms:servers:batchCreateBaremetalServerTags	-
POST /v1/{project_id}/baremetalservers/{server_id}/tags/action	bms:servers:batchDeleteBaremetalServerTags	-
POST /v1/{project_id}/baremetalservers/{server_id}/nics	bms:servers:addNics	-
POST /v1/{project_id}/baremetalservers/{server_id}/nics/delete	bms:server:deleteNics	-
POST /v1/{project_id}/baremetalservers/{server_id}/remote_console	bms:servers:serialConsole	-
PUT /v1/{project_id}/baremetalservers/{server_id}/os-interface/{port_id}	bms:server:updateInterface	-

Resources

A resource type indicates the resources that an SCP applies to. If you specify a resource type for any action in Table 3, the resource URN must be specified in the SCP statements using that action, and the SCP applies only to resources of this type. If no resource type is specified, the Resource element is marked with an asterisk (*) and the SCP applies to all resources. You can also set condition keys in an SCP to define resource types.

The following table lists the resource types that you can define in SCP statements for BMS.

**Table 3** Resource types supported by BMS
Resource Type	URN
instance	bms:<region>:<account-id>:instance:<server-id>

<region> indicates the region where a user is authorized to perform operations.
<account-id> indicates the ID of an authorized user account. Obtain an account ID as instructed in API Credentials.
<server-id>: indicates the ID of the BMS on which operations will be performed.