Present: Miguel Santos, Ignacio R., Matthias S., Veronique L., Ulrich S., Tim Bell, Juan Antonio Lopez Perez (CMS)

Description of the current usage of /test /preprod /prod:

• See https://twiki.cern.ch/twiki/bin/view/FIOgroup/InterventionPlanning-2008-04-14 for the description of a typical scheduled sw upgrade.
  • every night, /test receives automatically a new version of pro_software_packages_default_[arch]_[os].tpl
    • these define the default version (production version) of LinuxSoft packages only
    • the defaults are defined as being the most recent version found on the LinuxSoft repository (note: what is available on SWrep itself is NOT looked at, but of course, the LinuxSoft repository is regularly mirrored onto SWrep)
  • if needed, for new dependencies or changes in package names, the MUD (monthly upgrader on-duty) will put under /test a new version of pro_software_packages_cern_[arch]_[os]_release_base.tpl (and any other .tpl where the dependency would need to be updated)
  • on a given and announced date, what is in /test is copied to /preprod, and /preprod is frozen for 1 week, to allow users to test the sw upgrades
  • one week later, what is in /preprod is moved to /prod: the sw upgrade is deployed.

Discussion and agreements:

• /test:
  • everyone is free to put anything under /test, and will benefit from the /test, and /preprod phases to test new software or new configuration. It means that, anyone is allowed to put under /test any template, but has to be aware that:
    • pro_software_packages_default_[arch]_[os].tpl are created automatically and should NEVER be edited by hand (else the change will be overwritten anyway)
    • anything under /test will end-up under /preprod and then under /prod according to the software upgrade schedule (SLA with users)
      
• /preprod:
  • NOBODY, except for the MUD (monthly upgrader on-duty), can put anything there.
  • the MUD will announce, one week in advance, on project-elfms@cern.ch, when /preprod will be frozen, so that you still have 1 week to put whatever you need under /test
  • for Service-specific templates ONLY: If you want to "test" something on "preprod" machines, or if you had no time to put your new templates under /test before that /preprod become frozen, then use a new stage, for example:
    • variable loadpath = list('usertest/vero/mypreprod','preprod','prod');
    • put under usertest/vero/mypreprod the templates you want to test
    • then move them yourself under /prod when you are ready.
      
    • this is allowed for service-specific templates ONLY, where you know exactly that only YOUR machines will be affected