GN2 SA3 Provisioning System Development Weekly Teleconference

Date

Location

Type

Attended By

Apologies

New Actions

1. BB to test if Bugtracker #15 is fixed in Pathfinder v0.98.
2. TR to retest and close Bugtracker #23.
3. BB to setup dir structure for the Config module in CVS.
4. BB to add the issue of granularity of timestamp in MySQL^?/PostgreSQL and Java as a feature request in flyspray.
5. BB to add the issue of conflicting SID in different domains as a feature request in bugtracker.

Ongoing Actions

1. BB to assign the bug about DB restart and hibernate loosing connections to a developer.
   • Bugtracker # 11
   • This was assined to a person who is now leaving PSNC. Needs to be reassigned to another person. Ongoing.
2. GRNet to check if traceroute can be used with the hopcount and/or start options as described by WZ.
   • This has been done in unix
   • for windows this is not done. WZ: there is a -h option.
   • CM to get this done for windows as well.
3. BB to explain the scenario of a fully internal reservation within a single domain with a diagram to the list.
   • BB: Ongoing
   • TR to do this on GEANT2 and DANTE topology
4. GRNet to test that PF works correctly in the fully internal reservation scenario
   • CM: Some of the testcases work with existing PF
   • CM We will test again with the new version.
5. GRNet to check how the cache is cleared. If this is not currently done by the Pathfinder then log this as a feature request for Pathfinder in phase 2.
   • CM to add this as a feature request in bugtracker.
6. PSNC to send their test scenario for pathfinder to GRNet and raise any bugs/issues in flyspray.
   • BB: Scenario sent.
   • BB: I still have to raise the bug. Ongoing.
7. GRNet to update the size of url field to 255 in the NIS and email the change to the list.
   • WZ has upgraded this to 100.
   • WZ to update this to 255. Ongoing.
8. TR, BB to update the network diagrams on wiki to include temporary changes to PSNC connectivity to GEANT.
   • TR: Done.
   • BB: Ongoing.
9. BB to add the internal subnets to the topology diagram on the wiki for internal reservation scenario.
   • Ongoing.
10. ALL to write up a testplan for Pathfinder for Intra-domain PS and Interdomain PS.
    • AP to create a new wiki page
    • ALL: Ongoing
11. ALL to test Pathfinder on their local installation.
    • New Pathfinder v0.98 released. Ongoing.
12. APO to give the pros and cons of the two policy module integration approaches.
    • APO: I do not understand this action.
    • AP: Which one should be called to check first - availability or policy? Discuss with TR also.
    • Ongoing
13. FX/SM to report the decision taken in this meeting to AP/TR. AP/TR can then re-evaluate what work can be assigned to FX/SM to make more efficient use of the resource.
    • Ongoing.
14. WZ to implement the CLT parameter in Intra-domain PS and refuse reservations if starting less than CLT.
    • Ongoing.
15. WZ to add a batch job so that Intra-domain PS will trigger the config module in phase 2. Add to flyspray as a feature request.
    • Ongoing.
16. FX to add exceptions to the the configuration module schema/wsdl.
    • Ongoing.
17. WZ to write a autodeploy script.
    • WZ: 2 scripts required one to build one to deploy. These are almost done. Nneed to generalise them for use by all
    • Ongoing.
18. ALL to update the install documentation as per RedIRIS feedback.
    • Ongoing

Completed Actions

1. GRNet to check if the 'DB-restart/hibernate-lose-connection' problem occurs with Torque/Pathfinder as well.
   • APO: Yes this happens with Torque also.
2. GRNet to test that PF returns a proper error message if ICMP is blocked.
3. GRNet to test that PF returns a proper error message if traceroute hangs.
4. GRNet to test that PF is able to handle "* * *" situation in traceroute.
   • CM: This is tested to be working in Pathfinder v0.98 - fixed by WZ.
