[Fiware-cloud] RV: [Fiware-testbed] Fwd: URGENT: GEis installation and test

Alex Glikson GLIKSON at il.ibm.com
Wed Apr 16 08:17:48 CEST 2014


I don't think this applies to Cloud. In addition to internal validation 
already covered in WP10, additional validation is done by XiFi, in close 
collaboration with us -- no need to duplicate. This is part of the 
packaging effort that they pursue, as discussed in another thread.

By the way, as you probably remember, we don't have hardware to apply such 
testing anyway.

Regards,
Alex


====================================================================================================
Alex Glikson
Manager, Cloud Operating System Technologies, IBM Haifa Research Lab
http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | 
http://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml 
Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: 
+972-54-6466667 | Fax: +972-4-8296112




From:   HENAR MUÑOZ FRUTOS <henar at tid.es>
To:     Alex Glikson/Haifa/IBM at IBMIL, 
Cc:     "fiware-cloud at lists.fi-ware.org" <fiware-cloud at lists.fi-ware.org>
Date:   16/04/2014 09:09 AM
Subject:        RV: [Fiware-testbed] Fwd: URGENT: GEis installation and 
test



Hi Alex
 
Stefano commented to me about this google docs file, that we need to fill 
in, regarding installation and testing.
Regard,s
Henar
 
De: fiware-testbed-bounces at lists.fi-ware.org [
mailto:fiware-testbed-bounces at lists.fi-ware.org] En nombre de stefano de 
panfilis
Enviado el: martes, 15 de abril de 2014 10:12
Para: fiware-testbed at lists.fi-ware.eu
Asunto: [Fiware-testbed] Fwd: URGENT: GEis installation and test
 
ciao,
stefano
 
---------- Forwarded message ----------
From: stefano de panfilis <stefano.depanfilis at eng.it>
Date: 2014-04-08 20:32 GMT+02:00
Subject: URGENT: GEis installation and test
To: "fiware-wpl at lists.fi-ware.eu" <fiware-wpl at lists.fi-ware.eu>, "
fiware-wpa at lists.fi-ware.eu" <fiware-wpa at lists.fi-ware.eu>

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
 


 
-- 
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
 


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[attachment 
"I10.2_Installation_and_Test_Template_v2.docx" deleted by Alex 
Glikson/Haifa/IBM] [attachment "ATT00001.txt" deleted by Alex 
Glikson/Haifa/IBM] 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-cloud/attachments/20140416/de65887e/attachment.html>


More information about the Old-Fiware-cloud mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy