Feature #9480

Set up a VM for monitoring tools experiments

Added by intrigeri 2015-05-28 14:11:04 . Updated 2015-08-26 06:10:39 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Tails_1.4.1
Start date:
2015-05-28
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:
268

Description

Subtasks

Related issues

Blocks Tails - Feature #8645: Research and decide what monitoring solution to use Resolved 2015-01-09 2015-09-28

History

#1 Updated by intrigeri 2015-05-28 14:11:23

  • blocks #8668 added

#2 Updated by intrigeri 2015-05-28 14:12:54

  • blocks Feature #8645: Research and decide what monitoring solution to use added

#3 Updated by intrigeri 2015-05-28 14:19:50

… and ideally, create a disk (LVM) snapshot so that Feature #9481 is easier.

#4 Updated by bertagaz 2015-06-12 19:37:12

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

Created monitor.lizard and sent connection informations to DrWhax and kurono.

It’s a jessie VM, where I’ve in the end uninstalled the puppet package and disabled the puppet agent cronjob, so that it is setup like most of our VM but puppet won’t interfer with the experiments.

I’ve taken a LVM snapshot at the end of the system setup: /dev/mapper/lizard-snap—monitor—system

#5 Updated by intrigeri 2015-06-12 19:48:13

> It’s a jessie VM, where I’ve in the end uninstalled the puppet package and disabled the puppet agent cronjob, so that it is setup like most of our VM but puppet won’t interfer with the experiments.

I don’t see why the base setup Puppet does (and manages) could interfere, especially in ways that can’t be overridden in some .d directory, but I’m probably missing something. Anyway, works for me!

> I’ve taken a LVM snapshot at the end of the system setup: /dev/mapper/lizard-snap—monitor—system

Yay!

#6 Updated by intrigeri 2015-08-26 06:10:39

  • Deliverable for set to 268