Schedule Summary | |||||||
---|---|---|---|---|---|---|---|
Session | DateTime CEST | DateTime UTC | UTC-07:00 | UTC-04:00 | UTC+02:00 | UTC+08:00 | UTC+10:00 |
Victoria BC/Pasadena | Washington DC | Bologna | Perth/Beijing | Canberra | |||
GWS 1 | 9 May 14:00 CEST | 9 May 12:00 UTC | 9 May 05:00 | 9 May 08:00 | 9 May 14:00 | 9 May 20:00 | 9 May 22:00 |
GWS 2 | 11 May 09:00 CEST | 11 May 07:00 UTC | 11 May 00:00 | 11 May 03:00 | 11 May 09:00 | 11 May 15:00 | 11 May 17:00 |
Speaker | Title | Time | Time | Material | Abstract |
---|---|---|---|---|---|
Giuliano Taffoni | GWS Status and perspectives | 5' | 14:00 | Introduction to the status of the GWS. Activity done during the last year. | |
Séverin Gaudet | Role of an Execution Planner in an SKA Regional Centre Network Demonstrator | 12' | 14:05 | The mini-SRCNet Demonstrator proposes to implement an interoperability model for data centres participating in the SKA Regional Centre Network and to understand the necessary APIs and services required to meet the goals of location-agnostic services for users. | |
Simon O'Toole | The Australian Data & Computing Landscape | 12' | 14:20 | An overview of the complex data and computing environment in Australia and some of the challenges to overcome for Science Platforms | |
Stefano Alberto Russo | Software containers and reproducibility | 12' | 14:30 | Software containers and reproducibility; what can IVOA learn from it? | |
Patrick Dowler | OIDC SSO in SRCNet prototypes | 12' | 14:40 | This is a short review of prototype work to integrate CADC data management services with an off-the-shelf OpenID Connect (OIDC) authentication and authorization (A&A) system. The short term goals are for services to accept access tokens provided by the OIDC provider and to understand how command-line tools and automated systems could use tokens to make authenticated calls to services. | |
Dave Morris | Execution Planner update | 10' | 14:55 | Changes to the design from new use cases. Adding time and date ranges, "when can I do this". Simplifying the API and using UWS for execution | |
Baptiste Cecconi | EXTRACT-TASKA: orchestration, data mining and decision making in radio astronomy | 10' | 15:05 | The EXTRACT project aims at building a compute continuum framework for extreme datamining. Radio astronomy is one of the selected use cases, with the NenuFAR instrument, an SKA pathfinder, focusing on transient astrophysics. The result of the project will be a computing framework enabling distributed computing, orchestrated across cloud infrastructures, from the raw data production to the public release of the derived data. | |
Stéphane Aicardi | EOSC computational service | 5' | 15:15 | In the context of VESPA, I have built a model of a computational service using the UWS protocol and the EOSC cloud. The objective is to make the best use of the EOSC resources by activating or deactivating virtual computing machines according to the requested load. | |
All | Discussion | 5' | 15:20 | General discussion following the talks |
Speaker | Title | Time | Time | Material | Abstract |
---|---|---|---|---|---|
Dave Morris | Introduction | 5' | 09:00 | - | Updating the IVOA specifications |
Frossie Economou | A “what-if?” VO service implementation | 20' | 09:05 | - | For historical reasons, Rubin Science Platform had a mature web services architecture before starting to implement many of the required VO-compliant APIs. This made the gaps between the our common development patterns and the ones required to implement the standards particularly noticeable. We have talked about these issues before in the IVOA context (see also sqr-063.lsst.io) but sometimes these arguments come across as theoretical, or can end up being dominated by format arguments (e.g., xml vs json). In order to demonstrate more concretely the issues we have raised, we have done a what-if implementation alongside our standard compliant SODA service to highlight some of the divergence with current web services practice. We would like to prompt a discussion on how the standards can change not to solve any specific concern as a one-off, but in order to be able to evolve again, and again. |
ALL | Discussion | 60' | 09:25 |
I | Attachment | History | Action | Size | Date | Who | Comment |
---|---|---|---|---|---|---|---|
2023-05_IVOA_GWS.pdf | r1 | manage | 2076.1 K | 2023-05-09 - 09:27 | SeverinGaudet | ||
20230509-ExecPlanner.pdf | r1 | manage | 421.4 K | 2023-05-09 - 10:50 | DaveMorris | ||
Software_containers_and_reproducibility_what_can_IVOA_learn_from_it.pdf | r1 | manage | 518.0 K | 2023-05-09 - 09:09 | DaveMorris | ||
StephaneAicardi_IVOAMay2023.pdf | r2 r1 | manage | 382.2 K | 2023-05-17 - 13:44 | StephaneAicardi | Fix an error in slide 6 | |
The_Australian_Data_and_Computing_landscape.pdf | r2 r1 | manage | 18899.3 K | 2023-05-09 - 09:41 | SimonOToole | ||
extract-bcecconi-gws-ivoa-2023-05.pdf | r2 r1 | manage | 2822.3 K | 2023-05-09 - 12:15 | BaptisteCecconi | New version | |
gws-srcnet-auth.pdf | r1 | manage | 151.4 K | 2023-05-08 - 21:14 | PatrickDowler |