Dear Pascal, SAME instructions/guidelines do apply to both Users' & Programmers' Guides and the Unit Test Plans and Report: * Users' & Programmers' Guides should guide developers in how to configure or program applications using the services provided by the GE. As I have explained multiple times, they should not be just a repetition of the GE's API specifications but some sort of "Hello World" example. And the way these Users' and Programmers' Guides would not vary because a GE instance is hosted in the FI-WARE Testbed dedicated datacenter facility or any other remote location. * The Unit Testing Plan should document "how-to-test" the different features of an GE instance, no matter where it is hosted. The report, of course, is relevant to a particular instance of the GE: the one against which you passed the tests of the Unit Testing Plan. In this respect, we are asking you to report on the execution of the Testing Plan against the instance of the GE you have used for Unit Testing purposes. In the case of GEs provided as a service, we would highly recommend that you run the Unit Testing Plan against the instance of the GE that will be provided as a service. In the case of GEs that will be hosted in the FI-WARE dedicated datacenter or in facilities owned by UC projects, we assume that you have run the Unit Testing Plan against an instance of the GE in your own lab. Of course, one thing you should be prepared for, is that someone from WP10 decides to run the Unit Testing Plan against the instance of a GE that has been deployed in the FI-WARE Testbed dedicated datacenter facility or remotely. That would lead to a report different from the one we are asking you now to provide. Such a second report, may be used as a sanity check and, eventually, to reject the deliverable in the case that the software doesn't pass a significant number of Tests in the Unit Testing Plan, provided that the Unit Testing Plan has been run properly. Amendment to my previous mail: the deadline extension regaring binaries of GEs that were agreed that would be provided as a service hosted remotely also applies to the Installation & Admin Guides of those GEs. Hope it helps, -- Juanjo On 20/07/12 15:20, BISSON Pascal wrote: Dear Juanjo, Ok but here you forgot one important point which is that the way GEs are released as a service versus as software package also impacts the content of the User guide, Install guide, Unit test plan & reporting. That's also why I was asking in one of my previous emails for different instructions/guidelines to be provided for each of the two cases. Hope you can share and agree. BR Pascal De : fiware-wpl-bounces at lists.fi-ware.eu<mailto:fiware-wpl-bounces at lists.fi-ware.eu> [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoyé : vendredi 20 juillet 2012 14:59 À : fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu> Objet : Re: [Fiware-wpl] deliverables for GE-s running as a service Hi all, Regarding software that will be provided on the FI-WARE Testbed as a Service, we will extend the deadline for delivery of binaries until we get the response from our PO regarding how he believes that delivery of the software can be confirmed. That extension doesn't apply neither to software that needs to be installed on the FI-WARE Testbed nor to software that will be provided for installation at UC projects' premises/facilities/equipments (e.g., Cloud Proxy). With respect to distinction between background and foreground, I will respond in a separate mail. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es<http://www.tid.es> email: jhierro at tid.es<mailto: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 On 20/07/12 14:07, Farkas, Lorant (NSN - HU/Budapest) wrote: Dear All, Recently there have been discussions around the need for providing binaries constituting background in case of FI-WARE. Several partners raised concerns about that. The issue is burning, because in the current situation unless the partner contributes the binary of the background by the 23rd of July, 40% of the PM-s are lost. Let me share NSN's view on this. 1. According to the FI-WARE contract special clause 41 (article 7.3) "other beneficiaries" (meaning FI-PPP partners excluding FI-WARE ones) rights and obligations are limited to foreground and do not extend to background. Translated: they should not have access to background. To comply to this clause with the tool called "fi-ware restricted" 1.1 either there would be no reason for exposing it to all FI-PPP consortium, but just FI-WARE and the commission 1.2 or there would be no reason for asking partners to upload binaries related to background 2. According to Annex 2 of the FI-WARE contract beneficiaries may define the background needed for the purposes of the project in a written agreement and, where appropriate, may agree to exclude specific background. All requests for access rights shall be made in writing. The granting of access rights may be made conditional on the acceptance of specific conditions aimed at ensuring that these rights will be used only for the intended purpose and that appropriate confidentiality obligations are in place. So when you expose background through "forge fi-ware restricted", even restricted to the FI-WARE partners, you take the possibility away from partners to impose such conditions. This would breach the contract. 3. According to Annex 2 of the FI-WARE contract access rights to background shall be granted to the other beneficiaries, if it is needed to enable those beneficiaries to carry out their own work under the project provided that the beneficiary concerned is entitled to grant them. Example: from our side for the NSN IDM solution there is no such need, because it is available as a service. 4. On the other hand beneficiaries shall provide all detailed data requested by the Commission for the purposes of the proper administration of this project. Our interpretation is that there might be a request from the Commission to take a look at binaries of background. The technical means for that would be to establish sharing space only for the Commission's representatives, not the entire FI-WARE/FI-PPP consortium. As a result, NSN rightfully believes there is no reason for any partner offering a GE as a service to provide binaries in "fi-ware restricted". Therefore also the content of the contributions to D8.x would be different for partners providing their assets as a service or as SW (e.g. unit testing plan, installation guide, etc.). Thanks & Br, Lóránt Farkas Senior Research Engineer H-1092 Budapest, Hungary Köztelek u.6. Tel: +36 20 977 7797 Mob: +36 20 936 9002 lorant.farkas at nsn.com<mailto:akos.fabian at nsn.com> http://www.nokiasiemensnetworks.com/global/ _______________________________________________ Fiware-wpl mailing list Fiware-wpl at lists.fi-ware.eu<mailto:Fiware-wpl at lists.fi-ware.eu> http://lists.fi-ware.eu/listinfo/fiware-wpl ________________________________ 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 ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20120720/a0ebaa97/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy