[glue-wg] glue2 cloud examples

[Salvatore Pinto]

Hi All,
I totally agree with JP, the focus is interoperability and we should 
reach an agreement which does not involve EGI to build his own 
particular profile or standard. But we can discuss about that at the 
teleconference today, togheter with the advantages and disadvantages of 
both my and Warren approaches.

Cheers,
   Salvatore.

On 05/05/2014 17:21, Navarro, John-Paul F. wrote:
> On May 2, 2014, at 2:29 PM, Warren Smith <wsmith at tacc.utexas.edu> wrote:
>
>> A better strategy may be to call what you are working on "EGI Cloud Extensions to GLUE 2.0" or something - a profile that describes how you use GLUE 2 to describe clouds in EGI. This would let you move forward with some input from the working group, but without needing approval from the working group. We could also see how your cloud profile works and how well my a cloud profile works, without trying to merge them now. We could use this information when we start work on GLUE 3.
> The purpose of the GLUE WG group is to provide a forum for sharing diverse requirements and trying to find a common interoperable design.  In my view, relinquishing the two current proposal as infrastructure specific profiles, that would not be interoperable, does not accomplish our purpose.  I think clouds have been around long enough, and are understood enough, that we could agree on an approach.  In fact, it sounds like there are ways to make both approaches work?  If this is not the case, we should focus on what requirements can't be met by one of the approaches in tomorrow's meeting.
>
> It seems like both approach provide a mechanism to add necessary entities.
> It's less clear if both approach can describe the required relationships.
>
> I think we there is room to come to an agreement on a single GLUE 2 compatible and interoperable way to support clouds.  I recommend we continue documenting the advantages and short comings of both approaches and try to come to a consensus.  Can Salvator and Warren prepare brief list of advantages an disadvantages for both approaches that we could discuss tomorrow?  In particular trying to highlight any use cases/requirements that are difficult to satisfy with either approach?
>
> Thanks,
>
> JP


-- 
Salvatore Pinto
Cloud Technologist, EGI.eu
e-mail: salvatore.pinto at egi.eu
skype: salvatore.pinto0
Science Park 140, Amsterdam, The Netherlands