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

    Weekly Meeting

    by Steve Fisher

    → Europe/Zurich
    CR12

    CR12
    Description
    <html> <head> <meta name="generator" content= "HTML Tidy for Linux/x86 (vers 1st March 2002), see www.w3.org"> <title></title> </head> <body>
    • Reports on Meetings
      • None
    • Future Events
      • None
    • Actions
      • Review Registry Replication and how to introduce it - Steve F, Rob and John - 11/7/2005
        Progress not expected
      • Write test specification. - John - 1/8/2005. Will be updated when the tests are stable
        Progress not expected
      • Track Dave K's progress to check R-GMA publisher in L&B test. - Antony - 13/10/2005
      • Read the UDDI specs to relate to SD API - Steve F - 31/10/2005
      • Write more service tests (many identified by Rob) - John - 31/10/2005
        Martin is doing this
      • Write Distributed Full System tests - John - 31/10/2005
        Rob is doing some of these
    • LCG2_4_0/2_6_0 - Do we encourage 1.4.1? - Antony
    • PPS - Antony
    • Bugs
      • #12253 SFS Test Consumer/Join sometimes fails - Martin.
        What to do about entropy - there may be other problems. Fixing this may also fix 12255. Much better now but still fails sometimes. Martin will keep working on it.
      • #12255 SFS Consumer/MultipleProducers - FAIL (6 & 7) - Martin.
        Needs further investigation. May result from the entropy problem.
      • #12258 SFS Test OnDemandProducer/SocketProtocol - FAIL - Steve H
      • #13434 Schema.dropTable doesn't. - Martin
      • #13511 Inconsistent use of X509-USER_PROXY and TRUSTFILE env vars - Martin.
        It was decided to follow the java trustmanager style for priority and if nothing is set it crashes. Martin has done the Python and Java and will do the C and C++.
      • #13517 Clean-up not working for glue archiver - Martin
      • #13545 Errors in the System API - John
      • #13596 Rgma-client-check does not respect $X509_CERT_DIR - Antony
    • gLite 1.5
      • Write missing service tests - and submit bugs as necessary - Martin
      • Ensure that the services don't use deprecated calls to other services unless absolutely necessary. This might be a major issue, I'm not sure. In theory, the only calls that still need to use the old interface are startStreaming, stopStreaming, execute and getStatus on a producer, and addProducer and removeProducer on a Consumer (because these will be sent to services that have not yet been upgraded). Calls to the Registry and Schema should use the new interface only, and calls from the Secondary Producer Service to the Primary Producer Service and Consumer Service should also only use the new interface. If they don't, it means we will have to wait until 1.7 before we can remove the deprecated code, and particularly for the Registry, this means retaining a lot of code we'd like to remove.

        Get the list first - John will probably be able to fix - John

      • Go through all of the tools (Service Tool, Site Publisher, Flexi Archiver, Glue Archiver, GIN, Command Line, Browser, rgma-client-check, rgma-service-check/Pong, log4cpp and log4 and fix anything that's directly hacking into the servlets (e.g. getStatus or getNewStatus). There is an issue here of which API things like rgma-service-check (that can't guarantee to have the client APIs are installed) is supposed to use, but some of our users might just ask the same question, so it's worth thinking about it.

        Get the list of problems first and assign as necessary - John

      • set/getProperty - Rob
      • Add some load tests to the resilience framework - Rob
      • Check through the installed system for any obsolete files (e.g. config files), any obsolete entries in those files (e.g. obsolete stuff in rgma.conf), and obsolete public classes (check the JAR files) and any obsolete service calls (i.e. are we listing anything as deprecated in the new-servlets spec. that can actually be dropped). Re-run ALL of the compatibility tests after doing this.

        Should be done today (Friday) - Alastair

      • Ensure that all tools look in the same places for their dependencies, e.g. what they put in CLASSPATH and where they look for server certificates, etc. We should also document somewhere what the right answer is (it doesn't belong in the spec because that's only concerned with the APIs and services).

        Should be done today (Friday) - Alastair

      • Check the Servlets and Services code (two classes per service) to ensure that compatibility code is only in the servlets layer (or clearly separated methods in the services layer) and that service implementation (including partial implementation and not-yet-implemented exceptions) are in the services layer. If we get this wrong, we can forget trying to add other (e.g. SOAP) interfaces until it's fixed. - ???
      • Make sure we are clear what users should pass in for parameters like vdbName; decide what the services should do with these values and ensure there are Service tests to check that's what they do. - ???
    • Priorities for 1.6
    • Plan for week ahead
    • AOB
    </body> </html>
    actionlist
    document
    minutes