Guide for Data and Computation Team Members
Contents
Guide for Data and Computation Team Members¶
This is a short write up facilitate the spin up of new team members for the Data and Computation Team and describe regular maintenance tasks.
Onboarding¶
Checklist for new members¶
[ ] Ask to be added to the Data and Computation Github team
[ ] Ask to be added to the
@data-and-computeSlack user group[ ] Subscribe to Relevant Slack channels
[ ] Consider enabling notifications for Relevant github repos
[ ] Make a PR to the
_config.yamlfile here in a PR. to add a picture and your personal data to the webpage.[ ] Get access to the Grafana Dashboard
Relevant Slack channels¶
data-and-computation-team: Private channel for internal discussions, please contact the Manager for Data and Computing to be added.leap-pangeo: Community wide channel where LEAP-Pangeo users can ask questions. Members of the team should join the channel and regularly engage with issues raised.
Relevant github repos¶
leap-stc.github.io: The source for the LEAP-Pangeo technical documentation. This also contains LEAP-Pangeo Discussion Forumdata-management: Contains all the pangeo-forge based code/automation to ingest new datasets. Point users to the issue tracker to request new datasets.
Regular Maintenance¶
Monitor User Directory Useage¶
The user directories of all members are on a shared volume of fixed size. We pay for the total size of the volume no matter if it is used or not, so we should strive to keep usage to a minimum. Our current policy is that <50GB per user is acceptable. Unfortunately we do not have a technical way to implement per user quotas, so we need to regularly check two things:
How much space is left on the entire shared volume? If the free space falls below 20% we need to discuss further actions.
Which users are taking up more than the allowed 50GB. For users who take up more than 50GB the suggested action is to reach out via slack or email.