API Guide

Table 4. Roles and associated privileges for OME - Modular(continued)

Privilege Roles

CHASSIS_ADMINI

STRATOR

COMPUTE_MANA

GER

STORAGE_MANA

GER

FABRIC_MANAGE

VIEWER

NETWORK_MANA

GEMENT

Y Y Y

OME

Table 5. Roles and associated privileges for OME

Privilege Roles

ADMINISTRATOR DEVICE_MANAGER VIEWER

APPLIANCE_SETUP Y

BASELINE_MANAGEMENT Y

DEVICE_CONFIGURATION Y Y

DEVICE_UPDATE Y Y

DISCOVERY_MANAGEMENT Y

GROUP_MANAGEMENT Y Y

INVENTORY_MANAGEMENT Y

JOB_MANAGEMENT Y Y

MONITORING_SETUP Y Y

OPERATING_SYSTEM_DEPLO

YMENT

Y Y

POWER_CONTROL Y Y

POWER_MANAGEMENT Y Y

REPORT_MANAGEMENT Y Y

REPORT_RUN Y Y Y

SECURITY_SETUP Y

TEMPLATE_MANAGEMENT Y Y

TRAP_MANAGEMENT Y

VIEW Y Y Y

Resource addressing

Each managed resource must be uniquely addressable using a distinct URI. The URI syntax must be intuitive and should indicate the

relationships with a parent resource.

There are several ways to address specific resources either as instances of specific resource classes or within an associated parent

context.

Following is the format of a resource URI:

<BASE_URI>/<resource class identifier>/<resource instance identifier>

Key integration concepts