VOBOX migration status meeting

Wednesday 5 Dec 2012, 14:00 → 16:15 Europe/Zurich

513/1-024 (CERN)

Meeting to inform the status of the AI project and the status of the VOBOX migration project.

Slides VOCsMeeting20121205.pdf VOCsMeeting20121205.pptx

Attendance:
IT-PES: Alex Lossent, Ignacio Reguero, Ulrich Schwickerath, Nacho Barrentos, Steve traylen, Gavin MacCance, Daniela Dorneonu, Manuel Guijarro
IT-ES: Alessandro Di Girolamo, Stefan Roiser, Maarten Litmaath
IT-DSS: Alex Iribarren
ATLAS: Sergey Makarychev, Vladimir Glafirov, Serguei Baranov
CMS: Jorge Molina
LHCb: Joel Closier
PH-LCD: Stephane Poss, Andre Sailer

Questions during the meeting:

• can we create puppet-managed VMs?
  • => yes, starting from today. Follow the VOCGettingStarted twiki page https://twiki.cern.ch/twiki/bin/viewauth/AgileInfrastructure/VOCGettingStarted
• (Atlas) we want to have own branches, separate puppet masters
  • => yes, there will be several branches. Will be presented in details later
• Can we create our own VM flavors?
  • => to be negotiated. Needs to be a Tenant manager.
• Max amount of memory/limits?
  • => to be negotiated. Not decided yet, input from VOCs desired.
• All virtualized?
  • =>  yes, as far as possible. Make sure flavors can be created with at least equivalent specifications to current physical hardware.
• high availability?
  • => not now. It's too early for the "pet" scenario with HA
• Can we add disk volumes?
  • => yes, both as part of the flavour and via additional block storage for the pet case (Elastic Block Storage – style)
• What if package dependencies are missing in Puppet configuration ?
  • => not a problem with Puppet as Puppet uses yum, which adds RPM dependencies automatically.
• Deployment of custom packages ?
  • => custom packages to be made available in a yum repository. Koji can automate the process. To be presented in details in a future meeting.
• Can we specify a given version of a RPM ?
  • => yes, also osdate-like functionality is planned
• Deploy system updates?
  • => via osdate-like functionality or manual run of yum update
• Foreman shows many sub-classes (e.g. mysal); is it necessary to select them?
  • => depends on the module. Will be necessary to look at the module's documentation. This may also evolve in the future.
• Mcollective ?
  • => no mcollective service at the moment. But wassh-like functionality will be made available.
• Write access to GIT repository ?
  • => need to subscribe to ai-admins e-group, this will allow to push changes to the devel branch 

 

Introduction

Current Status of the AI project

VOBox(es) and AI - How to get Started

Conclusion