5. GRNet to check that NIS supports the router - switch - two routers scenario.
6. GRNet to test that PF works correctly in the router - switch - two routers scenario.

   APO

   I have tested this with CM and it works exactly as with the router-router scenario.

7. GRNet to test if caching functionality works correctly in pathfinder.
   • Done by WZ.
8. GRNet to look into the PF giving null pointer exception problem.
   • CM: This should be solved in Pathfinder v0.98
9. GRNet to ensure that all internal PF exceptions are wrapped into a SystemException^? or other suitable exception.
   • Done by WZ.
10. GRnet to check on the code change on CVS done by WZ.
    • APO & CM: Done.
11. CM to update Pathfinder installation documentation to inculde the fact that traceroute should be installed and be on the path and the Pathfinder and the application has correct access rights to execute it.
    • Done by AP.
12. APO to send the draft Policy Module desing and architecture to the list.
    • APO: Done.
13. CM to create similar dev dir structure as Inter and Intra PS for Policy Module. A separate project will be created for PM and will follow the same directory structure and ant tasks etc like Intra-domain PS and Inter-domain PS module.
    • CM: Done
    • AP: Change name to PACE-PM - done by BB.
14. CM to use the factory methods as done by WZ. WZ to help CM.
    • CM/WZ: Done.
15. BB to check if the auto deploy software used in PTS is usable for PS.
    • BB: too complicated to use for PS.
    • AP: Marked as Done.
16. APO to ensure that the quota should be an integer field and is large enough to store large quota values.
    • APO: Done.
17. APO to define the Policy Module interface and mail it to the list.
    • APO: Done - the interface has already been implemented and uploaded to CVS.

Abandoned Actions

1. APO to explain the scenario with router - switch - two routers with a diagram to the list.
   • APO by email: Done in Paris meeting and does not need further explaination.
2. APO to give a comparison on actual usage of (1) only groups and (2) groups plus scope with example scenarios to the list.
   • APO by email: This has been discussed live at Paris. There is a scope example at the presentation that I have sent. I don't see any point in repeating myself, if you want we can discussing at the next meeting.
3. APO to give examples of scope mapping to the list.
   • APO by email: Also discussed at Paris. Besides we said that mappings will not be implemented, they may be implemented at the future if we find them useful.

Minutes

Pathfinder Update

CM: New version 0.98 of Pathfinder is released. Following bugs have been closed:

1. Bugtracker #14
2. Bugtracker #20

Bugtracker #15 - CM: new version 0.98 should have fixed this.[ACTION] BB to test.

Bugtracker #12 - NIS DB - update url field to be 255 characters. [ACTION] WZ

Bugtracker #23 - AP: Is IP validation done in Pathfinder?
CM: Yes IP address is checked.
[ACTION] TR to retest and close.

CM: Can we edit the first page of PS - to create a new page for Policy module?
AP: Yes.

[ACTION] BB to setup dir structure for the Config module.

Work for Next Week

• To test the MD with actual PF.
• BB this will be done in next 2-3 days.
• PSNC to focus on MD testing.
• GRNet to test PF as indipendent service with focus on MD requests.

Issues

BB: We found the following issues during testing:

• Utilisation module: Timestamp on MySQL^? and PostgreSQL^? granularity of seconds. Calendar on java has upto millisecond. This causes a mismatch.
• AP: We should tackle this in phase 2
• AP: Create our new class as a wrapper for calendar object which sets milliseconds to zero.
• [ACTION] BB add this as a feature request in bugtracker.

BB: What happens if people do not clear their test databases in time. Then it may happen that a SId exists in one domain and not in the other.
AP: We should handle this case in phase 2.
[ACTION] BB to add this as a feature request in bugtracker.

AP: To coordinate testing everyone should clear their DB at the same time.

AOB
None

DONM
25 Nov 2005 1030 GMT / 1130 CET

-- AnandPatil - 22 Nov 2005