GLUE2.1 draft: request for final discussion and approval
Dear all, 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. This is the draft document: https://docs.google.com/document/d/1BpeTBQfCn8xRo4Ff38esRhBwzoUHE4bVxba2rEAz... I still need to update the figures, which for the moment you can find here: https://docs.google.com/document/d/1x2gUt2lJNevle8evQu6LcKr9xs5NHRd6FbNzb1yK... Here is the list of the latest classes and attributes added/modified: Classes: ComputingShareAcceleratorInfo ComputingManagerAcceleratorInfo AcceleratorEnvironment CloudComputingShareAcceleratorInfo CloudComputingManagerAcceleratorInfo CloudComputingImageAcceleratorInfo CloudComputingImageNetworkTraffic CloudComputingInstanceAcceleratorInfo Attributes: GLUE2EndpointAuthentication GLUE2ComputingEndpointAuthentication GLUE2CloudComputingEndpointAuthentication GLUE2CloudComputingShareDefaultNetwokType GLUE2CloudComputingSharePublicNetwokName GLUE2CloudComputingShareProjectID GLUE2CloudComputingVirtualAcceleratorComputeCapability GLUE2CloudComputingVirtualAcceleratorVirtualizationType GLUE2CloudComputingImageContextualizationName GLUE2CloudComputingImageContextualizationVersion GLUE2CloudComputingImageDescription GLUE2CloudComputingImageVersion Storage attributes: StorageShareNumberOfFiles (requested by ATLAS) Best regards, Alessandro -- 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
glue-wg <glue-wg-bounces@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. 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. 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. 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. I'll look at the Cloud part later. Stephen
hi Stephen, thank you, some quick replies :) On 1 June 2018 at 11:39, Stephen Burke - UKRI STFC <stephen.burke@stfc.ac.uk
wrote:
glue-wg <glue-wg-bounces@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
I'll look at the Cloud part later.
These are mostly just technical comments, I don't know enough about how you use the cloud information to judge whether the attributes are the right ones, but I assume you've done some prototyping by now. In the Service you say that the AUP should be a URL - if you want that to be a hard restriction you should type it as a URL rather than a string so it could be type-checked. I'm a bit surprised that there are no new attributes in Endpoint, especially as the text above the table suggests that there should be - did something get missed out? For the Share relations you have 1..* for Endpoint and Resource which is wrong, they should follow the inherited attributes and be *, i.e. the only mandatory relation is Service. The diagram is correct. I won't necessarily spot all mistakes in relations so someone should probably go through and check systematically that everything is consistent. I would rename ShareAcceleratorInfo to AcceleratorLimit (lots of Info classes!). I find the Share limits a bit confusing, i.e. the InstanceMaxXxx. Presumably you've done that to allow for different Shares allowing users to instantiate the same VMs with different limits, but I wonder if that's an important feature - the alternative would be to put limits in InstanceType and just have multiple objects if you have instances with different limits. Anyway if I look at InstanceType you have mandatory CPU and RAM attributes which suggest that the values are just fixed, so I don't understand where the limits come in - are they just defaults, or what? For Manager: MaxRAM seems a slightly strange thing to publish, is it useful? I'm also not sure what you'd do with the InstanceMax/Min attributes. Clients should be looking at the Share rather than the Manager, so these would normally be for monitoring or accounting use cases, is there a need to monitor those things? InstanceType: I'd be inclined to call the ID attribute something like InstanceID or TemplateID rather than IDForEndpoint, I don't think there's any particular need to specify a use in the name. Again if MarketPlaceID is supposed to be a URL you should type it as such and perhaps call it URL rather than ID. Also a trivial point, I'd call it Marketplace rather than MarketPlace, it's a single word. The vCPU attribute should probably just be called CPU, the virtual part is implied by the context (and you don't have vRAM). And as above, I don't really understand what these mean if the number can be variable. Perhaps my ignorance, but is the network connectivity really bound to the image rather than being specified when you instantiate it? NetworkPortsIn/Out, do you really want an explicit list of every port rather than allowing a range? OtherHardware should probably be an open enumeration, otherwise it's effectively free text and not useful for selection. The text says CloudComputingPrice but the class is actually called CloudServicePrice. VirtualAcclelerator to InstanceType is *-*, better to have it *-1 and just duplicate it if necessary - logically it's part of the Instance. Also I'd again ask whether this is a realistic use case - will you really have VMs with multiple GPU types? Again ComputeCapability should probably be an open enumeration. I'll stop there and come back later ... Stephen
I'll stop there and come back later ...
CloudComputingImage: conceptually this seems like another kind of Resource. I don't think we ever considered having two types of Resource in one Service and maybe it's better not to do it explicitly, but I'd expect it to be similar, and it is except for not having a relationship to Manager. Doesn't a Manager manage Images too? There's also no relationship to InstanceType - does that mean that any VM can run any OS? For the first two attributes I have the same comments as for InstanceType. DefaultPassword is a bit surprising, should that be published? I find ImageAcceleratorInfo a bit surprising, are there OS images that require GPUs? And if so, it seems unlikely that there are images that require more than one type? NetworkTraffic doesn't seem like the right name, maybe NetworkConfiguration? And is it really part of the Image rather than the Instance? Maybe I just don't understand what it's for, the explanation isn't very detailed. CloudComputingInstance: again I don't especially like the ID names, maybe ExternalID and InternalID? It also seems like at least one of those should be mandatory so you can tell which job the object refers to. For Owner I'm not sure why you don't just make it an optional attribute and remove the CONFIDENTIAL value? You have two attributes with ComputeManager in the name, should be ComputingManager. ToStorageService: again I'd call the IDForEndpoint attribute something different, maybe LocationID? ... StorageSharePath: it still isn't clear to me that multiplicity * makes sense. This is supposed to be a default path, if there are several you don't know which to use. Also if there is any software using this (possibly not) it would expect a unique result and probably break if it got more than one. If this is really wanted I would say add a new multivalued attribute Paths or OtherPaths. (AccessMode also has an underline, was there a change for that?) Stephen
On 06/03/2018 04:28 PM, Stephen Burke - UKRI STFC wrote:
I find ImageAcceleratorInfo a bit surprising, are there OS images that require GPUs? And if so, it seems unlikely that there are images that require more than one type? I removed the class. I thought it was the right place for flavor definitions but, thinking twice, it was not a good idea. The flavor should correspond to the CloudComputingInstanceType class. What it is not clear to me if it is necessary to have hardware definitions (CPU, RAM) in the CloudComputingImage. I put a comment in the document.
-- ---------------------- Ing. Paolo Andreetto INFN Sezione di Padova Via Marzolo, 8 35131 Padova - Italy Tel: +39 049.967.7378 Skype: andreettopl ----------------------
On 06/01/2018 11:39 AM, Stephen Burke - UKRI STFC wrote:
A few quick comments ...
Generally it would be good to highlight all changes, e.g. new class 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. Even better, I think we can remove the suffix "Info" from both the class names.
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.
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.
It's not easy to design a model that can be suitable for any kind of future accelerator devices. We can have multiple (different) cards on the same WN, and we have some examples about that. I read about new architecture with multi-chip GPU on the same card. There're GPU appliances (Nvidia Quadro VCA) that can be shared among different WNs, and I'm not sure that cloning the AcceleratorEnvironment could get the point. The concept of "slot" is not so clear as the one defined for CPU, but in any case it should represent the minimum amount of resource usage for a job on a given device. The card, or socket, is just a physical description of the device. For what concerns the new AI/ML accelerator devices, like the Google TPU, honestly I'm not skilled enough for trying to propose a model. -- ---------------------- Ing. Paolo Andreetto INFN Sezione di Padova Via Marzolo, 8 35131 Padova - Italy Tel: +39 049.967.7378 Skype: andreettopl ----------------------
Paolo Andreetto <paolo.andreetto@pd.infn.it> said:
Even better, I think we can remove the suffix "Info" from both the class names.
That's probably OK, as long as all the names are still different.
It's not easy to design a model that can be suitable for any kind of future accelerator devices. We can have multiple (different) cards on the same WN, and we have some examples about that.
OK, if you think it's possible then you should allow for that - you shouldn't make the model more complicated than it needs to be but it's reasonable to allow for likely future developments. Also you have quite a few accelerator objects, the arguments aren't necessarily the same for all of them.
I read about new architecture with multi-chip GPU on the same card.
I think the objects usually only need to be one instance per GPU type, if you have multiple GPUs of the same type you could just publish a count in a single object.
There're GPU appliances (Nvidia Quadro VCA) that can be shared among different WNs, and I'm not sure that cloning the AcceleratorEnvironment could get the point.
You'd need to have some idea of what the sharing model would be - in general you'd need a new kind of resource object for that, but it may be that you could deal with it within the existing structure. Stephen
Dear GLUE working group members, For long-term sustainability, we are looking to host most of the OGF document preparation process in settings we can host in the cloud and in the process modernize some of the tools OGF uses for document preparation and production. I'd like to see if the folks in this working group would be willing to experiment with producing documents in GitHub using GitHub-Flavored Markdown (GFM) and using pull requests to track and review proposed changes. For this purpose I have created a GitHub-hosed copy of the current document draft and added it to the OGF-GLUE repository in the OpenGridForum organizational pages. Anyone can request to join, and we can designate certain people as authors with write privileges and others as administrators for the repository. For now this is an experiment, but I would be happy to walk the group through the procedures to propose and make document changes using git rather than exchanging documents by email or editing them directly in Google Docs. This can produce a more coherent way of discussing potential changes and adopting or rejecting them by the usual pull request process familiar to anyone who has used this method to prepare and maintain common source code. The OGF organizational pages are at https://github.com/OpenGridForum and the repository for the GLUE experiment is at https://github.com/OpenGridForum/OGF-GLUE . We'll be happy to add anyone in the team and to appoint people to administrator or author (write- and pull-enabled) status as required and agreed by the group. Let me know if you have any questions. Alan On Jun 4, 2018, at 4:57 AM, Stephen Burke - UKRI STFC <stephen.burke@stfc.ac.uk<mailto:stephen.burke@stfc.ac.uk>> wrote: Paolo Andreetto <paolo.andreetto@pd.infn.it<mailto:paolo.andreetto@pd.infn.it>> said: Even better, I think we can remove the suffix "Info" from both the class names. That's probably OK, as long as all the names are still different. It's not easy to design a model that can be suitable for any kind of future accelerator devices. We can have multiple (different) cards on the same WN, and we have some examples about that. OK, if you think it's possible then you should allow for that - you shouldn't make the model more complicated than it needs to be but it's reasonable to allow for likely future developments. Also you have quite a few accelerator objects, the arguments aren't necessarily the same for all of them. I read about new architecture with multi-chip GPU on the same card. I think the objects usually only need to be one instance per GPU type, if you have multiple GPUs of the same type you could just publish a count in a single object. There're GPU appliances (Nvidia Quadro VCA) that can be shared among different WNs, and I'm not sure that cloning the AcceleratorEnvironment could get the point. You'd need to have some idea of what the sharing model would be - in general you'd need a new kind of resource object for that, but it may be that you could deal with it within the existing structure. Stephen _______________________________________________ glue-wg mailing list glue-wg@ogf.org<mailto:glue-wg@ogf.org> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ogf.org%2Fmailman%2Flistinfo%2Fglue-wg&data=02%7C01%7Calan.sill%40ttu.edu%7C1c7e47606981456feb4c08d5ca022cb7%7C178a51bf8b2049ffb65556245d5c173c%7C0%7C0%7C636637033054435909&sdata=jAOIUTesKlfHpR1L5kl30HQfHOx8S5Mtl0itw0l7axM%3D&reserved=0
Hi Alan, thank you for the proposal, it will be very useful for the future documents. I know that this google doc is quite heavy in the browser, but I would rather stay on Google Doc since the draft needs only few minor changes and not having used github yet, it would take to much time for me getting familiar with it. cheers, alessandro On 5 June 2018 at 02:31, Sill, Alan <Alan.Sill@ttu.edu> wrote:
Dear GLUE working group members,
For long-term sustainability, we are looking to host most of the OGF document preparation process in settings we can host in the cloud and in the process modernize some of the tools OGF uses for document preparation and production.
I'd like to see if the folks in this working group would be willing to experiment with producing documents in GitHub using GitHub-Flavored Markdown (GFM) and using pull requests to track and review proposed changes. For this purpose I have created a GitHub-hosed copy of the current document draft and added it to the OGF-GLUE repository in the OpenGridForum organizational pages. Anyone can request to join, and we can designate certain people as authors with write privileges and others as administrators for the repository.
For now this is an experiment, but I would be happy to walk the group through the procedures to propose and make document changes using git rather than exchanging documents by email or editing them directly in Google Docs. This can produce a more coherent way of discussing potential changes and adopting or rejecting them by the usual pull request process familiar to anyone who has used this method to prepare and maintain common source code.
The OGF organizational pages are at https://github.com/OpenGridForum and the repository for the GLUE experiment is at https://github.com/ OpenGridForum/OGF-GLUE . We'll be happy to add anyone in the team and to appoint people to administrator or author (write- and pull-enabled) status as required and agreed by the group.
Let me know if you have any questions.
Alan
On Jun 4, 2018, at 4:57 AM, Stephen Burke - UKRI STFC < stephen.burke@stfc.ac.uk> wrote:
Paolo Andreetto <paolo.andreetto@pd.infn.it> said:
Even better, I think we can remove the suffix "Info" from both the class names.
That's probably OK, as long as all the names are still different.
It's not easy to design a model that can be suitable for any kind of future accelerator devices. We can have multiple (different) cards on the same WN, and we have some examples about that.
OK, if you think it's possible then you should allow for that - you shouldn't make the model more complicated than it needs to be but it's reasonable to allow for likely future developments. Also you have quite a few accelerator objects, the arguments aren't necessarily the same for all of them.
I read about new architecture with multi-chip GPU on the same card.
I think the objects usually only need to be one instance per GPU type, if you have multiple GPUs of the same type you could just publish a count in a single object.
There're GPU appliances (Nvidia Quadro VCA) that can be shared among different WNs, and I'm not sure that cloning the AcceleratorEnvironment could get the point.
You'd need to have some idea of what the sharing model would be - in general you'd need a new kind of resource object for that, but it may be that you could deal with it within the existing structure.
Stephen
_______________________________________________ glue-wg mailing list glue-wg@ogf.org https://na01.safelinks.protection.outlook.com/?url= https%3A%2F%2Fwww.ogf.org%2Fmailman%2Flistinfo%2Fglue- wg&data=02%7C01%7Calan.sill%40ttu.edu%7C1c7e47606981456feb4c08d5ca022cb7% 7C178a51bf8b2049ffb65556245d5c173c%7C0%7C0%7C636637033054435909&sdata= jAOIUTesKlfHpR1L5kl30HQfHOx8S5Mtl0itw0l7axM%3D&reserved=0
_______________________________________________ glue-wg mailing list glue-wg@ogf.org https://www.ogf.org/mailman/listinfo/glue-wg
-- 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
anyway, my account on GitHub is paolini78, please check if I already have the necessary privilegies On 5 June 2018 at 11:19, Alessandro Paolini <alessandro.paolini@egi.eu> wrote:
Hi Alan,
thank you for the proposal, it will be very useful for the future documents. I know that this google doc is quite heavy in the browser, but I would rather stay on Google Doc since the draft needs only few minor changes and not having used github yet, it would take to much time for me getting familiar with it.
cheers, alessandro
On 5 June 2018 at 02:31, Sill, Alan <Alan.Sill@ttu.edu> wrote:
Dear GLUE working group members,
For long-term sustainability, we are looking to host most of the OGF document preparation process in settings we can host in the cloud and in the process modernize some of the tools OGF uses for document preparation and production.
I'd like to see if the folks in this working group would be willing to experiment with producing documents in GitHub using GitHub-Flavored Markdown (GFM) and using pull requests to track and review proposed changes. For this purpose I have created a GitHub-hosed copy of the current document draft and added it to the OGF-GLUE repository in the OpenGridForum organizational pages. Anyone can request to join, and we can designate certain people as authors with write privileges and others as administrators for the repository.
For now this is an experiment, but I would be happy to walk the group through the procedures to propose and make document changes using git rather than exchanging documents by email or editing them directly in Google Docs. This can produce a more coherent way of discussing potential changes and adopting or rejecting them by the usual pull request process familiar to anyone who has used this method to prepare and maintain common source code.
The OGF organizational pages are at https://github.com/OpenGridForum and the repository for the GLUE experiment is at https://github.com/OpenGrid Forum/OGF-GLUE . We'll be happy to add anyone in the team and to appoint people to administrator or author (write- and pull-enabled) status as required and agreed by the group.
Let me know if you have any questions.
Alan
On Jun 4, 2018, at 4:57 AM, Stephen Burke - UKRI STFC < stephen.burke@stfc.ac.uk> wrote:
Paolo Andreetto <paolo.andreetto@pd.infn.it> said:
Even better, I think we can remove the suffix "Info" from both the class names.
That's probably OK, as long as all the names are still different.
It's not easy to design a model that can be suitable for any kind of future accelerator devices. We can have multiple (different) cards on the same WN, and we have some examples about that.
OK, if you think it's possible then you should allow for that - you shouldn't make the model more complicated than it needs to be but it's reasonable to allow for likely future developments. Also you have quite a few accelerator objects, the arguments aren't necessarily the same for all of them.
I read about new architecture with multi-chip GPU on the same card.
I think the objects usually only need to be one instance per GPU type, if you have multiple GPUs of the same type you could just publish a count in a single object.
There're GPU appliances (Nvidia Quadro VCA) that can be shared among different WNs, and I'm not sure that cloning the AcceleratorEnvironment could get the point.
You'd need to have some idea of what the sharing model would be - in general you'd need a new kind of resource object for that, but it may be that you could deal with it within the existing structure.
Stephen
_______________________________________________ glue-wg mailing list glue-wg@ogf.org https://na01.safelinks.protection.outlook.com/?url=https%3A% 2F%2Fwww.ogf.org%2Fmailman%2Flistinfo%2Fglue-wg&data=02% 7C01%7Calan.sill%40ttu.edu%7C1c7e47606981456feb4c08d5ca022cb 7%7C178a51bf8b2049ffb65556245d5c173c%7C0%7C0%7C6366370330544 35909&sdata=jAOIUTesKlfHpR1L5kl30HQfHOx8S5Mtl0itw0l7axM%3D&reserved=0
_______________________________________________ glue-wg mailing list glue-wg@ogf.org https://www.ogf.org/mailman/listinfo/glue-wg
-- 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
-- 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
Hi, Personally, I think that a PR-based workflow would be great, working with such a PDF is very complex, time-costly and error-prone, with a PR it's easy to see the changes, to discuss them and to amend them. And with the source code repository, it's easy to tag releases. And for agreeing on something such as a standard it would be a great tool. But I also agree with Alessandro: we would like to be able to finalize this ASAP, it has been an ongoing task for months (or years in fact), and it may take some more time to setup and convert everything to GitHub. Best, Baptiste On Tue, 5 Jun 2018 at 11:25 Alessandro Paolini <alessandro.paolini@egi.eu> wrote:
anyway, my account on GitHub is paolini78, please check if I already have the necessary privilegies
On 5 June 2018 at 11:19, Alessandro Paolini <alessandro.paolini@egi.eu> wrote:
Hi Alan,
thank you for the proposal, it will be very useful for the future documents. I know that this google doc is quite heavy in the browser, but I would rather stay on Google Doc since the draft needs only few minor changes and not having used github yet, it would take to much time for me getting familiar with it.
cheers, alessandro
On 5 June 2018 at 02:31, Sill, Alan <Alan.Sill@ttu.edu> wrote:
Dear GLUE working group members,
For long-term sustainability, we are looking to host most of the OGF document preparation process in settings we can host in the cloud and in the process modernize some of the tools OGF uses for document preparation and production.
I'd like to see if the folks in this working group would be willing to experiment with producing documents in GitHub using GitHub-Flavored Markdown (GFM) and using pull requests to track and review proposed changes. For this purpose I have created a GitHub-hosed copy of the current document draft and added it to the OGF-GLUE repository in the OpenGridForum organizational pages. Anyone can request to join, and we can designate certain people as authors with write privileges and others as administrators for the repository.
For now this is an experiment, but I would be happy to walk the group through the procedures to propose and make document changes using git rather than exchanging documents by email or editing them directly in Google Docs. This can produce a more coherent way of discussing potential changes and adopting or rejecting them by the usual pull request process familiar to anyone who has used this method to prepare and maintain common source code.
The OGF organizational pages are at https://github.com/OpenGridForum and the repository for the GLUE experiment is at https://github.com/OpenGridForum/OGF-GLUE . We'll be happy to add anyone in the team and to appoint people to administrator or author (write- and pull-enabled) status as required and agreed by the group.
Let me know if you have any questions.
Alan
On Jun 4, 2018, at 4:57 AM, Stephen Burke - UKRI STFC < stephen.burke@stfc.ac.uk> wrote:
Paolo Andreetto <paolo.andreetto@pd.infn.it> said:
Even better, I think we can remove the suffix "Info" from both the class names.
That's probably OK, as long as all the names are still different.
It's not easy to design a model that can be suitable for any kind of future accelerator devices. We can have multiple (different) cards on the same WN, and we have some examples about that.
OK, if you think it's possible then you should allow for that - you shouldn't make the model more complicated than it needs to be but it's reasonable to allow for likely future developments. Also you have quite a few accelerator objects, the arguments aren't necessarily the same for all of them.
I read about new architecture with multi-chip GPU on the same card.
I think the objects usually only need to be one instance per GPU type, if you have multiple GPUs of the same type you could just publish a count in a single object.
There're GPU appliances (Nvidia Quadro VCA) that can be shared among different WNs, and I'm not sure that cloning the AcceleratorEnvironment could get the point.
You'd need to have some idea of what the sharing model would be - in general you'd need a new kind of resource object for that, but it may be that you could deal with it within the existing structure.
Stephen
_______________________________________________ glue-wg mailing list glue-wg@ogf.org
_______________________________________________ glue-wg mailing list glue-wg@ogf.org https://www.ogf.org/mailman/listinfo/glue-wg
-- 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
-- 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 _______________________________________________ glue-wg mailing list glue-wg@ogf.org https://www.ogf.org/mailman/listinfo/glue-wg
-- Baptiste Grenier EGI Foundation - Operations Officer Phone: +31 627 860 852 Skype: baptiste.grenier.egi
Retitling this subject line to start a new thread with apologies for putting this discussion directly into the previous thread earlier. I’ve seen the PR system work well in other organizations aimed at standards production. This allows full discussion of each proposed change with merits and consequences of each alteration getting individual discussion without being buried in an email thread or forgotten. If you’d like to try, I have a rough preliminary conversion of the GLUE 2.1 draft 0.5 in the OGF-GLUE repository mentioned earlier. One thing to try would be to enter pull requests for any changes that have been agreed to since then. Another would be to enter PRs to replace the figure images that I extracted from the a Google Doc with the originals. I made JP an admin (if he accepts the invitation) and can do so with others at the group’s request. Good luck and let me know how or if I can help. Alan On Jun 5, 2018, at 6:28 AM, Baptiste Grenier <baptiste.grenier@egi.eu<mailto:baptiste.grenier@egi.eu>> wrote: Hi, Personally, I think that a PR-based workflow would be great, working with such a PDF is very complex, time-costly and error-prone, with a PR it's easy to see the changes, to discuss them and to amend them. And with the source code repository, it's easy to tag releases. And for agreeing on something such as a standard it would be a great tool. But I also agree with Alessandro: we would like to be able to finalize this ASAP, it has been an ongoing task for months (or years in fact), and it may take some more time to setup and convert everything to GitHub. Best, Baptiste On Tue, 5 Jun 2018 at 11:25 Alessandro Paolini <alessandro.paolini@egi.eu<mailto:alessandro.paolini@egi.eu>> wrote: anyway, my account on GitHub is paolini78, please check if I already have the necessary privilegies On 5 June 2018 at 11:19, Alessandro Paolini <alessandro.paolini@egi.eu<mailto:alessandro.paolini@egi.eu>> wrote: Hi Alan, thank you for the proposal, it will be very useful for the future documents. I know that this google doc is quite heavy in the browser, but I would rather stay on Google Doc since the draft needs only few minor changes and not having used github yet, it would take to much time for me getting familiar with it. cheers, alessandro On 5 June 2018 at 02:31, Sill, Alan <Alan.Sill@ttu.edu<mailto:Alan.Sill@ttu.edu>> wrote: Dear GLUE working group members, For long-term sustainability, we are looking to host most of the OGF document preparation process in settings we can host in the cloud and in the process modernize some of the tools OGF uses for document preparation and production. I'd like to see if the folks in this working group would be willing to experiment with producing documents in GitHub using GitHub-Flavored Markdown (GFM) and using pull requests to track and review proposed changes. For this purpose I have created a GitHub-hosed copy of the current document draft and added it to the OGF-GLUE repository in the OpenGridForum organizational pages. Anyone can request to join, and we can designate certain people as authors with write privileges and others as administrators for the repository. For now this is an experiment, but I would be happy to walk the group through the procedures to propose and make document changes using git rather than exchanging documents by email or editing them directly in Google Docs. This can produce a more coherent way of discussing potential changes and adopting or rejecting them by the usual pull request process familiar to anyone who has used this method to prepare and maintain common source code. The OGF organizational pages are at https://github.com/OpenGridForum<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOpenGridForum&data=02%7C01%7CAlan.Sill%40ttu.edu%7Ca6e8a262dff341190c4b08d5cad77d7b%7C178a51bf8b2049ffb65556245d5c173c%7C0%7C0%7C636637949243443303&sdata=aOm7Zrrdf1%2BD%2FCrZw%2FMUWCHLGTXv6oftaroLaptyw74%3D&reserved=0> and the repository for the GLUE experiment is at https://github.com/OpenGridForum/OGF-GLUE<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOpenGridForum%2FOGF-GLUE&data=02%7C01%7CAlan.Sill%40ttu.edu%7Ca6e8a262dff341190c4b08d5cad77d7b%7C178a51bf8b2049ffb65556245d5c173c%7C0%7C0%7C636637949243443303&sdata=G%2F%2FkVGhPDnXwHVAXDrXgV91D6hACuUaMHrVUZRuhAss%3D&reserved=0> . We'll be happy to add anyone in the team and to appoint people to administrator or author (write- and pull-enabled) status as required and agreed by the group. Let me know if you have any questions. Alan On Jun 4, 2018, at 4:57 AM, Stephen Burke - UKRI STFC <stephen.burke@stfc.ac.uk<mailto:stephen.burke@stfc.ac.uk>> wrote: Paolo Andreetto <paolo.andreetto@pd.infn.it<mailto:paolo.andreetto@pd.infn.it>> said: Even better, I think we can remove the suffix "Info" from both the class names. That's probably OK, as long as all the names are still different. It's not easy to design a model that can be suitable for any kind of future accelerator devices. We can have multiple (different) cards on the same WN, and we have some examples about that. OK, if you think it's possible then you should allow for that - you shouldn't make the model more complicated than it needs to be but it's reasonable to allow for likely future developments. Also you have quite a few accelerator objects, the arguments aren't necessarily the same for all of them. I read about new architecture with multi-chip GPU on the same card. I think the objects usually only need to be one instance per GPU type, if you have multiple GPUs of the same type you could just publish a count in a single object. There're GPU appliances (Nvidia Quadro VCA) that can be shared among different WNs, and I'm not sure that cloning the AcceleratorEnvironment could get the point. You'd need to have some idea of what the sharing model would be - in general you'd need a new kind of resource object for that, but it may be that you could deal with it within the existing structure. Stephen _______________________________________________ glue-wg mailing list glue-wg@ogf.org<mailto:glue-wg@ogf.org> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ogf.org%2Fmailman%2Flistinfo%2Fglue-wg&data=02%7C01%7Calan.sill%40ttu.edu%7C1c7e47606981456feb4c08d5ca022cb7%7C178a51bf8b2049ffb65556245d5c173c%7C0%7C0%7C636637033054435909&sdata=jAOIUTesKlfHpR1L5kl30HQfHOx8S5Mtl0itw0l7axM%3D&reserved=0 _______________________________________________ glue-wg mailing list glue-wg@ogf.org<mailto:glue-wg@ogf.org> https://www.ogf.org/mailman/listinfo/glue-wg<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ogf.org%2Fmailman%2Flistinfo%2Fglue-wg&data=02%7C01%7CAlan.Sill%40ttu.edu%7Ca6e8a262dff341190c4b08d5cad77d7b%7C178a51bf8b2049ffb65556245d5c173c%7C0%7C0%7C636637949243443303&sdata=DC6Y9YZ8V%2BtSVGnoC5K44Z8MSRaBq8IUzTeAjqgk7KU%3D&reserved=0> -- 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 -- 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 _______________________________________________ glue-wg mailing list glue-wg@ogf.org<mailto:glue-wg@ogf.org> https://www.ogf.org/mailman/listinfo/glue-wg<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ogf.org%2Fmailman%2Flistinfo%2Fglue-wg&data=02%7C01%7CAlan.Sill%40ttu.edu%7Ca6e8a262dff341190c4b08d5cad77d7b%7C178a51bf8b2049ffb65556245d5c173c%7C0%7C0%7C636637949243443303&sdata=DC6Y9YZ8V%2BtSVGnoC5K44Z8MSRaBq8IUzTeAjqgk7KU%3D&reserved=0> -- Baptiste Grenier EGI Foundation - Operations Officer Phone: +31 627 860 852 Skype: baptiste.grenier.egi
Hi Alan, Thanks, that's great! https://github.com/OpenGridForum/OGF-GLUE I would be happy to make a PR, but figuring what was already agreed or not is not easy for now, especially as lots of things were changed during the last few days. Would it be possible to make another export of the actual version to make a diff? It would be nice also to enable some automatic syntax (and more?) validation with something like travis, I would be happy to help set this up. Cheers, Baptiste On Fri, 8 Jun 2018 at 14:52 Sill, Alan <Alan.Sill@ttu.edu> wrote:
Retitling this subject line to start a new thread with apologies for putting this discussion directly into the previous thread earlier.
I’ve seen the PR system work well in other organizations aimed at standards production. This allows full discussion of each proposed change with merits and consequences of each alteration getting individual discussion without being buried in an email thread or forgotten.
If you’d like to try, I have a rough preliminary conversion of the GLUE 2.1 draft 0.5 in the OGF-GLUE repository mentioned earlier. One thing to try would be to enter pull requests for any changes that have been agreed to since then. Another would be to enter PRs to replace the figure images that I extracted from the a Google Doc with the originals.
I made JP an admin (if he accepts the invitation) and can do so with others at the group’s request.
Good luck and let me know how or if I can help.
Alan
On Jun 5, 2018, at 6:28 AM, Baptiste Grenier <baptiste.grenier@egi.eu> wrote:
Hi, Personally, I think that a PR-based workflow would be great, working with such a PDF is very complex, time-costly and error-prone, with a PR it's easy to see the changes, to discuss them and to amend them. And with the source code repository, it's easy to tag releases. And for agreeing on something such as a standard it would be a great tool. But I also agree with Alessandro: we would like to be able to finalize this ASAP, it has been an ongoing task for months (or years in fact), and it may take some more time to setup and convert everything to GitHub.
Best, Baptiste
On Tue, 5 Jun 2018 at 11:25 Alessandro Paolini <alessandro.paolini@egi.eu> wrote:
anyway, my account on GitHub is paolini78, please check if I already have the necessary privilegies
On 5 June 2018 at 11:19, Alessandro Paolini <alessandro.paolini@egi.eu> wrote:
Hi Alan,
thank you for the proposal, it will be very useful for the future documents. I know that this google doc is quite heavy in the browser, but I would rather stay on Google Doc since the draft needs only few minor changes and not having used github yet, it would take to much time for me getting familiar with it.
cheers, alessandro
On 5 June 2018 at 02:31, Sill, Alan <Alan.Sill@ttu.edu> wrote:
Dear GLUE working group members,
For long-term sustainability, we are looking to host most of the OGF document preparation process in settings we can host in the cloud and in the process modernize some of the tools OGF uses for document preparation and production.
I'd like to see if the folks in this working group would be willing to experiment with producing documents in GitHub using GitHub-Flavored Markdown (GFM) and using pull requests to track and review proposed changes. For this purpose I have created a GitHub-hosed copy of the current document draft and added it to the OGF-GLUE repository in the OpenGridForum organizational pages. Anyone can request to join, and we can designate certain people as authors with write privileges and others as administrators for the repository.
For now this is an experiment, but I would be happy to walk the group through the procedures to propose and make document changes using git rather than exchanging documents by email or editing them directly in Google Docs. This can produce a more coherent way of discussing potential changes and adopting or rejecting them by the usual pull request process familiar to anyone who has used this method to prepare and maintain common source code.
The OGF organizational pages are at https://github.com/OpenGridForum <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOpenGridForum&data=02%7C01%7CAlan.Sill%40ttu.edu%7Ca6e8a262dff341190c4b08d5cad77d7b%7C178a51bf8b2049ffb65556245d5c173c%7C0%7C0%7C636637949243443303&sdata=aOm7Zrrdf1%2BD%2FCrZw%2FMUWCHLGTXv6oftaroLaptyw74%3D&reserved=0> and the repository for the GLUE experiment is at https://github.com/OpenGridForum/OGF-GLUE <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOpenGridForum%2FOGF-GLUE&data=02%7C01%7CAlan.Sill%40ttu.edu%7Ca6e8a262dff341190c4b08d5cad77d7b%7C178a51bf8b2049ffb65556245d5c173c%7C0%7C0%7C636637949243443303&sdata=G%2F%2FkVGhPDnXwHVAXDrXgV91D6hACuUaMHrVUZRuhAss%3D&reserved=0> . We'll be happy to add anyone in the team and to appoint people to administrator or author (write- and pull-enabled) status as required and agreed by the group.
Let me know if you have any questions.
Alan
On Jun 4, 2018, at 4:57 AM, Stephen Burke - UKRI STFC < stephen.burke@stfc.ac.uk> wrote:
Paolo Andreetto <paolo.andreetto@pd.infn.it> said:
Even better, I think we can remove the suffix "Info" from both the class names.
That's probably OK, as long as all the names are still different.
It's not easy to design a model that can be suitable for any kind of future accelerator devices. We can have multiple (different) cards on the same WN, and we have some examples about that.
OK, if you think it's possible then you should allow for that - you shouldn't make the model more complicated than it needs to be but it's reasonable to allow for likely future developments. Also you have quite a few accelerator objects, the arguments aren't necessarily the same for all of them.
I read about new architecture with multi-chip GPU on the same card.
I think the objects usually only need to be one instance per GPU type, if you have multiple GPUs of the same type you could just publish a count in a single object.
There're GPU appliances (Nvidia Quadro VCA) that can be shared among different WNs, and I'm not sure that cloning the AcceleratorEnvironment could get the point.
You'd need to have some idea of what the sharing model would be - in general you'd need a new kind of resource object for that, but it may be that you could deal with it within the existing structure.
Stephen
_______________________________________________ glue-wg mailing list glue-wg@ogf.org
_______________________________________________ glue-wg mailing list glue-wg@ogf.org https://www.ogf.org/mailman/listinfo/glue-wg <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ogf.org%2Fmailman%2Flistinfo%2Fglue-wg&data=02%7C01%7CAlan.Sill%40ttu.edu%7Ca6e8a262dff341190c4b08d5cad77d7b%7C178a51bf8b2049ffb65556245d5c173c%7C0%7C0%7C636637949243443303&sdata=DC6Y9YZ8V%2BtSVGnoC5K44Z8MSRaBq8IUzTeAjqgk7KU%3D&reserved=0>
-- Dr. Alessandro Paolini Operations Officer - EGI Foundation Science Park 140 <https://maps.google.com/?q=Science+Park+140+%0D%0A1098+XG+Amsterdam+%0D%0AThe+Netherlands&entry=gmail&source=g> 1098 XG Amsterdam <https://maps.google.com/?q=Science+Park+140+%0D%0A1098+XG+Amsterdam+%0D%0AThe+Netherlands&entry=gmail&source=g> The Netherlands <https://maps.google.com/?q=Science+Park+140+%0D%0A1098+XG+Amsterdam+%0D%0AThe+Netherlands&entry=gmail&source=g> 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
-- Dr. Alessandro Paolini Operations Officer - EGI Foundation Science Park 140 <https://maps.google.com/?q=Science+Park+140+%0D%0A1098+XG+Amsterdam+%0D%0AThe+Netherlands&entry=gmail&source=g> 1098 XG Amsterdam <https://maps.google.com/?q=Science+Park+140+%0D%0A1098+XG+Amsterdam+%0D%0AThe+Netherlands&entry=gmail&source=g> The Netherlands <https://maps.google.com/?q=Science+Park+140+%0D%0A1098+XG+Amsterdam+%0D%0AThe+Netherlands&entry=gmail&source=g> 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 _______________________________________________ glue-wg mailing list glue-wg@ogf.org https://www.ogf.org/mailman/listinfo/glue-wg <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ogf.org%2Fmailman%2Flistinfo%2Fglue-wg&data=02%7C01%7CAlan.Sill%40ttu.edu%7Ca6e8a262dff341190c4b08d5cad77d7b%7C178a51bf8b2049ffb65556245d5c173c%7C0%7C0%7C636637949243443303&sdata=DC6Y9YZ8V%2BtSVGnoC5K44Z8MSRaBq8IUzTeAjqgk7KU%3D&reserved=0>
-- Baptiste Grenier EGI Foundation - Operations Officer Phone: +31 627 860 852 Skype: baptiste.grenier.egi
-- Baptiste Grenier EGI Foundation - Operations Officer Phone: +31 627 860 852 Skype: baptiste.grenier.egi
On 06/01/2018 11:39 AM, Stephen Burke - UKRI STFC wrote:
ComputeCapability would be better as an open enumeration if you expect software to be able to use it as a selection key. Hi Stephen
The ComputeCapability in the AcceleratorEnvironment is an attribute strongly recommended for Nvidia GPUs descriptions: https://en.wikipedia.org/wiki/CUDA#GPUs_supported It's not properly a version number, we may say that is a "category number" or "category ID", it can't be an enumeration. We discussed a lot in the past about that attribute but it seems to me that we still don't have a clear idea. BTW, since the list of comments for that attribute is getting very long I reset it and put a short description. -- ---------------------- Ing. Paolo Andreetto INFN Sezione di Padova Via Marzolo, 8 35131 Padova - Italy Tel: +39 049.967.7378 Skype: andreettopl ----------------------
Paolo Andreetto <paolo.andreetto@pd.infn.it> said:
The ComputeCapability in the AcceleratorEnvironment is an attribute strongly recommended for Nvidia GPUs descriptions: https://en.wikipedia.org/wiki/CUDA#GPUs_supported
OK, I see. In that case I think the description needs to be precise, both in terms of what the attribute should mean and for the expected format of the string. Stephen
Greetings Alessandro, Would you like a meeting to discuss these changes? If yes, which of these dates are you available at the usual 15:30-17:00 Central Europe, 8:30-10:00 AM US Central? June 12, 2018 June 26, 2018 July 10, 2018 Regards, JP
On May 31, 2018, at 10:31 AM, Alessandro Paolini <alessandro.paolini@egi.eu <mailto:alessandro.paolini@egi.eu>> wrote:
Dear all,
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.
This is the draft document: https://docs.google.com/document/d/1BpeTBQfCn8xRo4Ff38esRhBwzoUHE4bVxba2rEAz... <https://docs.google.com/document/d/1BpeTBQfCn8xRo4Ff38esRhBwzoUHE4bVxba2rEAzI-U/edit#>
I still need to update the figures, which for the moment you can find here: https://docs.google.com/document/d/1x2gUt2lJNevle8evQu6LcKr9xs5NHRd6FbNzb1yK... <https://docs.google.com/document/d/1x2gUt2lJNevle8evQu6LcKr9xs5NHRd6FbNzb1yK2eE/edit?usp=sharing>
Here is the list of the latest classes and attributes added/modified:
Classes: ComputingShareAcceleratorInfo ComputingManagerAcceleratorInfo AcceleratorEnvironment CloudComputingShareAcceleratorInfo CloudComputingManagerAcceleratorInfo CloudComputingImageAcceleratorInfo CloudComputingImageNetworkTraffic CloudComputingInstanceAcceleratorInfo
Attributes: GLUE2EndpointAuthentication GLUE2ComputingEndpointAuthentication GLUE2CloudComputingEndpointAuthentication GLUE2CloudComputingShareDefaultNetwokType GLUE2CloudComputingSharePublicNetwokName GLUE2CloudComputingShareProjectID GLUE2CloudComputingVirtualAcceleratorComputeCapability GLUE2CloudComputingVirtualAcceleratorVirtualizationType GLUE2CloudComputingImageContextualizationName GLUE2CloudComputingImageContextualizationVersion GLUE2CloudComputingImageDescription GLUE2CloudComputingImageVersion
Storage attributes: StorageShareNumberOfFiles (requested by ATLAS)
Best regards, Alessandro
-- 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 _______________________________________________ glue-wg mailing list glue-wg@ogf.org <mailto:glue-wg@ogf.org> https://www.ogf.org/mailman/listinfo/glue-wg
Hi JP, for me either June 12th or 26th would be fine. I will ask also my colleagues Baptiste, Enol, and Paolo. cheers, Alessandro On 1 June 2018 at 13:25, Navarro, JP <navarro@mcs.anl.gov> wrote:
Greetings Alessandro,
Would you like a meeting to discuss these changes?
If yes, which of these dates are you available at the usual 15:30-17:00 Central Europe, 8:30-10:00 AM US Central?
June 12, 2018 June 26, 2018 July 10, 2018
Regards,
JP
On May 31, 2018, at 10:31 AM, Alessandro Paolini < alessandro.paolini@egi.eu> wrote:
Dear all,
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.
This is the draft document: https://docs.google.com/document/d/ 1BpeTBQfCn8xRo4Ff38esRhBwzoUHE4bVxba2rEAzI-U/edit#
I still need to update the figures, which for the moment you can find here: https://docs.google.com/document/d/1x2gUt2lJNevle8evQu6LcKr9xs5NH Rd6FbNzb1yK2eE/edit?usp=sharing
Here is the list of the latest classes and attributes added/modified:
Classes: ComputingShareAcceleratorInfo ComputingManagerAcceleratorInfo AcceleratorEnvironment CloudComputingShareAcceleratorInfo CloudComputingManagerAcceleratorInfo CloudComputingImageAcceleratorInfo CloudComputingImageNetworkTraffic CloudComputingInstanceAcceleratorInfo
Attributes: GLUE2EndpointAuthentication GLUE2ComputingEndpointAuthentication GLUE2CloudComputingEndpointAuthentication GLUE2CloudComputingShareDefaultNetwokType GLUE2CloudComputingSharePublicNetwokName GLUE2CloudComputingShareProjectID GLUE2CloudComputingVirtualAcceleratorComputeCapability GLUE2CloudComputingVirtualAcceleratorVirtualizationType GLUE2CloudComputingImageContextualizationName GLUE2CloudComputingImageContextualizationVersion GLUE2CloudComputingImageDescription GLUE2CloudComputingImageVersion
Storage attributes: StorageShareNumberOfFiles (requested by ATLAS)
Best regards, Alessandro
-- 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 _______________________________________________ glue-wg mailing list glue-wg@ogf.org https://www.ogf.org/mailman/listinfo/glue-wg
-- 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
Other GLUE WG members who would like to participate in this meeting please reply with your availability on these two dates.
June 12, 2018 June 26, 2018
JP
On Jun 1, 2018, at 7:19 AM, Alessandro Paolini <alessandro.paolini@egi.eu <mailto:alessandro.paolini@egi.eu>> wrote:
Hi JP,
for me either June 12th or 26th would be fine. I will ask also my colleagues Baptiste, Enol, and Paolo.
cheers, Alessandro
On 1 June 2018 at 13:25, Navarro, JP <navarro@mcs.anl.gov <mailto:navarro@mcs.anl.gov>> wrote: Greetings Alessandro,
Would you like a meeting to discuss these changes?
If yes, which of these dates are you available at the usual 15:30-17:00 Central Europe, 8:30-10:00 AM US Central?
June 12, 2018 June 26, 2018 July 10, 2018
Regards,
JP
On May 31, 2018, at 10:31 AM, Alessandro Paolini <alessandro.paolini@egi.eu <mailto:alessandro.paolini@egi.eu>> wrote:
Dear all,
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.
This is the draft document: https://docs.google.com/document/d/1BpeTBQfCn8xRo4Ff38esRhBwzoUHE4bVxba2rEAz... <https://docs.google.com/document/d/1BpeTBQfCn8xRo4Ff38esRhBwzoUHE4bVxba2rEAzI-U/edit#>
I still need to update the figures, which for the moment you can find here: https://docs.google.com/document/d/1x2gUt2lJNevle8evQu6LcKr9xs5NHRd6FbNzb1yK... <https://docs.google.com/document/d/1x2gUt2lJNevle8evQu6LcKr9xs5NHRd6FbNzb1yK2eE/edit?usp=sharing>
Here is the list of the latest classes and attributes added/modified:
Classes: ComputingShareAcceleratorInfo ComputingManagerAcceleratorInfo AcceleratorEnvironment CloudComputingShareAcceleratorInfo CloudComputingManagerAcceleratorInfo CloudComputingImageAcceleratorInfo CloudComputingImageNetworkTraffic CloudComputingInstanceAcceleratorInfo
Attributes: GLUE2EndpointAuthentication GLUE2ComputingEndpointAuthentication GLUE2CloudComputingEndpointAuthentication GLUE2CloudComputingShareDefaultNetwokType GLUE2CloudComputingSharePublicNetwokName GLUE2CloudComputingShareProjectID GLUE2CloudComputingVirtualAcceleratorComputeCapability GLUE2CloudComputingVirtualAcceleratorVirtualizationType GLUE2CloudComputingImageContextualizationName GLUE2CloudComputingImageContextualizationVersion GLUE2CloudComputingImageDescription GLUE2CloudComputingImageVersion
Storage attributes: StorageShareNumberOfFiles (requested by ATLAS)
Best regards, Alessandro
-- 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 _______________________________________________ glue-wg mailing list glue-wg@ogf.org <mailto:glue-wg@ogf.org> https://www.ogf.org/mailman/listinfo/glue-wg <https://www.ogf.org/mailman/listinfo/glue-wg>
-- 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
On 06/01/2018 03:29 PM, Navarro, JP wrote:
Other GLUE WG members who would like to participate in this meeting please reply with your availability on these two dates.
June 12, 2018 June 26, 2018
For me it's fine, both the first and the second date. -- ---------------------- Ing. Paolo Andreetto INFN Sezione di Padova Via Marzolo, 8 35131 Padova - Italy Tel: +39 049.967.7378 Skype: andreettopl ----------------------
On 06/01/2018 03:29 PM, Navarro, JP wrote:
Other GLUE WG members who would like to participate in this meeting please reply with your availability on these two dates.
June 12, 2018 June 26, 2018
JP
Is it confirmed the meeting for this afternoon? Cheers -- ---------------------- Ing. Paolo Andreetto INFN Sezione di Padova Via Marzolo, 8 35131 Padova - Italy Tel: +39 049.967.7378 Skype: andreettopl ----------------------
hi Paolo, yes, you weren't included in the announcement, here the details: Greetings GLUE WG, Our next GLUE WG teleconference will be: : Tuesday, June 12, 2018 : 15:30-17:00 Central Europe, 8:30-10:00 AM US Central We will use Zoom teleconference and screen sharing: : By Browser: https://zoom.us/j/451341881 : By Phone: +1 646 876 9923 or +1 669 900 6833 or +1 408 638 0968 : By iPhone one-tap: +16468769923,,451341881# or +16699006833,,451341881# : International numbers: https://zoom.us/zoomconference?m= 7BCOXsCfNrZcQ9fxuSwFbJJY84d8IBfK : Conference ID: 451 341 881 IMPORTANT: Recommend that those that need to configure and test Zoom please try to connect 15 minutes early. Planned agenda: 1) Discuss GLUE2.1 draft with cloud and accelerator entities Lead: Alessandro Paolini and colleagues https://docs.google.com/document/d/1BpeTBQfCn8xRo4Ff38esRhBwzoUHE 4bVxba2rEAzI-U https://docs.google.com/document/d/1x2gUt2lJNevle8evQu6LcKr9xs5NH Rd6FbNzb1yK2eE On 12 June 2018 at 15:03, Paolo Andreetto <paolo.andreetto@pd.infn.it> wrote:
On 06/01/2018 03:29 PM, Navarro, JP wrote:
Other GLUE WG members who would like to participate in this meeting please reply with your availability on these two dates.
June 12, 2018
June 26, 2018
JP
Is it confirmed the meeting for this afternoon?
Cheers
-- ---------------------- Ing. Paolo Andreetto INFN Sezione di Padova Via Marzolo, 8 35131 Padova - Italy
Tel: +39 049.967.7378 Skype: andreettopl ----------------------
-- 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
Hi Paolo, Sorry, I didn’t realize you aren't on the GLUE WG e-mail list… See you in a few minutes. JP
On Jun 12, 2018, at 8:07 AM, Alessandro Paolini <alessandro.paolini@egi.eu <mailto:alessandro.paolini@egi.eu>> wrote:
hi Paolo,
yes, you weren't included in the announcement, here the details:
Greetings GLUE WG,
Our next GLUE WG teleconference will be: : Tuesday, June 12, 2018 : 15:30-17:00 Central Europe, 8:30-10:00 AM US Central
We will use Zoom teleconference and screen sharing: : By Browser: https://zoom.us/j/451341881 <https://zoom.us/j/451341881> : By Phone: +1 646 876 9923 or +1 669 900 6833 or +1 408 638 0968 : By iPhone one-tap: +16468769923,,451341881# or +16699006833,,451341881# : International numbers: https://zoom.us/zoomconference?m=7BCOXsCfNrZcQ9fxuSwFbJJY84d8IBfK <https://zoom.us/zoomconference?m=7BCOXsCfNrZcQ9fxuSwFbJJY84d8IBfK> : Conference ID: 451 341 881
IMPORTANT: Recommend that those that need to configure and test Zoom please try to connect 15 minutes early.
Planned agenda:
1) Discuss GLUE2.1 draft with cloud and accelerator entities Lead: Alessandro Paolini and colleagues https://docs.google.com/document/d/1BpeTBQfCn8xRo4Ff38esRhBwzoUHE4bVxba2rEAz... <https://docs.google.com/document/d/1BpeTBQfCn8xRo4Ff38esRhBwzoUHE4bVxba2rEAzI-U> https://docs.google.com/document/d/1x2gUt2lJNevle8evQu6LcKr9xs5NHRd6FbNzb1yK... <https://docs.google.com/document/d/1x2gUt2lJNevle8evQu6LcKr9xs5NHRd6FbNzb1yK2eE>
On 12 June 2018 at 15:03, Paolo Andreetto <paolo.andreetto@pd.infn.it <mailto:paolo.andreetto@pd.infn.it>> wrote: On 06/01/2018 03:29 PM, Navarro, JP wrote:
Other GLUE WG members who would like to participate in this meeting please reply with your availability on these two dates.
June 12, 2018 June 26, 2018
JP
Is it confirmed the meeting for this afternoon?
Cheers -- ---------------------- Ing. Paolo Andreetto INFN Sezione di Padova Via Marzolo, 8 35131 Padova - Italy
Tel: +39 049.967.7378 Skype: andreettopl ----------------------
-- 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
Hi all, Thanks for the proposition, it seems that the date that would the most suit us is June 12th, 2018 from 15:30 to 17:00 CEST. If you already have some point/remarks we can also think about them before the meeting, just let us know. Talk to you soon! Best, Baptiste On Fri, 1 Jun 2018 at 14:20 Alessandro Paolini <alessandro.paolini@egi.eu> wrote:
Hi JP,
for me either June 12th or 26th would be fine. I will ask also my colleagues Baptiste, Enol, and Paolo.
cheers, Alessandro
On 1 June 2018 at 13:25, Navarro, JP <navarro@mcs.anl.gov> wrote:
Greetings Alessandro,
Would you like a meeting to discuss these changes?
If yes, which of these dates are you available at the usual 15:30-17:00 Central Europe, 8:30-10:00 AM US Central?
June 12, 2018 June 26, 2018 July 10, 2018
Regards,
JP
On May 31, 2018, at 10:31 AM, Alessandro Paolini < alessandro.paolini@egi.eu> wrote:
Dear all,
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.
This is the draft document: https://docs.google.com/document/d/1BpeTBQfCn8xRo4Ff38esRhBwzoUHE4bVxba2rEAz...
I still need to update the figures, which for the moment you can find here:
https://docs.google.com/document/d/1x2gUt2lJNevle8evQu6LcKr9xs5NHRd6FbNzb1yK...
Here is the list of the latest classes and attributes added/modified:
Classes: ComputingShareAcceleratorInfo ComputingManagerAcceleratorInfo AcceleratorEnvironment CloudComputingShareAcceleratorInfo CloudComputingManagerAcceleratorInfo CloudComputingImageAcceleratorInfo CloudComputingImageNetworkTraffic CloudComputingInstanceAcceleratorInfo
Attributes: GLUE2EndpointAuthentication GLUE2ComputingEndpointAuthentication GLUE2CloudComputingEndpointAuthentication GLUE2CloudComputingShareDefaultNetwokType GLUE2CloudComputingSharePublicNetwokName GLUE2CloudComputingShareProjectID GLUE2CloudComputingVirtualAcceleratorComputeCapability GLUE2CloudComputingVirtualAcceleratorVirtualizationType GLUE2CloudComputingImageContextualizationName GLUE2CloudComputingImageContextualizationVersion GLUE2CloudComputingImageDescription GLUE2CloudComputingImageVersion
Storage attributes: StorageShareNumberOfFiles (requested by ATLAS)
Best regards, Alessandro
-- 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 _______________________________________________ glue-wg mailing list glue-wg@ogf.org https://www.ogf.org/mailman/listinfo/glue-wg
-- 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 _______________________________________________ glue-wg mailing list glue-wg@ogf.org https://www.ogf.org/mailman/listinfo/glue-wg
-- Baptiste Grenier EGI Foundation - Operations Officer Phone: +31 627 860 852 Skype: baptiste.grenier.egi
Dear all, Reviewing the cloud part of the proposed draft I think we should also change a bit the references to the hypervisors as these are not normally exposed at all to the users and even irrelevant for most cases. Instead the CloucComputingManager should be what is described now as the Cloud Middleware. In the "Conceptual Model of the Cloud Computing Service" it is stated: * An Hypervisor, usual name for Virtual Machine Manager, is a piece of computer software, firmware or hardware that creates, runs and manages Virtual Machine * A Cloud Middleware is a piece of computer software that leverages on hypervisor virtualization capabilities to provide Virtual Machines on-demand to final users. The Cloud Middleware may provide not only virtual servers (namely Infrastructure as a Service feature), but also storage (Storage as a Service) and other rich services (Platform as a Service, etc…). I would turn this into: * A Cloud Middleware is a piece of computer software that leverages on hypervisor virtualization capabilities to provide Virtual Machines on-demand to final users. The Cloud Middleware may provide not only virtual servers, but also storage and other rich services (e.g. Platform as a Service). And then in the CloudComputingManager: Current text: The CloudComputingManager class is a specialization of the Manager class for the computational capability (Virtual Machines) manager. The CloudComputingManager is responsible for the local control of resources. The CloudComputingManager layer is not exposed directly to external clients or to the Virtual Machines themselves. The Virtual Machine manager is usually referred as Hypervisor, thus a piece of software, firmware or hardware which creates, runs and manages Virtual Machines. A Compute Service will usually have only one Compute Manager, but MAY have more. The class provides aggregated information on controlled resources, hypervisors limits and also describes local storage extents accessible to the Virtual Machines. I propose to just remove the "The Virtual Machine manager is usually referred as Hypervisor, thus a piece of software, firmware or hardware which creates, runs and manages Virtual Machines." sentence. Any other references to hypervisor should be updated. Regards, Enol On Thu, 31 May 2018 at 16:31 Alessandro Paolini <alessandro.paolini@egi.eu> wrote:
Dear all,
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.
This is the draft document: https://docs.google.com/document/d/1BpeTBQfCn8xRo4Ff38esRhBwzoUHE4bVxba2rEAz...
I still need to update the figures, which for the moment you can find here:
https://docs.google.com/document/d/1x2gUt2lJNevle8evQu6LcKr9xs5NHRd6FbNzb1yK...
Here is the list of the latest classes and attributes added/modified:
Classes: ComputingShareAcceleratorInfo ComputingManagerAcceleratorInfo AcceleratorEnvironment CloudComputingShareAcceleratorInfo CloudComputingManagerAcceleratorInfo CloudComputingImageAcceleratorInfo CloudComputingImageNetworkTraffic CloudComputingInstanceAcceleratorInfo
Attributes: GLUE2EndpointAuthentication GLUE2ComputingEndpointAuthentication GLUE2CloudComputingEndpointAuthentication GLUE2CloudComputingShareDefaultNetwokType GLUE2CloudComputingSharePublicNetwokName GLUE2CloudComputingShareProjectID GLUE2CloudComputingVirtualAcceleratorComputeCapability GLUE2CloudComputingVirtualAcceleratorVirtualizationType GLUE2CloudComputingImageContextualizationName GLUE2CloudComputingImageContextualizationVersion GLUE2CloudComputingImageDescription GLUE2CloudComputingImageVersion
Storage attributes: StorageShareNumberOfFiles (requested by ATLAS)
Best regards, Alessandro
-- Dr. Alessandro Paolini Operations Officer - EGI Foundation Science Park 140 <https://maps.google.com/?q=Science+Park+140+1098+XG+Amsterdam+The+Netherlands&entry=gmail&source=g> 1098 XG Amsterdam <https://maps.google.com/?q=Science+Park+140+1098+XG+Amsterdam+The+Netherlands&entry=gmail&source=g> The Netherlands <https://maps.google.com/?q=Science+Park+140+1098+XG+Amsterdam+The+Netherlands&entry=gmail&source=g> 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
On 8 June 2018 at 13:59, Enol Fernández <enol.fernandez@egi.eu> wrote:
Dear all,
Reviewing the cloud part of the proposed draft I think we should also change a bit the references to the hypervisors as these are not normally exposed at all to the users and even irrelevant for most cases. Instead the CloucComputingManager should be what is described now as the Cloud Middleware.
In the "Conceptual Model of the Cloud Computing Service" it is stated: * An Hypervisor, usual name for Virtual Machine Manager, is a piece of computer software, firmware or hardware that creates, runs and manages Virtual Machine * A Cloud Middleware is a piece of computer software that leverages on hypervisor virtualization capabilities to provide Virtual Machines on-demand to final users. The Cloud Middleware may provide not only virtual servers (namely Infrastructure as a Service feature), but also storage (Storage as a Service) and other rich services (Platform as a Service, etc…).
I would turn this into: * A Cloud Middleware is a piece of computer software that leverages on hypervisor virtualization capabilities to provide Virtual Machines on-demand to final users. The Cloud Middleware may provide not only virtual servers, but also storage and other rich services (e.g. Platform as a Service).
And then in the CloudComputingManager: Current text:
The CloudComputingManager class is a specialization of the Manager class for the computational capability (Virtual Machines) manager. The CloudComputingManager is responsible for the local control of resources. The CloudComputingManager layer is not exposed directly to external clients or to the Virtual Machines themselves.
The Virtual Machine manager is usually referred as Hypervisor, thus a piece of software, firmware or hardware which creates, runs and manages Virtual Machines. A Compute Service will usually have only one Compute Manager, but MAY have more. The class provides aggregated information on controlled resources, hypervisors limits and also describes local storage extents accessible to the Virtual Machines.
I propose to just remove the "The Virtual Machine manager is usually referred as Hypervisor, thus a piece of software, firmware or hardware which creates, runs and manages Virtual Machines." sentence.
Any other references to hypervisor should be updated.
it is fine with me (and we should add "Cloud" before "Compute Service" and "Compute Manager" cheers, alessandro
Regards,
Enol
On Thu, 31 May 2018 at 16:31 Alessandro Paolini <alessandro.paolini@egi.eu> wrote:
Dear all,
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.
This is the draft document: https://docs.google.com/document/d/ 1BpeTBQfCn8xRo4Ff38esRhBwzoUHE4bVxba2rEAzI-U/edit#
I still need to update the figures, which for the moment you can find here: https://docs.google.com/document/d/1x2gUt2lJNevle8evQu6LcKr9xs5NH Rd6FbNzb1yK2eE/edit?usp=sharing
Here is the list of the latest classes and attributes added/modified:
Classes: ComputingShareAcceleratorInfo ComputingManagerAcceleratorInfo AcceleratorEnvironment CloudComputingShareAcceleratorInfo CloudComputingManagerAcceleratorInfo CloudComputingImageAcceleratorInfo CloudComputingImageNetworkTraffic CloudComputingInstanceAcceleratorInfo
Attributes: GLUE2EndpointAuthentication GLUE2ComputingEndpointAuthentication GLUE2CloudComputingEndpointAuthentication GLUE2CloudComputingShareDefaultNetwokType GLUE2CloudComputingSharePublicNetwokName GLUE2CloudComputingShareProjectID GLUE2CloudComputingVirtualAcceleratorComputeCapability GLUE2CloudComputingVirtualAcceleratorVirtualizationType GLUE2CloudComputingImageContextualizationName GLUE2CloudComputingImageContextualizationVersion GLUE2CloudComputingImageDescription GLUE2CloudComputingImageVersion
Storage attributes: StorageShareNumberOfFiles (requested by ATLAS)
Best regards, Alessandro
-- Dr. Alessandro Paolini Operations Officer - EGI Foundation Science Park 140 <https://maps.google.com/?q=Science+Park+140+1098+XG+Amsterdam+The+Netherlands&entry=gmail&source=g> 1098 XG Amsterdam <https://maps.google.com/?q=Science+Park+140+1098+XG+Amsterdam+The+Netherlands&entry=gmail&source=g> The Netherlands <https://maps.google.com/?q=Science+Park+140+1098+XG+Amsterdam+The+Netherlands&entry=gmail&source=g> 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
-- 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
participants (7)
-
Alessandro Paolini -
Baptiste Grenier -
Enol Fernández -
Navarro, JP -
Paolo Andreetto -
Sill, Alan -
Stephen Burke - UKRI STFC