Functional-test-call2

From GEANT2-JRA1 Wiki

Contents

[edit]

Information

Date and Time: Tuesday 31 October 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: 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).
  • IT: talk to sysadmin about virtual server.
  • MM: ask sysadmin about installing the OS on the server.
  • 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.
  • 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.
  • NS and LK to follow-up on the documentation.
[edit]

Last Call actions

  • MM: investigate capability to install virtual server.
    • Should be OK.
    • NS: 6 weeks for procurement + 1 week to ship.
    • What type of Operating system does Cynet use. Is it OK for them to install the operating system and maintain the box.
    • 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:
  • 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.
    • No template out.
  • MM: fill the webpage by the 27 of October.
    • Done.
  • NS: follow-up on schema documentation and template
    • On-going for the template.
  • MM: ask Martin and Jason why there are some field which are mandatory and for which the data passed are of no importance.
    • They are not mandatory even if mentioned on the wiki. Update the wiki and the documentation.
    • Michalis to send the pointer, NS to ensure that the page are updated.


[edit]

Status Update

[edit]

Ilias on RRD MA functional tests

  • No new functionality due to local dealine. Should be back full time at the end of the week. Started on the set-up data request with metadata. So far 2 requests out of 6 have been done.

ACTION: add the list of request and which are ready. IT: investigate if redhat has virtual server to get the same support.

ACTION: throw an eye on the virtual server for redhat.

[edit]

Michalis on LS

Finished the second request, some things don't work as they are suppose to. The service lack functionalities specified in the schema.

  • LS register request - done (stuck with parser class of the LS register request, some things are not implemented in the service)
  • LS update request - next request (very similar, with the addition of a previsouly generated key). Some things are not properly working.
  • Deregister request
  • Keepalive request
  • LSquerry request

MM: do we need to have more information about why the test fail? IT: yes, you should because someone else may use your script and don't understand why a test failed. And for you too it is useful as you will have to contact the developers. A Normal way of work is to send the request and the response and let the developer deal with it, but additional info as the one you suggest would be nice (but it is optional). MM will add it later on. MM: there is a problem with the NM-WG handler of the schema, in touch with Martin and Jason.

Next steps: more investigate on the parsing of the request. Will start the creator class for the third class of the request.

[edit]

Other

  • IT: question about release management: due date too soon. November the 10th, you can't have the functional test ready by November the 17th.
    • Talk to Loukik about finding out a more suitable date for the functional test scripts to be ready.
  • Clarify the difference of use in our case between environment and virtual server. ** Different environments: performance testing, training purpose, functional testing, production.
    • Virtual server: multiple OS on a single machine (Allows multiple operating system).
  • NS to send to MM: Who to access the server, who to maintain and support.


[edit]

Next conf call:

Thursday, the 9th of November.

Retrieved from "http://wiki.perfsonar.net/jra1-wiki/index.php/Functional-test-call2"
Personal tools