Project

General

Profile

Bug #14613

Sysadmin documentation is unclear about Git repositories for Puppet code

Added by groente 3 months ago. Updated 15 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Start date:
09/08/2017
Due date:
% Done:

100%

QA Check:
Pass
Feature Branch:
Type of work:
Contributors documentation
Blueprint:
Starter:
Affected tool:

Description

In particular, https://tails.boum.org/contribbute/working_together/roles/sysadmins/ does not mention where the puppet stuff actually lives nor the synchronisation that goes on between immerda and git.puppet.tails.boum.org


Related issues

Blocks Tails - Feature #13242: Core work 2017Q4: Sysadmin (Maintain our already existing services) Confirmed 06/29/2017

Associated revisions

Revision 761c577f (diff)
Added by intrigeri 16 days ago

Clarify sysadmin doc about Git repositories for Puppet modules (refs: #14613)

- Document the authoritative place for our Puppet modules
and the synchronization mechanism to the public mirrors.
- Clarify what's the manifests repo and its use of submodules.
- Avoid pointing non-sysadmins to doc that won't work for them.
- Point to the Puppet modules Git repo doc from contribute/how/sysadmin.
- Make the link to our Puppet code more obvious on
contribute/working_together/roles/sysadmins

History

#1 Updated by intrigeri 3 months ago

  • Category set to Infrastructure
  • Target version set to Tails_3.5

#2 Updated by intrigeri 3 months ago

  • Blocks Feature #13242: Core work 2017Q4: Sysadmin (Maintain our already existing services) added

#3 Updated by intrigeri 3 months ago

  • Subject changed from Sysadmin documentation is unclear about git repositories to Sysadmin documentation is unclear about Git repositories for Puppet code
  • Priority changed from Low to Normal

(Having basic info in our contributors doc is >> low prio :)

#4 Updated by intrigeri 16 days ago

  • Status changed from Confirmed to In Progress

#5 Updated by intrigeri 16 days ago

  • Assignee changed from intrigeri to groente
  • % Done changed from 0 to 50
  • QA Check set to Ready for QA

See 761c577ff253130b12045263a519d7df9a9ebb33. I've missed my own comment above so ended up implementing this slightly differently. I think my proposal above was slightly better but what I've implemented is good enough IMO.

#6 Updated by groente 15 days ago

  • Status changed from In Progress to Resolved
  • % Done changed from 50 to 100
  • QA Check changed from Ready for QA to Pass

Looks good, thanks for the clarification!

Also available in: Atom PDF