[glue-wg] glue2 cloud examples

[Warren Smith]

That spreadsheet is very helpful. I've attached a new version with a few quick notes.

I really do need to explain/document the meaning of things like ComputingActivity (process? batch job? workflow?) and ComputingShare (partition? allocation? quota? queue?) to everyone that has tried to use our GLUE2. These are infrastructure developers, rather than end user scientists, too. Once they look at the contents of the documents, they understand what they represent, but it is the content that is useful in understanding, not the entity name.


Warren


________________________________
From: Salvatore Pinto [salvatore.pinto at egi.eu]
Sent: Tuesday, June 17, 2014 8:11 AM
To: Warren Smith; Navarro, John-Paul F.
Cc: OGF GLUE Working Group
Subject: Re: [glue-wg] glue2 cloud examples

(Hi Warren,
replies inline...

On 17/06/2014 03:00, Warren Smith wrote:

Another disadvantage of adding new cloud entities to the model is that new renderings would also need to be defined.


Comments on your points:

* I've only had to use a couple extensions to represent clouds in the current GLUE2. I've used a few extensions to represent clusters, too (see https://github.com/OGF-GLUE/JSON/tree/master/examples). So, without some examples showing that a lot of extensions are needed, I don't agree with that point.

you are right, without examples it is difficult to make a decision. I have compared your implementations of JSON rendering for Compute_OpenStack with my 2.1 cloud entities and I come up with the attached draft of "profile". Considering the number of original attributes not used and the number of extensions, in my opinion, since most of the old attributes are not used and there are quite a few extensions to be added, there is a rational for defining new entities...

* I don't think the GLUE2 entity names are self-explanatory in general - I always have to explain what they mean to new users. I don't think this is much worse for a cloud infrastructure than for a cluster or grid.


for me users with a basic knowledge of Grid computing should understand the meaning, of course this is not valid for all the users, what I was saying is that users with basic knowledge of Cloud computing would probably not be able to understand all the meaning of the profiled attributes without reading the doc...

* I don't quite follow the first advantage you list under "GLUE 2.1". In GLUE 2.0, ComputingActivity (instance) has a RequestedApplicationEnvironment attribute (image). ComputingActivity also has a Share association (inherited from Activity), but I'm not sure what a Share represents here.


a share in my view represented a zone (or sub site), like "Amazon Asia Pacific Site", with related quota, resources and templates associated

Warren

Cheers,
  Salvatore.

________________________________________
From: Salvatore Pinto [salvatore.pinto at egi.eu<mailto:salvatore.pinto at egi.eu>]
Sent: Tuesday, May 06, 2014 9:16 AM
To: Navarro, John-Paul F.; Warren Smith
Cc: OGF GLUE Working Group
Subject: Re: [glue-wg] glue2 cloud examples

Hi All,
here my comments to be discussed in today's teleconferece.

Cloud Profile for GLUE 2.0
   Advantages:
     * No need to update the implementation.
     * No need to manage two separate group of entities.
   Disadvantages:
     * Big usage of extended attributes to represent all the needed
additional attributes and many attributes are not needed. Eg. you add
around 3-4 new attributes to each entities and you do not use more than
10 in average.
     * Some attributes names from the implementation
(ApplicationEnvironment, ExecutionEnvironment) will not be
self-explanatory and user will always need to read the profile to
understand the meaning of the implementation.

GLUE 2.1
   Advantages:
     * Possibility to represent a different conceptual model, where the
OS images (application environment) are directly linked to the VM
(computing activity) and to the Share (Computing Share) so to the
Policies (VM can be private and started only to a given share associated
to given VOs)
     * Easier extension to future non-IaaS computing services (with its
own set of resources, you can edit them without messing with the Grid
entities)
   Disadvantages:
     * Need to update the implementation, adding the new cloud entities.
     * Cloud and Grid are seen separated, not as an unique computing
resource.

Cheers,
   Salvatore.





--
Salvatore Pinto
Cloud Technologist, EGI.eu
e-mail: salvatore.pinto at egi.eu<mailto:salvatore.pinto at egi.eu>
skype: salvatore.pinto0
Science Park 140, Amsterdam, The Netherlands
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ogf.org/pipermail/glue-wg/attachments/20140617/a3dc0957/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: GlueProfileTest-wsmith.xlsx
Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
Size: 27698 bytes
Desc: GlueProfileTest-wsmith.xlsx
URL: <http://www.ogf.org/pipermail/glue-wg/attachments/20140617/a3dc0957/attachment-0001.xlsx>