Choose timezone
Your profile timezone:
VOC working group meeting - GIT Service in the Agile Infrastructure Project
→
Europe/Zurich
31/S-028 (CERN)
Attendance:
IT-PES: Alex Lossent, Vitor Gomes, Alvaro Gonzalez, Nacho Barrentos, Steve traylen, Tomas Karasek, Daniel Lobato Garcia, Manuel Guijarro, Nils Hoimyr, Peter Jones, Evangelos Atlidakis
IT-ES: Pabo Saiz, Maarten Litmaath
IT-DI: Denise Heagerty
IT-DB: Ruebn Gaspar
IT-CIS: Pedro Ferreira
IT-OIS: Jan Van Eldik
ATLAS: Vladimir Glafirov
CMS: Jorge Molina
LHCb: Joel Closier
Questions during the meeting:
IT-PES: Alex Lossent, Vitor Gomes, Alvaro Gonzalez, Nacho Barrentos, Steve traylen, Tomas Karasek, Daniel Lobato Garcia, Manuel Guijarro, Nils Hoimyr, Peter Jones, Evangelos Atlidakis
IT-ES: Pabo Saiz, Maarten Litmaath
IT-DI: Denise Heagerty
IT-DB: Ruebn Gaspar
IT-CIS: Pedro Ferreira
IT-OIS: Jan Van Eldik
ATLAS: Vladimir Glafirov
CMS: Jorge Molina
LHCb: Joel Closier
Questions during the meeting:
-
(VG) there is 1 branch for all VOs!? (JC) can a VO modify files in anotehr VO?
- => the Vocs_devel branch is shared by all VOs. It is a temporary setup meant to allow VOs to experiment with the system during its development phase. This does not reflect the final setup of branches wrt VOs, which has yet to be finalized.
-
(ML, about module lifecyle) Will the RMT include people from the experiments?
- => (ST) yes
-
(JC, about module lifecycle) what about modules that are not shared (e.g. Dirac)? VOs should be able to publish updates to their own Modules; with no approval workflow.
- => (AL) this is just a proposal, it was written with Shared modules in mind. Discussion ongoing, detailed feedback desired: http://community.web.cern.ch/forum/feedback-module-lifecycle-proposal
-
List of modules included by default for all machines?
- => visible in the manifests for the "base" module, which is included by default
- (ST/ML) since branches include copies of all other hostgroups, it is possible to develop and submit patches to other people's clusters like aiadm -- whose managers may or may not accept to apply
-
support for Eclipse?
- => (AL) no support. A recipe is provided 'as-is' to set up eclipse for git and puppet, without warranty. Nothing can be done with eclipse that could not be done with command-line tools. Steps will be added to the documentation to implement puppet best practices (tabulation etc.) in eclipse
-
(JC) support for slc5?
- => (ST) strictly speaking yes but slc6 highly recommended.
- (AL) topics for next meeting: hiera and facter
There are minutes attached to this event.
Show them.
