Hi Juanjo, the preliminary pages of the I2ND architecture are currently on the public FI-WARE wiki at link https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Interface_to_Networks_and_Devices_%28I2ND%29_Architecture_%28PRELIMINARY%29#Architecture_description_of_GEs I have translated the pages according to the guidelines, along with doing those modifications discussed today, like insertion of the sentences we agreed for the Architecture description of each GE, in particular for NetIC and S3C. Please check if everything is fine and let me know, thanks. Have a nice week-end! Pier -----Messaggio originale----- Da: Juanjo Hierro [mailto:jhierro at tid.es] Inviato: venerdì 9 marzo 2012 08:53 A: Garino Pierangelo Cc: Hans.Einsiedler at telekom.de; jhierro >> "Juan J. Hierro" Oggetto: IMPORTANT: Approach regarding I2ND Hi Pier, Despite I haven't interacted with you on the matter ... I have been reviewing the contents of the I2ND chapter contribution to both the Architecture Description and the Technical Roadmap deliverables ... In general, your contributions are in a good shape (as used to be the case, BTW :-) but what I would like to discuss with you is a more fundamental question. My major concern is what we should commit for the first Release of FI-WARE. I'm rather reluctant to commit anything regarding NetIC and S3C for the first release. I believe this deserves a more careful planning. I would go first for consolidating a stable version of the Dedicated FI-WARE DataCenter in Sevilla with most relevant GEs coming from the Cloud, Data, IoT, Apps and Security chapters. Then plan how this could connect with some of the experimental facilities where we may have a setup of the NetIC and S3C GEs. Also think carefully what switching equipments can be acquired, for the planned second phase of acquisition of equipments for the FI-WARE DataCenter, and integrated in the infrastructure of the FI-WARE DataCenter that may help to test NetIC and S3C GEs. There is nothing in the DoW that obligues us to deliver anything regarding any chapter on the first Release. Therefore, it is up to us to decide. And not put artificial pressure on our shoulders ourselves. IMHO, FI-WARE capabilities brought by means of adding NetIC and S3C GEs are fine if they are available for the second release of FI-WARE, even for the third. Regarding the CDI, I feel more or less the same. In this case because it is better to commit bringing something complete that just a few features ... but I'm more open here. Regarding the Cloud Edge/proxy component, I feel like this is a better candidate for the first release, but I wouldn't dismiss to declare we are going to plan an updgrade of the FI-WARE Tesbed by Q42012 and commit it there. All the contents of the Architecture Description deliverable may be published now but with a note on those we would label as preliminary, since they won't go on the first release, and should be considered therefore by the reader as still work in progress. Note that all the above is not because I'm not confident that the I2ND chapter could deliver things on time and with the expected quality. It's more about not delivering things earlier than is needed and be able to focus in less number of GEs while consolidating a first release of FI-WARE and the FI-WARE testbed. Please note that, the more GEs we commit for the first Release, the more complex will be managing the integration of FI-WARE and delivery of a working FI-WARE Testbed environment. So better we keep numbers manageable. If the FI-WARE Testbed becomes a disaster, and unstable piece, because there were many things to digest, then it will be a problem for all of us involved, no matter if a particular chapter has done things well. So people dealing with coordination of the integration activities (not only owners of some tasks in the Testbed WP but coordinators of each chapter) should concentrate in a "piece of cake they can digest". Let's discuss this in our bilateral follow up confcall today ... I wanted to send you this mail early this morning so that you can think a bit about the above, its pros and cons, so we can have a more fruitful discussion later in the follow-up confcall Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy