[Fiware-lab-recovery-tf] Status of infograph for the FIWARE Lab nodes

stefano de panfilis stefano.depanfilis at eng.it
Fri May 22 18:39:31 CEST 2015


dear federico and juanjo,


i also prefer option 3, but avoiding to be too punishing/negative, the
sentence should be something like:

"last updated at hh:mm:ss on dd/mm"

ciao,
stefano


2015-05-22 16:24 GMT+02:00 Federico Michele Facca <
federico.facca at create-net.org>:

>
>
> > On 22/mag/2015, at 16:17, Juanjo Hierro <juanjose.hierro at telefonica.com>
> wrote:
> >
> >
> >   Did you announce the availability of the infographic recently on
> Basecamp?   Just to be on sync.
>
>
> not really, i can do in the weekend, unless you prefer to do it!
>
> >
> >   To answer your question: I believe that when a node doesn't provide
> data, at least the node should be listed with either:
> >       • showing a message ("unable to gather data"); or
> >       • showing the last gathered data (this would require marking the
> message with some special color or note)
> >       • showing a message ("unable to gather data (latest gathered data
> from <date>/<time> here)", 'here' being a link that would retrive latest
> gathered data) and then explain a the very beginning of the page that
> sometimes the nodes may not be providing data in which case the latest
> gathered data is made available but cannot be taken as accurate)
> >
> >   I would personally go for option 3.   I would go even for a phased
> development.   First supporting 1 and then with time and resources, provide
> 3.
>
>
> we should be able to achieve 3 quite quickly, but let me check
>
> >   Best regards,
> > -- Juanjo
> >
> >
> > On 20/05/15 13:37, Federico Michele Facca wrote:
> >> Hi Juanjo,
> >>
> >> a couple of input:
> >> 1) infographic is already public and it was also advertised to users
> and ec;
> >> 2) data are almost real time (5 min delay) and depends on what nodes
> provides to the monitoring layer;
> >> 3) when - for any reasons - data collector service on the node stops,
> there is a timeout of 2 hours, after that data are not showed. this
> behaviour can be changed, but we set the timeout because the overall point
> is to have a real and actual data;
> >>
> >> we ask nodes to daily check that everything is ok. but of course we do
> not have access to nodes, so we cannot restart data collector service on
> their behalf (and this is part of the karma status check).
> >>
> >> please advise what is your preferred way to handle the thing, e.g.:
> >> - live with the fact that nodes may not provide data;
> >> - enabled indefinite time caching of data when a node is not providing
> them;
> >>
> >> thanks,
> >> federico
> >>
> >> On Wed, May 20, 2015 at 1:22 PM, Juanjo Hierro <
> juanjose.hierro at telefonica.com> wrote:
> >> Dear Federico,
> >>
> >>   Any news?
> >>
> >>   I guess we cannot show this yet because there is info missing (as an
> example, Waterford has disappeared ...)
> >>
> >>   Please confirm what the status is ...
> >>
> >>   Cheers,
> >>
> >> -- Juanjo
> >>
> >> On 19/05/15 18:28, Juanjo Hierro wrote:
> >>> Dear Federico,
> >>>
> >>>   I understand you have addressed this during the daily FIWARE Lab
> Recovery Task Force follow-up confcall, but I wanted to confirm that the
> Infographic tool is now ready to be made avaliable to FIWARE Lab users:
> >>> http://infographic.lab.fiware.org/
> >>>
> >>>   If you agree, I would like to announce its availability.   Of
> course, users should be aware of what nodes are actually working.   For
> that, the fi-health dashboard tool would be available.
> >>>
> >>>   BTW, I remember that we wanted to be able to show the number of
> Basic, Trial and Community users ...   When do you believe that
> functionality would be available ?   I would suggest we add the request to
> have this functionality implemented as an action point.
> >>>
> >>>   Cheers,
> >>>
> >>> -- Juanjo
> >>>
> >>> ______________________________________________________
> >>>
> >>> Coordinator and Chief Architect, FIWARE platform
> >>> CTO Industrial IoT, Telefónica
> >>>
> >>> email:
> >>> juanjose.hierro at telefonica.com
> >>>
> >>> twitter: @JuanjoHierro
> >>>
> >>> You can follow FIWARE at:
> >>>   website:
> >>> http://www.fiware.org
> >>>
> >>>   twitter:  @FIWARE
> >>>   facebook:
> >>> http://www.facebook.com/pages/FI-WARE/251366491587242
> >>>
> >>>   linkedIn:
> >>> http://www.linkedin.com/groups/FIWARE-4239932
> >>
> >>
> >> --
> >>
> >> ______________________________________________________
> >>
> >> Coordinator and Chief Architect, FIWARE platform
> >> CTO Industrial IoT, Telefónica
> >>
> >> email:
> >> juanjose.hierro at telefonica.com
> >>
> >> twitter: @JuanjoHierro
> >>
> >> You can follow FIWARE at:
> >>   website:
> >> http://www.fiware.org
> >>
> >>   twitter:  @FIWARE
> >>   facebook:
> >> http://www.facebook.com/pages/FI-WARE/251366491587242
> >>
> >>   linkedIn:
> >> http://www.linkedin.com/groups/FIWARE-4239932
> >>
> >>
> >> Este mensaje y sus adjuntos se dirigen exclusivamente a su
> destinatario, puede contener información privilegiada o confidencial y es
> para uso exclusivo de la persona o entidad de destino. Si no es usted. el
> destinatario indicado, queda notificado de que la lectura, utilización,
> divulgación y/o copia sin autorización puede estar prohibida en virtud de
> la legislación vigente. Si ha recibido este mensaje por error, le rogamos
> que nos lo comunique inmediatamente por esta misma vía y proceda a su
> destrucción.
> >>
> >> The information contained in this transmission is privileged and
> confidential information intended only for the use of the individual or
> entity named above. If the reader of this message is not the intended
> recipient, you are hereby notified that any dissemination, distribution or
> copying of this communication is strictly prohibited. If you have received
> this transmission in error, do not read it. Please immediately reply to the
> sender that you have received this communication in error and then delete
> it.
> >>
> >> Esta mensagem e seus anexos se dirigem exclusivamente ao seu
> destinatário, pode conter informação privilegiada ou confidencial e é para
> uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o
> destinatário indicado, fica notificado de que a leitura, utilização,
> divulgação e/ou cópia sem autorização pode estar proibida em virtude da
> legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos
> o comunique imediatamente por esta mesma via e proceda a sua destruição
> >>
> >>
> >>
> >> --
> >> --
> >> Future Internet is closer than you think!
> >> http://www.fiware.org
> >>
> >> Official Mirantis partner for OpenStack Training
> >> https://www.create-net.org/community/openstack-training
> >>
> >> --
> >> Dr. Federico M. Facca
> >>
> >> CREATE-NET
> >> Via alla Cascata 56/D
> >> 38123 Povo Trento (Italy)
> >>
> >> P  +39 0461 312471
> >> M +39 334 6049758
> >> E  federico.facca at create-net.org
> >> T @chicco785
> >> W  www.create-net.org
> >
> > --
> >
> > ______________________________________________________
> >
> > Coordinator and Chief Architect, FIWARE platform
> > CTO Industrial IoT, Telefónica
> >
> > email:
> > juanjose.hierro at telefonica.com
> >
> > twitter: @JuanjoHierro
> >
> > You can follow FIWARE at:
> >   website:
> > http://www.fiware.org
> >
> >   twitter:  @FIWARE
> >   facebook:
> > http://www.facebook.com/pages/FI-WARE/251366491587242
> >
> >   linkedIn:
> > http://www.linkedin.com/groups/FIWARE-4239932
> >
> >
> > Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario,
> puede contener información privilegiada o confidencial y es para uso
> exclusivo de la persona o entidad de destino. Si no es usted. el
> destinatario indicado, queda notificado de que la lectura, utilización,
> divulgación y/o copia sin autorización puede estar prohibida en virtud de
> la legislación vigente. Si ha recibido este mensaje por error, le rogamos
> que nos lo comunique inmediatamente por esta misma vía y proceda a su
> destrucción.
> >
> > The information contained in this transmission is privileged and
> confidential information intended only for the use of the individual or
> entity named above. If the reader of this message is not the intended
> recipient, you are hereby notified that any dissemination, distribution or
> copying of this communication is strictly prohibited. If you have received
> this transmission in error, do not read it. Please immediately reply to the
> sender that you have received this communication in error and then delete
> it.
> >
> > Esta mensagem e seus anexos se dirigem exclusivamente ao seu
> destinatário, pode conter informação privilegiada ou confidencial e é para
> uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o
> destinatário indicado, fica notificado de que a leitura, utilização,
> divulgação e/ou cópia sem autorização pode estar proibida em virtude da
> legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos
> o comunique imediatamente por esta mesma via e proceda a sua destruição
>
>
> --
> Future Internet is closer than you think!
> http://www.fiware.org
>
> Official Mirantis partner for OpenStack Training
> https://www.create-net.org/community/openstack-training
>
> --
> Dr. Federico M. Facca
>
> CREATE-NET
> Via alla Cascata 56/D
> 38123 Povo Trento (Italy)
>
> P +39 0461 312471
> M +39 334 6049758
> E  federico.facca at create-net.org
> T @chicco785
> W  www.create-net.org
>
> _______________________________________________
> Fiware-lab-recovery-tf mailing list
> Fiware-lab-recovery-tf at lists.fiware.org
> https://lists.fiware.org/listinfo/fiware-lab-recovery-tf
>



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

tel (direct): +39-06-8759-4253
tel (secr.): +39-068307-4513
fax: +39-068307-4200
cell: +39-335-7542-567
skype: depa01
twitter: @depa01
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-lab-recovery-tf/attachments/20150522/8d4cb3a6/attachment.html>


More information about the Fiware-lab-recovery-tf mailing list

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