Feature #11844

Enable monitoring for buse (labs.r.n)

Added by intrigeri 2016-09-26 00:19:12 . Updated 2016-11-03 09:48:43 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Tails_2.7
Start date:
2016-09-26
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:
270

Description

VPN set up, so I think the only remaining bits to do are:

  • adjust firewall
  • run Puppet agent (tracked by Bug #11805)
  • fix the configuration to connect to ecours instead of monitor.lizard
  • add extra checks (HTTPS)

Subtasks

History

#1 Updated by intrigeri 2016-09-26 00:52:30

  • Description updated
  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 10

#2 Updated by intrigeri 2016-09-26 00:52:39

  • blocked by Bug #11805: Unplug buse (labs.r.n) from Riseup's private network added

#3 Updated by intrigeri 2016-10-01 17:16:21

  • blocks deleted (Bug #11805: Unplug buse (labs.r.n) from Riseup's private network)

#4 Updated by intrigeri 2016-10-01 17:22:19

  • Description updated
  • Assignee changed from intrigeri to bertagaz
  • % Done changed from 10 to 20

I’ve done what I could and everything seems to be set up correctly, except that buse tries to connect to monitor.lizard. I’ve not found anything in our doc wrt. hosts that are neither the monitoring master, nor the satellite, nor a guest on lizard. bertagaz, can you please either fix that yourself and update the doc, or give me enough info so that I can do it myself?

#5 Updated by bertagaz 2016-10-05 11:55:27

  • Description updated
  • Status changed from In Progress to Resolved
  • Assignee deleted (bertagaz)
  • % Done changed from 20 to 100

intrigeri wrote:
> I’ve done what I could and everything seems to be set up correctly, except that buse tries to connect to monitor.lizard. I’ve not found anything in our doc wrt. hosts that are neither the monitoring master, nor the satellite, nor a guest on lizard. bertagaz, can you please either fix that yourself and update the doc, or give me enough info so that I can do it myself?

I fixed that.

Just so you know, buse tails::monitoring::agent was set with the default zone (‘Lizard’), which imply it was configured to report through monitor.lizard.

For hosts other than the one on lizard, we have to set their parent zone to Tails so that they report directly to ecours, and set the Icinga2 agent IP to its VPN one, so that reporting goes through the VPN.

I’ve updated the installation documentation accordingly.

Seems to be the last item of this ticket, so I’m boldly closing it. :)

#6 Updated by intrigeri 2016-10-05 12:11:01

Thanks a lot!

#7 Updated by intrigeri 2016-11-03 09:48:43

  • Deliverable for set to 270