DOMA / QoS Meeting
DOMA-QoS 2020-01-06
Present:
- Martin Barisits,
- Oliver Keeble,
- Mario Lassnig,
- Paul Millar
Agenda:
- Doodle poll,
- White-paper,
- QoS workshop
Doodle poll
We still anticipate closing the poll on Wednesday 2020-01-15.
AP/ Paul to send reminder for the poll today to DOMA-QoS, DOMA (general) lists, and WLCG ops WG.
Paul mentioned receiving an email from Eric (Lancon) expressing interest in presenting MAS to DOMA-QoS group.
Suggestion is to offer:
- a DOMA-QoS meeting dedicated to MAS, especially once we have a US-friendly timeslot.
- Remind Eric about the doodle poll.
- Offer a slot at February's Inter-GDB workshop.
AP/ Paul to reply to Eric's email.
Oliver suggested a "News from QoS working group" email, including both the doodle poll, the workshop, and the white-paper.
After discussing this, we decided to announce these three things independently; however, each announcement would include the already announced items as reminders.
White paper
Oliver felt there is not much more to do.
AP/ Paul to add some diagrams, where it would make sense.
There was some discussion about whether the transitions table should include the "VO QoS Class" column. The table would work without it and the column names would be VO-specific anyway. In the end, we decided to keep the column as it may help the reader confirm their understanding, but we should add a throw-away sentence (or otherwise adjust the text) so it is clear that these names are only examples, and that VOs (individually) would likely choose their own names.
AP/ Oliver to check document and adjust text to make it clear the names are meant to be examples, and not suggestions or recommendations.
After some discussion, we decided to rename "VO QoS Class" to "VO QoS Policy" throughout the document. The term "Storage QoS Class" is kept as-is.
AP/ Paul to update document, changing references to "VO QoS Class" to "VO QoS Policy".
Oliver wanted to have another look through, with a fresh pair of eyes.
AP/ Oliver another look through the document by end of Tuesday.
Both Martin and Mario will look through the document today (Monday), providing feedback
AP/ Martin to check whether the document matches his ideas for Rucio.
AP/ Mario to check whether the document matches his ideas for ATLAS.
We aim to have the white-paper fully reviewed by end-of-Tuesday. This should leave enough time to fix any remaining issued by Friday.
We decided that, once the document is finished, we would simply announce it, without going through another round of DOMA-QoS internal reviews.
Announcing the white-paper
We can announce the white paper on Friday with the DOMA mailing list and through the WLCG ops mailing list.
It looks like the WLCG ops group will have a meeting next Monday. We can announce the white-paper there.
We can also announce the doodle poll and the QoS workshop.
QoS workshop
This is on Friday 2020-02-07.
Oliver has booked a room and created an initial INDICO page. This page includes a description that is a "call for contributions".
We can announce the workshop on Tuesday, after some updates to the page.
We can use announcement of white paper (on Friday) to remind people of workshop.
AP/ Oliver to verify when is the next WLCG Ops meeting.
AP/ Oliver to add our contributions to the workshop agenda.
AP/ Oliver to update INDICO description, to say how sites should request a slot.
AP/ Paul to contact VOs to invite them for a slot. They can use it to present their views on QoS, including feedback on the white paper.
The survey is another source of contributions for the QoS workshop. Going through the survey, Oliver found some 13 sites who wrote "something interesting".
AP/ Paul look through answers from the survey to find his list of sites to invite.
Starting offer of 20' slots (15'+5'), but we can extend this, if needed.
Announcing the workshop
We can announce the workshop on:
- the GDB mailing list,
- WLCG OPS mailing list,
- on the DOMA (general) list.
Next meeting
The next scheduled meeting will be in two weeks time, Monday 2020-01-20 at 10:30 CET. This should be the last meeting at this time slot, with the following meeting taking place at a US-friendly timeslot.