From GEANT2-JRA1 Wiki

Contents 1 Information 2 Agenda 3 ACTIONS 3.1 Last conf call actions: 4 Status Update 4.1 Ilias on RRD MA functional tests 4.2 Michalis on LS 4.3 Other 4.4 Next conf call:

Information

Date and Time: Friday 20 October 2006, 0900 hrs BST, 1000 hrs CEST, 1100hrs GR

The conf call are 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: 004910091212314***4522

ISDN 0049 30 254 10800

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

Backup - Skypecast (More information later)

Agenda

1. Follow-up on actions:

• IT: Attend the Montpeller session
• LK: raise point to ps-dev about the versioning issue.
• NS: raise PO for servers.
  • second one for functional testing (differnet OS) and trainning (on GEANT)
• MM: 5 type of request by the mid November
• Next meeting - Thursday, the 19th 11:00 CEST
• LK: liaison wiht developers on the snapshot version
• IT and MM : further thinking on how to check the inter-action between multiple services.

2. Status update

ACTIONS

• MM: investigate capability to install virtual server.
• NS: to send specification of the machines so that IT can double check with the system administrator if it is sufficient for the task.
• IT, MM: to comment on what's needed in the documentation from the functional testers standpoint:

http://monstera.man.poznan.pl/jra1-wiki/index.php/SA3-WI15-Pages

• 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.
• MM: fill the webpage by the 27 of October.
• NS: follow-up on schema documentation and template
• MM: ask Martin and Jason why there are some field which are mandatory and for which the data passed are of no importance.

Last conf call actions:

• LK: raise point to ps-dev about the versioning issue.
  • Point raised. To be followed by LK.
• NS: raise PO for servers.
  • second one for functional testing (differnet OS) and trainning (on GEANT)
  • Not done. Main question is what to do with the second one.

IT: deploy virtual servers on a host and run at the same speed, same memory (you can avoid having the need to have a machine for training and for functional tests). Anything would do for it. IT: for performance testing, you need to have similar specification that what we will recommend to the NRENs. Gentoo vservers: It will slows down the performances (open source, part of the gentoo linux distribution).

• LK: liaison with developers on the snapshot version
  • to do.
• IT and MM : further thinking on how to check the inter-action between multiple services.
  • Action still opened.

Status Update

Ilias on RRD MA functional tests

Get wroking on the parsing scripts. Expecting to have finished it by the 3rd of November. Expect to need about a week and a halve on the touch-up job by the 15th of November. Specification for 1.1 expected by mid November at the latest (one week before the first release candidate).

4 request (Some have multiple types)

• store request
• setup data request (filtering, chaining)
• metadatakeyrequest - done
• setup data request - done

In general it seems OK, but not tested.

Michalis on LS

Class for delivering the request and parse the response. (Store request and checked up the response and got a strange response when get more than one pair of data and metadata). He checked with Maciej to find out where the problem is (either in the LS or in the test scripts). Another potential bug with the LS: require the request to have an access point. 5 type of request:

• LS register request - done (stuck with parser class of the LS register request)
• LS update request - next request (very similar, with the addition of a previsouly generated key).
• Deregister request
• Keepalive request
• LSquerry request

Problem with bugzilla - don't communicate with each other.

Other

MM: mis-understanding about what should be in the request. Some elements must be there, but if there is no values needed, that's working fine too. What's the point of having them. IT: they are there for the schema itself.

MM: need proper documentation!!! We need a RFC like document (what actions each service takes). That's crucial for functional testing.

Integration testing are the next steps.

Next conf call:

Monday the 30th of October same time.