Onboarding new starters
The following checklist is to be used as a reminder of the admin tasks needed to onboard a new member to the DevOps team. These should be done after the University's onboarding tasks for any new member of staff.
To track the completion of these tasks the manager or a peer should raise a new starter issue in the administration project. Assign both the line manager and new starter to this issue once created.
Performed by manager or admin staff before start date¶
- Add to the corresponding DevOps team (subgroup) within DevOps Division lookup group.
- Add to the University Information Services, UIS DevOps, and any other relevant teams on MS Teams.
- Add to the regular meetings they are expected to attend.
Performed by manager or peer before start date¶
- Add to the DevOps GitLab group and other corresponding GitLab groups.
- Add as a viewer, or deployer as appropriate in Team Data for Google Cloud resources
When the user is added to the corresponding DevOps team in lookup, they should get access to:
- Google Shared drive for DevOps and possibly other Shared drives relevant to the project(s) they will be working on.
- Invite to 1password and add to appropriate vaults.
Performed by the new starter¶
Follow the instructions for the first time setup of Raven.
- Login to your Google acccount (use firstname.lastname@example.org in google.com) and accept the T&Cs.
- Enable 2FA in your Google Account.
- Login to your Microsoft account (use email@example.com in office.com) and accept the T&Cs. It may take some hours before it is ready.
- Enable 2FA in your Microsoft Account.
- Validate that your calendar (Outlook) and email (Exchange Online) is working correctly.
Subscribe to appropriate lists by searching for them in sympa search. Note that with some you will need to wait for approval.
- social (various, optional)
You will automatically be added to some mailing lists corresponding to your DevOps team (lookup subgroup).
- Create a 4096 bit RSA key if you don't already have a preferred one
- Add your SSH public key to gitlab to allow for git over SSH
- Open Merge Requests as appropriate to add your key to the various resources:
- ansible-roles which will only be needed if you are dealing with legacy systems
You may want to at least:
- Re-encrypt ansible vault passwords, see setting up GPG to decrypt secrets for guidance
- Add public GPG key to team public keyring
- Update the guidebook - copy the updated file
There are more detailed instructions in the general docs to add your GPG key.