<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">
<div>
<p class="MsoNormal">Dear Jesus, Dave and Sara,</p>
</div>
<div>
<p class="MsoNormal">Thank you for your minutes and email.</p>
</div>
<div>
<p class="MsoNormal">I'm sorry i was not able to attend.</p>
</div>
<div>
<p class="MsoNormal">I have a question : how do we register
computing services in the VO registry.</p>
</div>
<div>
<p class="MsoNormal">Is there a capability "execution planner
interface" to be added to some of the services ? Or can we
imagine one in a ComputerServiceRegistryExtension maybe ?</p>
<p class="MsoNormal">Something which could read : "well, this
service has an execution planner interface. So go to this
endpoint and it will give you the details."<br>
</p>
</div>
<div>
<p class="MsoNormal">Or do we integrate the execution planner
interface metadata in the registry metadata for corresponding
services ?</p>
</div>
<div>
<p class="MsoNormal">I think the document answers in the
direction of the first solution.</p>
</div>
<div>
<p class="MsoNormal">Right ?</p>
</div>
<div>
<p class="MsoNormal">Cheers</p>
</div>
François</div>
<div class="moz-cite-prefix">Le 21/09/2023 à 12:25, Salgado, Jesus a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:0D1C2B5E-A818-4903-803F-B321432B0439@skao.int">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
<style>@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ligatures:standardcontextual;
mso-fareast-language:EN-US;}a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}div.WordSection1
{page:WordSection1;}ol
{margin-bottom:0cm;}ul
{margin-bottom:0cm;}</style>
<div class="WordSection1">
<p class="MsoNormal">Dear all,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks for the big attendance and the
productive discussion during yesterday’s GWS meeting on
Federated Execution across astronomical science platforms
kick-off meeting.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Minutes of the meeting are at:<o:p></o:p></p>
<p class="MsoNormal"><a
href="https://wiki.ivoa.net/twiki/bin/view/IVOA/GWSTelecon20230920"
moz-do-not-send="true" class="moz-txt-link-freetext">https://wiki.ivoa.net/twiki/bin/view/IVOA/GWSTelecon20230920</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">It was presented a summary of the issues to
be address and Dave Morris presented the status of the
Execution Planner, the first standard we want to promote
within the team.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As this was a kick-off session, we have
identified some points that could be further discussed in the
mailing list or during next interop session in Tucson.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoNormal" style="mso-list:l2 level1 lfo6">Are we
replicating work already solved by the Grid community?<o:p></o:p></li>
</ul>
<p class="MsoNormal">Our initial answer is that the grid (or
later cloud communities) has some agreed standards that we
need to study to introduce concepts but that are not usually
software stack agnostics. In the same way we defined UWS (what
is a job scheduler when many job schedulers are present in
many other contexts), the abstraction layer of the Execution
Planner could be implemented with different software stacks
below. In any case, of course we need to take attention to
other standard ways to solve these problems.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoNormal" style="mso-list:l4 level1 lfo7">Status
of Execution Planner and missing points?<o:p></o:p></li>
</ul>
<p class="MsoNormal">Note is quite complete. It must be
addressed the data model to characterise capabilities of the
platforms and characterisation of the workflows (in the
general sense). This data model could be part of the Execution
Planner standard (not a separate document) and, also, it
should address data location (this is an open issue)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoNormal" style="mso-list:l5 level1 lfo8">Why not
to create a layer on top of orchestrators? (Most of science
platforms already have, e.g. a Kubernetes cluster)<o:p></o:p></li>
</ul>
<p class="MsoNormal">Although it is true that some technologies
are quite standard for most of the science platforms,
technologies could change, and older platforms could have
different set-ups. This is why IVOA protocols are usually
software stack agnostics so they could be implemented by all.
In any case, it is important to know the level of
heterogeneity of the different partners to identify if some
things could be simplified assuming that compatible
technologies.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoNormal" style="mso-list:l7 level1 lfo9">Could
IVOA endorse or accept S3 as a data transfer protocol?<o:p></o:p></li>
</ul>
<p class="MsoNormal">Not clear answer. Interesting to be
discussed in the mailing list.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoNormal" style="mso-list:l8 level1 lfo10">Next
steps?<o:p></o:p></li>
</ul>
<p class="MsoNormal">The more important step is to identify who
is willing to help on the prototyping as, in this particular
case, the prototyping will clarify a lot about possible
missing points on the execution planner definition.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best Regards,<br>
Jesus Salgado, Sara Bertocco and Dave Morris<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<table class="MsoNormalTable" style="width:450.0pt"
width="600" cellspacing="0" cellpadding="0" border="0">
<tbody>
<tr>
<td colspan="3" style="padding:3.75pt 3.75pt 3.75pt
3.75pt" valign="bottom">
<p class="MsoNormal"><span
style="mso-ligatures:none;mso-fareast-language:EN-GB"><img
style="width:6.25in;height:.3125in"
id="Picture_x0020_3"
src="cid:part1.ftm00fuE.YgFRsX9L@astro.unistra.fr"
alt="SKAO Horizontal Dividing Rule" class=""
width="600" height="30" border="0"><o:p></o:p></span></p>
</td>
</tr>
<tr style="height:114.0pt">
<td style="padding:3.75pt 3.75pt 3.75pt
3.75pt;height:114.0pt" valign="top">
<p class="MsoNormal"><span
style="mso-ligatures:none;mso-fareast-language:EN-GB"><img
style="width:1.9166in;height:1.5833in"
id="Picture_x0020_2"
src="cid:part2.jzwgagBG.D5T95VuB@astro.unistra.fr"
alt="SKAO Logo" class="" width="184"
height="152" border="0"><o:p></o:p></span></p>
</td>
<td style="padding:3.75pt 3.75pt 3.75pt
3.75pt;height:114.0pt" valign="top">
<p class="MsoNormal" style="text-align:center"
align="center"><span
style="mso-ligatures:none;mso-fareast-language:EN-GB"><img
style="width:.427in;height:1.5833in"
id="Picture_x0020_1"
src="cid:part3.7npzdaY6.fhzBc4Jt@astro.unistra.fr"
alt="SKAO Vertical Dividing Rule" class=""
width="41" height="152" border="0"><o:p></o:p></span></p>
</td>
<td style="width:281.25pt;padding:3.75pt 3.75pt 3.75pt
3.75pt;height:114.0pt" width="375" valign="top">
<p class="MsoNormal"><span
style="color:#070068;mso-ligatures:none;mso-fareast-language:EN-GB"
lang="ES">Jesús Salgado</span><span
style="font-size:9.0pt;font-family:"Verdana",sans-serif;mso-ligatures:none;mso-fareast-language:EN-GB"
lang="ES"> <br>
<span style="color:#E70068">SKA Regional Centre
Architect</span></span><span
style="mso-ligatures:none;mso-fareast-language:EN-GB"
lang="ES"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:#5B6770;mso-ligatures:none;mso-fareast-language:EN-GB"><a
href="mailto:jesus.salgado@skao.int"
moz-do-not-send="true"><span
style="color:#0563C1" lang="ES">jesus.salgado@skao.int</span></a></span><span
style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:#5B6770;mso-ligatures:none;mso-fareast-language:EN-GB"
lang="ES"><br>
</span><span
style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:#5B6770;mso-ligatures:none;mso-fareast-language:EN-GB"><a
href="https://www.skao.int/"
moz-do-not-send="true"><span
style="color:#5B6770" lang="ES">www.skao.int</span></a></span><span
style="mso-ligatures:none;mso-fareast-language:EN-GB" lang="ES"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:#5B6770;mso-ligatures:none;mso-fareast-language:EN-GB">SKA
Observatory<br>
Jodrell Bank, Lower Withington,<br>
Macclesfield, SK11 9FT, UK</span><span
style="mso-ligatures:none;mso-fareast-language:EN-GB"><o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<br>
<font size="1.5px">
The SKA Observatory is an inter-governmental organisation and
the successor of SKA Organisation, a private limited company by
guarantee registered in England and Wales with registered number
07881918, with a registered office of Jodrell Bank, Lower
Withington, Macclesfield, Cheshire, England, SK11 9FT.
<br>
<br>
This message is intended solely for the addressee and may
contain confidential information. If you have received this
message in error, please inform the sender, and immediately and
permanently delete the email. Do not use, copy or disclose the
information contained in this message or in any attachment.
<br>
<br>
This email has been scanned for viruses and malware, and may
have been automatically archived, by Mimecast Ltd. Although SKA
Observatory and SKA Organisation have taken reasonable
precautions to ensure no viruses are present in this email,
neither SKA Observatory nor SKA Organisation accept
responsibility for any loss or damage sustained as a result of
computer viruses and the recipient must ensure that the email
(and attachments) are virus free.
</font>
</blockquote>
<p><br>
</p>
</body>
</html>