uabrc / uabrc/devops-docs

Procedure for fulfilling researcher storage purchase requests

Open
#55 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1
Forks
9
PR merge metrics
No merged PRs in 30d

Description

  1. If we do not have a valid quote, or the quote won't last through the PO process (less than about a week or so?), inform the researcher we will need to get the latest quote. Currently JP handles this but I'll see about getting the name of our vendor rep. The vendor name will not be listed in this public repository, you'll have to ask me, JP, or Ralph.
  2. Confirm that the researcher wishes to buy in a ticket in writing. Send them the following information.
    • The total amount of the quote(s).
    • The total amount of usable storage. Ask me, JP, or Ralph how to read this. Typically there will be separate hardware and software quotes. The highest-cost line item will have something like 24 x 24TB HDD. Calculate that product and divide by three to get usable storage. In this example 24*24 -> 576 and 576/3 -> 192, so 192 TB usable.
  3. Communicate with our Program Coordinator to process the PO. Send the following info to our program coordinator:
    • Contact info for the person who handles POs and accounting information on the researcher's side.
    • Copies of the quotes.
    • Exactly what is intended to be purchased. Typically this is one of each line item in the quotes, but if in doubt, check with me, JP, or Ralph.
    • The "ship-to" or "courtesy of" person should be JP or other lead ops person.
  4. After the PO is committed for purchase, and if we have the storage capacity, increase their storage capacity by the purchased amount. In other words, give them an advance on their purchase.
  5. Inform the researcher when (6) has been completed.
  6. Ops team will install the new hardware after it arrives.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names a six-step procedure but no target file or existing entry point. Start by locating the relevant storage-purchase documentation and confirm the vendor and storage-calculation details with the named contacts; done means the documented procedure accurately covers quote validation, purchase confirmation, PO processing, capacity allocation, researcher notification, and installation.

Written by the indexing model from the issue text.

Assessment

Domain
devops, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.