Opening

Rémy

Rémy introduces the participants, highlighting their roles in Global Services.
Rémy also welcomes new participants from NCM, Saudi Arabia, willing to provide the Global Cache services.

Update on progress

Rémy

Test specification were shared on GitHub. GitHub - wmo-im/wis2-global-services-testing: WIS2 Global Services testing

• GB missing components (awaiting Steve's Pull Request for the second version)

  • Steve: it will be completed today.

• GC: No progress; Max will provide an update soon.

• GDC: Currently on hold due to Tom’s vacation.

• GM: no progress from last week. XUE Lei will update after discussing with Chems.

Test infrastructure update

Rémy

A set of VMs to be used as WIS2 Nodes, will be deployed for 3 months. Rémy to share the details with Timo to implement the test environment.

(Question: Steve) Two test environment

• (Rémy) WIS2 Dev environment is different from Performance Test for Global Services in October. For WIS2 Dev environment, GC is missing. Option 1 is to use the stripped down version of the current GC provided by UK/USA (SYNOPTIC). Max will provide the cost of stripped down version of the GC on AWS cloud credits to work as one option, which is pending to decide.

GC (NCM)

NCM colleagues

Saad Almajnooni requests to have a one-on-one meeting with Secretariat and/or Rémy for the next steps.

Rémy confirmed that the next steps for NCM to connect to the WIS2 Network is 1) to provide the GC endpoint connections details with the Secretariat to be shared with all GB operators to subscribe to the GC(NCM). 2) the Secretariat to share the GB connection details with GC(NCM) to subscribe.

Xiaoxia confirmed such information was shared last Tuesday and will resend it.

Timetable change

All

The final report of the Global Services Performance Tests Preparation meeting held from 21 to 24 May 2024 in Tokyo, Japan , with the updated schedule, can be found here.

Highlight of the changes:

Global Broker:

• China: 30 September 27 September

• France: 1 October 30 September

Global Cache:

• Saudi Arabia: 10 October

• Japan: 10 October 11 October

• Korea: pending confirmation to join the test

(Note: Considering a) Korea (KMA) is likely not to join the test, pending confirmation, and b) Friday and Saturday are the official days of rest in Saudi Arabia, JMA readily accepted the adjustment, moving the date from October 10 to October 11. Test for Saudi Arabia is scheduled on 10 October. If KMA decides to join the GC test, an additional day will be scheduled.)

• Germany: (Antje) From Thorsten: It is still not confirmed whether DWD will take part in the Performance Test in October due to significant issues related to the reorganization within DWD.

  • (Action): Rémy to schedule a bilateral meeting with Thorsten to discuss this.

Discussion

All

• GC(JMA) & GC(UK/USA) shared cache?

  • (Masato) to schedule another meeting with Jeremy, Max to discuss it.

• Prometheus instance available for tests

  • (Antje) Asked if any Prometheus instance in the test environment is available for the API to request the metrics?

  • (Rémy) Confirmed currently no single instance is available. To be discussed at the later stage. (For the Metrics collection during the test. )

• Global Cache testing

  • (Antje) Clarified the need for performance test of parallel downloads from the data server

  • (Rémy) Explained two tools are currently described: one for creating notification messages and one for data generation, planned for Global Cache test.

• Getting data out of Global Cache: Using JMeter?

  • (Max) Suggested using tools like JMeter for performance tests, inviting suggestions for alternatives.

  • (Antje) Agreed JMeter is suitable and emphasized the need for shared tools to avoid parallel installations.

  • (Action) Max to provide a proposal for the team to agree on

  • (Rémy) Highlighted the need to write specific scenarios for JMeter to test file downloads.

  • (Action) Max, Antje and Lei to discuss on the proposals for the different scenarios of GC and test them.

• (Timo) metrics calculation and consistency across Global Services.

  • (Rémy) Metrics will be part of the assessing the result. Functional test will be YES or NO, relying on the actual results observed from the test subscribers. Performance test is served as complementing, but not solely determine, the test results.

  • (Action): Timo to provide the texts to add the predictable scenarios

Next meeting

All

22 July 13:00-15:00 UTC to continue discussion on the updated version of GB document, GDC, GC and download part.

Teams Link:

Join the meeting now

Meeting ID: 354 241 739 113

Passcode: 35YDCC