Opened 5 years ago

Closed 3 years ago

#1641 closed change (invalid)

Integrate general XEN module with Puppet

Reported by: matze Assignee: matze
Priority: P3 Milestone:
Module: Infrastructure Keywords:
Cc: AAlvz, poz2k4444 Blocked By:
Blocking: Platform: Unknown
Ready: yes Confidential: no
Tester: Unknown Verified working: no
Review URL(s):

Description

We have started using more in-house hardware and services (*.eyeo.intern).

These need to become integrated with Puppet, especially the general XEN setups and resources. Also we need to keep portability in mind (e.g. when introducing a new XEN module) - in order to ensure the same resources being suitable for both in-house and possible future production use.

Change History (3)

comment:1 Changed 4 years ago by matze

  • Owner set to matze
  • Priority changed from Unknown to P3

comment:2 Changed 4 years ago by matze

  • Ready set

comment:3 Changed 3 years ago by matze

  • Resolution set to invalid
  • Status changed from new to closed
  • Tester set to Unknown

We'll use KVM.

Note: See TracTickets for help on using tickets.