Opened on 12/01/2014 at 06:21:59 AM

Closed on 12/07/2016 at 09:04:50 AM

#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.

Attachments (0)

Change History (3)

comment:1 Changed on 03/16/2015 at 12:39:58 PM by matze

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

comment:2 Changed on 03/16/2015 at 12:40:13 PM by matze

  • Ready set

comment:3 Changed on 12/07/2016 at 09:04:50 AM by matze

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

We'll use KVM.

Add Comment

Modify Ticket

Change Properties
Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from matze.
Attachments ↑ Description ↑
 
Note: See TracTickets for help on using tickets.