[Fiware-iot] R: R: Agreement regarding Architecture Deliverable and Clarifications for the GE's logging task

Guerra Sabrina sabrina.guerra at telecomitalia.it
Fri Mar 8 11:09:02 CET 2013


Hi Carlos,
regarding the architecture revision I accessed to the following link to update the Gateway Protocol Adapter GE description
https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Internet_of_Things_(IoT)_Services_Enablement_Architecture
In particular I made some editing on this page updating the description to the current situation
https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.IoT.Gateway.ProtocolAdapter
About ETSI M2M description I didn't made any change because it is up to date (maybe Fraunhofer will make some changes when they will be involved)
https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/ETSI_M2M_Architecture_Overview

Please let me know if it is ok.
Best regards,
Sabrina





Da: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di Guerra Sabrina
Inviato: venerdì 8 marzo 2013 09:31
A: CARLOS RALLI UCENDO
Cc: fiware-iot at lists.fi-ware.eu
Oggetto: [Fiware-iot] R: Agreement regarding Architecture Deliverable and Clarifications for the GE's logging task

Hi Carlos,
I have added the file Quo vadis IoT (WP5)_GEs_Telecom Italia .pptx in the IoT FI-WARE DocManager in order to use it as presentation in the F2F meeting.
Best regards,
Sabrina

Da: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di CARLOS RALLI UCENDO
Inviato: mercoledì 6 marzo 2013 19:03
A: fiware-iot at lists.fi-ware.eu
Oggetto: [Fiware-iot] Agreement regarding Architecture Deliverable and Clarifications for the GE's logging task

Dear Colleagues,

Just to provide feedback on those two open items as identified this morning:

1) How to proceed regarding the Architecture Deliverable:

After discussing this with Miguel, Juanjo and Thierry we have established the following procedure:

1.1) We will generate a snapshot of all IoT architecture GEs next Friday March 8th that will be provided on Monday to I2ND chapter in charge of our peer-review.
1.2) Some GEs will be totally ready for such a review (although they might be updated as a result of the meeting,  that's not an issue).
 We understand GEs in this case are: Conf.Man (TID), IoT Broker (NEC) (although we know connections to UoS GE and BE Dev Man aren't clear/fixed), SOL/CEP (ATOS).

1.3) On the other hand, some GEs will not be ready for this peer review and will suffer significant updates during our meeting next week.
These GEs are: BE Dev Man and GW Dev Man.
For these ones, we will communicate to I2ND peer-reviewers that they shouldn't be considered . However, right after the meeting, on Wed 13th we will be providing a new document with updated versions.
I2ND will provide the outputs for them on the 16th (instead of the 13th) but we will have to incorporate changes anyway before 22nd (as with all others).

Somehow, we are establishing two branches of GEs, although we are always generating documents with all (but indicating I2ND what should be reviewed within).

2) GE's logging task (e-mail from Davide Dallecarbonare - Engineering).

I managed to get more information. Looks like IBM and Engineering are at the specification phase of a Logs/Traces analysis tool.
Therefore, there is no agreement on the way to provide logs or the format of them. The only thing to do at this point, by each GE owner, is the following:

 *   Send an e-mail back to Davide (davide.dallecarbonare at eng.it<mailto:davide.dallecarbonare at eng.it>) and  Marcel (marcel at il.ibm.com<mailto:marcel at il.ibm.com>) providing where your GE stores logs (specific files, system log files, etc) and which is the format of them (i.e. Send them an example = text of some logs or a file with logs).
->I think it is enough if you send this info by Monday next week (as Item 1 may take most of your time until friday).
-> In the case your GE has no specific log files and they log nothing too in the system's files, you MUST send also send this e-mail stating it.

Original mail from Davide:
********
Dear partners,
I'd like to remind you one point we've on the minutes:

"Monitoring of log/trace files"

https://docs.google.com/document/d/1ml3Z1DidK1fW-vIgaUy9t06m0-VGdAOhmcQD8c3qBlk/edit#heading=h.kqxdoinbwzxy

@Juanjo, can you kindly send a feedback on what's your take on the
purpose and technology points reported on the minutes?

@WPAs, can you kindly forward to your GEi providers the request to
send an example of log/trace files produced by their GE implementations?
Please send the logs to Marcel Zalmanovici <MARCEL at il.ibm.com<mailto:MARCEL at il.ibm.com>>
and to the WPA mailing list.
I'm expecting to receive one example per GEi that will be available
for release 2.

Kind Regards,
Davide
********

Thanks,
Best regards,
--

------------------------------------------------------------------------------------------------------------------------

Carlos Ralli Ucendo (ralli at tid.es<mailto:ralli at tid.es>)

Cell: +34696923588

Twitter: @carlosralli

IPv6 Blog: http://the-internet6.blogspot.com.es

Product Development & Innovation (Telefónica Digital)

Telefónica I+D SAU

Madrid, Spain

------------------------------------------------------------------------------------------------------------------------

Follow FI-WARE project (Future Internet Services Core Platform):

Website:  http://www.fi-ware.eu

Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242

Twitter: @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.
[cid:image001.gif at 01CE1BED.56FF63E0]Rispetta l'ambiente. Non stampare questa mail se non è necessario.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20130308/23d1addf/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 677 bytes
Desc: image001.gif
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20130308/23d1addf/attachment.gif>


More information about the Old-Fiware-iot mailing list

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