Collaboration meeting

Europe/Zurich
Vidyo

Vidyo

# Argus Collaboration - 2/9/2016


[Agenda](https://indico.cern.ch/event/566689/)


## General News

New recruitment for INDIGO: selection hopefully in October...


## New Release Status

CERN now running 1.7 in production: great step forward, no issue seen since the upgrade
* Since August 11
* Confident that 1.7 is really ready for production and is the best Argus version
* Need to mention in the release notes that some proxy mappings may change following the upgrade
  * Happens in particular when a wildcard is used in the configuration to match secondary FQANs (in fact every time there are mapped secondary FQANs): such FQANs now always result in a group added at the end of the gridmapdir entry (even if the FQANs are mapped to the same group), resulting in a different pool account being used
  * Maarten will propose a text for the release notes
  * If concerned by potential failure, drain your CE, else the upgrade can be done on the fly
* No change required in the Argus configuration compared to 1.6, even on CentOS7 (but note that YAIM is absent on CentOS7, i.e. one has to use something else to configure the service: Puppet, Quattor, manually, ...)
* Impact on the system load: need confirmation but Maarten has the feeling that there was a reduction compared to 1.6: just 3 VMs can easily handle the whole load of CERN
  * No time/opportunity yet to disable the NFS file attribute caching
  
Release notes: [draft](http://argus-documentation.readthedocs.io/en/latest/release_notes.html) prepared by Andrea
* Need to add Maarten contribution on the gridmapdir entry changes
* Make clear that you can reuse the 1.6 config, in particular if you have a config management tool like Puppet or Quattor able to configure 1.6
* As soon as, release notes are finalized, we'll make the new repo production and launch inclusion into UMD-4
  * CERN tests are considered as a successful staged rollout
  
PIPs are ready
* PRs are open and waiting to be merged: will be merged right after 1.7.0 release
  * Will be part of 1.7.1
  
  
## Development organization

Organization of GitHub repositories: server code scattered over many repositories and this makes producing releases and following up issues quite complex
* Andrea proposes to merge all the server components into one repo: will result in 1 common version number for all those components
  * Would probably make the deployment management easier (easier to assess consistency of deployed components)
  * Need to keep the history of exiting repositories


## AOB

Next meeting : Friday, November 4, 2pm

There are minutes attached to this event. Show them.
    • 14:00 14:10
      General news 10m
    • 14:10 14:30
      New release: development and testing status 20m

      Development news (Andrea)
      Site testing (CERN, others?)
      Test suite and stress tests (Tamas)
      New PIPs (Misha)

    • 14:30 14:40
      UMD4 Integration status 10m
    • 14:40 14:50
      Open issues 10m

      Documentation ?

    • 14:55 15:05
      AOB 10m

      Next meeting