UMRCP requests that come in from new users will have up to three storage requests:

• Data Den
• Non-sensitive Turbo volume
• Sensitive Turbo volume

The following is an process of handling storage volumes for UMRCP requests.

1. Check the department of the requestor. Depending on where the requestor is from will determine which steps below you need to complete. For any entry on this page - List of unit attributes for major schools and colleges at UM - that includes an email address in the TDxGroup or Email column skip to number 3.
2. Create a task on the ticket to request an Active Directory group for each volume requested. 
   1. For all departments/schools besides LSA title the task as  - *Please create the following AD groups for <requestor uniqname>. *For LSA the task title should be - Storage request for <requestor uniqname>
   2. Inside the task make a list of the following for each volume:
      1. AD group name. This will be shown in the mcommunity group: line listed for each volume. 
      2. The GID for the AD group. This can be found by running the following command on gl-build:
         1. /usr/arcts/systems/scripts/get_ldap_gid <mcommunity group name>
      3. The list of users that are to have access to the volume. This can be found on this line DataDen users: or *Turbo users:
      4. The information should look like this
         1. New <volume type> request -
         2. AD group = dept-uniqname-volumetype
         3. GID = xxxxxxxxxxxx
         4. Users = bleh blah 
   3. Assign the task to the appropriate TDx group as shown in this table - List of unit attributes for major schools and colleges at UM
   4. Set the ticket to Awaiting Third Party and make a note the you are waiting for AD groups to be created
   5. Alert the appropriate unit support group in Slack if possible (ummedsupport and sph channels in the UM Flux workspace). LSA and CoE do not need to be notified as they monitor ticket tasks that come in. 
3. If the department/school lists an email address as the contact for AD do the following:
   1. Title the email - Please create the following AD groups for <requestor uniqname>. If the requestor is from UM Dearborn title the email - [ARC UMRCP]
   2. Include all of the information from `b` above.
   3. Create a task on the ticket titled - *Emailed <department> on MM-DD at X:XX am/pm to request AD group creation
   4. Set the ticket status to Awaiting Third Party and make a comment that you are waiting for the AD groups to be created.

Once you are done with the AD group, go to this spreadsheet: https://docs.google.com/spreadsheets/d/1Z1hT0rVDOVRMTgAI4hFjWSbiI37fd_bFQvDbUaHzxG8/edit#gid=0

In the spreadsheet, move the ticket number from column C to column D.  Please try your best to ensure that ticket numbers remain in sequence, if possible to maintain first in first out priorities. 

Once an email has been sent back or the task on the ticket for AD group creation has been completed (you can tell by the last person to modify Ticket Zero) the storage team can be notified that the volume(s) need to be created.

• Create tasks on the ticket with the following titles depending on what is being asked for.  Each volume gets its own task:

  • Title of task for non-sensitive Turbo volume -Please create the following (non-sensitive)Turbo volume - <volume name>
  • Title of task for sensitive Turbo volume - *Please create the following (sensitive)Turbo volume: <volume name> *
  • Title of task for Data Den -Please create the following Data Den volume - <volume name>

• For any volumes that are managed by MiWorkspace please change the beginning of the title on the task to - Please create the following MiWorkspace volumes. A list of departments/schools handled by MiWorkspace can be found here:

  • List of unit attributes for major schools and colleges at UM

• When requesting a volume to be created by storage please include the appropriate shortcodes - Turbo - 123150 Data Den - 123758

• **Ticket zero does not automatically prefix any volume name with the user's department. That step must be done manually during volume creation. **

• Inside the task enter one or all of the following blocks of information depending on what storage is being requested (make sure to replace <pi name> with the requestors' uniqname):

Title: Please create the following Data Den volume - <volume name>

UID =
Notification group = arcts-<pi-name>-admins
GID =
Volume name = 
AD group/owner =
Size = 100T
Shortcode = 123758
Users =

Turbo volume (non-sensitive)

Title: Please create the following (non-sensitive)Turbo volume - <volume name>

UID = 
Notification group = arcts-<pi-name>-admins
GID =
Regulated/Sensitive = No
Volume name = 
Basic + Snapshots + Replication
Size = 10T
Multi-protocol = true
AD group/owner = 
Hosts = 
Shortcode = 123150
Users =

Turbo volume (sensitive)

Title: Please create the following (sensitive)Turbo volume: <volume name> 

UID = 
Notification group = arcts-<pi-name>-admins
GID =
Regulated/Sensitive = Yes
Volume name = 
Basic + Snapshots + Replication
Size = 10T
Multi-protocol = true
AD group/owner = 
Hosts = 
Shortcode = 123150
Users =

• For example : 

• Data Den volume:

  Volume name = lsa-ntronson
  AD group/owner = lsa-ntronson-dataden
  UID = 99399114 GID = 2450139 Notification group = arcts-ntronson-admins Size = 100T
  Users = ntronson Shortcode = 123758

  Turbo volume (non-sensitive):

  Volume name = lsa-ntronson
  AD group/owner = lsa-ntronson-turbo UID = 99399114 GID = 2450140
  Notification group = arcts-ntronson-admins Size = 10T Multiprotocol = true Basic + Snapshots + Replication Users = ntronson Shortcode = 123150 Hosts = Great Lakes

***Make sure to preface the volume name with the correct departmental prefix. Check the MCommunity group that was created for the correct prefix. ***

If the volumes are managed by MiWorkspace make sure to include that in the title of the task (check this page to see if the unit is managed by MiWorkspace - List of unit attributes for major schools and colleges at UM):

• ex: - Please create the following MiWorkspace volumes - Turbo (non-sensitive): <volume name> , Turbo (sensitive): <volume name>

If there are two Turbo volumes requested PLEASE make sure to check the size of each. A user can request any ration between the two to add up to 10T.

The information that is contained in the task will also be used for the volume entry in SRS. A SRS entry for new storage volume will create a new ticket in TeamDynamix. These tickets are automatically assigned to the storage team and this information is then used to provision the vlumes in Isilon. 

Once you have finished with the SRS entries, please go back to this spreadsheet: https://docs.google.com/spreadsheets/d/1Z1hT0rVDOVRMTgAI4hFjWSbiI37fd_bFQvDbUaHzxG8/edit#gid=0

In the spreadsheet, move the ticket number that you worked on from column E to column F, and then fill out the ticket numbers for the SRS tickets in column G. Please try your best to ensure that ticket numbers remain in sequence, if possible to maintain first in first out priorities. 

Once a volume has been provisioned the DNS entries need to be created in BlueCat, the arcts-<requestor uniqname>-admins group gets added to the ARCTS Storage Notifications MCommunity group, and a PR request is sent to the systems team in the #systemstickets channel asking them to mount th evolume on the needed clusters. 

After all of the above is complete the requestor can then be notified on the original UMRCP request (ticket zero). The following link includes pre-formatted responses for each type of service requested. A separate response is required for each service. Makes sure to update the sections shown in < bold>:

• https://docs.google.com/document/d/1P86ESuC4brBtcD7HQQAm75hJ3mmdWD0YU389bLifrtw/edit

At this point all services on the ticket should have been fulfilled. It is good practice to go back and make sure that all SRS tickets and ticket tasks have been closed.