[Fiware-lab-recovery-tf] Meeting for discussing new IdM federation approach

Pietropaolo Alfonso Alfonso.Pietropaolo at eng.it
Wed May 27 12:32:01 CEST 2015


Hi Joaquín,
I don't know why, but no one is connected either by Powwownow or by the chat you mentioned below.

Alfonso

On Wed, 2015-05-27 at 11:45 +0200, Joaquín Salvachúa wrote:
Hello we may use a WebRTC app.


You must use chrome and accept the access to the microphone .


the url is :


http://chotis2.dit.upm.es/room?id=5565913d918182e666001778




Best Regards


Joaquín




El 25/5/2015, a las 9:58, Juanjo Hierro <juanjose.hierro at telefonica.com<mailto:juanjose.hierro at telefonica.com>> escribió:

Hi Alfonso,

  Apologies.

  We have moved this meeting to Wednesday 11:30 ...

  I forgot to send it to the FIWARE Lab Recovery TF mailing list ... Sorry about that.

  Cheers,

-- Juanjo

On 25/05/15 09:36, Pietropaolo Alfonso wrote:

Is not 940541 the usual one? No one is connected at both pin.

Alfonso

On Fri, 2015-05-22 at 13:11 +0200, Juanjo Hierro wrote:

  Yes.

On 22/05/15 12:27, stefano de panfilis wrote:

usual 050662 pin?

2015-05-22 11:27 GMT+02:00 Juanjo Hierro <juanjose.hierro at telefonica.com<mailto:juanjose.hierro at telefonica.com>>:
Dear all,

  Let's go for having a first discussion meeting this coming Monday from 09:30am to 11:00am CET.   I have already announced this as part of the current plan of FIWARE Architects meetings schedule.

  I believe that presence of UPM is mandatory.   Presence of the Cloud team in TID as well as Create-NET is also needed.   Presence of Alfonso I believe is quite relevant because this will be something that will end meaning the deployment of new releases of the IdM GE or complementary components.   It would have quite a relevant impact on the operations of the federation of FIWARE Lab nodes.

  I know that Federico and Fernando could not make it but it is important to move forward.   There will be sure additional meetings which can be agreed adhoc.

  I would kindly ask UPM to prepare some slides summarizing the discussion so far that we can share as basis for the discussion at the meeting.   Please confirm you will prepare that.

  Cheers,

-- Juanjo


-------- Forwarded Message --------
Subject:        Next FIWARE Architects meetings
Date:   Fri, 22 May 2015 11:20:21 +0200
From:   Juanjo Hierro <juanjose.hierro at telefonica.com><mailto:juanjose.hierro at telefonica.com>
To:     fiware-chapter-architects at lists.fi-ware.org<mailto:fiware-chapter-architects at lists.fi-ware.org> <fiware-chapter-architects at lists.fi-ware.org><mailto:fiware-chapter-architects at lists.fi-ware.org>, fiware-chapter-leaders at lists.fi-ware.org<mailto:fiware-chapter-leaders at lists.fi-ware.org> <fiware-chapter-leaders at lists.fi-ware.org><mailto:fiware-chapter-leaders at lists.fi-ware.org>
CC:     Juanjo Hierro <juanjose.hierro at telefonica.com><mailto:juanjose.hierro at telefonica.com>


Dear FIWARE architects,

  This is to summarize the topics that will be covered in our next FIWARE Architecs calls (monday mornings, from 09:30am to 11:00am CET):

  *   Monday May 25th: revision of architecture to support federated user account management on the FIWARE Lab
  *   Monday June 1st: support of dockers in FIWARE Architecture
  *   Monday June 8th: 2nd meeting about POIs

  Feel free to invite anyone you believe can add value to the discussions.   FIWARE chapter leaders are of course welcome to join.


  Best regards,




-- Juanjo

______________________________________________________

Coordinator and Chief Architect, FIWARE platform
CTO Industrial IoT, Telefónica

email: juanjose.hierro at telefonica.com<mailto:juanjose.hierro at telefonica.com>
twitter: @JuanjoHierro

You can follow FIWARE at:
  website:  http://www.fiware.org<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


_______________________________________________
Fiware-lab-recovery-tf mailing list
Fiware-lab-recovery-tf at lists.fiware.org<mailto:Fiware-lab-recovery-tf at lists.fiware.org>
https://lists.fiware.org/listinfo/fiware-lab-recovery-tf







_______________________________________________
Fiware-lab-recovery-tf mailing list
Fiware-lab-recovery-tf at lists.fiware.org<mailto:Fiware-lab-recovery-tf at lists.fiware.org>
https://lists.fiware.org/listinfo/fiware-lab-recovery-tf





--

______________________________________________________

Coordinator and Chief Architect, FIWARE platform
CTO Industrial IoT, Telefónica

email: juanjose.hierro at telefonica.com<mailto:juanjose.hierro at telefonica.com>
twitter: @JuanjoHierro

You can follow FIWARE at:
  website:  http://www.fiware.org<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

_______________________________________________
Fiware-lab-recovery-tf mailing list
Fiware-lab-recovery-tf at lists.fiware.org<mailto:Fiware-lab-recovery-tf at lists.fiware.org>
https://lists.fiware.org/listinfo/fiware-lab-recovery-tf




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-lab-recovery-tf/attachments/20150527/96a29b19/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