Feature #12447

Set up a Mumble server for the fundraising team

Added by intrigeri 2017-04-14 15:56:23 . Updated 2017-04-15 08:50:56 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Tails_2.12
Start date:
2017-04-14
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Following up on Feature #11003: Feature #5688 is now planned for 2017Q4 and DYI self-hosted Mumble servers have shown their limits recently (e.g. due to poor or costly Internet connections, or due to too few people having bothered checking if they like the blueprint/mumble-server script enough to run it).

So as said on Feature #11003#note-4 I might start with setting up one such server on im.lizard for one of our teams, and will skip the more complex discussion.

Subtasks

Related issues

Related to Tails - Feature #11003: Decide if we want to host a Mumble server for the project Rejected 2016-01-27
Related to Tails - Feature #9851: Internal VoIP meetings Resolved 2015-08-01

History

#1 Updated by intrigeri 2017-04-14 15:59:30

  • related to Feature #11003: Decide if we want to host a Mumble server for the project added

#2 Updated by intrigeri 2017-04-14 15:59:38

#3 Updated by intrigeri 2017-04-14 16:03:53

Only looking at metadata and author reputation, https://forge.puppet.com/puppet/mumble/readme seems to be the best module around to manage Mumble with Puppet. Didn’t read the code yet.

#4 Updated by intrigeri 2017-04-15 08:50:56

  • Status changed from Confirmed to Resolved
  • Assignee deleted (intrigeri)
  • % Done changed from 0 to 100

Done, documented credentials in fundraising.git. Server-side credentials are in Hiera.

If we ever want to open this to other teams, we’ll need Mumble “virtual servers” and/or ACLs: