Known issues

  • i686 build for NSS.
  • AFS backup not in place.

Build software updates

Please note you need to login as the build user on the lxsoft cluster.

ssh build@lxsoft

Workflow for Centos updates

The Centos repo is synchronized every 6 hours to:

/mnt/data1/dist/centos/7/

Then we pull updates from this directory and move them to our -testing tree in :

/mnt/data1/dist/cern/centos/7/*-testing

Then every Thursday all -testing updates are moved to our production tree.

/mnt/data1/dist/cern/centos/7/*

Update SRPMS/RPMS from upstream Centos

Packages that need your attention

  • NSS (recompile with CERN certs)
  • KERNEL (recompile openafs)

release to -testing

CC7
bscentos2test -d cc7 -r all
bsregenrepos -d cc7 -r "updates-testing extras-testing centosplus-testing cr-testing sclo-testing cloud-testing virt-testing"
bssync -d cc7 -r "updates-testing extras-testing centosplus-testing cr-testing sclo-testing cloud-testing virt-testing" -t "data1 afs"
bsmailusers -d cc7 -r testing -e -s -w

release to -production

bstest2prod -d cc7 -r "updates extras centosplus virt" pkgname (or \* for all)
bsregenrepos -d cc7 -r "updates-testing extras-testing centosplus-testing cr-testing sclo-testing cloud-testing updates extras centosplus cr sclo cloud virt-testing virt"
bssync -d cc7 -r "updates-testing extras-testing centosplus-testing cr-testing sclo-testing cloud-testing virt-testing updates extras centosplus cr sclo cloud virt" -t "data1 afs"
bsmailusers -d cc7 -r updates -e -s -w

CERN Updates

Incoming

Incoming is split for each repository : cern, cernonly so you need to copy your package to the right destination.

Please note that source or binary package can be added to incoming.

CC7
Incoming CERN Incoming CERNONLY
/mnt/data2/home/build/packages/incoming/cc7/cern /mnt/data2/home/build/packages/incoming/cc7/cernonly

Build cern SRPMS

CC7
bsbuild -d cc7 -r all
bsdownload -s -d cc7 -r all

Release to -testing

CC7
bsbuild2test -d cc7 -r all
bsregenrepos -d cc7 -r "cern-testing cernonly-testing"
bssync -d cc7 -r "cern-testing cernonly-testing" -t "data1 afs"
bsmailusers -d cc7 -r testing -e -s -w

Release to production

bstest2prod -d cc7 -r "cern cernonly" pkgname
bsregenrepos -d cc7 -r "cern cernonly cern-testing cernonly-testing"
bssync -d cc7 -r "cern cernonly cern-testing cernonly-testing" -t "data1 afs"
bsmailusers -d cc7 -r updates -e -s -w

Build kernel modules (e.g. kmod-openafs)

Use

bsbuildmodules -k kernel-number -d cc7
bscopymodules -k kernel-number -d cc7 

To build the kernel modules for the centos-plus kernel append .centos.plus to the kernel-number, eg

bsbuildmodules -k 3.10.0-327.4.5.el7.centos.plus -d cc7

Minor release process

Testing packages from CR repo

When CentOS publishes the new CR repo including all updates we can as well push it to the CR repo.

* Push all packages to cr-testing with the standard workflow, * Add an entry in the website * Send an email

  SUBJECT : 2015.12.03 CC72 - CERN CentOS 7.2 TEST available.

  Dear CERN Linux users.

We would like to announce availability of next
CERN Linux TEST release:

TEST version of CC72: CERN CentOS 7.2 for x86_64
************************************************

* What is CERN CentOS 7.2 (CC72) TEST ?

- TEST minor release of CC7X series.

* Updating from previous CERN CentOS 7 to "7.2 TEST":

In order to test the update,
run as root on your system:

# yum update
# yum --enablerepo=cr update

* Problem reporting:

Please report problems to Linux.Support@cern.ch
Feedback is welcome.
Edit | Attach | Watch | Print version | History: r17 < r16 < r15 < r14 < r13 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r17 - 2017-10-27 - ThomasOulevey
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LinuxSupport All webs login

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