(Rémy) Emphasizes there are numerous open issues discussed over the past weeks and highlights the importance of making decisions to move forward with the pre-operational phase. The approach involves categorizing the issues by urgency. One urgent issue concerns the accuracy of data and metadata flows reported by Kai. The plan is to rewrite the documentation. This process will extend to other issues, with a goal of making decisions and closing issues.
(Jeremy) WIS2 documents to be submitted to INFCOM-3 to be held in April need to be finalized by the first week of February, including WIS2 guide, Transition Guidance, Pilot phase final report and preparation of pre-operational phase. Jeremy guides through the organization of current project: https://github.com/orgs/wmo-im/projects/30/views/2, aiming to identify and close various issues. Urgent matters are to be discussed in ET-W2AT to be held in USA next month. Jeremy provides instructions for adding WIS2 related issues (which need to be tagged accordingly) to be better tracked.
(Summary background) the current WIS2 guide session 4 (https://wmo-im.github.io/wis2-guide ) is too technical for readers, especially for those implementers. The consensus is 1) to discuss data and metadata sharing introduction in WIS2 guide to be written in which detailed level; 2) location for detailed information
(Rémy) 1)emphasizes the need for the separate resource to accurately reflect the agreed architecture, even if it is not directly included in the WIS2 guide. GitHub should be consistent with the new WIS2 guide architecture https://wmo-im.github.io/wis2-guide/ 2)WIS2 guide needs to be user-centric and implementation centric. Specification to be kept for availability but to be published in the Guide. E.g, WIS2 node registration documents, is to showcase which level of details to be included in the WIS2 guide.
(Baudouin) graphs is readable. But don’t put everything in one diagram if there are conditions.
(Rémy) Tools used for creating the diagrams: Mermaid Markdown
(Actions) Tom to open a new issue in the WIS2-Guide repository to check that Mermaid Markdown can be incorporated into the asciidoc publication workflow
(Decisions) The team agrees a) remove WIS2 guide session 4- data and metadata flows and publish in a separate document with the simple data sharing removed. b) an external link to detailed technical specification (no need for INFCOM approval) to be determined
(Jeremy) The WIS2 guide is served for users including: end data consumers, those operating wis2node or operating global services. The current session 4 to be removed is more for developers.
(Tom) emphasizes the need for a definitive source to explain the workings of the system. Proposes a technical blueprint details to be in a separate document, such as WIS2 Architecture implementation guide?
(Weiqing) Does WIS2 guide need to be approved by INFCOM?
(Enrico): YES
(Hassan) In WIS 1.0 guide, there was a link to an external resources for detailed technical specification.
(Rémy) discussion for external document location is not urgent.
(Baudouin) No special treatment towards data and metadata. There are two methods to handle it. One is what Rémy suggests, pushing the entire catalog as a file daily, with potential redundancy. The other is the proposed approach, allowing the data provider to set the cache lifetime, which aligns with simplicity and respects the data provider’s specified duration. The decision rests on the group’s consensus.
(Decision) Agrees that Global Cache treats metadata and data at the same level.
WIS2 components local broker
(Rémy) Suggests a method involving the GDC creating a file with all data and publishing a notification message. Each component in WIS2 needs a broker.
(Tom) Emphasizes the importance of treating metadata and data equally in terms of cache retention.
(Kai) Suggests the possibility of different WIS2nodes or Global Services (including GDC) sharing a common broker.
(Enrico) GDC, GC, a local broker needs to be known. Needs to be registered.
(Tom) GDC publishes a daily message that points to the new archive. Acknowledges there is a need to consider various types of reports that may be employed through this mechanism. Expresses readiness to handle the technical aspects, emphasizing the importance of updating the WIS2 guide for clarity on the responsibilities involved in this process.
(Action) Tom: open an issue to start identifying different types of report messages
Managing WIS2 monitoring and Alerting Repos
(Rémy): Currently, there are other two repos. One is WIS2 monitoring (more on implementation), the other one is wis2-metric-hierarchy (a follow-up on Topic Hierarchy). Whether to create a New Repo-WIS2 alerting.
(Action) Rémy will prepare presentation to trigger the discussion on WIS2 monitoring and alerting. And then decide how to structure these topics.
Cache lifetime discussion
(Weiqing) Who decides the duration of data being cached?
(Hassan) tech regulation, by default, at least 24 hours
(Action) Jeremy to 1) create an issue for cache lifetime (not urgent, for next year); 2)create an issue for notification message repo regarding considering adding an expiry time
Agree agenda for face-to-face ET-W2AT meeting, November 13-15th.
Not discussed
Action items
Tom: open a new issue in the WIS2-Guide repository to check that Mermaid Markdown can be incorporated into the asciidoc publication workflow (Rémy shares the visual code of the WIS2 node registration flow diagram with Tom)
Rémy will prepare presentation to trigger the discussion on WIS2 monitoring and alerting. And then decide how to structure these topics.
Tom to open an issue to start identifying different types of report messages
Jeremy to 1) create an issue for cache lifetime (not urgent, for next year); 2)create an issue for notification message repo regarding considering adding an expiry time
Tom to finalize the proposal of merging country and centre-id within TT-WISMD and then present it for approval in ET-W2AT
Decisions
Agrees to remove WIS2 guide session 4- data and metadata flows and publish in a separate document with the simple data sharing removed
Agrees that Global Cache treats metadata and data at the same level.
Agrees that each component in WIS2 architecture has a local broker. (GDC needs a local broker too.)