1.Progress on the preparation of the performance tests of GS (all GSs)

• GB(Rémy)

  • Share VMs running on AWS + WIS2 Node deployment + central broker is ready + WIS2 nodes are subscribed by gb.wis2dev.io

• GDC (Tom)

  • python is a prominent language, common framework, codes set up needed in repo, weekly Thursday meeting (Rémy+Max+Tom)

• Jeremy (dev GB, dev GM) Question1: dev GC and dev GDC are needed too?

  • (Rémy) Global service testing, no need for GC wis2dev.io and gdc.wis2dev.io. The environment will be used for further tests. wis2dev.io has all the components.

  • (Rémy) master.wis2dev.io, will be migrated to EWC, giving access to all GS testing participants.

• Jeremy Question2: are you ready to plug in the python testing environment? adoc (summary) → pytest environment

• Max:

• Documentation is available: https://github.com/wmo-im/wis2-global-services-testing/blob/main/tools/Documentation/Preparing%20Global%20Broker%20for%20functional%20and%20performance%20testing.adoc

  • GDC (Tom): to complete the documentation this week

  • GC(Max): to complete the documentation (setup and teardown) this week and start working on actual tooling

• Rémy: coordination work is not yet discussed. Independent testing contact points from tested GS operators.

• Jeremy: First half September to test the orchestration test scripts

• Hassan: pre-test/dry run

• Decision: the GS operators to inform Hassan if the GS test participants want to do the dry run after the orchestration test scripts is completed and before the real test

• XUE Lei: any downloader is needed for GC? (Rémy) Some WIS2 nodes will emulate the downloader.

• GC (South Korea): Yes, to join the GC test. (temporary set up on the same date as Saudi Arabia)

• GDC: Lei to review GDC documentation for GDC (CMA), and Lei to contact Hassan to schedule a mock test in the second half September

• GM: (Jeremy) Priority: metrics, alerts, Jira tickets tests are higher than the GM dashboard in scripts.

  • (Lei) Asking if any documentation to be shared to access Jira IMS system.

  • Hassan shared an update. An Jira account was created for GM (Morocco) to access Jira IMS for test. A meeting will be scheduled this week between CMA and Secretariat.

  • Chems: Antje, Masato and Hyunmin to review the GC Dashboard to validate it provided by GM(Morocco). The next step is to move onto the GDC Dashboard. (in 2 or 3 weeks)

  • Hassan: to coordinate the GC/GDC Dashboard provided by GM (Morocco)

  • Lei: to discuss with Chems about GC/GDC dashboard before reaching out to GC/GDC to review.

  • Antje: to open a Github issue how to keep metrics clean over a longer period

2.Progress of the dashboards for GC and GDC (China, Morocco)

GM(China) and GM(Morocco) have the regular meeting.

GM(Morocco) dashboard for GB is ready, working on GC, plans to move to GDC in 2 or 3 weeks.

3.metrics for the transition from GTS to WIS2 (Morocco)

Chems:

Antje: the amount of message differs between the number of GTS messages and WIS2 messages. (Chems) GTS bulletins are extracted as a single file to be counted as single WIS2 file.

(Rémy) comparison between the messages coming from GTS-to-WIS2 Gateway and coming directly to WIS2 from the Members is needed. Metrics names need the conventions too. (wmo_wis2_gm_messages_gts needs to be renamed)

4.Incident management system (WMO, Morocco)

Hassan presents the current progress of IMS provided by the Secretariat and a list of questions including accident definition, type of incidents, whom to be informed to discuss.

Proposed time for discussion: November. (With Chems testing the access to Jira system as a starting point)

Decision: Hassan will present the progress at our next meeting on the Jira IMS system.

5.Gateway WIS2 to GTS (China)

Whitelist: a list of TTAAiiCCCC and centre-id that are ready to turn off their MSS system.

Action: Jeremy to connect Lei to Met Office WIS2 to GTS gateway team for further discussion.

Action: Lei to create a Github issue for this.

Rémy proposed to get JMA and BoM to review the gateway is fully GTS compliant.