uabrc / uabrc/devops-docs

Incorporate welcome email info into docs

Open
#6 0 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

Moved from https://github.com/uabrc/uabrc.github.io/issues/285

Subject:
Your cloud.rc S3 account is ready!

Body:
Your Research Computing Long Term Storage S3 account is now available. Your account has a 5TB limit.

You can use the service with the Access Key and Secret Key found at this link: {link-to-box-note}

Please note: We do not currently have user self-service available for this service, so you will not be able to change your access and secret keys yourself. If you would like to change them, please let us know at support@listserv.uab.edu.

Configuration settings you will need:
region: default
endpoint: https://s3.lts.rc.uab.edu/
S3 provider: Ceph Object Storage

We have documentation available to help get you started at https://uabrc.github.io/data_management/lts/lts/

You can use any client that is compatible with the Amazon S3 API. Some examples we have used in Research Computing are rclone, S3cmd, AWS CLI, AWS SDK for Python (Boto3), etc.

Please note this service is currently only available from campus and VPN networks.

Let us know if you have any problems or questions by emailing us at support@listserv.uab.edu

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

Start by reading the LTS documentation at https://uabrc.github.io/data_management/lts/lts/ and compare it with the welcome email details in this issue. Update the relevant documentation with the account limit, access-key guidance, configuration settings, supported clients, and campus/VPN restriction; it is done when the documented setup matches the email.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, python
Domain
cloud, 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.