Skip to main content

We've Moved!

Product Documentation has moved to docs.hitachivantara.com
Hitachi Vantara Knowledge

Ops Center Automator user responsibilities and workflows

There are two main storage administrator user categories in Ops Center Automator: Service Administrator and Service User. In addition to the user type, Ops Center Automatorprovides user roles (Admin, Develop, Modify, Submit). To understand the responsibilities of each user role, review the workflow for each.

User responsibilities

In addition to the system administrator and security administrator, Ops Center Automator gives two global user roles for storage administrators: service administrator and service user.

Security administrator

If you log on with Hitachi Ops Center, the security administrator is responsible for user management such as creating, editing, deleting users and user groups.

System administrator

After installing Ops Center Automator, the system administrator completes the initial setup tasks of creating pools, discovering storage systems, registering hosts, creating users and defining user permissions. When the initial setup is complete, the service administrator and service user take over management of the system.

Service administrator

The service administrator is an administrator who has advanced knowledge of data center functions and is responsible for managing end-to-end IT infrastructure including prioritizing and routing service requests to service users, attending to all critical service requests, and meeting Service Level Objectives (SLO). In Ops Center Automator, this type of storage administrator is responsible for creating and managing all automation services and delegating the responsibility of running services to service users as needed.

Service user

The service user is an administrator who is responsible for the management of automation requests, which consists of submitting and verifying the completion of automation services and monitoring all pending and scheduled tasks.

User Actions

The actions that users can complete after the initial setup depend on the Ops Center Automator user role as follows.

Users Available Actions Ops Center Automator User Roles

System administrators

Modify shared property settings.

Create users and user groups.

Create service groups and associate services with the groups.

Create infrastructure groups and add storage resources with the groups.

Associate infrastructure groups with service groups to enable the services in the service groups to use resources in the infrastructure groups.

Admin

Service administrators

Service users

Create requests.

Stop tasks.

Suspend schedules.

Cancel schedules.

Resume schedules.

Resubmit tasks.

Admin, Develop, Modify, or Submit

Service administrators

Archive tasks.

Create services.

Edit services.

Admin, Develop, or Modify

Service administrators

Service Builder actions:

Create, modify, build, and release templates and plug-ins.

Admin or Develop

Operational workflow for service administrators and service users

The following figure shows the basic prerequisite tasks and high-level flow of operations for a service administrator.

Prerequisite tasks for a service administrator.

The following figure shows the high-level flow of operations for a service user.

Operation tasks of a service user

Admin user workflow

The Admin user configures Ops Center Automator.

The Admin user role is the only one that confers access to the Administration tab and the Admin user is responsible for configuring Ops Center Automator. The Admin user also has access to all parts of Ops Center Automator and Service Builder.

The Admin user workflow in the Administration tab is as follows:

  1. Log on to Ops Center Automator.
  2. Click the Administration tab.
  3. Connect to one or more instances of Configuration Manager.
  4. Configure remote connections as needed.
  5. Create users. This step is not necessary if you have integrated users from Common Services.
  6. Configure user groups, if needed. Ops Center Automator includes four built-in user groups.
  7. Create infrastructure groups and assign resources to them. If necessary, you can also assign Web Service Connections and remote connections to infrastructure groups.
  8. Create service groups and associate user groups with service groups. This step also assigns the user role (Admin, Develop, Modify, Submit) associated with the user group.
  9. Associate infrastructure groups with the service groups to enable the services in the service group to use the resources in the infrastructure groups.

Develop user workflow

The Develop user creates service templates in Service Builder and tests them in Ops Center Automator before releasing them for use.

Much of the Develop user's workflow takes place in Service Builder. The Develop user has access to all parts of Ops Center Automator except the Administration tab.

The Develop user workflow is as follows:

  1. Log on to Ops Center Automator and start Service Builder.
  2. Create or modify a service template in Service Builder.
  3. Build the service template in Service Builder.
  4. Test the service template in Ops Center Automator.

    At this point the template in not available for use.

  5. Release the template from Service Builder.

    After the template is released, you can access it in Ops Center Automator and use it to create services.

Modify user workflow

The Modify user creates and tests services and is typically a service administrator.

The Modify user role is designed to enable expert users to create services from within their service groups. This means that the Modify user can only create services that are in the service group that is associated with the Modify user's user group.

The Modify user can access the Dashboard, the Services tab, the Tasks tab and the Service Templates tab.

The Modify user workflow is as follows:

  1. Log on to Ops Center Automator and access the Service Templates tab to find a service template.

    The Modify user can only view service templates that are released.

  2. Locate a service template that matches the service requirements.
  3. Use the service template to create a service.
  4. Test the service.
  5. Release the service for use.

Submit user workflow

The Submit user role is a user of services created by the Modify user.

The Submit user can only access services that have already been released and does not have access to the Debug tab in the Tasks tab. The Submit user can access the Dashboard, the Services tab and the Tasks tab.

The workflow for the Submit user is as follows:

  1. Log on to Ops Center Automator and access the Services tab.
  2. Select the service that you want to submit and create a request. Submit the service.
  3. Click the Tasks tab to verify that tasks associated with the service are in the Tasks tab.
  4. (Optional) Monitor the tasks and their status.

For more information on these workflows, including examples, see the video tutorial for Setting Up and Submitting a Hitachi Automation Director Smart Provisioning Service.