2025-01-20-ET-WISOP meeting

Date

20 Jan 2025 13:00-15:00 UTC

\uD83D\uDC65 ET-WISOP members

Invited Experts

• Rémy GIRAUD (SC-IMT Chair)

• Jeremy TANDY (SC-IMT Co-vice-chair)

Others

• Wenjing GU (CMA)

• Vera KORBULAKOVA (Roshydromet)

• Kai Wirt (DWD)

WMO Secretariat

• Enrico Fucile

• Hassan Haddouch

• Xiaoxia Chen

• David Inglis Berry

• Anna Milan

• Timo Proescholdt

Preliminary agenda

1.Review the GISC Roles action list

2.Update on the Incident Management System (IMS) JIRA and its way forward

3.GISC Watch

4.WIS2 Operational Newsletter

5.AoB

Meeting note

1.Review the GISC Roles action list, presented by Lei

https://github.com/orgs/wmo-im/projects/61

GISC Roles: short-term (by April 2025), mid-term (by September 2025) and longer-term (2026)

Q: All GB operators: discard invalid messages?

A: (Rémy): not yet; A:(Tom) WIS metadata, TT-WISMD needs to validate at the next FastTrack. Leaf vs non-leaf, Validated Topic Hierarchy . Decision: more clarification other than change in the Specification.

GB (China) has already switched on discarding invalid messages. (schema)

GB(France) will implement the schema discard.

Question: who to notify the WIS2 node having the invalid schema, GISC or GB?

Decision: To invite the GISC to take a look and liaison with the centres.

Action 1: All ET-WISOP members to share with the GitHub handlers with Hassan to get access to the GitHub repo project. Now only need to focus more on short-term tasks(15 items). To complete the status of each action item.

(Hassan) There is no order for the 15 action tasks. The aim to complete all these 15 items by April 2025.

2.Update on the Incident Management System (IMS) JIRA and its way forward

(Enrico) Presents Guide to WIS2 IMS. To create a ticket (Triage) → Assign (To-do/In progress/In review/done)

5 status: Triage/To-do/In progress/In review/Done
3 types of issues: incident/maintenance/support

4 priorities: low/medium/high/Very high

Labels: WIS2 components (such as Global Broker, Global Cache, Global Discovery Catalogue, Global Monitor, Node, WIS2_to_GTS_Gateway, GTS_to_WIS2_Gateway)

(Amro) to present the Jira system

Question from Lei:(1) Any sound alert available for the tickets?

(2) Any API to be used in local operational system?

(3) How can I delete the tickets by bulk? (Amro will check this feature.)

Question from Chems: is it possible to add associated centre in the tickets?

Question from David: are all tickets needed for On-duty GISC Watch to triage?

Answer: People creating the ticket manually can assign the ticket to known entity directly.

Rémy: automated tickets are created for important operational reasons. The functions of assigning the automated tickets directly to the relevant GISCs is needed.

Users creating tickets can

3.GISC Watch

David Podeur will lead the task, working together with GISC Tokyo.

(Quite note from ET-WISOP kick-off meeting for this item)

Decision 1: no GISC watch first four period, (Beijing, Melbourne, Pretoria, Exeter) till 28 Feb 2025, no GISC Watch for the last http://period.No GISC watch from 16 December 2024 to 28 Febuary 2025
Decision 2: GISC Jeddah to be included in the GISC Roaster
Decision 3: GISC Watch Guide (a doc format), David will lead this task.
Decision 4: period for each roaster: 2 weeks

4.WIS2 Operational Newsletter

The first WIS2 operational Newsletter was issued on 9th January: https://community.wmo.int/en/news/wis2-operational-newsletter The newsletter was sent to 800+ contacts including Experts in SC-IMT, NFP on WIS matters, and also the subscribers. 90% was delivered, 45.5% open the email, 17.3 clicked the links shared in the newsletter.

5.AoB

GISC watch roater: monitor different aspects

Difference among different Global service operators is now observed from GM dashboard. It can rise from two reasons, one for the metrics, the other one for the Global Services operators.

Action: The Grafana Dashboard for all GISCs will be available after GM (China) and GM (Morocco) make some adjustments.

Next meeting:

3 February