Functional-test-call3

From GEANT2-JRA1 Wiki

Contents

[edit]

Information

Date and Time: Monday, the 13th of November 2006, 0930 hrs BST, 1030 hrs CEST, 1130hrs GR

The conf call is about the progress on the functional test suite for the LS and the RRD MA.

Gatekeeper: pgk.vc.dfn.de (for non-GDS members)

  • GDS number:***4522

ISDN

  • Listen to the lady
  • Type conf-id***4522#

Backup - Skypecast (More information later)

[edit]

Actions


  • IT co contact RL and work closely with him on the interface changes between 1.0 and 1.1.
  • IT to get an understanding on the effort and timelines for the implementation of 1.1 tests.
  • LK to contact RL to describe what's expected from him on what's needed.
  • LK to schedule a conf call for Wednesday afternoon UTC: 14:00, CEST: 15:00, 16:00 GR.
  • NS: clarify with AP the difference between virtual server and environment.
  • NS: send to Michalis the different type of use and access to the server. (who to access it and what for, which port to open)
  • IT, MM: to comment on what's needed in the documentation from the functional testers standpoint:
  • IT: In respect with the previous point, Ilias to mention if it is relevant to the existing information or to the template that will be provided.
[edit]

Last Meeting actions

  • IT: Mention to Loukik about the timeline (17th of November) to have the script finished. Not enough time. We need to find a more suitable date for the functional test scripts to be ready (liais between LK, MM and IT).
    • Covered over the conf call. See IT actions.
  • IT: talk to sysadmin about virtual server.
    • Virtual servers available fro Redhat, open source free of charges.
  • MM: ask sysadmin about installing the OS on the server.
    • OK for Cynet to get the support
  • NS: clarify with AP the difference between virtual server and environment.
    • Not done.
  • NS: send to Michalis the different type of use and access to the server.
    • Not done.
  • IT, MM: to comment on what's needed in the documentation from the functional testers standpoint:
  • IT: In respect with the previous point, Ilias to mention if it is relevant to the existing information or to the template that will be provided.
    • Awaiting for the templates.
  • NS and LK to follow-up on the documentation.
    • On-going.
[edit]

Status Update

Attendance: Michalis, Loukik, Nicolas, Ilias, Luis.

[edit]

Lookup Service

  • LS register request - done
  • LS update request - done
  • Deregister request - done
  • Keepalive request - done
  • LSquerry request - done (need to do the class for response parser, script that coordinates the requests - Estimate it to be done by 17/11)
  • Next step coordinator.
  • Follow-up test: robustness test (need modification).

Maciej suggested to used ANT. Is it the right choice?

LK: when you get a request with an error, what's happening? MM: I parsed the request, knowing what is expected, then the test has passed. MM: If the error code is an error, it is also checked against the DB that this is an error.

LK: have you done some tests against the LS. MM: yes, I have found some bugs and sent them to Maciej.

MM: investigate the capability of testing different cleanup time. But it is quite difficult, because we are missing an API.

MM: don't know what's right or wrong because there is a lack of documentation. So what Maciej says is what's right (as there currently a lack of documentation).


[edit]

RRD MA

  • store request
  • setup data request (filtering, chaining)
  • metadatakeyrequest - done (1.0) - refinement for the parser
  • setup data request
    • with a key
      • filtering - request and deliver are done. Working on the parser. (1.0)
      • chaining - not started.
    • without a key
      • filtering - request and deliver are done. Working on the parser. (1.0)
      • chaining - not started.
  • coordinator script - done

All the parsers for the RRD MA will be done by 24/11 for 1.0.

IT: no documentation about error codes. IT: not installed the 1.1 version.

LK: should focus on 1.1 instead of 1.0. LK: the biggest difference are the results code implementation, plus other minors ones.

IT: need to know about what changes happened between 1.0 and 1.1. The changes are trial, will take some time. (4-5 hours for testing).

[edit]

Next Conf call

  • Wedesday afternoon UTC: 14:00, CEST: 15:00, 16:00 GR.
Retrieved from "http://wiki.perfsonar.net/jra1-wiki/index.php/Functional-test-call3"
Personal tools