FOSSRIT / tasks

Public ticket tracking system for tasks, planning, and strategy for FOSS@MAGIC efforts
https://github.com/orgs/FOSSRIT/projects/1?fullscreen=true
Creative Commons Attribution Share Alike 4.0 International
7 stars 1 forks source link

Restore service to Slack <=> IRC bridges with matterbridge #76

Closed jwflory closed 5 years ago

jwflory commented 5 years ago

Summary

Restore service to the matterbridge bot we used for Slack <=> IRC bridges

Background

Around Saturday, Nov. 24th, the virtual machine used for bridge bots in RITlug's infrastructure was wiped because of unanticipated issues with the VM. The Slack bridge was not properly documented (a mistake on my end) and the configuration was lost.

The service needs to be installed and configured from scratch. Instead of doing it manually, it makes more sense to do this with automation.

Details

I plan to integrate a new Ansible role in FOSSRIT/infrastructure. I plan to follow matterbridge's Slack bridge documentation. I'll work to make the configurations open source so anyone can submit new configurations or propose new ones if desired later.

I need the RITlug bot API token too.

Outcome

  1. Bridges are back online
  2. More reliable, sustainable deployments to continue using the bridges
jwflory commented 5 years ago

This ticket shares the same blocker as #75. #75 will be used for discussion around the current blocker. This ticket will be addressed after #75.

jwflory commented 5 years ago

An implementation in progress exists at FOSSRIT/infrastructure:add-role/matterbridge.

jwflory commented 5 years ago

Initial work to get the bridge configured is done (see FOSSRIT/infrastructure#21). However, there is a blocker issue to restoring service. It is explained in more detail in the pull request. I'm hoping to follow back up on this later this week.

jwflory commented 5 years ago

Service came back online this evening. Reliable up-time is expected from this point. If anyone notices an issue, please open a new issue on FOSSRIT/infrastructure.

I downgraded the bot to v1.12.0, according to upstream. It worked as expected with little changes needed. Upstream will eventually have a new release, but for now, we will stay off of v1.12.1.