[Fiware-apps] FW: [Fiware-wpl] URGENT: GEis installation and test

[Heller, Markus]

Hi,

After having fixed the partner testing agreements in our chapter, now the next step:

2. within 25 april 2014 all the installations and tests must be completed either by the organisations leaving the project at m36, and by those organisation if a test assigned to them involve a gei owned by an organisation leaving the project at m36.

There is this restriction mentioned here by Stefano that M36-leaving partners are enforced to test now or have their GEs tested now.

Nevertheless, as with other activities I recommend that ALL WP3 partners stick to the first until the deadline 25.4. complete the tests. Only partners going to extension period could choose to do it later (no one has until now asked for it), but I recommend to get it done now - only short task and we can stay together to complete it until end of April.

For the GE tests, please follow instructions from Stefano below until 25.4 (we received it earlier, no changes):

1.       Contact the GE owner of the GE you have to test and align with him how to test it.

2.       Perform the test and fill out for each test an instance of the attached WORD document from Stefano and send it to...mmmh not mentioned what to do with it.....for example, send them to me for now...

3.       Document your activity completion in the given GOOGLE DOC document or send directly to Stefano (I do not have a google doc account and cannot do it for you)

Best
Markus


From: fiware-wpl-bounces at lists.fi-ware.org [mailto:fiware-wpl-bounces at lists.fi-ware.org] On Behalf Of stefano de panfilis
Sent: Dienstag, 8. April 2014 20:32
To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu
Subject: [Fiware-wpl] URGENT: GEis installation and test

dear all,

as discussed yesterday during our call and refined this morning in the wp10 call, here is the procedure to install and test the geis as requested in the scope of recommendation 18 of the review report 6 excerpt of which is "Obviously, hardly any of the documentation can claim completeness in the remaining time, but should at least cover all known grounds. To this end, extensive and directed installation and usage tests should be performed - not only through the Use Case projects, but also within the consortium. For example, partners not involved in the development of a specific Generic Enabler can verify it through installation and testing. The according results and findings should be incorporated in the forthcoming Release 3 and the validation reporting of deliverable D10.5.3."

the wpl migth already have received at this time an invitation from me to access a googledoc (here again the link for your convenience: https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdDBPb2gwYm11aUVQZzBPU3ZZZHowREE&usp=docslist_api#gid=0)
this doc contains all the geis implemented at the moment or in the very near future.

1. each wpl must, within this friday (11 april 2014), fill, in agreement with their wp participants, the name of the organisation responsible for installing a testing a specific gei. in addition the wpl should declare which geis will be tested. the overal rules are:
1.1 no geis of wp4 for what concerns fi-lab installation and test
1.2 only the geis of wp7 which do not require special network environment
1.3 no geis for which do not exist an oss version

2. within 25 april 2014 all the installations and tests must be completed either by the organisations leaving the project at m36, and by those organisation if a test assigned to them involve a gei owned by an organisation leaving the project at m36.

3. all the remaining installations and tests must be fulfilled by 30 june 2014.

the installation and tests must be documented using the form described in the attached document.

please note that, as you can easily guess from point 1 above, there are two different kind of installations to be tested:
1. manual deplyoment, which involves all oss released geis
2. recipes supported deployment in the fi-ware testbed. this case the person making the test must create a vm, which should be removed immediately after the installation and test is completed (due to the obvious resource cosumption)

it would be great if the persons who will make the installation and tests are completely outside the fi-ware environment.

this procedure refines and superseeds what sent by thorsten, thank you for triggering the process, on last wednesday.

for any clarification you migth need, please do not hesitate to contact me.

ciao,
stefano

--
Stefano De Panfilis
Chief Innovation Officer
Engineering Ingegneria Informatica S.p.A.
via Riccardo Morandi 32
00148 Roma
Italy

tel (direct): +39-068307-4295
tel (secr.): +39-068307-4513
fax: +39-068307-4200
cell: +39-335-7542-567
skype: depa01

-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 238880 bytes
Desc: not available
URL: <https://lists.fiware.org/private/old-fiware-apps/attachments/20140415/f5f7d22c/attachment.bin>