Go to the Indico Home Page Oldest event Older event Up to category Newer event Newest event Printable version
  • Event
  • Lecture
    • Switch to the management area of this event
    Login
    JRA1-UK

    R-GMA and SA1

    by Steve Fisher

    → Europe/Zurich
    +41 22 767 7000 and ask for R-GMA/Fisher

    +41 22 767 7000 and ask for R-GMA/Fisher
    Description
    <html> <head> <meta name="generator" content= "HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org"> <title></title> </head> <body>
    • Actions
      • Tidy up inspector, too much data is displayed on the page. Organise R-GMA tutorial for SC - Rob/John - 29/9/2005.
      • Introduce new test for APEL - Piotr - 31/10/05
      • Test the JRA1 flexy tool - Laurence - 21/11/2005
      • Make use of the information from Dave Kant's checking scripts to spot RB problems early - Antony - 21/11/2005/
      • Monitor introduction of secure connectors - Antony/Laurence - 5/12/2005
      • Fix client test on patch 617 - Steve H - 20/12/2005
      • Look into a problem with the GLUECE and SE table - Antony - 20/12/2005
      • Quick hack to publish data from Dave Kant's checking scripts - ??? - 09/01/06
      • Upgrade to patch #633 - Laurence - 9/1/2006
      • Provide estimate for when R-GMA will support Oracle - JRA1 - 09/01/06
      • Provide list of sites who are having problems with their host certificate - Piotr - 09/01/06
      • Change the SFTs will to grep the rgma.conf file for https - Piotr - 09/01/06
      • Contact Ludek about L&B log - Laurence - 09/01/06
      • Package Steve H's change for the date field used by the job status publisher and distribute it - Laurence - 09/01/06
    • New issues
      • Consider Laurence's e-mail: 
        1) Certify new versions of R-GMA before we push out a release.
        
2) Check that R-GMA Server at a sites is working correctly.
        
3) Check that the different publishers that are running at a sites are
correctly working.
        
4)  Ensure Archivers are working correctly.
        
5) Monitor the performance of R-GMA so that we can spot and fix bugs.
        

        
We need to do things in such a way that:
        

        
1) The operations team (CIC on duty etc.) are checking that things have
been deployed correctly.
        
2) The certification team are testing new versions of R-GMA.
        
3) The R-GMA team is free to only concentrate on fixing bugs and
improving R-GMA.
      • L&B problems and responsibilities
      • LCG2.7 and YAIM testing
    • AOB
    </body> </html>
    actionlist
    minutes