Please add any items you would like to see discussed at one of the next meetings.

Current

Item Added By Description Concerned parties Date Added
01 Quattor ACLs Peter Kreuzer (e-mail) "Say the main VOC creates a new quattor configuration file attached to a VoBox, then he/she will be the owner of that file; how can the backup VOC take ownership of that file, in case the main VOC is absent? In other words, there seem to be no automatic way to inherit from a group permission set on a top directory, for files which are subsequently created, which is rather inconvenient operationally. How do other VO's handle such case?"
Savannah #23841
VOCs and CDB Support 13-Oct-2011
02 VOBOX Warranty (If needed) Bernd Panzer (e-mail) (To) "clarify the hardware warranty situation of physical hardware installed in the computer center." Service_Nodes_Hardware_Warranty_Issues.pdf: Service Nodes Warranty Clarifications for VoBoxes VOCs, IT/CF, Bernd P. 7-Mar-2012
03 Update on VOBOX VMs Alex Lossent

- SLC6 supported since a few months. Updated SLC6 paravirtualization drivers deployed with OSDATE >=20120504 improve resilience in case of disk access delays due to live migration or SAN glitches. Update recommended.

- remote-power-control integration: can be used for on/off/reset operations on VMs

- Vobox/VM FAQ moved to Service Portal KB: https://cern.service-now.com/service-portal/faq.do?name=VOBox-infrastructure-support

- Recurrent issues with non-paravirtualized network. Actions taken: improved PrepareInstall now enables paravirtualized network for all new/reinstalled VMs. Alarm on production SLC6 nodes if not using paravirtualized network. Upcoming campain to switch all remaining VMs to paravirtualized.

- VM expiration: 3 years by default for new VMs (as per hardware request form). Lifetime extension possible via CVI web site, notifications of upcoming expiration sent to LanDB owners (at -1 month, -1 week etc.). But current infrastructure expected to be decomissioned before VMs start expiring.

- DHCP: default on slc6, but static IP on slc5. DHCP would provide more flexibility for moving VMs to different hypervisor clusters. Proposal: switch all SLC5 VMs to DHCP in upcoming OSDATE. Note that proper DHCP support requires deploying ncm-network. Any objection from VOCs?

- reporting on VOBOX VMs: project https://espace.cern.ch/vobox-service-consolidation-reports/Lists/VoboxVM/AllItems.aspx. Useful? Send e.g. weekly reports to VOCs?

- Service consolidation capacity: projection https://twiki.cern.ch/twiki/bin/view/PESgroup/VirtualMachineInfrastructureCapacityProjection => full by early 2013. IaaS will then take over (See below).

- Disk volume capacity: as some volumes are filling up there may be a need in the next months to move VMs to a different storage volume, with a few minutes of unavailability.

VOCs, other users of Service Consolidation infrastructure 5-Apr-2012
04 Future of VOBox: IaaS Alex Lossent

IT is working on an Infrastructure-as-a-Service project, aiming for production in 2013, which will eventually replace the Quattor-based VOBox service. Main features will be self-provisioning of VMs and node management via Puppet. See presentation at last ITUM.

Migration of existing VOBox VMs expected to take place in 2013.

A fellow in IT-PES will work on the transition process from Quattor-managed VMs to Puppet / IaaS, in particular provide tools and documentation. We expect to enable VOCs to experiment with the new system this autumn

VOCs, other users of Service Consolidation infrastructure 23-May-2012
05 Quattor to Puppet Joel Closier (notes from Cross Experiment meeting, Thu 14 June 2012) Joel Closier asked what IT will provide to help Experiments move their VOBoxes from Quattor to Puppet? The easier it is for the Experiments to replace Quattor then the more likely they are to do so.   14-June-2012
 
Nr Example Title Person Description Groups nn-Mar-2012

Archived

Item Added By Description Concerned parties Date Added

-- RicardoSilva - 13-Oct-2011

Topic attachments
I Attachment History Action Size Date Who Comment
PDFpdf Service_Nodes_Hardware_Warranty_Issues.pdf r1 manage 32.1 K 2012-03-12 - 10:19 JuanManuelGuijarro Service Nodes Warranty Clarifications for VoBoxes
Edit | Attach | Watch | Print version | History: r10 < r9 < r8 < r7 < r6 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r10 - 2012-07-05 - AlexLossent
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LCG All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback