AI How to: System Update and Additional Software

Slides:



Advertisements
Similar presentations
Installing software on personal computer
Advertisements

CVMFS: Software Access Anywhere Dan Bradley Any data, Any time, Anywhere Project.
FileSecure Implementation Training Patch Management Version 1.1.
Downloading & Installing Software Chapter 13. Maintaining the System Yum Pirut BitTiorrent Rpm Keeping Software Up To Date Up2date Red Hat Network Wget.
Module 10 – Linux Installations. Wikipedia: Red Hat Package Manager or RPM Package Manager (RPM) is a package management system. The name RPM variously.
Installation Overview Charles (Cal) Loomis & Mohammed Airaj LAL, Univ. Paris-Sud, CNRS/IN2P October 2013.
SUSE Linux Enterprise Server Administration (Course 3037) Chapter 4 Manage Software for SUSE Linux Enterprise Server.
The EPIKH Project (Exchange Programme to advance e-Infrastructure Know-How) Overview of software tools for gLite installation & configuration.
AI project components: Facter and Hiera
October, Scientific Linux INFN/Trieste B.Gobbo – Compass R.Gomezel - T.Macorini - L.Strizzolo INFN - Trieste.
1 Introduction to the tutorial for site managers Antonio Fuentes Red.es/RedIRIS EGEE/EUMedGrid/EELA Tutorial for Managers Sevilla,
CERN Manual Installation of a UI – Oxford July - 1 LCG2 Administrator’s Course Oxford University, 19 th – 21 st July Developed.
Michael Still Google Inc. October, Managing Unix servers the slack way Tools and techniques for managing large numbers of Unix machines Michael.
Quattor-for-Castor Jan van Eldik Sept 7, Outline Overview of CERN –Central bits CDB template structure SWREP –Local bits Updating profiles.
Platform & Engineering Services CERN IT Department CH-1211 Geneva 23 Switzerland t PES AI’s user access, OpenStack security groups and firewall.
Large Farm 'Real Life Problems' and their Solutions Thorsten Kleinwort CERN IT/FIO HEPiX II/2004 BNL.
Enabling Grids for E-sciencE EGEE and gLite are registered trademarks Usage of virtualization in gLite certification Andreas Unterkircher.
SPMA & SWRep: Basic exercises HEPiX hands-on, NIKHEF 5/03 German Cancio
Online System Status LHCb Week Beat Jost / Cern 9 June 2015.
QWG Errata Management Framework Ian Collier 10 th Quattor Workshop Rutherford Appleton Laboratory October 2010.
Configuration Report 12/02/2015
Enabling Grids for E-sciencE EGEE and gLite are registered trademarks Tools and techniques for managing virtual machine images Andreas.
Maite Barroso - 10/05/01 - n° 1 WP4 PM9 Deliverable Presentation: Interim Installation System Configuration Management Prototype
Configuration Report (nearly) Christmas Edition
EGEE-II INFSO-RI Enabling Grids for E-sciencE YAIM Overview MiMOS Grid tutorial HungChe, ASGC OPS Team.
RedHat Package Management RPM and YUM in RedHat Enterprise, Fedora, Suse and Centos.
Feedback from CMS Andrew Lahiff STFC Rutherford Appleton Laboratory Contributions from Christoph Wissing, Bockjoo Kim, Alessandro Degano CernVM Users Workshop.
Platform & Engineering Services CERN IT Department CH-1211 Geneva 23 Switzerland t PES AI Images, flavours and partitions Vítor Gouveia,
CERN AI Config Management 16/07/15 AI for INFN visit2 Overview for INFN visit.
Platform & Engineering Services CERN IT Department CH-1211 Geneva 23 Switzerland t PES Agile Infrastructure Project Overview : Status and.
ICS Software Development Environment Blaž Zupanc and Leandro Fernandez 19 February 2016.
FP6−2004−Infrastructures−6-SSA E-infrastructure shared between Europe and Latin America Worker Node & Torque Client Installation.
1 Policy Based Systems Management with Puppet Sean Dague
Platform & Engineering Services CERN IT Department CH-1211 Geneva 23 Switzerland t PES GIT Service in the Agile Infrastructure Project Vítor.
April 1st, 2009 Cobbler Provisioning Made Easy Jasper Capel.
CERN Openlab Openlab II virtualization developments Havard Bjerke.
Overview of software tools for gLite installation & configuration
Introduction to Ansible
Fundamentals Sunny Sharma Microsoft
DAQ LHC Workshop Configuration management systems
PTF for the PS Admin A PTF Overview for the PeopleSoft Administrator
NA61/NA49 virtualisation:
High Availability Linux (HA Linux)
NTP, Syslog & Secure Shell
Progress on NA61/NA49 software virtualisation Dag Toppe Larsen Wrocław
SVN intro (review).
Installation, setup and use - Ferro Backup – V1.1
Automatized Update & Upgrade for POVClientS.
Spring Cleaning the Software Repositories Matthias Schröder
NIGHTLY BUILD SCRIPT FOR THE LEVEL-1 TRIGGER ONLINE SOFTWARE
Spacewalk and Koji at Fermilab
Puppet
June 2011 David Front Weizmann Institute
EMI Componets Installation And Configuration
Bomgar Remote support software
Get Oracle 8i Running on Your Linux Server Straight Away!
More Scripting & Chapter 11
RedHat Package Management
Microsoft Virtual Academy
Open Source Toolkit for Turn-Key AI Cluster (Introduction)
OPS235: Lab 2 Virtual Machines – Part I
Module 01 ETICS Overview ETICS Online Tutorials
JENKINS TIPS Ideas for making your life with Jenkins easier
SUSE Linux Enterprise Desktop Administration
Quattor Advanced Tutorial, LAL
Update & Upgrade your POVClient.
Basic Dynamic Analysis VMs and Sandboxes
VirgoStaging Status F.Carbognani, S. Cortese, E. Pacaud.
System Center Third Party Tools Ivanti Patch and RCT Recast April 2019.
Presentation transcript:

