[glue-wg] GLUE2.1 draft: request for final discussion and approval

[Alessandro Paolini]

hi Stephen,

thank you, some quick replies :)

On 1 June 2018 at 11:39, Stephen Burke - UKRI STFC <stephen.burke at stfc.ac.uk
> wrote:

> glue-wg <glue-wg-bounces at ogf.org> On Behalf Of Alessandro Paolini said:
> > over the last months it was discussed with the cloud providers the
> necessary network attributes to publish in the BDII and we arrived to a
> good compromise.
> > So we would like to discuss with you the latest changes to the draft
> before getting the approval for implementing the new schema in production.
>
> A few quick comments ...
>
> Generally it would be good to highlight all changes, e.g. new class
> definitions.
>

I (should have) highlighted the latest changes since the last discussion,
and de-highlighted the past ones. sorry if it created confusion (in general
there is also a comment in the document to track the new definitions)


>
> You have new classes called ComputingShareAcceleratorInfo and
> ComputingManagerAcceleratorInfo - I wonder if it's possible to have a
> better name than Info, although perhaps you might want to be able to put
> new information there. Also having two slightly different objects both
> called Info may be a bit confusing. And you don't need Accelerator in the
> attribute names, e.g. TotalAcceleratorSlots, it makes them longer and
> they're scoped by the class name anyway.
>

ok, I will check in detail with Paolo. The same naming issue occurs then
also with the corresponding Cloud classes.


>
> In ManagerInfo you have TotalPhysicalAccelerators - why not Logical too?
> It also isn't clear to me what the relationship is between a card and a
> slot - for CPUs there is no particular relationship, the OS takes care of
> scheduling processes to CPUs, but I don't know how GPUs are used.
>

maybe Paolo can provide a more detailed comment


>
> The relationship between AcceleratorEnvironment and ExecutionEnvironment
> is *-*, which is complicated to implement and navigate and seems like
> overkill to me. At least I'd make it *-1 and if you happen to have the same
> AE info for multiple EEs you just publish the same thing multiple times. I
> also somewhat wonder if you would really have multiple Accelerator types in
> one EE, i.e. several different GPU types in a single WN - if not you could
> just add the attributes to the EE and not have a new class at all.
> ComputeCapability would be better as an open enumeration if you expect
> software to be able to use it as a selection key.
>

we will check with Paolo

cheers,
Alessandro



>
> I'll look at the Cloud part later.
>
> Stephen
>
>


-- 
Dr. Alessandro Paolini
Operations Officer - EGI Foundation
Science Park 140
1098 XG Amsterdam
The Netherlands
skype: alessandro.paolini.egi
*********************************
"I believe in the power of laughter and tears"
    "as an antidote to hatred and terror"
          "A day without laughter"
             "is a wasted day" >>> Charlie Chaplin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ogf.org/pipermail/glue-wg/attachments/20180601/607897ba/attachment.html>