Dear Carlos,

We could not hear back from you regarding this. Could you kindly provide some support or direct us to the right person?

Thanks,

ilknur

From: Chulani, Ilknur
Sent: Tuesday, August 18, 2015 2:05 PM
To: 'CARLOS RALLI UCENDO'
Cc: Romero, Javier
Subject: RE: [Fractals] OLIfly - IDAS question

Dear Carlos,

I am the coach for the Fractals accelerator, could you kindly help with the question from one of their SMEs below?

I assigned the related Coaching Help Desk ticket to you:
https://jira.fiware.org/browse/HELC-950

Could you kindly reply in the ticket or as a reply to this email?

Thanks,

ilknur

From: fiware-fractals-coaching-atos-bounces@lists.atosresearch.eu<fiware-fractals-coaching-atos-bounces@lists.atosresearch.eu> fiware-fractals-coaching-atos-bounces@lists.atosresearch.eu On Behalf Of Romero, Javier
Sent: Tuesday, August 18, 2015 12:21 PM
To: FRACTALS coach (fiware-fractals-coaching@lists.fi-ware.org<fiware-fractals-coaching@lists.fi-ware.org>)
Subject: [Fiware-fractals-coaching-atos] [Fiware-fractals-coaching] [Fractals] OLIfly - IDAS question

Dear coachers

OLIfly Project has submitted the following questions related to IDAS GE.

I'm looking at adding IDAS GE between RPI-s and Orion context broker for device management. On FIWARE catalog site it is written that:
"For next releases, an IoT Agent Manager component has been identified. It will address
monitoring and management of IoT Agent instances."
So what i need is an GE which will tell me if my cameras, RPI-s etc. are working properly, if they are connected, if they have power issues etc.
I need to decide whether to use IDAS and implement my own monitoring while waiting for upgrade, or just use something else...
My question is when will this functionality be available in IDAS? Is there some another GE with monitoring and management capabilities?

Can we have some help with this questions, please?

Thanks in advance.

Best Regards
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Este mensaje y los ficheros adjuntos pueden contener información confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente y pueden estar protegidos por secreto profesional.
Si usted recibe este correo electrónico por error, gracias por informar inmediatamente al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningún compromiso para el grupo Atos, salvo ratificación escrita por ambas partes.
Aunque se esfuerza al máximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no será responsable de cualesquiera daños que puedan resultar de una transmisión de virus.
Bu mesaj ve ekleri gönderilen kişiye özeldir ve gizli bilgiler içerebilir. Eğer mesajın gönderilmek istendiği kişi değilseniz lütfen kopyalamayınız, başkalarına göndermeyiniz ve göndericiyi bilgilendiriniz. Internet üzerinden gönderilen mesajların güvenli ve hatasız olduğunun garantisi olmadığından Atos grubu mesajın içeriğinden sorumlu tutulamaz. Göndericinin bilgisayarı anti-virüs sistemleri tarafından taranmaktadır, ancak yine de mesajın virüs içermediği garanti edilemez ve gönderici, meydana gelebilecek zararlardan sorumlu tutulamaz.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Hi,

The IoT Manager will be in charge of monitoring and managing the different instances of IoT Agents but will not implement Device Management per-se.

For Device Management we are exploring alternatives based on OMA LWM2M mainly to be used with that specific IoT Agent.

Therefore, today, for those tasks you have two alternatives: build your own device management or push from the RPIs Device Management attributes to the device entities at the ContextBroker.

Thanks for using IDAS!

Dear Javier,

Forwarding this reply from Carlos, as it seems the ticketing system did not forward the answer to the mailing list.

Best regards,

ilknur

The issue has been emailed:

• Time sent: 28/Aug/15 11:59 AM
• To: javier.romero@atos.net
• with subject: *(HELC-950) [Fiware-fractals-coaching] [Fractals] OLIfly - IDAS question *
  

Hi,

( I am re-posting my answer as I think it did not reach the correct mailbox)

The IoT Manager will be in charge of monitoring and managing the different instances of IoT Agents but will not implement Device Management per-se.

For Device Management we are exploring alternatives based on OMA LWM2M mainly to be used with that specific IoT Agent.

Therefore, today, for those tasks you have two alternatives: build your own device management or push from the RPIs Device Management attributes to the device entities at the ContextBroker.

Thanks for using IDAS!