AI How to: System Update and Additional Software Vítor Gouveia, vitor.gouveia@cern.ch IT-PES-PS

Agenda System update for AI Add additional repositories Deploy additional software Questions?? 2

System update for AI Quattor way AI way (SLC6 only) Typical process: 1. Update osdateversion in CDB for a cluster 2. Run spma on each node (typically with wassh) – this actually updates the RPMs. Trigger a reboot if necessary. 3. Spma is also run automatically when a node reboots Puppet typically will not update packages by itself. A specific module provides the following process: Update hiera variable os_repos_repository_date A daily cron job will update the RPMs If the VM needs a reboot (new kernel), this has to be done manually 3

System update for AI - OSREPOS puppet module for repository control one of the default modules of the AI Installed before the base module install the repositories SLC, EPEL and AI two different behaviours according with the version of the OS (SLC6 or SLC5) On slc6 machines the system is keep up to date with the osrepos On slc5 machines the system needs manual intervention to be updated 4

System update for AI – SLC6 yum distro-sync synchronizes the installed package set with the latest packages available, this is done by either obsoleting, upgrading or downgrading as appropriate. cronjob repos_sync: installed and executed once per day. during the execution of the distro_sync.sh script: yum distro-sync is executed log file: /var/log/distro_sync.log 5

System update for AI – SLC6 Linuxsoft provides daily snapshots of the CERN SLC and EPEL repositories. http://linuxsoft.cern.ch/internal/yumsnapshot/yyyymmdd/... How do we use them ? Hiera variable osrepos_repository_date osrepos_repository_date values: osrepos_repository_date not set (default value) the official CERN SLC and EPEL repositories will be used very latest updates from SLC and EPEL repos will always be installed snapshot date format (yyyy-mm-dd) integer X The snapshot used will be the one that is X days before the current day 6

System update for AI – SLC6 Useful hiera variables: osrepos_sync_exclude_packages list of package to be exclude of the synchronization osrepos_sync_include_packages list of packages to synchronize, if this is not set all packages are synchronized. Fixed day: 2013-02-02 5 days before: 2013-03-31 Current day: 2013-04-05 osrepos_repository_date: ‘2013-02-02’ osrepos_repository_date: ‘5’ Fixed day: 2013-02-02 10 days before: 2013-03-27 5 days before: 2013-04-01 Current day: 2013-04-06 7

System update for AI – SLC5 SLC5 does not have the command yum distro-sync  If you want to update a node You need to do it manually e.g. yum update the latest updates from the installed repositories will be installed At the moment, osrepos_repository_date does not work on slc5 machines The official CERN repositories are always installed 8

Add additional repositories The resource osrepos::ai121yumrepo should be use to add any additional yum repositories, this includes external repositories Nothing more a wrapper around the standard puppet yumrepo resource osrepos::ai121yumrepo{"rpmforge": baseurl => "http://apt.sw.be/redhat/el6/en/x86_64/rpmforge/", descr => "RPM forge repository", enabled => 1, gpgcheck => 0, } 9

Additional repositories - caveats Using external repositories creates a number of issues: machines without internet access will not be able to use them dependency issues / glitches can arise No control of what is updated and when 10

Replicating repositories Whenever extra repositories are needed, they should be replicated to linuxsoft Don’t set up repos yourself, just make sure the RPMs are available somewhere for linuxsoft to pick up Linuxsoft will make sure the repos are both available to all CERN nodes (including technical network and other networks without internet access) and scale properly This is the process used to replicate EPEL For custom/private software The source to replicate in linuxsoft may be e.g. an AFS folder Also, some repos are generated by Koji E.g. the AI repo and some others BUT THIS IS NOT OFFERED AS A BUILD SERVICE 11

Request a repository replica Requests for repo duplication to be done via linux.support line Exact process is yet to be formalized… 12

Deploy additional software the ensure attribute of the puppet resource package: present or installed puppet will install the latest version of the package that it finds in the hosts configured software repos when the manifest first runs, but never updates it latest Puppet will install a package if absent and upgrade the package to newer versions when they become available (to be used carefully) absent If present remove the package version string If available install a specific package version 14

Software not in a yum repository… What if? use puppet to install a RPM package that is not present in a repository Source parameter should point to the file local file (or on a network file system) or a URL Problems: dependency issues how to update… package { "emacs-puppet": source => "http://linuxsoft.cern.ch/rpmforge/redhat/el6/en/x86_64/rpmforge/RPMS/emacs-puppet-2.7.9-1.el6.rf.noarch.rpm", provider => "rpm", } 13

???????????????????????