Operations grimoire/Onboarding: Difference between revisions
From Nasqueron Agora
| Line 17: | Line 17: | ||
* Ensure [https://devcentral.nasqueron.org/L3 L3] has been signed | * Ensure [https://devcentral.nasqueron.org/L3 L3] has been signed | ||
* Add member to [https://devcentral.nasqueron.org/project/members/68/ Nasqueron Operations Squad] | * Add member to [https://devcentral.nasqueron.org/project/members/68/ Nasqueron Operations Squad] | ||
* If member is involved in security operations, add member to [https://devcentral.nasqueron.org/project/profile/31/ Nasqueron security operations squad] | |||
=== Salt === | === Salt === | ||
Latest revision as of 17:53, 3 March 2023
The current Nasqueron Operations SIG onboarding process is still a work in progress. When onboarding new members, this process should be refined and improve.
Request
To join the Nasqueron Operations SIG:
- Create a task on DevCentral
- Document the work previously done for Nasqueron projet, with focus on the infrastructure, state you want to join Operations.
- Tag it Nasqueron Operations Squad
- Announce the task on Libera #nasqueron-ops
- When invited to do so, sign https://devcentral.nasqueron.org/L3
- Ensure you follow the useful ops resource to communicate:
- IRC: join and follow Libera #nasqueron-ops
- DevCentral: have a working account on with notifications enabled
Onboarding
Phabricator
- Ensure L3 has been signed
- Add member to Nasqueron Operations Squad
- If member is involved in security operations, add member to Nasqueron security operations squad
Salt
- rOPS: pillar/core/groups.sls: add username to ops group
- Deploy roles/core/users to each machine:
salt '*' state.apply roles/core/users
NetBox
- Create new contact, add it to the Nasqueron Operations SIG
