Hi Salvatore, Then we don´t need to worry. The use cases are clear and as you have described, the applications or users who will make use of this information will know which top BDIIs they have to use. Apart from this use case in EGI, I´m not aware of any other use cases interested in using this information although I will check in WLCG. Regards, Maria
-----Original Message----- From: Salvatore Pinto [mailto:salvatore.pinto@egi.eu] Sent: 01 August 2014 09:45 To: Maarten Litmaath; Maria Alandes Pradillo Cc: Florido Paganelli; glue-wg@ogf.org Subject: Re: [glue-wg] VOTE by 8/1: GLUE 2.1 for describing cloud resources?
Hi, please consider that this issue will be only for the Top BDIIs and only for the cloud resources. For the site BDIIs, this will hot have this issue, since to publish cloud resources they will need to update to version 2.1 (and our fedcloud probes will check that), so update of the cloud-provider-info script will force update of the glue2-schema.
Regarding the Top-BDII, the problem is also mitigated. In the fedcloud, we have two kind of "users": the automatic systems (like AppDB and in the future COMPs, SlipStream, etc...), who will install and manage a Top-BDII locally, so they will ensure that the Top-BDII is updated when they will update their query to use 2.1 (and fall back to 2.0) and the "manual users", which uses the Top-BDIIs indicated by the FedCloud, reported into a wiki page, which we can easily check if they are updated to 2.1 or not.
Cheers, Salvatore.
On 31/07/2014 17:38, Maarten.Litmaath@cern.ch wrote:
Hi,
There is no chaos because of this, the chaos remains in any case no matter what you know about what´s installed out there. And in any case, it´s still an assumption to think that because a site upgraded the bdii package it also upgraded the glue-schema package. Maybe a fair assumption, but an assumption after all. I think we need a clear way to see which BDIIs supposedly support the use of GLUE 2.1. Else we may run into nasty operational issues, where things sometimes work and sometimes do not, while at the same time all BDIIs present themselves as equal... That would be a _disservice_ to the user communities and their support infrastructures.
Since only the BDII version is published today, the easiest way is to increase its version number, unfortunately. At the same time we may want to consider publishing the schema version explicitly.
-- Salvatore Pinto Cloud Technologist, EGI.eu e-mail: salvatore.pinto@egi.eu skype: salvatore.pinto0 Science Park 140, Amsterdam, The Netherlands