...
Item | Presenter | Notes |
---|---|---|
| Rémy | Discussion on /wiki/spaces/WIS2/pages/306970677 Thorsten: it is better to seperate political issues from technical solutionsfocus more on technical functions and let the political issues outside the discussion Remy: 15 GISCs, running same cache/Catalogue, not working, in WIS2, we should not go for this path. Shared service among 1 GISCs. Hassan: WIS2 architecture is on key components/an We all agreed about the shared services. the strategy of WIS is based on evolution not revolution. I think to be efficient, let’s focus more on technical functions and go, as we agreed in the previous meeting to reach TT-GISC for the volunteers to run the shared service, not to think aobut the number. To focus on technical issues and then validate them. Rémy: Kai: avoid the supercenter that is running all shared services. Henning: This is a scale-out problem. For modern architecture, it should be designed to be scaled with more flexibility, such as in future there would be more GISCs that can run the shared service. Rémy: The fact is that not all the 15 GISCs are not working properly. The concern is not the GISC center number (of 15 )GISC , but to have the center that pretends to work but actually notsome of them pretending to fulfil the GISC role but in reality not. we should learn from the experience of WIS1 to success WIS2. Summary:
|
2. | ALL vote for global cache/broker? |
|
3 | Jeremy | Jeremy presents the data flow between NC/DCPC |
✅Action items
- To discuss the Core services in the ET-W2AT plenary meeting (2022-Feb-02)
- To continue the discussion on the data flow
- To discuss the monitoring in next meetings
⤴Decision
The team agreed that Global Cache, Global Broker, and the Global Discovery Catalogue are needed for WIS2