Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

\uD83D\uDDD3Date

14:30-15:30 UTC

\uD83D\uDC65Participants

ET-W2AT

WMO Secretariat

\uD83E\uDD45Goals

\uD83D\uDDE3Discussion topics

Item

Presenter

Notes

  1. Opening

Jeremy

Topology was discussed at last weekly meeting.

MQP protocols include …

2. Presentation by Remy

Remy

Remy presented WIS2.0 MQP Architecture and Data Exchange Topology Disussion

  • Core services: Global broker, Cache, Monitoring

    • a small number of “Global Brokers” (3 or 4)

    • a small number of cache

    • a small number of monitoring centers

  • Topology: NC/DCPC

  • MQP:

  • Auto discovery of the services

3. Discussion

All

Thorsten

  • MQP: NC to run the MQP ?

    • (Remy) Transition: 5/6 years. All NCs run a broker gradually.

    • (Peter)

      • (Remy) WIS2 architecture is not only about GTS data, but to deal with all data and services

    • (Henning) Any selection criteria for 3/4 global brokers?

      • (Remy) no strict limit for the number, cache, gateway, metadata.

      • (Thorsten) a list of services to be defined is helpful for WIS2 architecture.

    • (Jeremy) shared service model agreed?

      • (Enrico) a structured way of approaching the model

      • (Remy) two operational core services at least.

    • Kai

      • less optimistic for all NCs to be running as a broker and store data. Some service cannot be run as a shared service, such as gateway.

    • Peter

      • cache and the broker work together, do not split

    • Timo

      • messages advertertize the data

      • data storage

    • Kai

      • WIS 1.0 metadata: quality and completeness problems

    • Enrico: it is members to decide the engagement of private company

    • Hassan

      • to start by asking the volunteers to run the global brokers

    • Remy

      • the need to split cache and broker: cache is only for weather data; and broker in WIS2.0 is for all data

      • commericial providers: cache service for LDCs

    • Jeremy

      • AOR

        • Enrico: problem of AoR is that when they have requests, the GISC cannot meet the need. Function of AoR should be dynamic, be outside of Manual.

        • Jeremy: mechanism is needed for the implementation of AoR

        • Timo: to use monitoring for activie services.

        • Remy: Although AoR concept is outdated, we now only focus on important pillars

        • Kai: some GISCs provide service to AoR. During transition period, organization is needed.

        • Enrico: We secretariat now have the regional officers to help during transition.

    • Question: metadata catalogues; how is all the information shared? (to be discussed next time)

    • Question: Center running a cache

    • Timo: to make sure discovery metadata work is the core service of WIS2.0

    • Hassan: learn the architecture of YouTube providing search, download, notification…

4 Wrap up

Remy

The team agree that shared service works in WIS2.0 architecture

To work into 2 ways:

1) TT-GISC feedback on running the shared service

2) Transition period: GTS centers to receive data from WIS2.0

Next step:

  1. workflow

  2. a list of shared service

✅Action items

  •  

   

⤴Decision

  • No labels