Create a group

post/compute-ops-mgmt/v1/groups

Create a group for a specific user.

SecurityBearer
Request
header Parameters
Content-Type
required
string

Content-Type header must designate 'application/json' in order for the request to be performed.

Value: "application/json"
Request Body schema: application/json
required
name
required
string [ 1 .. 100 ] characters
description
string <= 10000 characters
deviceType
required
string (deviceType)

Device type of all devices in the group.

  • DIRECT_CONNECT_SERVER - servers
  • OVE_APPLIANCE_SYNERGY - OneView Synergy appliances
  • OVE_APPLIANCE_VM - OneView VM appliances

Note: Depending on the deviceType the response payload will change. Selecting the dropdown to change the deviceType will change the response details.

settingsUris
Array of strings
Default: []

URIs for group device settings

object (groupServerPolicies-v1)

Store policy settings for server group actions.

autoAddTags
object

A case insensitive tag that can be associated with a group to automatically add devices to the group. A group can have a maximum of one tag and multiple groups can not have the same tag.

When a device is onboarded or has its tags changed, the devices's tags will be checked against the group's autoAddTags. If at least one of the device tags matches one group's autoAddTags, the device will be placed into the associated group. Once a device has been connected, it becomes ineligible for automatically being placed into groups, even if it is later disconnected.

If a device's tags match more than one group, it will not be put into any group.

If a devices is in a group, any further tag changes will not move it to another group. If the device was added to a group but has been removed, is not in any group, and still has not been activated, changing the device tags will automatically assign it to the matching group.

Tags can contain any alphaneumeric characters, any Unicode space separators, and the following characters: _ . : = + - @. An example of one of these tags can be seen in the sample request on this page.

Responses
201

Successful Response

400

Bad request

401

Unauthorized

403

Forbidden

406

Not acceptable

409

Conflict

415

Unsupported media type

500

Internal server error

Request samples
application/json
{
  • "name": "Production Group",
  • "description": "All prod servers",
  • "deviceType": "DIRECT_CONNECT_SERVER",
  • "settingsUris": [
    ],
  • "policies": {
    },
  • "autoAddTags": {
    }
}
Response samples
application/json
{
  • "deviceType": "DIRECT_CONNECT_SERVER",
  • "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
  • "name": "Production Group",
  • "type": "compute-mgmt-ops/group",
  • "description": "All prod servers",
  • "complianceStatus": "COMPLIANT",
  • "settingsUris": [
    ],
  • "devicesUri": "/compute-ops-mgmt/v1/groups/6081a383-b9e5-45e3-8371-1e0ba7b72068/devices",
  • "devices": [ ],
  • "policies": {
    },
  • "autoAddTags": {
    },
  • "securityStatus": "RISK",
  • "groupCompliance": {
    },
  • "resourceUri": "/compute-ops-mgmt/v1/groups/0e7f516c-0829-4135-83d6-09ce844ddd9d",
  • "generation": 1,
  • "createdAt": "2019-08-24T14:15:22Z",
  • "updatedAt": "2019-08-24T14:15:22Z"
}