Hi Maria, since we are only adding new entities in the schema, I think it will be possible to perform the migration quite smoothly in 4 steps: 1. Top-BDII & Site-BDII s to update schema to 2.1 (this can be done via an update of the BDII software in the UMD/EMI and will not distrupt anything) 2. Site-BDII provider update to publish cloud info in both 2.0 and 2.1 (this can be done in parallel with #1, since Top-BDIIs not already updated to 2.1 will just ignore the new 2.1 entities) 3. When 1&2 are complete, update clients to consume 2.1 information (at the time, only AppDB is consuming this info, the new clients we are going to develop will be already based on at least a draft of 2.1) 4. When 3 is complete, Site-BDII provider update to publish cloud info only in 2.1 Cheers, Salvatore. On 29/07/2014 12:03, Maria Alandes Pradillo wrote:
Dear Florido,
The only problem I see if we go for a 2.1 version is that we need to understand how to deploy all this in the hierarchical BDII model. What happens if a site BDII hasn´t upgraded the schema to 2.1, it only understands 2.0, and it queries a cloud resource which supports 2.1? will it fail? Or will it fail to publish only those new entities that do not exist yet in 2.0? The same scenario goes for a 2.0 top BDII trying to query 2.1 site BDIIs. I guess until the whole grid hasn´t moved to 2.1 we may have some inconsistent things published around. I haven´t tested this so I´m not sure what happens when you want to publish something in LDAP that is not declared in the LDAP schema file. It is not possible to add ldap entities to an LDAP database if these entities do no refer to objects in the schema. In short, any BDII using the 2.0 schema will reject all 2.1-specific objects, that is, the cloud stuff. OK, so this is going to be the case in the infrastructure until all resource, site and top BDIIs are updated to glue-schema 2.1.
Regards, Maria _______________________________________________ glue-wg mailing list glue-wg@ogf.org https://www.ogf.org/mailman/listinfo/glue-wg
-- Salvatore Pinto Cloud Technologist, EGI.eu e-mail: salvatore.pinto@egi.eu skype: salvatore.pinto0 Science Park 140, Amsterdam, The Netherlands