From juanjose.hierro at telefonica.com Mon Apr 13 19:17:48 2015 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Mon, 13 Apr 2015 19:17:48 +0200 Subject: [Fiware-lab-recovery-tf] Test - please discard Message-ID: <552BFA3C.9090904@telefonica.com> -- ______________________________________________________ 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 From fernando.lopezaguilar at telefonica.com Mon Apr 13 19:18:07 2015 From: fernando.lopezaguilar at telefonica.com (FERNANDO LOPEZ AGUILAR) Date: Mon, 13 Apr 2015 17:18:07 +0000 Subject: [Fiware-lab-recovery-tf] test Message-ID: test ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From juanjose.hierro at telefonica.com Mon Apr 13 20:01:50 2015 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Mon, 13 Apr 2015 20:01:50 +0200 Subject: [Fiware-lab-recovery-tf] Message ready to be sent to FIWARE Lab Users Message-ID: <552C048E.9070905@telefonica.com> An HTML attachment was scrubbed... URL: From federico.facca at create-net.org Mon Apr 13 20:27:34 2015 From: federico.facca at create-net.org (Federico Michele Facca) Date: Mon, 13 Apr 2015 20:27:34 +0200 Subject: [Fiware-lab-recovery-tf] Message ready to be sent to FIWARE Lab Users In-Reply-To: <552C048E.9070905@telefonica.com> References: <552C048E.9070905@telefonica.com> Message-ID: done On Mon, Apr 13, 2015 at 8:01 PM, Juanjo Hierro < juanjose.hierro at telefonica.com> wrote: > Dear all, > > I have just reviewed the message that can be sent to the FIWARE Lab > users. It is available here: > > > https://docs.google.com/document/d/1FreMU2soDr6yx61z7-c7iftM9vmjj0sKbxYD9zi2nEs/edit?usp=sharing > > ?lvaro: Please proceed sending the message to user accounts through the > corresponding mailing list, also made it available as a screen that is pop > up whenever a user logs in. > > Federico: Please proceed sending the message on Basecamp > > I will post a message on twitter as well as to the AB and SB mailing > lists. > > Best regards, > > -- 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 > > > ------------------------------ > > 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 > https://lists.fiware.org/listinfo/fiware-lab-recovery-tf > > -- -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From fernando.lopezaguilar at telefonica.com Tue Apr 14 16:30:16 2015 From: fernando.lopezaguilar at telefonica.com (FERNANDO LOPEZ AGUILAR) Date: Tue, 14 Apr 2015 14:30:16 +0000 Subject: [Fiware-lab-recovery-tf] Text to show when reached the Trial users limit Message-ID: Dear all, This is the text that I should show in this case: "Trial users limit reached, FIWARE Lab is unable to create new Trial users as it has exceeded it's resource limit. Please check back in 2 weeks for the next open window to create new Trial users. If you have any questions, please contact our Technical Support Team in ". Comments. BR, Fernando.- ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From federico.facca at create-net.org Tue Apr 14 17:00:53 2015 From: federico.facca at create-net.org (Federico Michele Facca) Date: Tue, 14 Apr 2015 17:00:53 +0200 Subject: [Fiware-lab-recovery-tf] Text to show when reached the Trial users limit In-Reply-To: References: Message-ID: I would end with: If you are applying for an account on behalf of an Accelerator Programme or if you have any questions, please contact our Technical Support Team in < fiware-lab-help at list.fi-ware.org>. cheers, federico On Tue, Apr 14, 2015 at 4:30 PM, FERNANDO LOPEZ AGUILAR < fernando.lopezaguilar at telefonica.com> wrote: > Dear all, > > This is the text that I should show in this case: > > "Trial users limit reached, FIWARE Lab is unable to create new Trial > users as it has exceeded it?s resource limit. Please check back in 2 weeks > for the next open window to create new Trial users. If you have any > questions, please contact our Technical Support Team in < > fiware-lab-help at list.fi-ware.org>?. > > Comments. > > BR, Fernando.- > > > ------------------------------ > > 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 > https://lists.fiware.org/listinfo/fiware-lab-recovery-tf > > -- -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From juanjose.hierro at telefonica.com Tue Apr 14 20:32:05 2015 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Tue, 14 Apr 2015 20:32:05 +0200 Subject: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab Message-ID: <552D5D25.1060506@telefonica.com> An HTML attachment was scrubbed... URL: From juanjose.hierro at telefonica.com Wed Apr 15 05:56:33 2015 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Wed, 15 Apr 2015 05:56:33 +0200 Subject: [Fiware-lab-recovery-tf] Fwd: [Fiware-coaches] FIWARE lab access In-Reply-To: References: Message-ID: <552DE171.4050907@telefonica.com> An HTML attachment was scrubbed... URL: -------------- next part -------------- _______________________________________________ Fiware-coaches mailing list Fiware-coaches at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-coaches From juanjose.hierro at telefonica.com Wed Apr 15 08:08:10 2015 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Wed, 15 Apr 2015 08:08:10 +0200 Subject: [Fiware-lab-recovery-tf] Daily checkpoints Message-ID: <552E004A.7020509@telefonica.com> An HTML attachment was scrubbed... URL: From thierry.nagellen at orange.com Wed Apr 15 08:53:09 2015 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Wed, 15 Apr 2015 06:53:09 +0000 Subject: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab In-Reply-To: <552D5D25.1060506@telefonica.com> References: <552D5D25.1060506@telefonica.com> Message-ID: <6984_1429080790_552E0AD6_6984_1370_1_976A65C5A08ADF49B9A8523F7F81925C2AE652@PEXCVZYM13.corporate.adroot.infra.ftgroup> Hi Juanjo Thanks to add me in the list. We miss a critical point: Dashboard to monitor resouces availability. This dashboard has to include per node the following elements, at least in a first round: Number of Core Number of VM in use/available Public Ip Addresses: allocated/available Helpdesk tickets At least to manage the impact of new T&C and to have some facts in case of request from our ?clients? and EC BR Thierry De : fiware-lab-recovery-tf-bounces at lists.fiware.org [mailto:fiware-lab-recovery-tf-bounces at lists.fiware.org] De la part de Juanjo Hierro Envoy? : mardi 14 avril 2015 20:32 ? : fiware-lab-recovery-tf at lists.fiware.org Objet : [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab Dear all, I have added Thierry Nagellen from Orange to this mailing list because despite he is not involved in the Task Force "per se", we are synchronized also with Orange overall with respect to messages to pass to the EC and rest of FI-PPP projects. If you believe someone else has to be in this list, please let me know. It has come out that deployment of the new IdM/Keystone is not feasible as planned. Therefore, we have to define a new plan. This morning, the TID team (including me) have had the opportunity to meet with the UPM team to understand the issue and we have come with an alternative plan for the recovery of the FIWARE Lab than the one we defined yesterday which sounds pretty reasonable and may help us to soon improve the situation. Let me summarize the plan in this email so that we are all on the same page. If you find some weakness/issue, please raise it. Otherwise, let's stick to it. Fortunately, the first steps remain the same and they have already been done, so we are on the right track. An important matter: I plan to send this plan to the EC tomorrow morning at 11:00. If you have comments, you should provide them before that deadline. I will also communicate this plan to FIWARE Accelerator projects on Basecamp as well as to Use Case projects through the FI-PPP mailing lists. Federico or Engineering should communicate this plan to organizations operating the FIWARE Lab nodes also at that time. A very sensible matter: when you review step 6 you will see that we cover the case in which some FIWARE Lab nodes may be put in quarantine. I would like to propose to the EC that those FIWARE lab nodes which are put into quarantine will be labeled as non-performance so they won't get the grant they were assigned in the XiFi Open Call, at least for the remaining of the XiFi project (until September). Maybe these funds can be given away to other partners or launch another Open Call. I would like to know your views on this. Step 1: reminder about new user account management policies enforcement. A first email aking existing FIWARE Lab users to accept the new user account management policies, also covered in the new FIWARE Lab use terms and conditions, was sent to all FIWARE Lab users several weeks ago. A reminder has been sent yesterday and today to current users of the FIWARE Lab telling them that they have until April 15th 2015 19:00 CET. This message will be disseminated through different means: * mailed to current users of the FIWARE Lab * shown in a screen at login of users of the FIWARE Lab * posted on Basecamp so that FIWARE accelerator projects get aware and can forward the remainder to SMEs/startups under their respective programmes * mailed to the FI-PPP SB and the old FI-PPP AB members so that coordinators/architects of the FIWARE Use Case projects can forward the reminder to SMEs/startups under their respective Use Case projects Step 2: Increase of computing capacity in Spain-2 node In parallel and starting TODAY, activities to expand the capacity of the recently launched Spain-2 node will be prioritized so that we reach a capacity of aprox 500 cores in the datacenters located in both Sevilla and Malaga. We expect this expansion be completed by April 20th if not earlier. Additionally, additional capacity (close to 500 additional cores) will be activated in the Spain-2 node with servers located in a new datacenter located in Las Palmas. Conversations are ongoing with Red.es trying to accelerate this process so that this additional 500 cores get available closer to the end of next week. Step 3: New Trial users only allowed to work on Spain-2 node. Limitation of number of concurrent trial users. Changes will be implemented in the Cloud portal and the user account registration process/tool by UPM so that new Trial users will only see the Spain-2 node. In addition, Trial users will be limited to 100 Trial users. Note that the "Trial Users", until the new IdM/Keystone component is deployed, will need to be identified by considering the creation of their user account. Actually, "Trial users" will be those users who have created their account after April 16th. Most likely, the fact that Trial users will only be allowed to work on Spain will remain. The number of Trial users allowed may increase (the EC has shown its concern about keeping the number of Trial users too low) but will see. Users who try to create an account when the limit on Trial users have been reached, will receive a message indicating that the limit has been reached, inviting them to try again in two weeks (Fernando to send the wording for this message to UPM). This step should be implemented by this Wednesday April 15th. Step 4: Freeing resources on current nodes, giving users the ability to apply to become community users, asking users in Spain-1 and Prague to migrate Starting April 16th, current nodes will free resources on their nodes (virtual infrastructure and public IP addresses allocated to users who didn't accept the new user account management policies). They should complete this process before April 23rd. FIWARE Lab node providers are aware of the current situation so they should accelerate this process as much as possible, trying to complete the process the sooner the better. Situation will be assessed on April 20th and April 23rd. It is expected that the status of the FIWARE Lab will improve drastically during the week and will become stable by April 23rd. In parallel, we will encourage legacy users (those who created their account before April 16th and have accepted the new terms and conditions) to apply for becoming community users. They should be able to submit their application completing an application form that will be provided to them and will be made available on the Cloud Portal. Those legacy users whose application is accepted and who were hosted in the Spain-1 or the Prague nodes will be asked to migrate their environments to any of the other nodes (a recommendation will be given). The Spain-1 and the Prague nodes will not host community users. As a result, no users will remain in these two nodes by May 1st. Step 5: Deployment of new IdM/Keystone component and upgrading of Community Users. Migration of Spain-1 and Prague nodes to OpenStack Juno. This step will start May 1st. Then, we will deploy the new version of the IdM/Keystone component. Users whose application to become Community Users has been approved will become Community Users. Environments of those Trial users who has overpass the 2 weeks trial period will be cleaned out. From then on, the new user account management policies will be in place, with the new IdM/keystone component supporting the ability to distinguish between kind of users and the nodes each will be able to get access to. In parallel, Spain-1 and Prague nodes should start their migration to Juno. Once they migrate, they will be made available as part of the federation (maybe the physical resources allocated to the Spain-1 node will be assigned to the Spain-2 node). Step 6: Assessment of nodes in the FIWARE Lab federation. Bringing FIWARE Lab nodes into quarantine. After April 23th, performance of the several nodes in the FIWARE Lab federation will be weekly assessed. Those nodes who exhibit a bad performance (instability, low response to request for help by users) will be put into quarantine and their users (Community Users) will be asked to migrate to the Spain-2 node. 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 ________________________________ 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 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From aalonsog at dit.upm.es Wed Apr 15 10:14:30 2015 From: aalonsog at dit.upm.es (=?utf-8?Q?=C3=81lvaro_Alonso?=) Date: Wed, 15 Apr 2015 10:14:30 +0200 Subject: [Fiware-lab-recovery-tf] Text to show when reached the Trial users limit In-Reply-To: References: Message-ID: Ok so the message will be: "Trial users limit reached, FIWARE Lab is unable to create new Trial users as it has exceeded it?s resource limit. Please check back in 2 weeks for the next open window to create new Trial users. If you are applying for an account on behalf of an Accelerator Programme or if you have any questions, please contact our Technical Support Team in >" BR -- ?lvaro > El 14 Apr 2015, a las 17:00, Federico Michele Facca escribi?: > > I would end with: > > > > If you are applying for an account on behalf of an Accelerator Programme or if you have any questions, please contact our Technical Support Team in >. > > cheers, > federico > > On Tue, Apr 14, 2015 at 4:30 PM, FERNANDO LOPEZ AGUILAR > wrote: > Dear all, > > This is the text that I should show in this case: > > "Trial users limit reached, FIWARE Lab is unable to create new Trial users as it has exceeded it?s resource limit. Please check back in 2 weeks for the next open window to create new Trial users. If you have any questions, please contact our Technical Support Team in >?. > > Comments. > > BR, Fernando.- > > > > 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 > https://lists.fiware.org/listinfo/fiware-lab-recovery-tf > > > > > -- > -- > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From juanjose.hierro at telefonica.com Wed Apr 15 08:27:25 2015 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Wed, 15 Apr 2015 08:27:25 +0200 Subject: [Fiware-lab-recovery-tf] Test Message-ID: <552E04CD.4070106@telefonica.com> A ver si funciona ... -- ______________________________________________________ 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 From juanjose.hierro at telefonica.com Wed Apr 15 06:24:17 2015 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Wed, 15 Apr 2015 06:24:17 +0200 Subject: [Fiware-lab-recovery-tf] Final text to show when reached the Trial users limit In-Reply-To: References: Message-ID: <552DE7F1.1030607@telefonica.com> An HTML attachment was scrubbed... URL: From juanjose.hierro at telefonica.com Wed Apr 15 07:21:29 2015 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Wed, 15 Apr 2015 07:21:29 +0200 Subject: [Fiware-lab-recovery-tf] Clarification on how we are going to manage user accounts Message-ID: <552DF559.8080905@telefonica.com> Hi, I would like to clarify a couple of questions regarding how we are going to manage user accounts. First question: How do we pretend that users linked to SMEs and startups included in the FIWARE Accelerator Programme create their accounts on the FIWARE Lab? Should they first create an Trial user account and then apply for becoming a Community User? I understand that until May 1st, this will be the case but what afterwards? Does the new IdM come with an update on the new user account creation process so that they will be able to apply for a Community User account? If so, we have to be rather quickly in serving their request for the Community User account ... Did we decide to automate the process, how? Otherwise, Who will be in charge of serving the requests for Community Users? FIWARE coaches? I understand that it is manually (applications captured through some sort of web application form which I understand is the one associated to the link to be provided by Federico, see my previous mail on message to be sent to Trial Users when reaching the limit) and the FIWARE coaches will take care of requests. Please confirm or clarify. Second question: I understand we agreed time ago that we wanted to allow users that do not require booking Cloud/IP resources ... As an example, users that may be required for the application that I wish to run on top of the virtual infrastructure I'm deploying, but do not require to create VMs, etc (they will take advantage of existing ones). How are we going to support this? My understanding is that a Cloud tenant will be indeed linked to the organization which is implicitly created when a Trial User account is created and then these kind of users not consuming Cloud resources would be created linked to that organization. However ... Can a User create other User accounts under his organization without them going through the sign up process? If not ... how have we planned to manage the scenario in which a given organization wishes to create accounts, not necessarily being able to book cloud/IP resources? One possibility is that we allow "Basic Users" (or however we want to call them) to be created that will simply not get access to the Cloud portal ... Otherwise I'm afraid we may find issues (I cannot decide that Trial Users will be used for this because they will be deleted in 2 weeks and these are users a given SME/startup under the FIWARE Accelerator project may be requesting ...) Maybe these question had already been addressed by you, but I want to have a clear picture written black on white. 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 ________________________________ 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 From juanjose.hierro at telefonica.com Wed Apr 15 08:28:47 2015 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Wed, 15 Apr 2015 08:28:47 +0200 Subject: [Fiware-lab-recovery-tf] Test - please discard Message-ID: <552E051F.7060207@telefonica.com> -- ______________________________________________________ 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 From Alfonso.Pietropaolo at eng.it Wed Apr 15 11:02:30 2015 From: Alfonso.Pietropaolo at eng.it (Pietropaolo Alfonso) Date: Wed, 15 Apr 2015 09:02:30 +0000 Subject: [Fiware-lab-recovery-tf] Daily checkpoints In-Reply-To: <552E004A.7020509@telefonica.com> References: <552E004A.7020509@telefonica.com> Message-ID: <1429088572.3010.5.camel@Fujimint> Ok for me today at 15:30. I have also voted for the daily conf calls. Alfonso On Wed, 2015-04-15 at 08:08 +0200, Juanjo Hierro wrote: 15:30 to 16:00 -------------- next part -------------- An HTML attachment was scrubbed... URL: From juanjose.hierro at telefonica.com Wed Apr 15 14:05:59 2015 From: juanjose.hierro at telefonica.com (JUAN JOSE HIERRO SUREDA) Date: Wed, 15 Apr 2015 12:05:59 +0000 Subject: [Fiware-lab-recovery-tf] FIWARE Lab Remediation Task Force Daily meeting Message-ID: ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3150 bytes Desc: not available URL: From juanjose.hierro at telefonica.com Wed Apr 15 15:38:15 2015 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Wed, 15 Apr 2015 15:38:15 +0200 Subject: [Fiware-lab-recovery-tf] Action Plan in Google docs Message-ID: <552E69C7.1040605@telefonica.com> https://docs.google.com/document/d/1BanhzbYZONjAflT3jpmMfl5wi-xp25RckrakqklJLow/edit?usp=sharing -- ______________________________________________________ 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 From juanjose.hierro at telefonica.com Wed Apr 15 17:56:14 2015 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Wed, 15 Apr 2015 17:56:14 +0200 Subject: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab In-Reply-To: References: <552D5D25.1060506@telefonica.com> Message-ID: <552E8A1E.30808@telefonica.com> An HTML attachment was scrubbed... URL: From juanjose.hierro at telefonica.com Wed Apr 15 18:04:22 2015 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Wed, 15 Apr 2015 18:04:22 +0200 Subject: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab In-Reply-To: References: <552D5D25.1060506@telefonica.com> Message-ID: <552E8C06.1020105@telefonica.com> An HTML attachment was scrubbed... URL: From juanjose.hierro at telefonica.com Wed Apr 15 18:06:03 2015 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Wed, 15 Apr 2015 18:06:03 +0200 Subject: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab In-Reply-To: <6984_1429080790_552E0AD6_6984_1370_1_976A65C5A08ADF49B9A8523F7F81925C2AE652@PEXCVZYM13.corporate.adroot.infra.ftgroup> References: <552D5D25.1060506@telefonica.com> <6984_1429080790_552E0AD6_6984_1370_1_976A65C5A08ADF49B9A8523F7F81925C2AE652@PEXCVZYM13.corporate.adroot.infra.ftgroup> Message-ID: <552E8C6B.5080400@telefonica.com> An HTML attachment was scrubbed... URL: From aalonsog at dit.upm.es Wed Apr 15 18:15:34 2015 From: aalonsog at dit.upm.es (=?utf-8?Q?=C3=81lvaro_Alonso?=) Date: Wed, 15 Apr 2015 18:15:34 +0200 Subject: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab In-Reply-To: <552E8C06.1020105@telefonica.com> References: <552D5D25.1060506@telefonica.com> <552E8C06.1020105@telefonica.com> Message-ID: <3964F66E-FA4A-409A-AACE-F68AB0E15E22@dit.upm.es> Hi, today tests made by Henar in havana suggest that havana is not compatible with v3. Federico found a post (https://www.mirantis.com/blog/manage-openstack-projects-using-domains-havana/ ) that says it is partially compatible but we are not sure of that. My understanding was that every nodes had to be migrated to Icehouse, for that reason I was only concerned by old spain node. @Federico, do you know haw many nodes are still Grizzly? The will be migrated before May 1? Is it possible to decide that if a node is not migrated to Icehouse by May 1, it will be out of the federation until it migrates? BR -- ?lvaro > El 15 Apr 2015, a las 18:04, Juanjo Hierro escribi?: > > > > On 15/04/15 05:58, Federico Michele Facca wrote: >> Dear Juanjo, >> some comments from my side: >> >> 1) Maurizio as XIFI coordinator, needs to be in the loop. While I agree that some nodes - probably like some GEs developers btw - don't deserve ths money they have been granted for the service given, any action and decision in this direction within XIFI is beyond my role. Not sure if and how saved money could be employed. Moved to FI-CORE? >> > > I have added him. > >> 2) According to a short discussion I had with Alvaro, Migration to new IDM my affect as well other nodes still using Grizzly, this needs to be clarified asap in order to take proper actions (i.e. Accelerate migration plan). >> > > People from UPM has to clarify this URGENTLY. I was about to send an email to Basecamp sharing the plan (to show we are reacting and we have setup a Recovery Task Force but I want to know to what extend I have to modify anything in the description of the plan. > >> 3) It is very important to agree on fair, objective and not arguable metrics to define performance. As early mentioned errors from tests due to finished resources do not mean "bad performance" (if not this would be the case as well for spain), this case is a more general issue related to the tools and functions provided on top of nodes, for which we cannot account them. >> > > Agreed. That's why, a) we will only be able to measure performance once nodes get cleaned b) we need to make sure that the tests run well (it is my impression that some of them do not give an accurate photo of the status) > >> 4) There are nodes operating for "free", what should we do in such cases? I would keep possibility fir user with proper role to use them, regardeless, no financial penality can be passed over to them. >> > > We should come with a way to label the different nodes and let users take decision. Of course, there is no penalty that can be passed to them. But certainly something we can do is to put them in quarantine. > > Cheers, > > -- Juanjo >> when the message is finalized and agreed, i can inform lab nodes. >> >> Best, >> Federico >> >> ----------------------------------------- >> Apologizes for mispellings. My thumb is not compatible with Android >> >> On Apr 14, 2015 8:32 PM, "Juanjo Hierro" > wrote: >> Dear all, >> >> I have added Thierry Nagellen from Orange to this mailing list because despite he is not involved in the Task Force "per se", we are synchronized also with Orange overall with respect to messages to pass to the EC and rest of FI-PPP projects. If you believe someone else has to be in this list, please let me know. >> >> It has come out that deployment of the new IdM/Keystone is not feasible as planned. Therefore, we have to define a new plan. >> >> This morning, the TID team (including me) have had the opportunity to meet with the UPM team to understand the issue and we have come with an alternative plan for the recovery of the FIWARE Lab than the one we defined yesterday which sounds pretty reasonable and may help us to soon improve the situation. >> >> Let me summarize the plan in this email so that we are all on the same page. If you find some weakness/issue, please raise it. Otherwise, let's stick to it. Fortunately, the first steps remain the same and they have already been done, so we are on the right track. >> >> An important matter: I plan to send this plan to the EC tomorrow morning at 11:00. If you have comments, you should provide them before that deadline. I will also communicate this plan to FIWARE Accelerator projects on Basecamp as well as to Use Case projects through the FI-PPP mailing lists. Federico or Engineering should communicate this plan to organizations operating the FIWARE Lab nodes also at that time. >> >> A very sensible matter: when you review step 6 you will see that we cover the case in which some FIWARE Lab nodes may be put in quarantine. I would like to propose to the EC that those FIWARE lab nodes which are put into quarantine will be labeled as non-performance so they won't get the grant they were assigned in the XiFi Open Call, at least for the remaining of the XiFi project (until September). Maybe these funds can be given away to other partners or launch another Open Call. I would like to know your views on this. >> >> >> Step 1: reminder about new user account management policies enforcement. >> >> A first email aking existing FIWARE Lab users to accept the new user account management policies, also covered in the new FIWARE Lab use terms and conditions, was sent to all FIWARE Lab users several weeks ago. >> >> A reminder has been sent yesterday and today to current users of the FIWARE Lab telling them that they have until April 15th 2015 19:00 CET. This message will be disseminated through different means: >> mailed to current users of the FIWARE Lab >> shown in a screen at login of users of the FIWARE Lab >> posted on Basecamp so that FIWARE accelerator projects get aware and can forward the remainder to SMEs/startups under their respective programmes >> mailed to the FI-PPP SB and the old FI-PPP AB members so that coordinators/architects of the FIWARE Use Case projects can forward the reminder to SMEs/startups under their respective Use Case projects >> >> Step 2: Increase of computing capacity in Spain-2 node >> In parallel and starting TODAY, activities to expand the capacity of the recently launched Spain-2 node will be prioritized so that we reach a capacity of aprox 500 cores in the datacenters located in both Sevilla and Malaga. We expect this expansion be completed by April 20th if not earlier. >> >> Additionally, additional capacity (close to 500 additional cores) will be activated in the Spain-2 node with servers located in a new datacenter located in Las Palmas. Conversations are ongoing with Red.es trying to accelerate this process so that this additional 500 cores get available closer to the end of next week. >> >> >> Step 3: New Trial users only allowed to work on Spain-2 node. Limitation of number of concurrent trial users. >> >> Changes will be implemented in the Cloud portal and the user account registration process/tool by UPM so that new Trial users will only see the Spain-2 node. In addition, Trial users will be limited to 100 Trial users. >> >> Note that the "Trial Users", until the new IdM/Keystone component is deployed, will need to be identified by considering the creation of their user account. Actually, "Trial users" will be those users who have created their account after April 16th. >> >> Most likely, the fact that Trial users will only be allowed to work on Spain will remain. The number of Trial users allowed may increase (the EC has shown its concern about keeping the number of Trial users too low) but will see. >> >> Users who try to create an account when the limit on Trial users have been reached, will receive a message indicating that the limit has been reached, inviting them to try again in two weeks (Fernando to send the wording for this message to UPM). >> >> This step should be implemented by this Wednesday April 15th. >> >> >> Step 4: Freeing resources on current nodes, giving users the ability to apply to become community users, asking users in Spain-1 and Prague to migrate >> >> Starting April 16th, current nodes will free resources on their nodes (virtual infrastructure and public IP addresses allocated to users who didn't accept the new user account management policies). >> >> They should complete this process before April 23rd. FIWARE Lab node providers are aware of the current situation so they should accelerate this process as much as possible, trying to complete the process the sooner the better. Situation will be assessed on April 20th and April 23rd. It is expected that the status of the FIWARE Lab will improve drastically during the week and will become stable by April 23rd. >> >> In parallel, we will encourage legacy users (those who created their account before April 16th and have accepted the new terms and conditions) to apply for becoming community users. They should be able to submit their application completing an application form that will be provided to them and will be made available on the Cloud Portal. >> >> Those legacy users whose application is accepted and who were hosted in the Spain-1 or the Prague nodes will be asked to migrate their environments to any of the other nodes (a recommendation will be given). The Spain-1 and the Prague nodes will not host community users. As a result, no users will remain in these two nodes by May 1st. >> >> >> Step 5: Deployment of new IdM/Keystone component and upgrading of Community Users. Migration of Spain-1 and Prague nodes to OpenStack Juno. >> >> This step will start May 1st. Then, we will deploy the new version of the IdM/Keystone component. >> >> Users whose application to become Community Users has been approved will become Community Users. Environments of those Trial users who has overpass the 2 weeks trial period will be cleaned out. From then on, the new user account management policies will be in place, with the new IdM/keystone component supporting the ability to distinguish between kind of users and the nodes each will be able to get access to. >> >> In parallel, Spain-1 and Prague nodes should start their migration to Juno. Once they migrate, they will be made available as part of the federation (maybe the physical resources allocated to the Spain-1 node will be assigned to the Spain-2 node). >> >> >> Step 6: Assessment of nodes in the FIWARE Lab federation. Bringing FIWARE Lab nodes into quarantine. >> >> After April 23th, performance of the several nodes in the FIWARE Lab federation will be weekly assessed. Those nodes who exhibit a bad performance (instability, low response to request for help by users) will be put into quarantine and their users (Community Users) will be asked to migrate to the Spain-2 node. >> >> >> 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 >> >> >> 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 >> 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 > 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 > _______________________________________________ > Fiware-lab-recovery-tf mailing list > 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: From federico.facca at create-net.org Wed Apr 15 19:00:49 2015 From: federico.facca at create-net.org (Federico Michele Facca) Date: Wed, 15 Apr 2015 19:00:49 +0200 Subject: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab In-Reply-To: <552E8C6B.5080400@telefonica.com> References: <552D5D25.1060506@telefonica.com> <6984_1429080790_552E0AD6_6984_1370_1_976A65C5A08ADF49B9A8523F7F81925C2AE652@PEXCVZYM13.corporate.adroot.infra.ftgroup> <552E8C6B.5080400@telefonica.com> Message-ID: <9E1FAFEA-6B78-4065-85DB-CB078E1CAC5C@create-net.org> > On 15/apr/2015, at 18:06, Juanjo Hierro wrote: > > > I agree this should be part of our plan but not shared with the EC and others until we have those tools. Otherwise, we'll put pressure on us regarding availability of these tools unnecessarily IMHO. > we had the same feeling, thus why I already asked Attilio and Silvio to analyze this issue. we plan to update to support this information the all current monitoring chain: ODC, monitoring apis and Infographics. first two should not take much time, the third one a bit more (GUI, so not affecting querability of data), i may need a back up developer (or my own time to work on it!), the owner is in maternity. > Cheers, > > -- Juanjo > > On 15/04/15 08:53, thierry.nagellen at orange.com wrote: >> Hi Juanjo >> >> Thanks to add me in the list. >> >> We miss a critical point: Dashboard to monitor resouces availability. This dashboard has to include per node the following elements, at least in a first round: >> Number of Core >> Number of VM in use/available >> Public Ip Addresses: allocated/available >> Helpdesk tickets >> >> At least to manage the impact of new T&C and to have some facts in case of request from our ?clients? and EC >> >> BR >> Thierry >> >> De : fiware-lab-recovery-tf-bounces at lists.fiware.org [mailto:fiware-lab-recovery-tf-bounces at lists.fiware.org] De la part de Juanjo Hierro >> Envoy? : mardi 14 avril 2015 20:32 >> ? : fiware-lab-recovery-tf at lists.fiware.org >> Objet : [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab >> >> Dear all, >> >> I have added Thierry Nagellen from Orange to this mailing list because despite he is not involved in the Task Force "per se", we are synchronized also with Orange overall with respect to messages to pass to the EC and rest of FI-PPP projects. If you believe someone else has to be in this list, please let me know. >> >> It has come out that deployment of the new IdM/Keystone is not feasible as planned. Therefore, we have to define a new plan. >> >> This morning, the TID team (including me) have had the opportunity to meet with the UPM team to understand the issue and we have come with an alternative plan for the recovery of the FIWARE Lab than the one we defined yesterday which sounds pretty reasonable and may help us to soon improve the situation. >> >> Let me summarize the plan in this email so that we are all on the same page. If you find some weakness/issue, please raise it. Otherwise, let's stick to it. Fortunately, the first steps remain the same and they have already been done, so we are on the right track. >> >> An important matter: I plan to send this plan to the EC tomorrow morning at 11:00. If you have comments, you should provide them before that deadline. I will also communicate this plan to FIWARE Accelerator projects on Basecamp as well as to Use Case projects through the FI-PPP mailing lists. Federico or Engineering should communicate this plan to organizations operating the FIWARE Lab nodes also at that time. >> >> A very sensible matter: when you review step 6 you will see that we cover the case in which some FIWARE Lab nodes may be put in quarantine. I would like to propose to the EC that those FIWARE lab nodes which are put into quarantine will be labeled as non-performance so they won't get the grant they were assigned in the XiFi Open Call, at least for the remaining of the XiFi project (until September). Maybe these funds can be given away to other partners or launch another Open Call. I would like to know your views on this. >> >> >> Step 1: reminder about new user account management policies enforcement. >> >> A first email aking existing FIWARE Lab users to accept the new user account management policies, also covered in the new FIWARE Lab use terms and conditions, was sent to all FIWARE Lab users several weeks ago. >> >> A reminder has been sent yesterday and today to current users of the FIWARE Lab telling them that they have until April 15th 2015 19:00 CET. This message will be disseminated through different means: >> ? mailed to current users of the FIWARE Lab >> ? shown in a screen at login of users of the FIWARE Lab >> ? posted on Basecamp so that FIWARE accelerator projects get aware and can forward the remainder to SMEs/startups under their respective programmes >> ? mailed to the FI-PPP SB and the old FI-PPP AB members so that coordinators/architects of the FIWARE Use Case projects can forward the reminder to SMEs/startups under their respective Use Case projects >> >> Step 2: Increase of computing capacity in Spain-2 node >> >> In parallel and starting TODAY, activities to expand the capacity of the recently launched Spain-2 node will be prioritized so that we reach a capacity of aprox 500 cores in the datacenters located in both Sevilla and Malaga. We expect this expansion be completed by April 20th if not earlier. >> >> Additionally, additional capacity (close to 500 additional cores) will be activated in the Spain-2 node with servers located in a new datacenter located in Las Palmas. Conversations are ongoing with Red.es trying to accelerate this process so that this additional 500 cores get available closer to the end of next week. >> >> >> Step 3: New Trial users only allowed to work on Spain-2 node. Limitation of number of concurrent trial users. >> >> Changes will be implemented in the Cloud portal and the user account registration process/tool by UPM so that new Trial users will only see the Spain-2 node. In addition, Trial users will be limited to 100 Trial users. >> >> Note that the "Trial Users", until the new IdM/Keystone component is deployed, will need to be identified by considering the creation of their user account. Actually, "Trial users" will be those users who have created their account after April 16th. >> >> Most likely, the fact that Trial users will only be allowed to work on Spain will remain. The number of Trial users allowed may increase (the EC has shown its concern about keeping the number of Trial users too low) but will see. >> >> Users who try to create an account when the limit on Trial users have been reached, will receive a message indicating that the limit has been reached, inviting them to try again in two weeks (Fernando to send the wording for this message to UPM). >> >> This step should be implemented by this Wednesday April 15th. >> >> >> Step 4: Freeing resources on current nodes, giving users the ability to apply to become community users, asking users in Spain-1 and Prague to migrate >> >> Starting April 16th, current nodes will free resources on their nodes (virtual infrastructure and public IP addresses allocated to users who didn't accept the new user account management policies). >> >> They should complete this process before April 23rd. FIWARE Lab node providers are aware of the current situation so they should accelerate this process as much as possible, trying to complete the process the sooner the better. Situation will be assessed on April 20th and April 23rd. It is expected that the status of the FIWARE Lab will improve drastically during the week and will become stable by April 23rd. >> >> In parallel, we will encourage legacy users (those who created their account before April 16th and have accepted the new terms and conditions) to apply for becoming community users. They should be able to submit their application completing an application form that will be provided to them and will be made available on the Cloud Portal. >> >> Those legacy users whose application is accepted and who were hosted in the Spain-1 or the Prague nodes will be asked to migrate their environments to any of the other nodes (a recommendation will be given). The Spain-1 and the Prague nodes will not host community users. As a result, no users will remain in these two nodes by May 1st. >> >> >> Step 5: Deployment of new IdM/Keystone component and upgrading of Community Users. Migration of Spain-1 and Prague nodes to OpenStack Juno. >> >> This step will start May 1st. Then, we will deploy the new version of the IdM/Keystone component. >> >> Users whose application to become Community Users has been approved will become Community Users. Environments of those Trial users who has overpass the 2 weeks trial period will be cleaned out. From then on, the new user account management policies will be in place, with the new IdM/keystone component supporting the ability to distinguish between kind of users and the nodes each will be able to get access to. >> >> In parallel, Spain-1 and Prague nodes should start their migration to Juno. Once they migrate, they will be made available as part of the federation (maybe the physical resources allocated to the Spain-1 node will be assigned to the Spain-2 node). >> >> >> Step 6: Assessment of nodes in the FIWARE Lab federation. Bringing FIWARE Lab nodes into quarantine. >> >> After April 23th, performance of the several nodes in the FIWARE Lab federation will be weekly assessed. Those nodes who exhibit a bad performance (instability, low response to request for help by users) will be put into quarantine and their users (Community Users) will be asked to migrate to the Spain-2 node. >> >> >> 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 >> >> >> 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 >> _________________________________________________________________________________________________________________________ >> >> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc >> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler >> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, >> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. >> >> This message and its attachments may contain confidential or privileged information that may be protected by law; >> they should not be distributed, used or copied without authorisation. >> If you have received this email in error, please notify the sender and delete this message and its attachments. >> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. >> Thank you. >> > > -- > > ______________________________________________________ > > 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 > _______________________________________________ > Fiware-lab-recovery-tf mailing list > Fiware-lab-recovery-tf at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-lab-recovery-tf -- 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 From federico.facca at create-net.org Wed Apr 15 19:02:23 2015 From: federico.facca at create-net.org (Federico Michele Facca) Date: Wed, 15 Apr 2015 19:02:23 +0200 Subject: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab In-Reply-To: <3964F66E-FA4A-409A-AACE-F68AB0E15E22@dit.upm.es> References: <552D5D25.1060506@telefonica.com> <552E8C06.1020105@telefonica.com> <3964F66E-FA4A-409A-AACE-F68AB0E15E22@dit.upm.es> Message-ID: > On 15/apr/2015, at 18:15, ?lvaro Alonso wrote: > > Hi, > > today tests made by Henar in havana suggest that havana is not compatible with v3. Federico found a post (https://www.mirantis.com/blog/manage-openstack-projects-using-domains-havana/) that says it is partially compatible but we are not sure of that. > > My understanding was that every nodes had to be migrated to Icehouse, for that reason I was only concerned by old spain node. > > @Federico, do you know haw many nodes are still Grizzly? The will be migrated before May 1? Is it possible to decide that if a node is not migrated to Icehouse by May 1, it will be out of the federation until it migrates? > i share yesterday the last info i had on this with fernando. but it?s better to re-asses and force migration plans if not already happened as per schedule. give me some time. i will create an up-to-date status. > BR > -- > ?lvaro > >> El 15 Apr 2015, a las 18:04, Juanjo Hierro escribi?: >> >> >> >> On 15/04/15 05:58, Federico Michele Facca wrote: >>> Dear Juanjo, >>> some comments from my side: >>> >>> 1) Maurizio as XIFI coordinator, needs to be in the loop. While I agree that some nodes - probably like some GEs developers btw - don't deserve ths money they have been granted for the service given, any action and decision in this direction within XIFI is beyond my role. Not sure if and how saved money could be employed. Moved to FI-CORE? >>> >> >> I have added him. >> >>> 2) According to a short discussion I had with Alvaro, Migration to new IDM my affect as well other nodes still using Grizzly, this needs to be clarified asap in order to take proper actions (i.e. Accelerate migration plan). >>> >> >> People from UPM has to clarify this URGENTLY. I was about to send an email to Basecamp sharing the plan (to show we are reacting and we have setup a Recovery Task Force but I want to know to what extend I have to modify anything in the description of the plan. >> >>> 3) It is very important to agree on fair, objective and not arguable metrics to define performance. As early mentioned errors from tests due to finished resources do not mean "bad performance" (if not this would be the case as well for spain), this case is a more general issue related to the tools and functions provided on top of nodes, for which we cannot account them. >>> >> >> Agreed. That's why, a) we will only be able to measure performance once nodes get cleaned b) we need to make sure that the tests run well (it is my impression that some of them do not give an accurate photo of the status) >> >>> 4) There are nodes operating for "free", what should we do in such cases? I would keep possibility fir user with proper role to use them, regardeless, no financial penality can be passed over to them. >>> >> >> We should come with a way to label the different nodes and let users take decision. Of course, there is no penalty that can be passed to them. But certainly something we can do is to put them in quarantine. >> >> Cheers, >> >> -- Juanjo >>> when the message is finalized and agreed, i can inform lab nodes. >>> >>> Best, >>> Federico >>> >>> ----------------------------------------- >>> Apologizes for mispellings. My thumb is not compatible with Android >>> >>> On Apr 14, 2015 8:32 PM, "Juanjo Hierro" wrote: >>> Dear all, >>> >>> I have added Thierry Nagellen from Orange to this mailing list because despite he is not involved in the Task Force "per se", we are synchronized also with Orange overall with respect to messages to pass to the EC and rest of FI-PPP projects. If you believe someone else has to be in this list, please let me know. >>> >>> It has come out that deployment of the new IdM/Keystone is not feasible as planned. Therefore, we have to define a new plan. >>> >>> This morning, the TID team (including me) have had the opportunity to meet with the UPM team to understand the issue and we have come with an alternative plan for the recovery of the FIWARE Lab than the one we defined yesterday which sounds pretty reasonable and may help us to soon improve the situation. >>> >>> Let me summarize the plan in this email so that we are all on the same page. If you find some weakness/issue, please raise it. Otherwise, let's stick to it. Fortunately, the first steps remain the same and they have already been done, so we are on the right track. >>> >>> An important matter: I plan to send this plan to the EC tomorrow morning at 11:00. If you have comments, you should provide them before that deadline. I will also communicate this plan to FIWARE Accelerator projects on Basecamp as well as to Use Case projects through the FI-PPP mailing lists. Federico or Engineering should communicate this plan to organizations operating the FIWARE Lab nodes also at that time. >>> >>> A very sensible matter: when you review step 6 you will see that we cover the case in which some FIWARE Lab nodes may be put in quarantine. I would like to propose to the EC that those FIWARE lab nodes which are put into quarantine will be labeled as non-performance so they won't get the grant they were assigned in the XiFi Open Call, at least for the remaining of the XiFi project (until September). Maybe these funds can be given away to other partners or launch another Open Call. I would like to know your views on this. >>> >>> >>> Step 1: reminder about new user account management policies enforcement. >>> >>> A first email aking existing FIWARE Lab users to accept the new user account management policies, also covered in the new FIWARE Lab use terms and conditions, was sent to all FIWARE Lab users several weeks ago. >>> >>> A reminder has been sent yesterday and today to current users of the FIWARE Lab telling them that they have until April 15th 2015 19:00 CET. This message will be disseminated through different means: >>> ? mailed to current users of the FIWARE Lab >>> ? shown in a screen at login of users of the FIWARE Lab >>> ? posted on Basecamp so that FIWARE accelerator projects get aware and can forward the remainder to SMEs/startups under their respective programmes >>> ? mailed to the FI-PPP SB and the old FI-PPP AB members so that coordinators/architects of the FIWARE Use Case projects can forward the reminder to SMEs/startups under their respective Use Case projects >>> >>> Step 2: Increase of computing capacity in Spain-2 node >>> In parallel and starting TODAY, activities to expand the capacity of the recently launched Spain-2 node will be prioritized so that we reach a capacity of aprox 500 cores in the datacenters located in both Sevilla and Malaga. We expect this expansion be completed by April 20th if not earlier. >>> >>> Additionally, additional capacity (close to 500 additional cores) will be activated in the Spain-2 node with servers located in a new datacenter located in Las Palmas. Conversations are ongoing with Red.es trying to accelerate this process so that this additional 500 cores get available closer to the end of next week. >>> >>> >>> Step 3: New Trial users only allowed to work on Spain-2 node. Limitation of number of concurrent trial users. >>> >>> Changes will be implemented in the Cloud portal and the user account registration process/tool by UPM so that new Trial users will only see the Spain-2 node. In addition, Trial users will be limited to 100 Trial users. >>> >>> Note that the "Trial Users", until the new IdM/Keystone component is deployed, will need to be identified by considering the creation of their user account. Actually, "Trial users" will be those users who have created their account after April 16th. >>> >>> Most likely, the fact that Trial users will only be allowed to work on Spain will remain. The number of Trial users allowed may increase (the EC has shown its concern about keeping the number of Trial users too low) but will see. >>> >>> Users who try to create an account when the limit on Trial users have been reached, will receive a message indicating that the limit has been reached, inviting them to try again in two weeks (Fernando to send the wording for this message to UPM). >>> >>> This step should be implemented by this Wednesday April 15th. >>> >>> >>> Step 4: Freeing resources on current nodes, giving users the ability to apply to become community users, asking users in Spain-1 and Prague to migrate >>> >>> Starting April 16th, current nodes will free resources on their nodes (virtual infrastructure and public IP addresses allocated to users who didn't accept the new user account management policies). >>> >>> They should complete this process before April 23rd. FIWARE Lab node providers are aware of the current situation so they should accelerate this process as much as possible, trying to complete the process the sooner the better. Situation will be assessed on April 20th and April 23rd. It is expected that the status of the FIWARE Lab will improve drastically during the week and will become stable by April 23rd. >>> >>> In parallel, we will encourage legacy users (those who created their account before April 16th and have accepted the new terms and conditions) to apply for becoming community users. They should be able to submit their application completing an application form that will be provided to them and will be made available on the Cloud Portal. >>> >>> Those legacy users whose application is accepted and who were hosted in the Spain-1 or the Prague nodes will be asked to migrate their environments to any of the other nodes (a recommendation will be given). The Spain-1 and the Prague nodes will not host community users. As a result, no users will remain in these two nodes by May 1st. >>> >>> >>> Step 5: Deployment of new IdM/Keystone component and upgrading of Community Users. Migration of Spain-1 and Prague nodes to OpenStack Juno. >>> >>> This step will start May 1st. Then, we will deploy the new version of the IdM/Keystone component. >>> >>> Users whose application to become Community Users has been approved will become Community Users. Environments of those Trial users who has overpass the 2 weeks trial period will be cleaned out. From then on, the new user account management policies will be in place, with the new IdM/keystone component supporting the ability to distinguish between kind of users and the nodes each will be able to get access to. >>> >>> In parallel, Spain-1 and Prague nodes should start their migration to Juno. Once they migrate, they will be made available as part of the federation (maybe the physical resources allocated to the Spain-1 node will be assigned to the Spain-2 node). >>> >>> >>> Step 6: Assessment of nodes in the FIWARE Lab federation. Bringing FIWARE Lab nodes into quarantine. >>> >>> After April 23th, performance of the several nodes in the FIWARE Lab federation will be weekly assessed. Those nodes who exhibit a bad performance (instability, low response to request for help by users) will be put into quarantine and their users (Community Users) will be asked to migrate to the Spain-2 node. >>> >>> >>> 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 >>> >>> >>> 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 >>> 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 >> >> 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 >> _______________________________________________ >> Fiware-lab-recovery-tf mailing list >> 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 > https://lists.fiware.org/listinfo/fiware-lab-recovery-tf -- 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 From juanjose.hierro at telefonica.com Wed Apr 15 19:04:18 2015 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Wed, 15 Apr 2015 19:04:18 +0200 Subject: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab In-Reply-To: <3964F66E-FA4A-409A-AACE-F68AB0E15E22@dit.upm.es> References: <552D5D25.1060506@telefonica.com> <552E8C06.1020105@telefonica.com> <3964F66E-FA4A-409A-AACE-F68AB0E15E22@dit.upm.es> Message-ID: <552E9A12.7040407@telefonica.com> An HTML attachment was scrubbed... URL: From federico.facca at create-net.org Wed Apr 15 19:07:04 2015 From: federico.facca at create-net.org (Federico Michele Facca) Date: Wed, 15 Apr 2015 19:07:04 +0200 Subject: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab In-Reply-To: <552E9A12.7040407@telefonica.com> References: <552D5D25.1060506@telefonica.com> <552E8C06.1020105@telefonica.com> <3964F66E-FA4A-409A-AACE-F68AB0E15E22@dit.upm.es> <552E9A12.7040407@telefonica.com> Message-ID: i would say that the safe threashold is icehouse. tricks may work for havana and grizlly but tricks do not fall in "safe" until we test. On Wed, Apr 15, 2015 at 7:04 PM, Juanjo Hierro < juanjose.hierro at telefonica.com> wrote: > Gentlemen, > > I need to know where to put a safe threshold (Grizzly,Havana, IceHouse, > ...), so that last paragraph of Step 4 changes and I mention that all > legacy users who get upgraded to become Community Users but were hosted on > nodes not in version XXX of OpenStack or will have to migrate to other > nodes (as per recommendation given in response to their request for the > upgrade). > > I need this response URGENTLY. > > Best regards, > > -- Juanjo > > > On 15/04/15 18:15, ?lvaro Alonso wrote: > > Hi, > > today tests made by Henar in havana suggest that havana is not > compatible with v3. Federico found a post ( > https://www.mirantis.com/blog/manage-openstack-projects-using-domains-havana/) > that says it is partially compatible but we are not sure of that. > > My understanding was that every nodes had to be migrated to Icehouse, > for that reason I was only concerned by old spain node. > > @Federico, do you know haw many nodes are still Grizzly? The will be > migrated before May 1? Is it possible to decide that if a node is not > migrated to Icehouse by May 1, it will be out of the federation until it > migrates? > > BR > -- > ?lvaro > > El 15 Apr 2015, a las 18:04, Juanjo Hierro < > juanjose.hierro at telefonica.com> escribi?: > > > > On 15/04/15 05:58, Federico Michele Facca wrote: > > Dear Juanjo, > some comments from my side: > > 1) Maurizio as XIFI coordinator, needs to be in the loop. While I agree > that some nodes - probably like some GEs developers btw - don't deserve ths > money they have been granted for the service given, any action and decision > in this direction within XIFI is beyond my role. Not sure if and how saved > money could be employed. Moved to FI-CORE? > > > I have added him. > > 2) According to a short discussion I had with Alvaro, Migration to new > IDM my affect as well other nodes still using Grizzly, this needs to be > clarified asap in order to take proper actions (i.e. Accelerate migration > plan). > > > People from UPM has to clarify this URGENTLY. I was about to send an > email to Basecamp sharing the plan (to show we are reacting and we have > setup a Recovery Task Force but I want to know to what extend I have to > modify anything in the description of the plan. > > > 3) It is very important to agree on fair, objective and not arguable > metrics to define performance. As early mentioned errors from tests due to > finished resources do not mean "bad performance" (if not this would be the > case as well for spain), this case is a more general issue related to the > tools and functions provided on top of nodes, for which we cannot account > them. > > > Agreed. That's why, a) we will only be able to measure performance > once nodes get cleaned b) we need to make sure that the tests run well (it > is my impression that some of them do not give an accurate photo of the > status) > > 4) There are nodes operating for "free", what should we do in such > cases? I would keep possibility fir user with proper role to use them, > regardeless, no financial penality can be passed over to them. > > > We should come with a way to label the different nodes and let users > take decision. Of course, there is no penalty that can be passed to > them. But certainly something we can do is to put them in quarantine. > > Cheers, > > -- Juanjo > > when the message is finalized and agreed, i can inform lab nodes. > > Best, > Federico > > ----------------------------------------- > Apologizes for mispellings. My thumb is not compatible with Android > On Apr 14, 2015 8:32 PM, "Juanjo Hierro" > wrote: > >> Dear all, >> >> I have added Thierry Nagellen from Orange to this mailing list because >> despite he is not involved in the Task Force "per se", we are synchronized >> also with Orange overall with respect to messages to pass to the EC and >> rest of FI-PPP projects. If you believe someone else has to be in this >> list, please let me know. >> >> It has come out that deployment of the new IdM/Keystone is not feasible >> as planned. Therefore, we have to define a new plan. >> >> This morning, the TID team (including me) have had the opportunity to >> meet with the UPM team to understand the issue and we have come with an >> alternative plan for the recovery of the FIWARE Lab than the one we defined >> yesterday which sounds pretty reasonable and may help us to soon improve >> the situation. >> >> Let me summarize the plan in this email so that we are all on the same >> page. If you find some weakness/issue, please raise it. Otherwise, >> let's stick to it. Fortunately, the first steps remain the same and they >> have already been done, so we are on the right track. >> >> An important matter: I plan to send this plan to the EC tomorrow >> morning at 11:00. If you have comments, you should provide them before >> that deadline. I will also communicate this plan to FIWARE Accelerator >> projects on Basecamp as well as to Use Case projects through the FI-PPP >> mailing lists. Federico or Engineering should communicate this plan to >> organizations operating the FIWARE Lab nodes also at that time. >> >> A very sensible matter: when you review step 6 you will see that we >> cover the case in which some FIWARE Lab nodes may be put in quarantine. I >> would like to propose to the EC that those FIWARE lab nodes which are put >> into quarantine will be labeled as non-performance so they won't get the >> grant they were assigned in the XiFi Open Call, at least for the remaining >> of the XiFi project (until September). Maybe these funds can be given >> away to other partners or launch another Open Call. I would like to know >> your views on this. >> >> >> *Step 1: reminder about new user account management policies enforcement.* >> >> A first email aking existing FIWARE Lab users to accept the new user >> account management policies, also covered in the new FIWARE Lab use terms >> and conditions, was sent to all FIWARE Lab users several weeks ago. >> >> A reminder has been sent yesterday and today to current users of the >> FIWARE Lab telling them that they have until April 15th 2015 19:00 CET. >> This message will be disseminated through different means: >> >> - mailed to current users of the FIWARE Lab >> - shown in a screen at login of users of the FIWARE Lab >> - posted on Basecamp so that FIWARE accelerator projects get aware >> and can forward the remainder to SMEs/startups under their respective >> programmes >> - mailed to the FI-PPP SB and the old FI-PPP AB members so that >> coordinators/architects of the FIWARE Use Case projects can forward the >> reminder to SMEs/startups under their respective Use Case projects >> >> >> *Step 2: Increase of computing capacity in Spain-2 node* >> In parallel and starting TODAY, activities to expand the capacity of >> the recently launched Spain-2 node will be prioritized so that we reach a >> capacity of aprox 500 cores in the datacenters located in both Sevilla and >> Malaga. We expect this expansion be completed by April 20th if not >> earlier. >> >> Additionally, additional capacity (close to 500 additional cores) will >> be activated in the Spain-2 node with servers located in a new datacenter >> located in Las Palmas. Conversations are ongoing with Red.es trying to >> accelerate this process so that this additional 500 cores get available >> closer to the end of next week. >> >> >> *Step 3: New Trial users only allowed to work on Spain-2 node**. >> Limitation of number of concurrent trial users.* >> >> Changes will be implemented in the Cloud portal and the user account >> registration process/tool by UPM so that new Trial users will only see the >> Spain-2 node. In addition, Trial users will be limited to 100 Trial users. >> >> Note that the "Trial Users", until the new IdM/Keystone component is >> deployed, will need to be identified by considering the creation of their >> user account. Actually, "Trial users" will be those users who have >> created their account after April 16th. >> >> Most likely, the fact that Trial users will only be allowed to work on >> Spain will remain. The number of Trial users allowed may increase (the EC >> has shown its concern about keeping the number of Trial users too low) but >> will see. >> >> Users who try to create an account when the limit on Trial users have >> been reached, will receive a message indicating that the limit has been >> reached, inviting them to try again in two weeks (Fernando to send the >> wording for this message to UPM). >> >> This step should be implemented by this Wednesday April 15th. >> >> >> *Step 4: Freeing resources on current nodes**, giving users the ability >> to apply to become community users, asking users in Spain-1 and Prague to >> migrate* >> >> Starting April 16th, current nodes will free resources on their nodes >> (virtual infrastructure and public IP addresses allocated to users who >> didn't accept the new user account management policies). >> >> They should complete this process before April 23rd. FIWARE Lab node >> providers are aware of the current situation so they should accelerate this >> process as much as possible, trying to complete the process the sooner the >> better. Situation will be assessed on April 20th and April 23rd. It is >> expected that the status of the FIWARE Lab will improve drastically during >> the week and will become stable by April 23rd. >> >> In parallel, we will encourage legacy users (those who created their >> account before April 16th and have accepted the new terms and conditions) >> to apply for becoming community users. They should be able to submit >> their application completing an application form that will be provided to >> them and will be made available on the Cloud Portal. >> >> Those legacy users whose application is accepted and who were hosted in >> the Spain-1 or the Prague nodes will be asked to migrate their environments >> to any of the other nodes (a recommendation will be given). The Spain-1 >> and the Prague nodes will not host community users. As a result, no users >> will remain in these two nodes by May 1st. >> >> >> *Step 5: Deployment of new IdM/Keystone component and upgrading of >> Community Users*. * Migration of Spain-1 and Prague nodes to OpenStack >> Juno.* >> >> This step will start May 1st. Then, we will deploy the new version of >> the IdM/Keystone component. >> >> Users whose application to become Community Users has been approved >> will become Community Users. Environments of those Trial users who has >> overpass the 2 weeks trial period will be cleaned out. From then on, the >> new user account management policies will be in place, with the new >> IdM/keystone component supporting the ability to distinguish between kind >> of users and the nodes each will be able to get access to. >> >> In parallel, Spain-1 and Prague nodes should start their migration to >> Juno. Once they migrate, they will be made available as part of the >> federation (maybe the physical resources allocated to the Spain-1 node will >> be assigned to the Spain-2 node). >> >> >> *Step 6: Assessment of nodes in the FIWARE Lab federation. Bringing >> FIWARE Lab nodes into quarantine.* >> >> After April 23th, performance of the several nodes in the FIWARE Lab >> federation will be weekly assessed. Those nodes who exhibit a bad >> performance (instability, low response to request for help by users) will >> be put into quarantine and their users (Community Users) will be asked to >> migrate to the Spain-2 node. >> >> >> 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 >> >> >> ------------------------------ >> >> 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 >> 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 > 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 > _______________________________________________ > Fiware-lab-recovery-tf mailing list > 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 > 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 > > _______________________________________________ > Fiware-lab-recovery-tf mailing list > Fiware-lab-recovery-tf at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-lab-recovery-tf > > -- -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From juanjose.hierro at telefonica.com Thu Apr 16 07:34:45 2015 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Thu, 16 Apr 2015 07:34:45 +0200 Subject: [Fiware-lab-recovery-tf] Fwd: FIWARE Lab Recovery Task Force In-Reply-To: <552F4707.4000508@telefonica.com> References: <552F4707.4000508@telefonica.com> Message-ID: <552F49F5.2060700@telefonica.com> An HTML attachment was scrubbed... URL: From juanjose.hierro at telefonica.com Thu Apr 16 07:49:08 2015 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Thu, 16 Apr 2015 07:49:08 +0200 Subject: [Fiware-lab-recovery-tf] Daily meetings Message-ID: <552F4D54.9080608@telefonica.com> Hi all, Following results of the doodle poll, Daily meetings will be defined every day from 16:30 to 17:00 starting today. Federico: you are the only one that could not make it at that time. However, you could make it starting at 17:00. I believe it is quite important that you attend. Please adjust your commitments so that you can accommodate the slot. We will use powwownow (PIN 940541) I will work to get ready the Crash Action Plan table before the meeting today. Best regards, -- 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 ________________________________ 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 From juanjose.hierro at telefonica.com Thu Apr 16 07:50:28 2015 From: juanjose.hierro at telefonica.com (JUAN JOSE HIERRO SUREDA) Date: Thu, 16 Apr 2015 05:50:28 +0000 Subject: [Fiware-lab-recovery-tf] FIWARE Lab Recovery Task Force - Daily meeting Message-ID: ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3178 bytes Desc: not available URL: From federico.facca at create-net.org Thu Apr 16 07:53:30 2015 From: federico.facca at create-net.org (Federico Michele Facca) Date: Thu, 16 Apr 2015 07:53:30 +0200 Subject: [Fiware-lab-recovery-tf] Daily meetings In-Reply-To: <552F4D54.9080608@telefonica.com> References: <552F4D54.9080608@telefonica.com> Message-ID: Hi Juanjo, I am in on a business travel, at that time, I am supposed to be in the meeting. If I am not the one speaking, I will try to sneak out and connect. Federico On Thu, Apr 16, 2015 at 7:49 AM, Juanjo Hierro < juanjose.hierro at telefonica.com> wrote: > Hi all, > > Following results of the doodle poll, Daily meetings will be defined > every day from 16:30 to 17:00 starting today. > > Federico: you are the only one that could not make it at that time. > However, you could make it starting at 17:00. I believe it is quite > important that you attend. Please adjust your commitments so that you > can accommodate the slot. > > We will use powwownow (PIN 940541) > > I will work to get ready the Crash Action Plan table before the > meeting today. > > Best regards, > > -- 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 > > > ________________________________ > > 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 > https://lists.fiware.org/listinfo/fiware-lab-recovery-tf > -- -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From federico.facca at create-net.org Thu Apr 16 07:55:14 2015 From: federico.facca at create-net.org (Federico Michele Facca) Date: Thu, 16 Apr 2015 07:55:14 +0200 Subject: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab In-Reply-To: References: <552D5D25.1060506@telefonica.com> <552E8C06.1020105@telefonica.com> <3964F66E-FA4A-409A-AACE-F68AB0E15E22@dit.upm.es> <552E9A12.7040407@telefonica.com> Message-ID: https://wiki.openstack.org/wiki/ReleaseNotes/Juno Known Issues - When using libvirt, live snapshots are effectively disabled, due to this difficult-to-reproduce bug: https://bugs.launchpad.net/nova/+bug/1334398( https://review.openstack.org/#/c/102643/) - Glance v2 and Keystone v3 are not tested with Nova in Juno. On Wed, Apr 15, 2015 at 7:07 PM, Federico Michele Facca < federico.facca at create-net.org> wrote: > i would say that the safe threashold is icehouse. tricks may work for > havana and grizlly but tricks do not fall in "safe" until we test. > > On Wed, Apr 15, 2015 at 7:04 PM, Juanjo Hierro < > juanjose.hierro at telefonica.com> wrote: > >> Gentlemen, >> >> I need to know where to put a safe threshold (Grizzly,Havana, >> IceHouse, ...), so that last paragraph of Step 4 changes and I mention that >> all legacy users who get upgraded to become Community Users but were hosted >> on nodes not in version XXX of OpenStack or will have to migrate to other >> nodes (as per recommendation given in response to their request for the >> upgrade). >> >> I need this response URGENTLY. >> >> Best regards, >> >> -- Juanjo >> >> >> On 15/04/15 18:15, ?lvaro Alonso wrote: >> >> Hi, >> >> today tests made by Henar in havana suggest that havana is not >> compatible with v3. Federico found a post ( >> https://www.mirantis.com/blog/manage-openstack-projects-using-domains-havana/) >> that says it is partially compatible but we are not sure of that. >> >> My understanding was that every nodes had to be migrated to Icehouse, >> for that reason I was only concerned by old spain node. >> >> @Federico, do you know haw many nodes are still Grizzly? The will be >> migrated before May 1? Is it possible to decide that if a node is not >> migrated to Icehouse by May 1, it will be out of the federation until it >> migrates? >> >> BR >> -- >> ?lvaro >> >> El 15 Apr 2015, a las 18:04, Juanjo Hierro < >> juanjose.hierro at telefonica.com> escribi?: >> >> >> >> On 15/04/15 05:58, Federico Michele Facca wrote: >> >> Dear Juanjo, >> some comments from my side: >> >> 1) Maurizio as XIFI coordinator, needs to be in the loop. While I agree >> that some nodes - probably like some GEs developers btw - don't deserve ths >> money they have been granted for the service given, any action and decision >> in this direction within XIFI is beyond my role. Not sure if and how saved >> money could be employed. Moved to FI-CORE? >> >> >> I have added him. >> >> 2) According to a short discussion I had with Alvaro, Migration to new >> IDM my affect as well other nodes still using Grizzly, this needs to be >> clarified asap in order to take proper actions (i.e. Accelerate migration >> plan). >> >> >> People from UPM has to clarify this URGENTLY. I was about to send an >> email to Basecamp sharing the plan (to show we are reacting and we have >> setup a Recovery Task Force but I want to know to what extend I have to >> modify anything in the description of the plan. >> >> >> 3) It is very important to agree on fair, objective and not arguable >> metrics to define performance. As early mentioned errors from tests due to >> finished resources do not mean "bad performance" (if not this would be the >> case as well for spain), this case is a more general issue related to the >> tools and functions provided on top of nodes, for which we cannot account >> them. >> >> >> Agreed. That's why, a) we will only be able to measure performance >> once nodes get cleaned b) we need to make sure that the tests run well (it >> is my impression that some of them do not give an accurate photo of the >> status) >> >> 4) There are nodes operating for "free", what should we do in such >> cases? I would keep possibility fir user with proper role to use them, >> regardeless, no financial penality can be passed over to them. >> >> >> We should come with a way to label the different nodes and let users >> take decision. Of course, there is no penalty that can be passed to >> them. But certainly something we can do is to put them in quarantine. >> >> Cheers, >> >> -- Juanjo >> >> when the message is finalized and agreed, i can inform lab nodes. >> >> Best, >> Federico >> >> ----------------------------------------- >> Apologizes for mispellings. My thumb is not compatible with Android >> On Apr 14, 2015 8:32 PM, "Juanjo Hierro" >> wrote: >> >>> Dear all, >>> >>> I have added Thierry Nagellen from Orange to this mailing list because >>> despite he is not involved in the Task Force "per se", we are synchronized >>> also with Orange overall with respect to messages to pass to the EC and >>> rest of FI-PPP projects. If you believe someone else has to be in this >>> list, please let me know. >>> >>> It has come out that deployment of the new IdM/Keystone is not >>> feasible as planned. Therefore, we have to define a new plan. >>> >>> This morning, the TID team (including me) have had the opportunity to >>> meet with the UPM team to understand the issue and we have come with an >>> alternative plan for the recovery of the FIWARE Lab than the one we defined >>> yesterday which sounds pretty reasonable and may help us to soon improve >>> the situation. >>> >>> Let me summarize the plan in this email so that we are all on the same >>> page. If you find some weakness/issue, please raise it. Otherwise, >>> let's stick to it. Fortunately, the first steps remain the same and they >>> have already been done, so we are on the right track. >>> >>> An important matter: I plan to send this plan to the EC tomorrow >>> morning at 11:00. If you have comments, you should provide them before >>> that deadline. I will also communicate this plan to FIWARE Accelerator >>> projects on Basecamp as well as to Use Case projects through the FI-PPP >>> mailing lists. Federico or Engineering should communicate this plan to >>> organizations operating the FIWARE Lab nodes also at that time. >>> >>> A very sensible matter: when you review step 6 you will see that we >>> cover the case in which some FIWARE Lab nodes may be put in quarantine. I >>> would like to propose to the EC that those FIWARE lab nodes which are put >>> into quarantine will be labeled as non-performance so they won't get the >>> grant they were assigned in the XiFi Open Call, at least for the remaining >>> of the XiFi project (until September). Maybe these funds can be given >>> away to other partners or launch another Open Call. I would like to know >>> your views on this. >>> >>> >>> *Step 1: reminder about new user account management policies >>> enforcement.* >>> >>> A first email aking existing FIWARE Lab users to accept the new user >>> account management policies, also covered in the new FIWARE Lab use terms >>> and conditions, was sent to all FIWARE Lab users several weeks ago. >>> >>> A reminder has been sent yesterday and today to current users of the >>> FIWARE Lab telling them that they have until April 15th 2015 19:00 CET. >>> This message will be disseminated through different means: >>> >>> - mailed to current users of the FIWARE Lab >>> - shown in a screen at login of users of the FIWARE Lab >>> - posted on Basecamp so that FIWARE accelerator projects get aware >>> and can forward the remainder to SMEs/startups under their respective >>> programmes >>> - mailed to the FI-PPP SB and the old FI-PPP AB members so that >>> coordinators/architects of the FIWARE Use Case projects can forward the >>> reminder to SMEs/startups under their respective Use Case projects >>> >>> >>> *Step 2: Increase of computing capacity in Spain-2 node* >>> In parallel and starting TODAY, activities to expand the capacity of >>> the recently launched Spain-2 node will be prioritized so that we reach a >>> capacity of aprox 500 cores in the datacenters located in both Sevilla and >>> Malaga. We expect this expansion be completed by April 20th if not >>> earlier. >>> >>> Additionally, additional capacity (close to 500 additional cores) will >>> be activated in the Spain-2 node with servers located in a new datacenter >>> located in Las Palmas. Conversations are ongoing with Red.es trying >>> to accelerate this process so that this additional 500 cores get available >>> closer to the end of next week. >>> >>> >>> *Step 3: New Trial users only allowed to work on Spain-2 node**. >>> Limitation of number of concurrent trial users.* >>> >>> Changes will be implemented in the Cloud portal and the user account >>> registration process/tool by UPM so that new Trial users will only see the >>> Spain-2 node. In addition, Trial users will be limited to 100 Trial users. >>> >>> Note that the "Trial Users", until the new IdM/Keystone component is >>> deployed, will need to be identified by considering the creation of their >>> user account. Actually, "Trial users" will be those users who have >>> created their account after April 16th. >>> >>> Most likely, the fact that Trial users will only be allowed to work on >>> Spain will remain. The number of Trial users allowed may increase (the EC >>> has shown its concern about keeping the number of Trial users too low) but >>> will see. >>> >>> Users who try to create an account when the limit on Trial users have >>> been reached, will receive a message indicating that the limit has been >>> reached, inviting them to try again in two weeks (Fernando to send the >>> wording for this message to UPM). >>> >>> This step should be implemented by this Wednesday April 15th. >>> >>> >>> *Step 4: Freeing resources on current nodes**, giving users the ability >>> to apply to become community users, asking users in Spain-1 and Prague to >>> migrate* >>> >>> Starting April 16th, current nodes will free resources on their nodes >>> (virtual infrastructure and public IP addresses allocated to users who >>> didn't accept the new user account management policies). >>> >>> They should complete this process before April 23rd. FIWARE Lab node >>> providers are aware of the current situation so they should accelerate this >>> process as much as possible, trying to complete the process the sooner the >>> better. Situation will be assessed on April 20th and April 23rd. It is >>> expected that the status of the FIWARE Lab will improve drastically during >>> the week and will become stable by April 23rd. >>> >>> In parallel, we will encourage legacy users (those who created their >>> account before April 16th and have accepted the new terms and conditions) >>> to apply for becoming community users. They should be able to submit >>> their application completing an application form that will be provided to >>> them and will be made available on the Cloud Portal. >>> >>> Those legacy users whose application is accepted and who were hosted >>> in the Spain-1 or the Prague nodes will be asked to migrate their >>> environments to any of the other nodes (a recommendation will be given). >>> The Spain-1 and the Prague nodes will not host community users. As a >>> result, no users will remain in these two nodes by May 1st. >>> >>> >>> *Step 5: Deployment of new IdM/Keystone component and upgrading of >>> Community Users*. * Migration of Spain-1 and Prague nodes to OpenStack >>> Juno.* >>> >>> This step will start May 1st. Then, we will deploy the new version >>> of the IdM/Keystone component. >>> >>> Users whose application to become Community Users has been approved >>> will become Community Users. Environments of those Trial users who has >>> overpass the 2 weeks trial period will be cleaned out. From then on, the >>> new user account management policies will be in place, with the new >>> IdM/keystone component supporting the ability to distinguish between kind >>> of users and the nodes each will be able to get access to. >>> >>> In parallel, Spain-1 and Prague nodes should start their migration to >>> Juno. Once they migrate, they will be made available as part of the >>> federation (maybe the physical resources allocated to the Spain-1 node will >>> be assigned to the Spain-2 node). >>> >>> >>> *Step 6: Assessment of nodes in the FIWARE Lab federation. Bringing >>> FIWARE Lab nodes into quarantine.* >>> >>> After April 23th, performance of the several nodes in the FIWARE Lab >>> federation will be weekly assessed. Those nodes who exhibit a bad >>> performance (instability, low response to request for help by users) will >>> be put into quarantine and their users (Community Users) will be asked to >>> migrate to the Spain-2 node. >>> >>> >>> 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 >>> >>> >>> ------------------------------ >>> >>> 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 >>> 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 >> 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 >> _______________________________________________ >> Fiware-lab-recovery-tf mailing list >> 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 >> 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 >> >> _______________________________________________ >> Fiware-lab-recovery-tf mailing list >> Fiware-lab-recovery-tf at lists.fiware.org >> https://lists.fiware.org/listinfo/fiware-lab-recovery-tf >> >> > > > -- > -- > 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 > -- -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From juanjose.hierro at telefonica.com Thu Apr 16 08:22:29 2015 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Thu, 16 Apr 2015 08:22:29 +0200 Subject: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab In-Reply-To: References: <552D5D25.1060506@telefonica.com> <552E8C06.1020105@telefonica.com> <3964F66E-FA4A-409A-AACE-F68AB0E15E22@dit.upm.es> <552E9A12.7040407@telefonica.com> Message-ID: <552F5525.90509@telefonica.com> An HTML attachment was scrubbed... URL: From joseignacio.carreteroguarde at telefonica.com Thu Apr 16 08:38:47 2015 From: joseignacio.carreteroguarde at telefonica.com (=?windows-1252?Q?Jos=E9_Ignacio_Carretero?=) Date: Thu, 16 Apr 2015 08:38:47 +0200 Subject: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab In-Reply-To: <552F5525.90509@telefonica.com> References: <552D5D25.1060506@telefonica.com> <552E8C06.1020105@telefonica.com> <3964F66E-FA4A-409A-AACE-F68AB0E15E22@dit.upm.es> <552E9A12.7040407@telefonica.com> <552F5525.90509@telefonica.com> Message-ID: <552F58F7.1020609@telefonica.com> I think so, it is untested, we'll very likely have problems. We usually have problems even with tested features. El 16/04/15 a las 08:22, Juanjo Hierro escribi?: Does this mean that we are going to have a problem with Juno and the new IdM/Keystone ? On 16/04/15 07:55, Federico Michele Facca wrote: https://wiki.openstack.org/wiki/ReleaseNotes/Juno Known Issues * When using libvirt, live snapshots are effectively disabled, due to this difficult-to-reproduce bug: https://bugs.launchpad.net/nova/+bug/1334398(https://review.openstack.org/#/c/102643/) * Glance v2 and Keystone v3 are not tested with Nova in Juno. On Wed, Apr 15, 2015 at 7:07 PM, Federico Michele Facca > wrote: i would say that the safe threashold is icehouse. tricks may work for havana and grizlly but tricks do not fall in "safe" until we test. On Wed, Apr 15, 2015 at 7:04 PM, Juanjo Hierro > wrote: Gentlemen, I need to know where to put a safe threshold (Grizzly,Havana, IceHouse, ...), so that last paragraph of Step 4 changes and I mention that all legacy users who get upgraded to become Community Users but were hosted on nodes not in version XXX of OpenStack or will have to migrate to other nodes (as per recommendation given in response to their request for the upgrade). I need this response URGENTLY. Best regards, -- Juanjo On 15/04/15 18:15, ?lvaro Alonso wrote: Hi, today tests made by Henar in havana suggest that havana is not compatible with v3. Federico found a post (https://www.mirantis.com/blog/manage-openstack-projects-using-domains-havana/) that says it is partially compatible but we are not sure of that. My understanding was that every nodes had to be migrated to Icehouse, for that reason I was only concerned by old spain node. @Federico, do you know haw many nodes are still Grizzly? The will be migrated before May 1? Is it possible to decide that if a node is not migrated to Icehouse by May 1, it will be out of the federation until it migrates? BR -- ?lvaro El 15 Apr 2015, a las 18:04, Juanjo Hierro > escribi?: On 15/04/15 05:58, Federico Michele Facca wrote: Dear Juanjo, some comments from my side: 1) Maurizio as XIFI coordinator, needs to be in the loop. While I agree that some nodes - probably like some GEs developers btw - don't deserve ths money they have been granted for the service given, any action and decision in this direction within XIFI is beyond my role. Not sure if and how saved money could be employed. Moved to FI-CORE? I have added him. 2) According to a short discussion I had with Alvaro, Migration to new IDM my affect as well other nodes still using Grizzly, this needs to be clarified asap in order to take proper actions (i.e. Accelerate migration plan). People from UPM has to clarify this URGENTLY. I was about to send an email to Basecamp sharing the plan (to show we are reacting and we have setup a Recovery Task Force but I want to know to what extend I have to modify anything in the description of the plan. 3) It is very important to agree on fair, objective and not arguable metrics to define performance. As early mentioned errors from tests due to finished resources do not mean "bad performance" (if not this would be the case as well for spain), this case is a more general issue related to the tools and functions provided on top of nodes, for which we cannot account them. Agreed. That's why, a) we will only be able to measure performance once nodes get cleaned b) we need to make sure that the tests run well (it is my impression that some of them do not give an accurate photo of the status) 4) There are nodes operating for "free", what should we do in such cases? I would keep possibility fir user with proper role to use them, regardeless, no financial penality can be passed over to them. We should come with a way to label the different nodes and let users take decision. Of course, there is no penalty that can be passed to them. But certainly something we can do is to put them in quarantine. Cheers, -- Juanjo when the message is finalized and agreed, i can inform lab nodes. Best, Federico ----------------------------------------- Apologizes for mispellings. My thumb is not compatible with Android On Apr 14, 2015 8:32 PM, "Juanjo Hierro" > wrote: Dear all, I have added Thierry Nagellen from Orange to this mailing list because despite he is not involved in the Task Force "per se", we are synchronized also with Orange overall with respect to messages to pass to the EC and rest of FI-PPP projects. If you believe someone else has to be in this list, please let me know. It has come out that deployment of the new IdM/Keystone is not feasible as planned. Therefore, we have to define a new plan. This morning, the TID team (including me) have had the opportunity to meet with the UPM team to understand the issue and we have come with an alternative plan for the recovery of the FIWARE Lab than the one we defined yesterday which sounds pretty reasonable and may help us to soon improve the situation. Let me summarize the plan in this email so that we are all on the same page. If you find some weakness/issue, please raise it. Otherwise, let's stick to it. Fortunately, the first steps remain the same and they have already been done, so we are on the right track. An important matter: I plan to send this plan to the EC tomorrow morning at 11:00. If you have comments, you should provide them before that deadline. I will also communicate this plan to FIWARE Accelerator projects on Basecamp as well as to Use Case projects through the FI-PPP mailing lists. Federico or Engineering should communicate this plan to organizations operating the FIWARE Lab nodes also at that time. A very sensible matter: when you review step 6 you will see that we cover the case in which some FIWARE Lab nodes may be put in quarantine. I would like to propose to the EC that those FIWARE lab nodes which are put into quarantine will be labeled as non-performance so they won't get the grant they were assigned in the XiFi Open Call, at least for the remaining of the XiFi project (until September). Maybe these funds can be given away to other partners or launch another Open Call. I would like to know your views on this. Step 1: reminder about new user account management policies enforcement. A first email aking existing FIWARE Lab users to accept the new user account management policies, also covered in the new FIWARE Lab use terms and conditions, was sent to all FIWARE Lab users several weeks ago. A reminder has been sent yesterday and today to current users of the FIWARE Lab telling them that they have until April 15th 2015 19:00 CET. This message will be disseminated through different means: * mailed to current users of the FIWARE Lab * shown in a screen at login of users of the FIWARE Lab * posted on Basecamp so that FIWARE accelerator projects get aware and can forward the remainder to SMEs/startups under their respective programmes * mailed to the FI-PPP SB and the old FI-PPP AB members so that coordinators/architects of the FIWARE Use Case projects can forward the reminder to SMEs/startups under their respective Use Case projects Step 2: Increase of computing capacity in Spain-2 node In parallel and starting TODAY, activities to expand the capacity of the recently launched Spain-2 node will be prioritized so that we reach a capacity of aprox 500 cores in the datacenters located in both Sevilla and Malaga. We expect this expansion be completed by April 20th if not earlier. Additionally, additional capacity (close to 500 additional cores) will be activated in the Spain-2 node with servers located in a new datacenter located in Las Palmas. Conversations are ongoing with Red.es trying to accelerate this process so that this additional 500 cores get available closer to the end of next week. Step 3: New Trial users only allowed to work on Spain-2 node. Limitation of number of concurrent trial users. Changes will be implemented in the Cloud portal and the user account registration process/tool by UPM so that new Trial users will only see the Spain-2 node. In addition, Trial users will be limited to 100 Trial users. Note that the "Trial Users", until the new IdM/Keystone component is deployed, will need to be identified by considering the creation of their user account. Actually, "Trial users" will be those users who have created their account after April 16th. Most likely, the fact that Trial users will only be allowed to work on Spain will remain. The number of Trial users allowed may increase (the EC has shown its concern about keeping the number of Trial users too low) but will see. Users who try to create an account when the limit on Trial users have been reached, will receive a message indicating that the limit has been reached, inviting them to try again in two weeks (Fernando to send the wording for this message to UPM). This step should be implemented by this Wednesday April 15th. Step 4: Freeing resources on current nodes, giving users the ability to apply to become community users, asking users in Spain-1 and Prague to migrate Starting April 16th, current nodes will free resources on their nodes (virtual infrastructure and public IP addresses allocated to users who didn't accept the new user account management policies). They should complete this process before April 23rd. FIWARE Lab node providers are aware of the current situation so they should accelerate this process as much as possible, trying to complete the process the sooner the better. Situation will be assessed on April 20th and April 23rd. It is expected that the status of the FIWARE Lab will improve drastically during the week and will become stable by April 23rd. In parallel, we will encourage legacy users (those who created their account before April 16th and have accepted the new terms and conditions) to apply for becoming community users. They should be able to submit their application completing an application form that will be provided to them and will be made available on the Cloud Portal. Those legacy users whose application is accepted and who were hosted in the Spain-1 or the Prague nodes will be asked to migrate their environments to any of the other nodes (a recommendation will be given). The Spain-1 and the Prague nodes will not host community users. As a result, no users will remain in these two nodes by May 1st. Step 5: Deployment of new IdM/Keystone component and upgrading of Community Users. Migration of Spain-1 and Prague nodes to OpenStack Juno. This step will start May 1st. Then, we will deploy the new version of the IdM/Keystone component. Users whose application to become Community Users has been approved will become Community Users. Environments of those Trial users who has overpass the 2 weeks trial period will be cleaned out. From then on, the new user account management policies will be in place, with the new IdM/keystone component supporting the ability to distinguish between kind of users and the nodes each will be able to get access to. In parallel, Spain-1 and Prague nodes should start their migration to Juno. Once they migrate, they will be made available as part of the federation (maybe the physical resources allocated to the Spain-1 node will be assigned to the Spain-2 node). Step 6: Assessment of nodes in the FIWARE Lab federation. Bringing FIWARE Lab nodes into quarantine. After April 23th, performance of the several nodes in the FIWARE Lab federation will be weekly assessed. Those nodes who exhibit a bad performance (instability, low response to request for help by users) will be put into quarantine and their users (Community Users) will be asked to migrate to the Spain-2 node. 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 ________________________________ 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 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 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 _______________________________________________ Fiware-lab-recovery-tf mailing list 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 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 _______________________________________________ Fiware-lab-recovery-tf mailing list Fiware-lab-recovery-tf at lists.fiware.org https://lists.fiware.org/listinfo/fiware-lab-recovery-tf -- -- 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 -- -- 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 _______________________________________________ Fiware-lab-recovery-tf mailing list Fiware-lab-recovery-tf at lists.fiware.org https://lists.fiware.org/listinfo/fiware-lab-recovery-tf ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From federico.facca at create-net.org Thu Apr 16 08:43:20 2015 From: federico.facca at create-net.org (Federico Michele Facca) Date: Thu, 16 Apr 2015 08:43:20 +0200 Subject: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab In-Reply-To: <552F5525.90509@telefonica.com> References: <552D5D25.1060506@telefonica.com> <552E8C06.1020105@telefonica.com> <3964F66E-FA4A-409A-AACE-F68AB0E15E22@dit.upm.es> <552E9A12.7040407@telefonica.com> <552F5525.90509@telefonica.com> Message-ID: to be honest I am not sure, have been using juno and icehouse without problems, but always using keystone v2 as far as i know. i will ask internally. On Thu, Apr 16, 2015 at 8:22 AM, Juanjo Hierro < juanjose.hierro at telefonica.com> wrote: > > Does this mean that we are going to have a problem with Juno and the new > IdM/Keystone ? > > > On 16/04/15 07:55, Federico Michele Facca wrote: > > https://wiki.openstack.org/wiki/ReleaseNotes/Juno > > Known Issues > > - When using libvirt, live snapshots are effectively disabled, due to > this difficult-to-reproduce bug: > https://bugs.launchpad.net/nova/+bug/1334398( > https://review.openstack.org/#/c/102643/) > - Glance v2 and Keystone v3 are not tested with Nova in Juno. > > > On Wed, Apr 15, 2015 at 7:07 PM, Federico Michele Facca < > federico.facca at create-net.org> wrote: > >> i would say that the safe threashold is icehouse. tricks may work for >> havana and grizlly but tricks do not fall in "safe" until we test. >> >> On Wed, Apr 15, 2015 at 7:04 PM, Juanjo Hierro < >> juanjose.hierro at telefonica.com> wrote: >> >>> Gentlemen, >>> >>> I need to know where to put a safe threshold (Grizzly,Havana, >>> IceHouse, ...), so that last paragraph of Step 4 changes and I mention that >>> all legacy users who get upgraded to become Community Users but were hosted >>> on nodes not in version XXX of OpenStack or will have to migrate to other >>> nodes (as per recommendation given in response to their request for the >>> upgrade). >>> >>> I need this response URGENTLY. >>> >>> Best regards, >>> >>> -- Juanjo >>> >>> >>> On 15/04/15 18:15, ?lvaro Alonso wrote: >>> >>> Hi, >>> >>> today tests made by Henar in havana suggest that havana is not >>> compatible with v3. Federico found a post ( >>> https://www.mirantis.com/blog/manage-openstack-projects-using-domains-havana/) >>> that says it is partially compatible but we are not sure of that. >>> >>> My understanding was that every nodes had to be migrated to Icehouse, >>> for that reason I was only concerned by old spain node. >>> >>> @Federico, do you know haw many nodes are still Grizzly? The will be >>> migrated before May 1? Is it possible to decide that if a node is not >>> migrated to Icehouse by May 1, it will be out of the federation until it >>> migrates? >>> >>> BR >>> -- >>> ?lvaro >>> >>> El 15 Apr 2015, a las 18:04, Juanjo Hierro < >>> juanjose.hierro at telefonica.com> escribi?: >>> >>> >>> >>> On 15/04/15 05:58, Federico Michele Facca wrote: >>> >>> Dear Juanjo, >>> some comments from my side: >>> >>> 1) Maurizio as XIFI coordinator, needs to be in the loop. While I agree >>> that some nodes - probably like some GEs developers btw - don't deserve ths >>> money they have been granted for the service given, any action and decision >>> in this direction within XIFI is beyond my role. Not sure if and how saved >>> money could be employed. Moved to FI-CORE? >>> >>> >>> I have added him. >>> >>> 2) According to a short discussion I had with Alvaro, Migration to new >>> IDM my affect as well other nodes still using Grizzly, this needs to be >>> clarified asap in order to take proper actions (i.e. Accelerate migration >>> plan). >>> >>> >>> People from UPM has to clarify this URGENTLY. I was about to send an >>> email to Basecamp sharing the plan (to show we are reacting and we have >>> setup a Recovery Task Force but I want to know to what extend I have to >>> modify anything in the description of the plan. >>> >>> >>> 3) It is very important to agree on fair, objective and not arguable >>> metrics to define performance. As early mentioned errors from tests due to >>> finished resources do not mean "bad performance" (if not this would be the >>> case as well for spain), this case is a more general issue related to the >>> tools and functions provided on top of nodes, for which we cannot account >>> them. >>> >>> >>> Agreed. That's why, a) we will only be able to measure performance >>> once nodes get cleaned b) we need to make sure that the tests run well (it >>> is my impression that some of them do not give an accurate photo of the >>> status) >>> >>> 4) There are nodes operating for "free", what should we do in such >>> cases? I would keep possibility fir user with proper role to use them, >>> regardeless, no financial penality can be passed over to them. >>> >>> >>> We should come with a way to label the different nodes and let users >>> take decision. Of course, there is no penalty that can be passed to >>> them. But certainly something we can do is to put them in quarantine. >>> >>> Cheers, >>> >>> -- Juanjo >>> >>> when the message is finalized and agreed, i can inform lab nodes. >>> >>> Best, >>> Federico >>> >>> ----------------------------------------- >>> Apologizes for mispellings. My thumb is not compatible with Android >>> On Apr 14, 2015 8:32 PM, "Juanjo Hierro" >>> wrote: >>> >>>> Dear all, >>>> >>>> I have added Thierry Nagellen from Orange to this mailing list >>>> because despite he is not involved in the Task Force "per se", we are >>>> synchronized also with Orange overall with respect to messages to pass to >>>> the EC and rest of FI-PPP projects. If you believe someone else has to be >>>> in this list, please let me know. >>>> >>>> It has come out that deployment of the new IdM/Keystone is not >>>> feasible as planned. Therefore, we have to define a new plan. >>>> >>>> This morning, the TID team (including me) have had the opportunity to >>>> meet with the UPM team to understand the issue and we have come with an >>>> alternative plan for the recovery of the FIWARE Lab than the one we defined >>>> yesterday which sounds pretty reasonable and may help us to soon improve >>>> the situation. >>>> >>>> Let me summarize the plan in this email so that we are all on the >>>> same page. If you find some weakness/issue, please raise it. Otherwise, >>>> let's stick to it. Fortunately, the first steps remain the same and they >>>> have already been done, so we are on the right track. >>>> >>>> An important matter: I plan to send this plan to the EC tomorrow >>>> morning at 11:00. If you have comments, you should provide them before >>>> that deadline. I will also communicate this plan to FIWARE Accelerator >>>> projects on Basecamp as well as to Use Case projects through the FI-PPP >>>> mailing lists. Federico or Engineering should communicate this plan to >>>> organizations operating the FIWARE Lab nodes also at that time. >>>> >>>> A very sensible matter: when you review step 6 you will see that we >>>> cover the case in which some FIWARE Lab nodes may be put in quarantine. I >>>> would like to propose to the EC that those FIWARE lab nodes which are put >>>> into quarantine will be labeled as non-performance so they won't get the >>>> grant they were assigned in the XiFi Open Call, at least for the remaining >>>> of the XiFi project (until September). Maybe these funds can be given >>>> away to other partners or launch another Open Call. I would like to know >>>> your views on this. >>>> >>>> >>>> *Step 1: reminder about new user account management policies >>>> enforcement.* >>>> >>>> A first email aking existing FIWARE Lab users to accept the new user >>>> account management policies, also covered in the new FIWARE Lab use terms >>>> and conditions, was sent to all FIWARE Lab users several weeks ago. >>>> >>>> A reminder has been sent yesterday and today to current users of the >>>> FIWARE Lab telling them that they have until April 15th 2015 19:00 CET. >>>> This message will be disseminated through different means: >>>> >>>> - mailed to current users of the FIWARE Lab >>>> - shown in a screen at login of users of the FIWARE Lab >>>> - posted on Basecamp so that FIWARE accelerator projects get aware >>>> and can forward the remainder to SMEs/startups under their respective >>>> programmes >>>> - mailed to the FI-PPP SB and the old FI-PPP AB members so that >>>> coordinators/architects of the FIWARE Use Case projects can forward the >>>> reminder to SMEs/startups under their respective Use Case projects >>>> >>>> >>>> *Step 2: Increase of computing capacity in Spain-2 node* >>>> In parallel and starting TODAY, activities to expand the capacity of >>>> the recently launched Spain-2 node will be prioritized so that we reach a >>>> capacity of aprox 500 cores in the datacenters located in both Sevilla and >>>> Malaga. We expect this expansion be completed by April 20th if not >>>> earlier. >>>> >>>> Additionally, additional capacity (close to 500 additional cores) >>>> will be activated in the Spain-2 node with servers located in a new >>>> datacenter located in Las Palmas. Conversations are ongoing with >>>> Red.es trying to accelerate this process so that this additional 500 >>>> cores get available closer to the end of next week. >>>> >>>> >>>> *Step 3: New Trial users only allowed to work on Spain-2 node**. >>>> Limitation of number of concurrent trial users.* >>>> >>>> Changes will be implemented in the Cloud portal and the user account >>>> registration process/tool by UPM so that new Trial users will only see the >>>> Spain-2 node. In addition, Trial users will be limited to 100 Trial users. >>>> >>>> Note that the "Trial Users", until the new IdM/Keystone component is >>>> deployed, will need to be identified by considering the creation of their >>>> user account. Actually, "Trial users" will be those users who have >>>> created their account after April 16th. >>>> >>>> Most likely, the fact that Trial users will only be allowed to work >>>> on Spain will remain. The number of Trial users allowed may increase (the >>>> EC has shown its concern about keeping the number of Trial users too low) >>>> but will see. >>>> >>>> Users who try to create an account when the limit on Trial users have >>>> been reached, will receive a message indicating that the limit has been >>>> reached, inviting them to try again in two weeks (Fernando to send the >>>> wording for this message to UPM). >>>> >>>> This step should be implemented by this Wednesday April 15th. >>>> >>>> >>>> *Step 4: Freeing resources on current nodes**, giving users the >>>> ability to apply to become community users, asking users in Spain-1 and >>>> Prague to migrate* >>>> >>>> Starting April 16th, current nodes will free resources on their nodes >>>> (virtual infrastructure and public IP addresses allocated to users who >>>> didn't accept the new user account management policies). >>>> >>>> They should complete this process before April 23rd. FIWARE Lab >>>> node providers are aware of the current situation so they should accelerate >>>> this process as much as possible, trying to complete the process the sooner >>>> the better. Situation will be assessed on April 20th and April 23rd. >>>> It is expected that the status of the FIWARE Lab will improve drastically >>>> during the week and will become stable by April 23rd. >>>> >>>> In parallel, we will encourage legacy users (those who created their >>>> account before April 16th and have accepted the new terms and conditions) >>>> to apply for becoming community users. They should be able to submit >>>> their application completing an application form that will be provided to >>>> them and will be made available on the Cloud Portal. >>>> >>>> Those legacy users whose application is accepted and who were hosted >>>> in the Spain-1 or the Prague nodes will be asked to migrate their >>>> environments to any of the other nodes (a recommendation will be given). >>>> The Spain-1 and the Prague nodes will not host community users. As a >>>> result, no users will remain in these two nodes by May 1st. >>>> >>>> >>>> *Step 5: Deployment of new IdM/Keystone component and upgrading of >>>> Community Users*. * Migration of Spain-1 and Prague nodes to >>>> OpenStack Juno.* >>>> >>>> This step will start May 1st. Then, we will deploy the new version >>>> of the IdM/Keystone component. >>>> >>>> Users whose application to become Community Users has been approved >>>> will become Community Users. Environments of those Trial users who has >>>> overpass the 2 weeks trial period will be cleaned out. From then on, the >>>> new user account management policies will be in place, with the new >>>> IdM/keystone component supporting the ability to distinguish between kind >>>> of users and the nodes each will be able to get access to. >>>> >>>> In parallel, Spain-1 and Prague nodes should start their migration to >>>> Juno. Once they migrate, they will be made available as part of the >>>> federation (maybe the physical resources allocated to the Spain-1 node will >>>> be assigned to the Spain-2 node). >>>> >>>> >>>> *Step 6: Assessment of nodes in the FIWARE Lab federation. Bringing >>>> FIWARE Lab nodes into quarantine.* >>>> >>>> After April 23th, performance of the several nodes in the FIWARE Lab >>>> federation will be weekly assessed. Those nodes who exhibit a bad >>>> performance (instability, low response to request for help by users) will >>>> be put into quarantine and their users (Community Users) will be asked to >>>> migrate to the Spain-2 node. >>>> >>>> >>>> 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 >>>> >>>> >>>> ------------------------------ >>>> >>>> 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 >>>> 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 >>> 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 >>> _______________________________________________ >>> Fiware-lab-recovery-tf mailing list >>> 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 >>> 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 >>> >>> _______________________________________________ >>> Fiware-lab-recovery-tf mailing list >>> Fiware-lab-recovery-tf at lists.fiware.org >>> https://lists.fiware.org/listinfo/fiware-lab-recovery-tf >>> >>> >> >> >> -- >> -- >> 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 >> > > > > -- > -- > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From juanjose.hierro at telefonica.com Thu Apr 16 12:11:06 2015 From: juanjose.hierro at telefonica.com (JUAN JOSE HIERRO SUREDA) Date: Thu, 16 Apr 2015 10:11:06 +0000 Subject: [Fiware-lab-recovery-tf] FIWARE Lab Recovery Task Force - Daily meeting Message-ID: ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3452 bytes Desc: not available URL: From fernando.lopezaguilar at telefonica.com Thu Apr 16 13:31:16 2015 From: fernando.lopezaguilar at telefonica.com (FERNANDO LOPEZ AGUILAR) Date: Thu, 16 Apr 2015 11:31:16 +0000 Subject: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab In-Reply-To: References: <552D5D25.1060506@telefonica.com> <552E8C06.1020105@telefonica.com> <3964F66E-FA4A-409A-AACE-F68AB0E15E22@dit.upm.es> <552E9A12.7040407@telefonica.com> <552F5525.90509@telefonica.com> Message-ID: Well, let me share my thinks about it. OpenStack is working properly both v2 and v3 APIs of Keystone (except for the not testing one in nova). Like any other APIs, I think that it should access to the same stored information in the DB. So, what is the problem if the IdM and its portal use the v3 API and OpenStack services use the v2 API? De: Federico Michele Facca > Fecha: Thursday 16 April 2015 08:43 Para: JUAN JOSE HIERRO SUREDA > CC: "fiware-lab-recovery-tf at lists.fiware.org" > Asunto: Re: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab to be honest I am not sure, have been using juno and icehouse without problems, but always using keystone v2 as far as i know. i will ask internally. On Thu, Apr 16, 2015 at 8:22 AM, Juanjo Hierro > wrote: Does this mean that we are going to have a problem with Juno and the new IdM/Keystone ? On 16/04/15 07:55, Federico Michele Facca wrote: https://wiki.openstack.org/wiki/ReleaseNotes/Juno Known Issues * When using libvirt, live snapshots are effectively disabled, due to this difficult-to-reproduce bug: https://bugs.launchpad.net/nova/+bug/1334398(https://review.openstack.org/#/c/102643/) * Glance v2 and Keystone v3 are not tested with Nova in Juno. On Wed, Apr 15, 2015 at 7:07 PM, Federico Michele Facca > wrote: i would say that the safe threashold is icehouse. tricks may work for havana and grizlly but tricks do not fall in "safe" until we test. On Wed, Apr 15, 2015 at 7:04 PM, Juanjo Hierro > wrote: Gentlemen, I need to know where to put a safe threshold (Grizzly,Havana, IceHouse, ...), so that last paragraph of Step 4 changes and I mention that all legacy users who get upgraded to become Community Users but were hosted on nodes not in version XXX of OpenStack or will have to migrate to other nodes (as per recommendation given in response to their request for the upgrade). I need this response URGENTLY. Best regards, -- Juanjo On 15/04/15 18:15, ?lvaro Alonso wrote: Hi, today tests made by Henar in havana suggest that havana is not compatible with v3. Federico found a post (https://www.mirantis.com/blog/manage-openstack-projects-using-domains-havana/) that says it is partially compatible but we are not sure of that. My understanding was that every nodes had to be migrated to Icehouse, for that reason I was only concerned by old spain node. @Federico, do you know haw many nodes are still Grizzly? The will be migrated before May 1? Is it possible to decide that if a node is not migrated to Icehouse by May 1, it will be out of the federation until it migrates? BR -- ?lvaro El 15 Apr 2015, a las 18:04, Juanjo Hierro > escribi?: On 15/04/15 05:58, Federico Michele Facca wrote: Dear Juanjo, some comments from my side: 1) Maurizio as XIFI coordinator, needs to be in the loop. While I agree that some nodes - probably like some GEs developers btw - don't deserve ths money they have been granted for the service given, any action and decision in this direction within XIFI is beyond my role. Not sure if and how saved money could be employed. Moved to FI-CORE? I have added him. 2) According to a short discussion I had with Alvaro, Migration to new IDM my affect as well other nodes still using Grizzly, this needs to be clarified asap in order to take proper actions (i.e. Accelerate migration plan). People from UPM has to clarify this URGENTLY. I was about to send an email to Basecamp sharing the plan (to show we are reacting and we have setup a Recovery Task Force but I want to know to what extend I have to modify anything in the description of the plan. 3) It is very important to agree on fair, objective and not arguable metrics to define performance. As early mentioned errors from tests due to finished resources do not mean "bad performance" (if not this would be the case as well for spain), this case is a more general issue related to the tools and functions provided on top of nodes, for which we cannot account them. Agreed. That's why, a) we will only be able to measure performance once nodes get cleaned b) we need to make sure that the tests run well (it is my impression that some of them do not give an accurate photo of the status) 4) There are nodes operating for "free", what should we do in such cases? I would keep possibility fir user with proper role to use them, regardeless, no financial penality can be passed over to them. We should come with a way to label the different nodes and let users take decision. Of course, there is no penalty that can be passed to them. But certainly something we can do is to put them in quarantine. Cheers, -- Juanjo when the message is finalized and agreed, i can inform lab nodes. Best, Federico ----------------------------------------- Apologizes for mispellings. My thumb is not compatible with Android On Apr 14, 2015 8:32 PM, "Juanjo Hierro" > wrote: Dear all, I have added Thierry Nagellen from Orange to this mailing list because despite he is not involved in the Task Force "per se", we are synchronized also with Orange overall with respect to messages to pass to the EC and rest of FI-PPP projects. If you believe someone else has to be in this list, please let me know. It has come out that deployment of the new IdM/Keystone is not feasible as planned. Therefore, we have to define a new plan. This morning, the TID team (including me) have had the opportunity to meet with the UPM team to understand the issue and we have come with an alternative plan for the recovery of the FIWARE Lab than the one we defined yesterday which sounds pretty reasonable and may help us to soon improve the situation. Let me summarize the plan in this email so that we are all on the same page. If you find some weakness/issue, please raise it. Otherwise, let's stick to it. Fortunately, the first steps remain the same and they have already been done, so we are on the right track. An important matter: I plan to send this plan to the EC tomorrow morning at 11:00. If you have comments, you should provide them before that deadline. I will also communicate this plan to FIWARE Accelerator projects on Basecamp as well as to Use Case projects through the FI-PPP mailing lists. Federico or Engineering should communicate this plan to organizations operating the FIWARE Lab nodes also at that time. A very sensible matter: when you review step 6 you will see that we cover the case in which some FIWARE Lab nodes may be put in quarantine. I would like to propose to the EC that those FIWARE lab nodes which are put into quarantine will be labeled as non-performance so they won't get the grant they were assigned in the XiFi Open Call, at least for the remaining of the XiFi project (until September). Maybe these funds can be given away to other partners or launch another Open Call. I would like to know your views on this. Step 1: reminder about new user account management policies enforcement. A first email aking existing FIWARE Lab users to accept the new user account management policies, also covered in the new FIWARE Lab use terms and conditions, was sent to all FIWARE Lab users several weeks ago. A reminder has been sent yesterday and today to current users of the FIWARE Lab telling them that they have until April 15th 2015 19:00 CET. This message will be disseminated through different means: * mailed to current users of the FIWARE Lab * shown in a screen at login of users of the FIWARE Lab * posted on Basecamp so that FIWARE accelerator projects get aware and can forward the remainder to SMEs/startups under their respective programmes * mailed to the FI-PPP SB and the old FI-PPP AB members so that coordinators/architects of the FIWARE Use Case projects can forward the reminder to SMEs/startups under their respective Use Case projects Step 2: Increase of computing capacity in Spain-2 node In parallel and starting TODAY, activities to expand the capacity of the recently launched Spain-2 node will be prioritized so that we reach a capacity of aprox 500 cores in the datacenters located in both Sevilla and Malaga. We expect this expansion be completed by April 20th if not earlier. Additionally, additional capacity (close to 500 additional cores) will be activated in the Spain-2 node with servers located in a new datacenter located in Las Palmas. Conversations are ongoing with Red.es trying to accelerate this process so that this additional 500 cores get available closer to the end of next week. Step 3: New Trial users only allowed to work on Spain-2 node. Limitation of number of concurrent trial users. Changes will be implemented in the Cloud portal and the user account registration process/tool by UPM so that new Trial users will only see the Spain-2 node. In addition, Trial users will be limited to 100 Trial users. Note that the "Trial Users", until the new IdM/Keystone component is deployed, will need to be identified by considering the creation of their user account. Actually, "Trial users" will be those users who have created their account after April 16th. Most likely, the fact that Trial users will only be allowed to work on Spain will remain. The number of Trial users allowed may increase (the EC has shown its concern about keeping the number of Trial users too low) but will see. Users who try to create an account when the limit on Trial users have been reached, will receive a message indicating that the limit has been reached, inviting them to try again in two weeks (Fernando to send the wording for this message to UPM). This step should be implemented by this Wednesday April 15th. Step 4: Freeing resources on current nodes, giving users the ability to apply to become community users, asking users in Spain-1 and Prague to migrate Starting April 16th, current nodes will free resources on their nodes (virtual infrastructure and public IP addresses allocated to users who didn't accept the new user account management policies). They should complete this process before April 23rd. FIWARE Lab node providers are aware of the current situation so they should accelerate this process as much as possible, trying to complete the process the sooner the better. Situation will be assessed on April 20th and April 23rd. It is expected that the status of the FIWARE Lab will improve drastically during the week and will become stable by April 23rd. In parallel, we will encourage legacy users (those who created their account before April 16th and have accepted the new terms and conditions) to apply for becoming community users. They should be able to submit their application completing an application form that will be provided to them and will be made available on the Cloud Portal. Those legacy users whose application is accepted and who were hosted in the Spain-1 or the Prague nodes will be asked to migrate their environments to any of the other nodes (a recommendation will be given). The Spain-1 and the Prague nodes will not host community users. As a result, no users will remain in these two nodes by May 1st. Step 5: Deployment of new IdM/Keystone component and upgrading of Community Users. Migration of Spain-1 and Prague nodes to OpenStack Juno. This step will start May 1st. Then, we will deploy the new version of the IdM/Keystone component. Users whose application to become Community Users has been approved will become Community Users. Environments of those Trial users who has overpass the 2 weeks trial period will be cleaned out. From then on, the new user account management policies will be in place, with the new IdM/keystone component supporting the ability to distinguish between kind of users and the nodes each will be able to get access to. In parallel, Spain-1 and Prague nodes should start their migration to Juno. Once they migrate, they will be made available as part of the federation (maybe the physical resources allocated to the Spain-1 node will be assigned to the Spain-2 node). Step 6: Assessment of nodes in the FIWARE Lab federation. Bringing FIWARE Lab nodes into quarantine. After April 23th, performance of the several nodes in the FIWARE Lab federation will be weekly assessed. Those nodes who exhibit a bad performance (instability, low response to request for help by users) will be put into quarantine and their users (Community Users) will be asked to migrate to the Spain-2 node. 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 ________________________________ 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 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 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 _______________________________________________ Fiware-lab-recovery-tf mailing list 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 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 _______________________________________________ Fiware-lab-recovery-tf mailing list Fiware-lab-recovery-tf at lists.fiware.org https://lists.fiware.org/listinfo/fiware-lab-recovery-tf -- -- 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 -- -- 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 ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From federico.facca at create-net.org Thu Apr 16 13:41:38 2015 From: federico.facca at create-net.org (Federico Michele Facca) Date: Thu, 16 Apr 2015 13:41:38 +0200 Subject: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab In-Reply-To: References: <552D5D25.1060506@telefonica.com> <552E8C06.1020105@telefonica.com> <3964F66E-FA4A-409A-AACE-F68AB0E15E22@dit.upm.es> <552E9A12.7040407@telefonica.com> <552F5525.90509@telefonica.com> Message-ID: as i was commenting to fernando on skype, all services (e.g. nova) are always backward compatible, i.e. nova can offer at the same time api v2 and api v3. so it looks strange if the case of keystone it's different. but we need to test of course. federico On Thu, Apr 16, 2015 at 1:31 PM, FERNANDO LOPEZ AGUILAR < fernando.lopezaguilar at telefonica.com> wrote: > Well, let me share my thinks about it. OpenStack is working properly > both v2 and v3 APIs of Keystone (except for the not testing one in nova). > Like any other APIs, I think that it should access to the same stored > information in the DB. So, what is the problem if the IdM and its portal > use the v3 API and OpenStack services use the v2 API? > > De: Federico Michele Facca > Fecha: Thursday 16 April 2015 08:43 > Para: JUAN JOSE HIERRO SUREDA > CC: "fiware-lab-recovery-tf at lists.fiware.org" < > fiware-lab-recovery-tf at lists.fiware.org> > Asunto: Re: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of > the FIWARE Lab > > to be honest I am not sure, have been using juno and icehouse without > problems, but always using keystone v2 as far as i know. i will ask > internally. > > On Thu, Apr 16, 2015 at 8:22 AM, Juanjo Hierro < > juanjose.hierro at telefonica.com> wrote: > >> >> Does this mean that we are going to have a problem with Juno and the >> new IdM/Keystone ? >> >> >> On 16/04/15 07:55, Federico Michele Facca wrote: >> >> https://wiki.openstack.org/wiki/ReleaseNotes/Juno >> >> Known Issues >> >> - When using libvirt, live snapshots are effectively disabled, due to >> this difficult-to-reproduce bug: >> https://bugs.launchpad.net/nova/+bug/1334398( >> https://review.openstack.org/#/c/102643/) >> - Glance v2 and Keystone v3 are not tested with Nova in Juno. >> >> >> On Wed, Apr 15, 2015 at 7:07 PM, Federico Michele Facca < >> federico.facca at create-net.org> wrote: >> >>> i would say that the safe threashold is icehouse. tricks may work for >>> havana and grizlly but tricks do not fall in "safe" until we test. >>> >>> On Wed, Apr 15, 2015 at 7:04 PM, Juanjo Hierro < >>> juanjose.hierro at telefonica.com> wrote: >>> >>>> Gentlemen, >>>> >>>> I need to know where to put a safe threshold (Grizzly,Havana, >>>> IceHouse, ...), so that last paragraph of Step 4 changes and I mention that >>>> all legacy users who get upgraded to become Community Users but were hosted >>>> on nodes not in version XXX of OpenStack or will have to migrate to other >>>> nodes (as per recommendation given in response to their request for the >>>> upgrade). >>>> >>>> I need this response URGENTLY. >>>> >>>> Best regards, >>>> >>>> -- Juanjo >>>> >>>> >>>> On 15/04/15 18:15, ?lvaro Alonso wrote: >>>> >>>> Hi, >>>> >>>> today tests made by Henar in havana suggest that havana is not >>>> compatible with v3. Federico found a post ( >>>> https://www.mirantis.com/blog/manage-openstack-projects-using-domains-havana/) >>>> that says it is partially compatible but we are not sure of that. >>>> >>>> My understanding was that every nodes had to be migrated to Icehouse, >>>> for that reason I was only concerned by old spain node. >>>> >>>> @Federico, do you know haw many nodes are still Grizzly? The will be >>>> migrated before May 1? Is it possible to decide that if a node is not >>>> migrated to Icehouse by May 1, it will be out of the federation until it >>>> migrates? >>>> >>>> BR >>>> -- >>>> ?lvaro >>>> >>>> El 15 Apr 2015, a las 18:04, Juanjo Hierro < >>>> juanjose.hierro at telefonica.com> escribi?: >>>> >>>> >>>> >>>> On 15/04/15 05:58, Federico Michele Facca wrote: >>>> >>>> Dear Juanjo, >>>> some comments from my side: >>>> >>>> 1) Maurizio as XIFI coordinator, needs to be in the loop. While I agree >>>> that some nodes - probably like some GEs developers btw - don't deserve ths >>>> money they have been granted for the service given, any action and decision >>>> in this direction within XIFI is beyond my role. Not sure if and how saved >>>> money could be employed. Moved to FI-CORE? >>>> >>>> >>>> I have added him. >>>> >>>> 2) According to a short discussion I had with Alvaro, Migration to >>>> new IDM my affect as well other nodes still using Grizzly, this needs to be >>>> clarified asap in order to take proper actions (i.e. Accelerate migration >>>> plan). >>>> >>>> >>>> People from UPM has to clarify this URGENTLY. I was about to send >>>> an email to Basecamp sharing the plan (to show we are reacting and we have >>>> setup a Recovery Task Force but I want to know to what extend I have to >>>> modify anything in the description of the plan. >>>> >>>> >>>> 3) It is very important to agree on fair, objective and not arguable >>>> metrics to define performance. As early mentioned errors from tests due to >>>> finished resources do not mean "bad performance" (if not this would be the >>>> case as well for spain), this case is a more general issue related to the >>>> tools and functions provided on top of nodes, for which we cannot account >>>> them. >>>> >>>> >>>> Agreed. That's why, a) we will only be able to measure performance >>>> once nodes get cleaned b) we need to make sure that the tests run well (it >>>> is my impression that some of them do not give an accurate photo of the >>>> status) >>>> >>>> 4) There are nodes operating for "free", what should we do in such >>>> cases? I would keep possibility fir user with proper role to use them, >>>> regardeless, no financial penality can be passed over to them. >>>> >>>> >>>> We should come with a way to label the different nodes and let users >>>> take decision. Of course, there is no penalty that can be passed to >>>> them. But certainly something we can do is to put them in quarantine. >>>> >>>> Cheers, >>>> >>>> -- Juanjo >>>> >>>> when the message is finalized and agreed, i can inform lab nodes. >>>> >>>> Best, >>>> Federico >>>> >>>> ----------------------------------------- >>>> Apologizes for mispellings. My thumb is not compatible with Android >>>> On Apr 14, 2015 8:32 PM, "Juanjo Hierro" < >>>> juanjose.hierro at telefonica.com> wrote: >>>> >>>>> Dear all, >>>>> >>>>> I have added Thierry Nagellen from Orange to this mailing list >>>>> because despite he is not involved in the Task Force "per se", we are >>>>> synchronized also with Orange overall with respect to messages to pass to >>>>> the EC and rest of FI-PPP projects. If you believe someone else has to be >>>>> in this list, please let me know. >>>>> >>>>> It has come out that deployment of the new IdM/Keystone is not >>>>> feasible as planned. Therefore, we have to define a new plan. >>>>> >>>>> This morning, the TID team (including me) have had the opportunity >>>>> to meet with the UPM team to understand the issue and we have come with an >>>>> alternative plan for the recovery of the FIWARE Lab than the one we defined >>>>> yesterday which sounds pretty reasonable and may help us to soon improve >>>>> the situation. >>>>> >>>>> Let me summarize the plan in this email so that we are all on the >>>>> same page. If you find some weakness/issue, please raise it. Otherwise, >>>>> let's stick to it. Fortunately, the first steps remain the same and they >>>>> have already been done, so we are on the right track. >>>>> >>>>> An important matter: I plan to send this plan to the EC tomorrow >>>>> morning at 11:00. If you have comments, you should provide them before >>>>> that deadline. I will also communicate this plan to FIWARE Accelerator >>>>> projects on Basecamp as well as to Use Case projects through the FI-PPP >>>>> mailing lists. Federico or Engineering should communicate this plan to >>>>> organizations operating the FIWARE Lab nodes also at that time. >>>>> >>>>> A very sensible matter: when you review step 6 you will see that we >>>>> cover the case in which some FIWARE Lab nodes may be put in quarantine. I >>>>> would like to propose to the EC that those FIWARE lab nodes which are put >>>>> into quarantine will be labeled as non-performance so they won't get the >>>>> grant they were assigned in the XiFi Open Call, at least for the remaining >>>>> of the XiFi project (until September). Maybe these funds can be given >>>>> away to other partners or launch another Open Call. I would like to know >>>>> your views on this. >>>>> >>>>> >>>>> *Step 1: reminder about new user account management policies >>>>> enforcement.* >>>>> >>>>> A first email aking existing FIWARE Lab users to accept the new user >>>>> account management policies, also covered in the new FIWARE Lab use terms >>>>> and conditions, was sent to all FIWARE Lab users several weeks ago. >>>>> >>>>> A reminder has been sent yesterday and today to current users of the >>>>> FIWARE Lab telling them that they have until April 15th 2015 19:00 CET. >>>>> This message will be disseminated through different means: >>>>> >>>>> - mailed to current users of the FIWARE Lab >>>>> - shown in a screen at login of users of the FIWARE Lab >>>>> - posted on Basecamp so that FIWARE accelerator projects get aware >>>>> and can forward the remainder to SMEs/startups under their respective >>>>> programmes >>>>> - mailed to the FI-PPP SB and the old FI-PPP AB members so that >>>>> coordinators/architects of the FIWARE Use Case projects can forward the >>>>> reminder to SMEs/startups under their respective Use Case projects >>>>> >>>>> >>>>> *Step 2: Increase of computing capacity in Spain-2 node* >>>>> In parallel and starting TODAY, activities to expand the capacity >>>>> of the recently launched Spain-2 node will be prioritized so that we reach >>>>> a capacity of aprox 500 cores in the datacenters located in both Sevilla >>>>> and Malaga. We expect this expansion be completed by April 20th if not >>>>> earlier. >>>>> >>>>> Additionally, additional capacity (close to 500 additional cores) >>>>> will be activated in the Spain-2 node with servers located in a new >>>>> datacenter located in Las Palmas. Conversations are ongoing with >>>>> Red.es trying to accelerate this process so that this additional 500 >>>>> cores get available closer to the end of next week. >>>>> >>>>> >>>>> *Step 3: New Trial users only allowed to work on Spain-2 node**. >>>>> Limitation of number of concurrent trial users.* >>>>> >>>>> Changes will be implemented in the Cloud portal and the user account >>>>> registration process/tool by UPM so that new Trial users will only see the >>>>> Spain-2 node. In addition, Trial users will be limited to 100 Trial users. >>>>> >>>>> Note that the "Trial Users", until the new IdM/Keystone component is >>>>> deployed, will need to be identified by considering the creation of their >>>>> user account. Actually, "Trial users" will be those users who have >>>>> created their account after April 16th. >>>>> >>>>> Most likely, the fact that Trial users will only be allowed to work >>>>> on Spain will remain. The number of Trial users allowed may increase (the >>>>> EC has shown its concern about keeping the number of Trial users too low) >>>>> but will see. >>>>> >>>>> Users who try to create an account when the limit on Trial users >>>>> have been reached, will receive a message indicating that the limit has >>>>> been reached, inviting them to try again in two weeks (Fernando to send the >>>>> wording for this message to UPM). >>>>> >>>>> This step should be implemented by this Wednesday April 15th. >>>>> >>>>> >>>>> *Step 4: Freeing resources on current nodes**, giving users the >>>>> ability to apply to become community users, asking users in Spain-1 and >>>>> Prague to migrate* >>>>> >>>>> Starting April 16th, current nodes will free resources on their >>>>> nodes (virtual infrastructure and public IP addresses allocated to users >>>>> who didn't accept the new user account management policies). >>>>> >>>>> They should complete this process before April 23rd. FIWARE Lab >>>>> node providers are aware of the current situation so they should accelerate >>>>> this process as much as possible, trying to complete the process the sooner >>>>> the better. Situation will be assessed on April 20th and April 23rd. >>>>> It is expected that the status of the FIWARE Lab will improve drastically >>>>> during the week and will become stable by April 23rd. >>>>> >>>>> In parallel, we will encourage legacy users (those who created their >>>>> account before April 16th and have accepted the new terms and conditions) >>>>> to apply for becoming community users. They should be able to submit >>>>> their application completing an application form that will be provided to >>>>> them and will be made available on the Cloud Portal. >>>>> >>>>> Those legacy users whose application is accepted and who were hosted >>>>> in the Spain-1 or the Prague nodes will be asked to migrate their >>>>> environments to any of the other nodes (a recommendation will be given). >>>>> The Spain-1 and the Prague nodes will not host community users. As a >>>>> result, no users will remain in these two nodes by May 1st. >>>>> >>>>> >>>>> *Step 5: Deployment of new IdM/Keystone component and upgrading of >>>>> Community Users*. * Migration of Spain-1 and Prague nodes to >>>>> OpenStack Juno.* >>>>> >>>>> This step will start May 1st. Then, we will deploy the new version >>>>> of the IdM/Keystone component. >>>>> >>>>> Users whose application to become Community Users has been approved >>>>> will become Community Users. Environments of those Trial users who has >>>>> overpass the 2 weeks trial period will be cleaned out. From then on, the >>>>> new user account management policies will be in place, with the new >>>>> IdM/keystone component supporting the ability to distinguish between kind >>>>> of users and the nodes each will be able to get access to. >>>>> >>>>> In parallel, Spain-1 and Prague nodes should start their migration >>>>> to Juno. Once they migrate, they will be made available as part of the >>>>> federation (maybe the physical resources allocated to the Spain-1 node will >>>>> be assigned to the Spain-2 node). >>>>> >>>>> >>>>> *Step 6: Assessment of nodes in the FIWARE Lab federation. Bringing >>>>> FIWARE Lab nodes into quarantine.* >>>>> >>>>> After April 23th, performance of the several nodes in the FIWARE Lab >>>>> federation will be weekly assessed. Those nodes who exhibit a bad >>>>> performance (instability, low response to request for help by users) will >>>>> be put into quarantine and their users (Community Users) will be asked to >>>>> migrate to the Spain-2 node. >>>>> >>>>> >>>>> 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 >>>>> >>>>> >>>>> ------------------------------ >>>>> >>>>> 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 >>>>> 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 >>>> 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 >>>> _______________________________________________ >>>> Fiware-lab-recovery-tf mailing list >>>> 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 >>>> 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 >>>> >>>> _______________________________________________ >>>> Fiware-lab-recovery-tf mailing list >>>> Fiware-lab-recovery-tf at lists.fiware.org >>>> https://lists.fiware.org/listinfo/fiware-lab-recovery-tf >>>> >>>> >>> >>> >>> -- >>> -- >>> 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 >>> >> >> >> >> -- >> -- >> 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 > > ------------------------------ > > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From aalonsog at dit.upm.es Thu Apr 16 14:19:08 2015 From: aalonsog at dit.upm.es (=?utf-8?Q?=C3=81lvaro_Alonso?=) Date: Thu, 16 Apr 2015 14:19:08 +0200 Subject: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab In-Reply-To: References: <552D5D25.1060506@telefonica.com> <552E8C06.1020105@telefonica.com> <3964F66E-FA4A-409A-AACE-F68AB0E15E22@dit.upm.es> <552E9A12.7040407@telefonica.com> <552F5525.90509@telefonica.com> Message-ID: AFAIK, v3 is compatible with v2 but not in the oder sense. So you can access the data stored in v2 from v3 API, but you can not access data stored in v3 using v2 API. We need to store the data in v3 because of three reasons: - The migration of the current IdM data to Keystone is designed to migrate to v3 - Our Horizon version for the IdM is designed to use v3 - (Not mandatory but recommendable) v2 will be not supported in the next Openstack releases so, if we migrate to v2 we will have to migrate again in the future to v3 BR -- ?lvaro > El 16 Apr 2015, a las 13:41, Federico Michele Facca escribi?: > > as i was commenting to fernando on skype, all services (e.g. nova) are always backward compatible, i.e. nova can offer at the same time api v2 and api v3. so it looks strange if the case of keystone it's different. but we need to test of course. > > federico > > On Thu, Apr 16, 2015 at 1:31 PM, FERNANDO LOPEZ AGUILAR > wrote: > Well, let me share my thinks about it. OpenStack is working properly both v2 and v3 APIs of Keystone (except for the not testing one in nova). Like any other APIs, I think that it should access to the same stored information in the DB. So, what is the problem if the IdM and its portal use the v3 API and OpenStack services use the v2 API? > > De: Federico Michele Facca > > Fecha: Thursday 16 April 2015 08:43 > Para: JUAN JOSE HIERRO SUREDA > > CC: "fiware-lab-recovery-tf at lists.fiware.org " > > Asunto: Re: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab > > to be honest I am not sure, have been using juno and icehouse without problems, but always using keystone v2 as far as i know. i will ask internally. > > On Thu, Apr 16, 2015 at 8:22 AM, Juanjo Hierro > wrote: > > Does this mean that we are going to have a problem with Juno and the new IdM/Keystone ? > > > On 16/04/15 07:55, Federico Michele Facca wrote: >> https://wiki.openstack.org/wiki/ReleaseNotes/Juno >> >> Known Issues >> >> When using libvirt, live snapshots are effectively disabled, due to this difficult-to-reproduce bug: https://bugs.launchpad.net/nova/+bug/1334398 (https://review.openstack.org/#/c/102643/ ) >> Glance v2 and Keystone v3 are not tested with Nova in Juno. >> >> On Wed, Apr 15, 2015 at 7:07 PM, Federico Michele Facca > wrote: >> i would say that the safe threashold is icehouse. tricks may work for havana and grizlly but tricks do not fall in "safe" until we test. >> >> On Wed, Apr 15, 2015 at 7:04 PM, Juanjo Hierro > wrote: >> Gentlemen, >> >> I need to know where to put a safe threshold (Grizzly,Havana, IceHouse, ...), so that last paragraph of Step 4 changes and I mention that all legacy users who get upgraded to become Community Users but were hosted on nodes not in version XXX of OpenStack or will have to migrate to other nodes (as per recommendation given in response to their request for the upgrade). >> >> I need this response URGENTLY. >> >> Best regards, >> >> -- Juanjo >> >> >> On 15/04/15 18:15, ?lvaro Alonso wrote: >>> Hi, >>> >>> today tests made by Henar in havana suggest that havana is not compatible with v3. Federico found a post (https://www.mirantis.com/blog/manage-openstack-projects-using-domains-havana/ ) that says it is partially compatible but we are not sure of that. >>> >>> My understanding was that every nodes had to be migrated to Icehouse, for that reason I was only concerned by old spain node. >>> >>> @Federico, do you know haw many nodes are still Grizzly? The will be migrated before May 1? Is it possible to decide that if a node is not migrated to Icehouse by May 1, it will be out of the federation until it migrates? >>> >>> BR >>> -- >>> ?lvaro >>> >>>> El 15 Apr 2015, a las 18:04, Juanjo Hierro > escribi?: >>>> >>>> >>>> >>>> On 15/04/15 05:58, Federico Michele Facca wrote: >>>>> Dear Juanjo, >>>>> some comments from my side: >>>>> >>>>> 1) Maurizio as XIFI coordinator, needs to be in the loop. While I agree that some nodes - probably like some GEs developers btw - don't deserve ths money they have been granted for the service given, any action and decision in this direction within XIFI is beyond my role. Not sure if and how saved money could be employed. Moved to FI-CORE? >>>>> >>>> >>>> I have added him. >>>> >>>>> 2) According to a short discussion I had with Alvaro, Migration to new IDM my affect as well other nodes still using Grizzly, this needs to be clarified asap in order to take proper actions (i.e. Accelerate migration plan). >>>>> >>>> >>>> People from UPM has to clarify this URGENTLY. I was about to send an email to Basecamp sharing the plan (to show we are reacting and we have setup a Recovery Task Force but I want to know to what extend I have to modify anything in the description of the plan. >>>> >>>>> 3) It is very important to agree on fair, objective and not arguable metrics to define performance. As early mentioned errors from tests due to finished resources do not mean "bad performance" (if not this would be the case as well for spain), this case is a more general issue related to the tools and functions provided on top of nodes, for which we cannot account them. >>>>> >>>> >>>> Agreed. That's why, a) we will only be able to measure performance once nodes get cleaned b) we need to make sure that the tests run well (it is my impression that some of them do not give an accurate photo of the status) >>>> >>>>> 4) There are nodes operating for "free", what should we do in such cases? I would keep possibility fir user with proper role to use them, regardeless, no financial penality can be passed over to them. >>>>> >>>> >>>> We should come with a way to label the different nodes and let users take decision. Of course, there is no penalty that can be passed to them. But certainly something we can do is to put them in quarantine. >>>> >>>> Cheers, >>>> >>>> -- Juanjo >>>>> when the message is finalized and agreed, i can inform lab nodes. >>>>> >>>>> Best, >>>>> Federico >>>>> >>>>> ----------------------------------------- >>>>> Apologizes for mispellings. My thumb is not compatible with Android >>>>> >>>>> On Apr 14, 2015 8:32 PM, "Juanjo Hierro" > wrote: >>>>> Dear all, >>>>> >>>>> I have added Thierry Nagellen from Orange to this mailing list because despite he is not involved in the Task Force "per se", we are synchronized also with Orange overall with respect to messages to pass to the EC and rest of FI-PPP projects. If you believe someone else has to be in this list, please let me know. >>>>> >>>>> It has come out that deployment of the new IdM/Keystone is not feasible as planned. Therefore, we have to define a new plan. >>>>> >>>>> This morning, the TID team (including me) have had the opportunity to meet with the UPM team to understand the issue and we have come with an alternative plan for the recovery of the FIWARE Lab than the one we defined yesterday which sounds pretty reasonable and may help us to soon improve the situation. >>>>> >>>>> Let me summarize the plan in this email so that we are all on the same page. If you find some weakness/issue, please raise it. Otherwise, let's stick to it. Fortunately, the first steps remain the same and they have already been done, so we are on the right track. >>>>> >>>>> An important matter: I plan to send this plan to the EC tomorrow morning at 11:00. If you have comments, you should provide them before that deadline. I will also communicate this plan to FIWARE Accelerator projects on Basecamp as well as to Use Case projects through the FI-PPP mailing lists. Federico or Engineering should communicate this plan to organizations operating the FIWARE Lab nodes also at that time. >>>>> >>>>> A very sensible matter: when you review step 6 you will see that we cover the case in which some FIWARE Lab nodes may be put in quarantine. I would like to propose to the EC that those FIWARE lab nodes which are put into quarantine will be labeled as non-performance so they won't get the grant they were assigned in the XiFi Open Call, at least for the remaining of the XiFi project (until September). Maybe these funds can be given away to other partners or launch another Open Call. I would like to know your views on this. >>>>> >>>>> >>>>> Step 1: reminder about new user account management policies enforcement. >>>>> >>>>> A first email aking existing FIWARE Lab users to accept the new user account management policies, also covered in the new FIWARE Lab use terms and conditions, was sent to all FIWARE Lab users several weeks ago. >>>>> >>>>> A reminder has been sent yesterday and today to current users of the FIWARE Lab telling them that they have until April 15th 2015 19:00 CET. This message will be disseminated through different means: >>>>> mailed to current users of the FIWARE Lab >>>>> shown in a screen at login of users of the FIWARE Lab >>>>> posted on Basecamp so that FIWARE accelerator projects get aware and can forward the remainder to SMEs/startups under their respective programmes >>>>> mailed to the FI-PPP SB and the old FI-PPP AB members so that coordinators/architects of the FIWARE Use Case projects can forward the reminder to SMEs/startups under their respective Use Case projects >>>>> >>>>> Step 2: Increase of computing capacity in Spain-2 node >>>>> >>>>> In parallel and starting TODAY, activities to expand the capacity of the recently launched Spain-2 node will be prioritized so that we reach a capacity of aprox 500 cores in the datacenters located in both Sevilla and Malaga. We expect this expansion be completed by April 20th if not earlier. >>>>> >>>>> Additionally, additional capacity (close to 500 additional cores) will be activated in the Spain-2 node with servers located in a new datacenter located in Las Palmas. Conversations are ongoing with Red.es trying to accelerate this process so that this additional 500 cores get available closer to the end of next week. >>>>> >>>>> >>>>> Step 3: New Trial users only allowed to work on Spain-2 node. Limitation of number of concurrent trial users. >>>>> >>>>> Changes will be implemented in the Cloud portal and the user account registration process/tool by UPM so that new Trial users will only see the Spain-2 node. In addition, Trial users will be limited to 100 Trial users. >>>>> >>>>> Note that the "Trial Users", until the new IdM/Keystone component is deployed, will need to be identified by considering the creation of their user account. Actually, "Trial users" will be those users who have created their account after April 16th. >>>>> >>>>> Most likely, the fact that Trial users will only be allowed to work on Spain will remain. The number of Trial users allowed may increase (the EC has shown its concern about keeping the number of Trial users too low) but will see. >>>>> >>>>> Users who try to create an account when the limit on Trial users have been reached, will receive a message indicating that the limit has been reached, inviting them to try again in two weeks (Fernando to send the wording for this message to UPM). >>>>> >>>>> This step should be implemented by this Wednesday April 15th. >>>>> >>>>> >>>>> Step 4: Freeing resources on current nodes, giving users the ability to apply to become community users, asking users in Spain-1 and Prague to migrate >>>>> >>>>> Starting April 16th, current nodes will free resources on their nodes (virtual infrastructure and public IP addresses allocated to users who didn't accept the new user account management policies). >>>>> >>>>> They should complete this process before April 23rd. FIWARE Lab node providers are aware of the current situation so they should accelerate this process as much as possible, trying to complete the process the sooner the better. Situation will be assessed on April 20th and April 23rd. It is expected that the status of the FIWARE Lab will improve drastically during the week and will become stable by April 23rd. >>>>> >>>>> In parallel, we will encourage legacy users (those who created their account before April 16th and have accepted the new terms and conditions) to apply for becoming community users. They should be able to submit their application completing an application form that will be provided to them and will be made available on the Cloud Portal. >>>>> >>>>> Those legacy users whose application is accepted and who were hosted in the Spain-1 or the Prague nodes will be asked to migrate their environments to any of the other nodes (a recommendation will be given). The Spain-1 and the Prague nodes will not host community users. As a result, no users will remain in these two nodes by May 1st. >>>>> >>>>> >>>>> Step 5: Deployment of new IdM/Keystone component and upgrading of Community Users. Migration of Spain-1 and Prague nodes to OpenStack Juno. >>>>> >>>>> This step will start May 1st. Then, we will deploy the new version of the IdM/Keystone component. >>>>> >>>>> Users whose application to become Community Users has been approved will become Community Users. Environments of those Trial users who has overpass the 2 weeks trial period will be cleaned out. From then on, the new user account management policies will be in place, with the new IdM/keystone component supporting the ability to distinguish between kind of users and the nodes each will be able to get access to. >>>>> >>>>> In parallel, Spain-1 and Prague nodes should start their migration to Juno. Once they migrate, they will be made available as part of the federation (maybe the physical resources allocated to the Spain-1 node will be assigned to the Spain-2 node). >>>>> >>>>> >>>>> Step 6: Assessment of nodes in the FIWARE Lab federation. Bringing FIWARE Lab nodes into quarantine. >>>>> >>>>> After April 23th, performance of the several nodes in the FIWARE Lab federation will be weekly assessed. Those nodes who exhibit a bad performance (instability, low response to request for help by users) will be put into quarantine and their users (Community Users) will be asked to migrate to the Spain-2 node. >>>>> >>>>> >>>>> 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 >>>>> >>>>> 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 >>>>> 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 >>>> 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 >>>> _______________________________________________ >>>> Fiware-lab-recovery-tf mailing list >>>> 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 >> 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 >> >> _______________________________________________ >> Fiware-lab-recovery-tf mailing list >> Fiware-lab-recovery-tf at lists.fiware.org >> https://lists.fiware.org/listinfo/fiware-lab-recovery-tf >> >> >> >> >> -- >> -- >> 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 >> >> >> -- >> -- >> 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 > > > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From federico.facca at create-net.org Thu Apr 16 14:50:19 2015 From: federico.facca at create-net.org (Federico Michele Facca) Date: Thu, 16 Apr 2015 14:50:19 +0200 Subject: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab In-Reply-To: References: <552D5D25.1060506@telefonica.com> <552E8C06.1020105@telefonica.com> <3964F66E-FA4A-409A-AACE-F68AB0E15E22@dit.upm.es> <552E9A12.7040407@telefonica.com> <552F5525.90509@telefonica.com> Message-ID: node os version: https://docs.google.com/a/create-net.org/document/d/1jqypqp5Wf6dJgQufqVJicXDcJpoL1ajTPjjYtnQn-sw/edit On Thu, Apr 16, 2015 at 2:19 PM, ?lvaro Alonso wrote: > AFAIK, v3 is compatible with v2 but not in the oder sense. So you can > access the data stored in v2 from v3 API, but you can not access data > stored in v3 using v2 API. > > We need to store the data in v3 because of three reasons: > > - The migration of the current IdM data to Keystone is designed to migrate > to v3 > - Our Horizon version for the IdM is designed to use v3 > - (Not mandatory but recommendable) v2 will be not supported in the next > Openstack releases so, if we migrate to v2 we will have to migrate again in > the future to v3 > > > BR > -- > ?lvaro > > El 16 Apr 2015, a las 13:41, Federico Michele Facca < > federico.facca at create-net.org> escribi?: > > as i was commenting to fernando on skype, all services (e.g. nova) are > always backward compatible, i.e. nova can offer at the same time api v2 and > api v3. so it looks strange if the case of keystone it's different. but we > need to test of course. > > federico > > On Thu, Apr 16, 2015 at 1:31 PM, FERNANDO LOPEZ AGUILAR < > fernando.lopezaguilar at telefonica.com> wrote: > >> Well, let me share my thinks about it. OpenStack is working properly both >> v2 and v3 APIs of Keystone (except for the not testing one in nova). Like >> any other APIs, I think that it should access to the same stored >> information in the DB. So, what is the problem if the IdM and its portal >> use the v3 API and OpenStack services use the v2 API? >> >> De: Federico Michele Facca >> Fecha: Thursday 16 April 2015 08:43 >> Para: JUAN JOSE HIERRO SUREDA >> CC: "fiware-lab-recovery-tf at lists.fiware.org" < >> fiware-lab-recovery-tf at lists.fiware.org> >> Asunto: Re: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of >> the FIWARE Lab >> >> to be honest I am not sure, have been using juno and icehouse without >> problems, but always using keystone v2 as far as i know. i will ask >> internally. >> >> On Thu, Apr 16, 2015 at 8:22 AM, Juanjo Hierro < >> juanjose.hierro at telefonica.com> wrote: >> >>> >>> Does this mean that we are going to have a problem with Juno and the >>> new IdM/Keystone ? >>> >>> >>> On 16/04/15 07:55, Federico Michele Facca wrote: >>> >>> https://wiki.openstack.org/wiki/ReleaseNotes/Juno >>> >>> Known Issues >>> >>> - When using libvirt, live snapshots are effectively disabled, due >>> to this difficult-to-reproduce bug: >>> https://bugs.launchpad.net/nova/+bug/1334398( >>> https://review.openstack.org/#/c/102643/) >>> - Glance v2 and Keystone v3 are not tested with Nova in Juno. >>> >>> >>> On Wed, Apr 15, 2015 at 7:07 PM, Federico Michele Facca < >>> federico.facca at create-net.org> wrote: >>> >>>> i would say that the safe threashold is icehouse. tricks may work for >>>> havana and grizlly but tricks do not fall in "safe" until we test. >>>> >>>> On Wed, Apr 15, 2015 at 7:04 PM, Juanjo Hierro < >>>> juanjose.hierro at telefonica.com> wrote: >>>> >>>>> Gentlemen, >>>>> >>>>> I need to know where to put a safe threshold (Grizzly,Havana, >>>>> IceHouse, ...), so that last paragraph of Step 4 changes and I mention that >>>>> all legacy users who get upgraded to become Community Users but were hosted >>>>> on nodes not in version XXX of OpenStack or will have to migrate to other >>>>> nodes (as per recommendation given in response to their request for the >>>>> upgrade). >>>>> >>>>> I need this response URGENTLY. >>>>> >>>>> Best regards, >>>>> >>>>> -- Juanjo >>>>> >>>>> >>>>> On 15/04/15 18:15, ?lvaro Alonso wrote: >>>>> >>>>> Hi, >>>>> >>>>> today tests made by Henar in havana suggest that havana is not >>>>> compatible with v3. Federico found a post ( >>>>> https://www.mirantis.com/blog/manage-openstack-projects-using-domains-havana/) >>>>> that says it is partially compatible but we are not sure of that. >>>>> >>>>> My understanding was that every nodes had to be migrated to Icehouse, >>>>> for that reason I was only concerned by old spain node. >>>>> >>>>> @Federico, do you know haw many nodes are still Grizzly? The will be >>>>> migrated before May 1? Is it possible to decide that if a node is not >>>>> migrated to Icehouse by May 1, it will be out of the federation until it >>>>> migrates? >>>>> >>>>> BR >>>>> -- >>>>> ?lvaro >>>>> >>>>> El 15 Apr 2015, a las 18:04, Juanjo Hierro < >>>>> juanjose.hierro at telefonica.com> escribi?: >>>>> >>>>> >>>>> >>>>> On 15/04/15 05:58, Federico Michele Facca wrote: >>>>> >>>>> Dear Juanjo, >>>>> some comments from my side: >>>>> >>>>> 1) Maurizio as XIFI coordinator, needs to be in the loop. While I >>>>> agree that some nodes - probably like some GEs developers btw - don't >>>>> deserve ths money they have been granted for the service given, any action >>>>> and decision in this direction within XIFI is beyond my role. Not sure if >>>>> and how saved money could be employed. Moved to FI-CORE? >>>>> >>>>> >>>>> I have added him. >>>>> >>>>> 2) According to a short discussion I had with Alvaro, Migration to new >>>>> IDM my affect as well other nodes still using Grizzly, this needs to be >>>>> clarified asap in order to take proper actions (i.e. Accelerate migration >>>>> plan). >>>>> >>>>> >>>>> People from UPM has to clarify this URGENTLY. I was about to send >>>>> an email to Basecamp sharing the plan (to show we are reacting and we have >>>>> setup a Recovery Task Force but I want to know to what extend I have to >>>>> modify anything in the description of the plan. >>>>> >>>>> >>>>> 3) It is very important to agree on fair, objective and not arguable >>>>> metrics to define performance. As early mentioned errors from tests due to >>>>> finished resources do not mean "bad performance" (if not this would be the >>>>> case as well for spain), this case is a more general issue related to the >>>>> tools and functions provided on top of nodes, for which we cannot account >>>>> them. >>>>> >>>>> >>>>> Agreed. That's why, a) we will only be able to measure >>>>> performance once nodes get cleaned b) we need to make sure that the tests >>>>> run well (it is my impression that some of them do not give an accurate >>>>> photo of the status) >>>>> >>>>> 4) There are nodes operating for "free", what should we do in such >>>>> cases? I would keep possibility fir user with proper role to use them, >>>>> regardeless, no financial penality can be passed over to them. >>>>> >>>>> >>>>> We should come with a way to label the different nodes and let >>>>> users take decision. Of course, there is no penalty that can be passed to >>>>> them. But certainly something we can do is to put them in quarantine. >>>>> >>>>> >>>>> Cheers, >>>>> >>>>> -- Juanjo >>>>> >>>>> when the message is finalized and agreed, i can inform lab nodes. >>>>> >>>>> Best, >>>>> Federico >>>>> >>>>> ----------------------------------------- >>>>> Apologizes for mispellings. My thumb is not compatible with Android >>>>> On Apr 14, 2015 8:32 PM, "Juanjo Hierro" < >>>>> juanjose.hierro at telefonica.com> wrote: >>>>> >>>>>> Dear all, >>>>>> >>>>>> I have added Thierry Nagellen from Orange to this mailing list >>>>>> because despite he is not involved in the Task Force "per se", we are >>>>>> synchronized also with Orange overall with respect to messages to pass to >>>>>> the EC and rest of FI-PPP projects. If you believe someone else has to be >>>>>> in this list, please let me know. >>>>>> >>>>>> It has come out that deployment of the new IdM/Keystone is not >>>>>> feasible as planned. Therefore, we have to define a new plan. >>>>>> >>>>>> This morning, the TID team (including me) have had the opportunity >>>>>> to meet with the UPM team to understand the issue and we have come with an >>>>>> alternative plan for the recovery of the FIWARE Lab than the one we defined >>>>>> yesterday which sounds pretty reasonable and may help us to soon improve >>>>>> the situation. >>>>>> >>>>>> Let me summarize the plan in this email so that we are all on the >>>>>> same page. If you find some weakness/issue, please raise it. Otherwise, >>>>>> let's stick to it. Fortunately, the first steps remain the same and they >>>>>> have already been done, so we are on the right track. >>>>>> >>>>>> An important matter: I plan to send this plan to the EC tomorrow >>>>>> morning at 11:00. If you have comments, you should provide them before >>>>>> that deadline. I will also communicate this plan to FIWARE Accelerator >>>>>> projects on Basecamp as well as to Use Case projects through the FI-PPP >>>>>> mailing lists. Federico or Engineering should communicate this plan to >>>>>> organizations operating the FIWARE Lab nodes also at that time. >>>>>> >>>>>> A very sensible matter: when you review step 6 you will see that >>>>>> we cover the case in which some FIWARE Lab nodes may be put in >>>>>> quarantine. I would like to propose to the EC that those FIWARE lab nodes >>>>>> which are put into quarantine will be labeled as non-performance so they >>>>>> won't get the grant they were assigned in the XiFi Open Call, at least for >>>>>> the remaining of the XiFi project (until September). Maybe these funds >>>>>> can be given away to other partners or launch another Open Call. I would >>>>>> like to know your views on this. >>>>>> >>>>>> >>>>>> *Step 1: reminder about new user account management policies >>>>>> enforcement.* >>>>>> >>>>>> A first email aking existing FIWARE Lab users to accept the new >>>>>> user account management policies, also covered in the new FIWARE Lab use >>>>>> terms and conditions, was sent to all FIWARE Lab users several weeks ago. >>>>>> >>>>>> A reminder has been sent yesterday and today to current users of >>>>>> the FIWARE Lab telling them that they have until April 15th 2015 19:00 >>>>>> CET. This message will be disseminated through different means: >>>>>> >>>>>> - mailed to current users of the FIWARE Lab >>>>>> - shown in a screen at login of users of the FIWARE Lab >>>>>> - posted on Basecamp so that FIWARE accelerator projects get >>>>>> aware and can forward the remainder to SMEs/startups under their respective >>>>>> programmes >>>>>> - mailed to the FI-PPP SB and the old FI-PPP AB members so that >>>>>> coordinators/architects of the FIWARE Use Case projects can forward the >>>>>> reminder to SMEs/startups under their respective Use Case projects >>>>>> >>>>>> >>>>>> *Step 2: Increase of computing capacity in Spain-2 node* >>>>>> In parallel and starting TODAY, activities to expand the capacity >>>>>> of the recently launched Spain-2 node will be prioritized so that we reach >>>>>> a capacity of aprox 500 cores in the datacenters located in both Sevilla >>>>>> and Malaga. We expect this expansion be completed by April 20th if not >>>>>> earlier. >>>>>> >>>>>> Additionally, additional capacity (close to 500 additional cores) >>>>>> will be activated in the Spain-2 node with servers located in a new >>>>>> datacenter located in Las Palmas. Conversations are ongoing with >>>>>> Red.es trying to accelerate this process so that >>>>>> this additional 500 cores get available closer to the end of next week. >>>>>> >>>>>> >>>>>> *Step 3: New Trial users only allowed to work on Spain-2 node**. >>>>>> Limitation of number of concurrent trial users.* >>>>>> >>>>>> Changes will be implemented in the Cloud portal and the user >>>>>> account registration process/tool by UPM so that new Trial users will only >>>>>> see the Spain-2 node. In addition, Trial users will be limited to 100 >>>>>> Trial users. >>>>>> >>>>>> Note that the "Trial Users", until the new IdM/Keystone component >>>>>> is deployed, will need to be identified by considering the creation of >>>>>> their user account. Actually, "Trial users" will be those users who have >>>>>> created their account after April 16th. >>>>>> >>>>>> Most likely, the fact that Trial users will only be allowed to >>>>>> work on Spain will remain. The number of Trial users allowed may increase >>>>>> (the EC has shown its concern about keeping the number of Trial users too >>>>>> low) but will see. >>>>>> >>>>>> Users who try to create an account when the limit on Trial users >>>>>> have been reached, will receive a message indicating that the limit has >>>>>> been reached, inviting them to try again in two weeks (Fernando to send the >>>>>> wording for this message to UPM). >>>>>> >>>>>> This step should be implemented by this Wednesday April 15th. >>>>>> >>>>>> >>>>>> *Step 4: Freeing resources on current nodes**, giving users the >>>>>> ability to apply to become community users, asking users in Spain-1 and >>>>>> Prague to migrate* >>>>>> >>>>>> Starting April 16th, current nodes will free resources on their >>>>>> nodes (virtual infrastructure and public IP addresses allocated to users >>>>>> who didn't accept the new user account management policies). >>>>>> >>>>>> They should complete this process before April 23rd. FIWARE Lab >>>>>> node providers are aware of the current situation so they should accelerate >>>>>> this process as much as possible, trying to complete the process the sooner >>>>>> the better. Situation will be assessed on April 20th and April 23rd. >>>>>> It is expected that the status of the FIWARE Lab will improve drastically >>>>>> during the week and will become stable by April 23rd. >>>>>> >>>>>> In parallel, we will encourage legacy users (those who created >>>>>> their account before April 16th and have accepted the new terms and >>>>>> conditions) to apply for becoming community users. They should be able to >>>>>> submit their application completing an application form that will be >>>>>> provided to them and will be made available on the Cloud Portal. >>>>>> >>>>>> Those legacy users whose application is accepted and who were >>>>>> hosted in the Spain-1 or the Prague nodes will be asked to migrate their >>>>>> environments to any of the other nodes (a recommendation will be given). >>>>>> The Spain-1 and the Prague nodes will not host community users. As a >>>>>> result, no users will remain in these two nodes by May 1st. >>>>>> >>>>>> >>>>>> *Step 5: Deployment of new IdM/Keystone component and upgrading of >>>>>> Community Users*. * Migration of Spain-1 and Prague nodes to >>>>>> OpenStack Juno.* >>>>>> >>>>>> This step will start May 1st. Then, we will deploy the new >>>>>> version of the IdM/Keystone component. >>>>>> >>>>>> Users whose application to become Community Users has been >>>>>> approved will become Community Users. Environments of those Trial users >>>>>> who has overpass the 2 weeks trial period will be cleaned out. From then >>>>>> on, the new user account management policies will be in place, with the new >>>>>> IdM/keystone component supporting the ability to distinguish between kind >>>>>> of users and the nodes each will be able to get access to. >>>>>> >>>>>> In parallel, Spain-1 and Prague nodes should start their migration >>>>>> to Juno. Once they migrate, they will be made available as part of the >>>>>> federation (maybe the physical resources allocated to the Spain-1 node will >>>>>> be assigned to the Spain-2 node). >>>>>> >>>>>> >>>>>> *Step 6: Assessment of nodes in the FIWARE Lab federation. Bringing >>>>>> FIWARE Lab nodes into quarantine.* >>>>>> >>>>>> After April 23th, performance of the several nodes in the FIWARE >>>>>> Lab federation will be weekly assessed. Those nodes who exhibit a bad >>>>>> performance (instability, low response to request for help by users) will >>>>>> be put into quarantine and their users (Community Users) will be asked to >>>>>> migrate to the Spain-2 node. >>>>>> >>>>>> >>>>>> 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 >>>>>> >>>>>> >>>>>> ------------------------------ >>>>>> >>>>>> 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 >>>>>> 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 >>>>> 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 >>>>> _______________________________________________ >>>>> Fiware-lab-recovery-tf mailing list >>>>> 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 >>>>> 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 >>>>> >>>>> _______________________________________________ >>>>> Fiware-lab-recovery-tf mailing list >>>>> Fiware-lab-recovery-tf at lists.fiware.org >>>>> https://lists.fiware.org/listinfo/fiware-lab-recovery-tf >>>>> >>>>> >>>> >>>> >>>> -- >>>> -- >>>> 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 >>>> >>> >>> >>> >>> -- >>> -- >>> 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 >> >> ------------------------------ >> >> 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 > > > -- -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From federico.facca at gmail.com Wed Apr 15 05:58:47 2015 From: federico.facca at gmail.com (Federico Michele Facca) Date: Wed, 15 Apr 2015 05:58:47 +0200 Subject: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab In-Reply-To: <552D5D25.1060506@telefonica.com> References: <552D5D25.1060506@telefonica.com> Message-ID: Dear Juanjo, some comments from my side: 1) Maurizio as XIFI coordinator, needs to be in the loop. While I agree that some nodes - probably like some GEs developers btw - don't deserve ths money they have been granted for the service given, any action and decision in this direction within XIFI is beyond my role. Not sure if and how saved money could be employed. Moved to FI-CORE? 2) According to a short discussion I had with Alvaro, Migration to new IDM my affect as well other nodes still using Grizzly, this needs to be clarified asap in order to take proper actions (i.e. Accelerate migration plan). 3) It is very important to agree on fair, objective and not arguable metrics to define performance. As early mentioned errors from tests due to finished resources do not mean "bad performance" (if not this would be the case as well for spain), this case is a more general issue related to the tools and functions provided on top of nodes, for which we cannot account them. 4) There are nodes operating for "free", what should we do in such cases? I would keep possibility fir user with proper role to use them, regardeless, no financial penality can be passed over to them. when the message is finalized and agreed, i can inform lab nodes. Best, Federico ----------------------------------------- Apologizes for mispellings. My thumb is not compatible with Android On Apr 14, 2015 8:32 PM, "Juanjo Hierro" wrote: > Dear all, > > I have added Thierry Nagellen from Orange to this mailing list because > despite he is not involved in the Task Force "per se", we are synchronized > also with Orange overall with respect to messages to pass to the EC and > rest of FI-PPP projects. If you believe someone else has to be in this > list, please let me know. > > It has come out that deployment of the new IdM/Keystone is not feasible > as planned. Therefore, we have to define a new plan. > > This morning, the TID team (including me) have had the opportunity to > meet with the UPM team to understand the issue and we have come with an > alternative plan for the recovery of the FIWARE Lab than the one we defined > yesterday which sounds pretty reasonable and may help us to soon improve > the situation. > > Let me summarize the plan in this email so that we are all on the same > page. If you find some weakness/issue, please raise it. Otherwise, > let's stick to it. Fortunately, the first steps remain the same and they > have already been done, so we are on the right track. > > An important matter: I plan to send this plan to the EC tomorrow morning > at 11:00. If you have comments, you should provide them before that > deadline. I will also communicate this plan to FIWARE Accelerator > projects on Basecamp as well as to Use Case projects through the FI-PPP > mailing lists. Federico or Engineering should communicate this plan to > organizations operating the FIWARE Lab nodes also at that time. > > A very sensible matter: when you review step 6 you will see that we > cover the case in which some FIWARE Lab nodes may be put in quarantine. I > would like to propose to the EC that those FIWARE lab nodes which are put > into quarantine will be labeled as non-performance so they won't get the > grant they were assigned in the XiFi Open Call, at least for the remaining > of the XiFi project (until September). Maybe these funds can be given > away to other partners or launch another Open Call. I would like to know > your views on this. > > > *Step 1: reminder about new user account management policies enforcement.* > > A first email aking existing FIWARE Lab users to accept the new user > account management policies, also covered in the new FIWARE Lab use terms > and conditions, was sent to all FIWARE Lab users several weeks ago. > > A reminder has been sent yesterday and today to current users of the > FIWARE Lab telling them that they have until April 15th 2015 19:00 CET. > This message will be disseminated through different means: > > - mailed to current users of the FIWARE Lab > - shown in a screen at login of users of the FIWARE Lab > - posted on Basecamp so that FIWARE accelerator projects get aware and > can forward the remainder to SMEs/startups under their respective > programmes > - mailed to the FI-PPP SB and the old FI-PPP AB members so that > coordinators/architects of the FIWARE Use Case projects can forward the > reminder to SMEs/startups under their respective Use Case projects > > > *Step 2: Increase of computing capacity in Spain-2 node* > In parallel and starting TODAY, activities to expand the capacity of > the recently launched Spain-2 node will be prioritized so that we reach a > capacity of aprox 500 cores in the datacenters located in both Sevilla and > Malaga. We expect this expansion be completed by April 20th if not > earlier. > > Additionally, additional capacity (close to 500 additional cores) will > be activated in the Spain-2 node with servers located in a new datacenter > located in Las Palmas. Conversations are ongoing with Red.es trying to > accelerate this process so that this additional 500 cores get available > closer to the end of next week. > > > *Step 3: New Trial users only allowed to work on Spain-2 node**. > Limitation of number of concurrent trial users.* > > Changes will be implemented in the Cloud portal and the user account > registration process/tool by UPM so that new Trial users will only see the > Spain-2 node. In addition, Trial users will be limited to 100 Trial users. > > Note that the "Trial Users", until the new IdM/Keystone component is > deployed, will need to be identified by considering the creation of their > user account. Actually, "Trial users" will be those users who have > created their account after April 16th. > > Most likely, the fact that Trial users will only be allowed to work on > Spain will remain. The number of Trial users allowed may increase (the EC > has shown its concern about keeping the number of Trial users too low) but > will see. > > Users who try to create an account when the limit on Trial users have > been reached, will receive a message indicating that the limit has been > reached, inviting them to try again in two weeks (Fernando to send the > wording for this message to UPM). > > This step should be implemented by this Wednesday April 15th. > > > *Step 4: Freeing resources on current nodes**, giving users the ability > to apply to become community users, asking users in Spain-1 and Prague to > migrate* > > Starting April 16th, current nodes will free resources on their nodes > (virtual infrastructure and public IP addresses allocated to users who > didn't accept the new user account management policies). > > They should complete this process before April 23rd. FIWARE Lab node > providers are aware of the current situation so they should accelerate this > process as much as possible, trying to complete the process the sooner the > better. Situation will be assessed on April 20th and April 23rd. It is > expected that the status of the FIWARE Lab will improve drastically during > the week and will become stable by April 23rd. > > In parallel, we will encourage legacy users (those who created their > account before April 16th and have accepted the new terms and conditions) > to apply for becoming community users. They should be able to submit > their application completing an application form that will be provided to > them and will be made available on the Cloud Portal. > > Those legacy users whose application is accepted and who were hosted in > the Spain-1 or the Prague nodes will be asked to migrate their environments > to any of the other nodes (a recommendation will be given). The Spain-1 > and the Prague nodes will not host community users. As a result, no users > will remain in these two nodes by May 1st. > > > *Step 5: Deployment of new IdM/Keystone component and upgrading of > Community Users*. * Migration of Spain-1 and Prague nodes to OpenStack > Juno.* > > This step will start May 1st. Then, we will deploy the new version of > the IdM/Keystone component. > > Users whose application to become Community Users has been approved will > become Community Users. Environments of those Trial users who has > overpass the 2 weeks trial period will be cleaned out. From then on, the > new user account management policies will be in place, with the new > IdM/keystone component supporting the ability to distinguish between kind > of users and the nodes each will be able to get access to. > > In parallel, Spain-1 and Prague nodes should start their migration to > Juno. Once they migrate, they will be made available as part of the > federation (maybe the physical resources allocated to the Spain-1 node will > be assigned to the Spain-2 node). > > > *Step 6: Assessment of nodes in the FIWARE Lab federation. Bringing > FIWARE Lab nodes into quarantine.* > > After April 23th, performance of the several nodes in the FIWARE Lab > federation will be weekly assessed. Those nodes who exhibit a bad > performance (instability, low response to request for help by users) will > be put into quarantine and their users (Community Users) will be asked to > migrate to the Spain-2 node. > > > 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 > > > ------------------------------ > > 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 > https://lists.fiware.org/listinfo/fiware-lab-recovery-tf > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From federico.facca at gmail.com Wed Apr 15 06:11:22 2015 From: federico.facca at gmail.com (Federico Michele Facca) Date: Wed, 15 Apr 2015 06:11:22 +0200 Subject: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab In-Reply-To: References: <552D5D25.1060506@telefonica.com> Message-ID: Ps: i forgot to mention that in my understanding user type management was depending on the deployment of the new idm, but maybe upm has in mind a solution that does not require that. ----------------------------------------- Apologizes for mispellings. My thumb is not compatible with Android On Apr 15, 2015 5:58 AM, "Federico Michele Facca" wrote: > Dear Juanjo, > some comments from my side: > > 1) Maurizio as XIFI coordinator, needs to be in the loop. While I agree > that some nodes - probably like some GEs developers btw - don't deserve ths > money they have been granted for the service given, any action and decision > in this direction within XIFI is beyond my role. Not sure if and how saved > money could be employed. Moved to FI-CORE? > > 2) According to a short discussion I had with Alvaro, Migration to new IDM > my affect as well other nodes still using Grizzly, this needs to be > clarified asap in order to take proper actions (i.e. Accelerate migration > plan). > > 3) It is very important to agree on fair, objective and not arguable > metrics to define performance. As early mentioned errors from tests due to > finished resources do not mean "bad performance" (if not this would be the > case as well for spain), this case is a more general issue related to the > tools and functions provided on top of nodes, for which we cannot account > them. > > 4) There are nodes operating for "free", what should we do in such cases? > I would keep possibility fir user with proper role to use them, > regardeless, no financial penality can be passed over to them. > > when the message is finalized and agreed, i can inform lab nodes. > > Best, > Federico > > ----------------------------------------- > Apologizes for mispellings. My thumb is not compatible with Android > On Apr 14, 2015 8:32 PM, "Juanjo Hierro" > wrote: > >> Dear all, >> >> I have added Thierry Nagellen from Orange to this mailing list because >> despite he is not involved in the Task Force "per se", we are synchronized >> also with Orange overall with respect to messages to pass to the EC and >> rest of FI-PPP projects. If you believe someone else has to be in this >> list, please let me know. >> >> It has come out that deployment of the new IdM/Keystone is not feasible >> as planned. Therefore, we have to define a new plan. >> >> This morning, the TID team (including me) have had the opportunity to >> meet with the UPM team to understand the issue and we have come with an >> alternative plan for the recovery of the FIWARE Lab than the one we defined >> yesterday which sounds pretty reasonable and may help us to soon improve >> the situation. >> >> Let me summarize the plan in this email so that we are all on the same >> page. If you find some weakness/issue, please raise it. Otherwise, >> let's stick to it. Fortunately, the first steps remain the same and they >> have already been done, so we are on the right track. >> >> An important matter: I plan to send this plan to the EC tomorrow >> morning at 11:00. If you have comments, you should provide them before >> that deadline. I will also communicate this plan to FIWARE Accelerator >> projects on Basecamp as well as to Use Case projects through the FI-PPP >> mailing lists. Federico or Engineering should communicate this plan to >> organizations operating the FIWARE Lab nodes also at that time. >> >> A very sensible matter: when you review step 6 you will see that we >> cover the case in which some FIWARE Lab nodes may be put in quarantine. I >> would like to propose to the EC that those FIWARE lab nodes which are put >> into quarantine will be labeled as non-performance so they won't get the >> grant they were assigned in the XiFi Open Call, at least for the remaining >> of the XiFi project (until September). Maybe these funds can be given >> away to other partners or launch another Open Call. I would like to know >> your views on this. >> >> >> *Step 1: reminder about new user account management policies enforcement.* >> >> A first email aking existing FIWARE Lab users to accept the new user >> account management policies, also covered in the new FIWARE Lab use terms >> and conditions, was sent to all FIWARE Lab users several weeks ago. >> >> A reminder has been sent yesterday and today to current users of the >> FIWARE Lab telling them that they have until April 15th 2015 19:00 CET. >> This message will be disseminated through different means: >> >> - mailed to current users of the FIWARE Lab >> - shown in a screen at login of users of the FIWARE Lab >> - posted on Basecamp so that FIWARE accelerator projects get aware >> and can forward the remainder to SMEs/startups under their respective >> programmes >> - mailed to the FI-PPP SB and the old FI-PPP AB members so that >> coordinators/architects of the FIWARE Use Case projects can forward the >> reminder to SMEs/startups under their respective Use Case projects >> >> >> *Step 2: Increase of computing capacity in Spain-2 node* >> In parallel and starting TODAY, activities to expand the capacity of >> the recently launched Spain-2 node will be prioritized so that we reach a >> capacity of aprox 500 cores in the datacenters located in both Sevilla and >> Malaga. We expect this expansion be completed by April 20th if not >> earlier. >> >> Additionally, additional capacity (close to 500 additional cores) will >> be activated in the Spain-2 node with servers located in a new datacenter >> located in Las Palmas. Conversations are ongoing with Red.es trying to >> accelerate this process so that this additional 500 cores get available >> closer to the end of next week. >> >> >> *Step 3: New Trial users only allowed to work on Spain-2 node**. >> Limitation of number of concurrent trial users.* >> >> Changes will be implemented in the Cloud portal and the user account >> registration process/tool by UPM so that new Trial users will only see the >> Spain-2 node. In addition, Trial users will be limited to 100 Trial users. >> >> Note that the "Trial Users", until the new IdM/Keystone component is >> deployed, will need to be identified by considering the creation of their >> user account. Actually, "Trial users" will be those users who have >> created their account after April 16th. >> >> Most likely, the fact that Trial users will only be allowed to work on >> Spain will remain. The number of Trial users allowed may increase (the EC >> has shown its concern about keeping the number of Trial users too low) but >> will see. >> >> Users who try to create an account when the limit on Trial users have >> been reached, will receive a message indicating that the limit has been >> reached, inviting them to try again in two weeks (Fernando to send the >> wording for this message to UPM). >> >> This step should be implemented by this Wednesday April 15th. >> >> >> *Step 4: Freeing resources on current nodes**, giving users the ability >> to apply to become community users, asking users in Spain-1 and Prague to >> migrate* >> >> Starting April 16th, current nodes will free resources on their nodes >> (virtual infrastructure and public IP addresses allocated to users who >> didn't accept the new user account management policies). >> >> They should complete this process before April 23rd. FIWARE Lab node >> providers are aware of the current situation so they should accelerate this >> process as much as possible, trying to complete the process the sooner the >> better. Situation will be assessed on April 20th and April 23rd. It is >> expected that the status of the FIWARE Lab will improve drastically during >> the week and will become stable by April 23rd. >> >> In parallel, we will encourage legacy users (those who created their >> account before April 16th and have accepted the new terms and conditions) >> to apply for becoming community users. They should be able to submit >> their application completing an application form that will be provided to >> them and will be made available on the Cloud Portal. >> >> Those legacy users whose application is accepted and who were hosted in >> the Spain-1 or the Prague nodes will be asked to migrate their environments >> to any of the other nodes (a recommendation will be given). The Spain-1 >> and the Prague nodes will not host community users. As a result, no users >> will remain in these two nodes by May 1st. >> >> >> *Step 5: Deployment of new IdM/Keystone component and upgrading of >> Community Users*. * Migration of Spain-1 and Prague nodes to OpenStack >> Juno.* >> >> This step will start May 1st. Then, we will deploy the new version of >> the IdM/Keystone component. >> >> Users whose application to become Community Users has been approved >> will become Community Users. Environments of those Trial users who has >> overpass the 2 weeks trial period will be cleaned out. From then on, the >> new user account management policies will be in place, with the new >> IdM/keystone component supporting the ability to distinguish between kind >> of users and the nodes each will be able to get access to. >> >> In parallel, Spain-1 and Prague nodes should start their migration to >> Juno. Once they migrate, they will be made available as part of the >> federation (maybe the physical resources allocated to the Spain-1 node will >> be assigned to the Spain-2 node). >> >> >> *Step 6: Assessment of nodes in the FIWARE Lab federation. Bringing >> FIWARE Lab nodes into quarantine.* >> >> After April 23th, performance of the several nodes in the FIWARE Lab >> federation will be weekly assessed. Those nodes who exhibit a bad >> performance (instability, low response to request for help by users) will >> be put into quarantine and their users (Community Users) will be asked to >> migrate to the Spain-2 node. >> >> >> 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 >> >> >> ------------------------------ >> >> 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 >> https://lists.fiware.org/listinfo/fiware-lab-recovery-tf >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From federico.facca at gmail.com Wed Apr 15 10:23:56 2015 From: federico.facca at gmail.com (Federico Michele Facca) Date: Wed, 15 Apr 2015 10:23:56 +0200 Subject: [Fiware-lab-recovery-tf] Daily checkpoints In-Reply-To: <552E004A.7020509@telefonica.com> References: <552E004A.7020509@telefonica.com> Message-ID: I can't join either today or tomorrow before 6 pm, maybe silvio can ----------------------------------------- Apologizes for mispellings. My thumb is not compatible with Android On Apr 15, 2015 10:02 AM, "Juanjo Hierro" wrote: > Hi all, > > I believe that from now and until the FIWARE Lab environment gets > stabilized, we have to plan daily confcalls. > > They don't need to be long, just book 15-30 mins to double-check > everything is on track and monitor progress. It would be nice to review > action points and confirm they are evolving or will be completed that day > as planned. > > In the event there are issue that requires more time and discussion, > extend the duration of the planned daily confcall or plan a continuation > confcall the same day (or when appropriate). > > For today, I wish to have it from 15:30 to 16:00. > > I have setup a doodle to declare your preferences about what time would > be more suitable to you from tomorrow on. Please vote so that we can > close this today. > > http://doodle.com/crqrmxvmruzfb8nz > > > > 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 > > > ------------------------------ > > 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 > https://lists.fiware.org/listinfo/fiware-lab-recovery-tf > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From silvio.cretti at create-net.org Wed Apr 15 10:37:16 2015 From: silvio.cretti at create-net.org (Silvio Cretti) Date: Wed, 15 Apr 2015 10:37:16 +0200 Subject: [Fiware-lab-recovery-tf] Daily checkpoints In-Reply-To: References: <552E004A.7020509@telefonica.com> Message-ID: Sorry I am busy today during the afternoon. I could try to make it early this afternoon (let's say @13.30) but after 14.30 I am busy. Tomorrow I am busy all the day with the mid term review of CreatiFI. In case my presence is needed, just let me know. silvio On Wed, Apr 15, 2015 at 10:23 AM, Federico Michele Facca < federico.facca at gmail.com> wrote: > I can't join either today or tomorrow before 6 pm, maybe silvio can > > ----------------------------------------- > Apologizes for mispellings. My thumb is not compatible with Android > On Apr 15, 2015 10:02 AM, "Juanjo Hierro" > wrote: > >> Hi all, >> >> I believe that from now and until the FIWARE Lab environment gets >> stabilized, we have to plan daily confcalls. >> >> They don't need to be long, just book 15-30 mins to double-check >> everything is on track and monitor progress. It would be nice to review >> action points and confirm they are evolving or will be completed that day >> as planned. >> >> In the event there are issue that requires more time and discussion, >> extend the duration of the planned daily confcall or plan a continuation >> confcall the same day (or when appropriate). >> >> For today, I wish to have it from 15:30 to 16:00. >> >> I have setup a doodle to declare your preferences about what time would >> be more suitable to you from tomorrow on. Please vote so that we can >> close this today. >> >> http://doodle.com/crqrmxvmruzfb8nz >> >> >> >> 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 >> >> >> ------------------------------ >> >> 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 >> https://lists.fiware.org/listinfo/fiware-lab-recovery-tf >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From federico.facca at create-net.org Fri Apr 17 13:27:49 2015 From: federico.facca at create-net.org (Federico Michele Facca) Date: Fri, 17 Apr 2015 13:27:49 +0200 Subject: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab In-Reply-To: <552E8A1E.30808@telefonica.com> References: <552D5D25.1060506@telefonica.com> <552E8A1E.30808@telefonica.com> Message-ID: On Wed, Apr 15, 2015 at 5:56 PM, Juanjo Hierro < juanjose.hierro at telefonica.com> wrote: > Dear Federico, > > User type management indeed depends on the deployment of the new IdM, > but a) this doesn't prevent that we start taking note about who is willing > to become a Community User in May 1st, b) in some cases, eventually assign > them the requested quota before May 1st (even though they would not yet > ticketed as "Community Users" yet in the system). > > sure, i was asking only to be sure what information to pass to coaches and we will be able to close the consider close the community request processes. > Cheers, > > -- Juanjo > > > On 15/04/15 06:11, Federico Michele Facca wrote: > > Ps: i forgot to mention that in my understanding user type management was > depending on the deployment of the new idm, but maybe upm has in mind a > solution that does not require that. > > ----------------------------------------- > Apologizes for mispellings. My thumb is not compatible with Android > On Apr 15, 2015 5:58 AM, "Federico Michele Facca" < > federico.facca at gmail.com> wrote: > >> Dear Juanjo, >> some comments from my side: >> >> 1) Maurizio as XIFI coordinator, needs to be in the loop. While I agree >> that some nodes - probably like some GEs developers btw - don't deserve ths >> money they have been granted for the service given, any action and decision >> in this direction within XIFI is beyond my role. Not sure if and how saved >> money could be employed. Moved to FI-CORE? >> >> 2) According to a short discussion I had with Alvaro, Migration to new >> IDM my affect as well other nodes still using Grizzly, this needs to be >> clarified asap in order to take proper actions (i.e. Accelerate migration >> plan). >> >> 3) It is very important to agree on fair, objective and not arguable >> metrics to define performance. As early mentioned errors from tests due to >> finished resources do not mean "bad performance" (if not this would be the >> case as well for spain), this case is a more general issue related to the >> tools and functions provided on top of nodes, for which we cannot account >> them. >> >> 4) There are nodes operating for "free", what should we do in such cases? >> I would keep possibility fir user with proper role to use them, >> regardeless, no financial penality can be passed over to them. >> >> when the message is finalized and agreed, i can inform lab nodes. >> >> Best, >> Federico >> >> ----------------------------------------- >> Apologizes for mispellings. My thumb is not compatible with Android >> On Apr 14, 2015 8:32 PM, "Juanjo Hierro" >> wrote: >> >>> Dear all, >>> >>> I have added Thierry Nagellen from Orange to this mailing list because >>> despite he is not involved in the Task Force "per se", we are synchronized >>> also with Orange overall with respect to messages to pass to the EC and >>> rest of FI-PPP projects. If you believe someone else has to be in this >>> list, please let me know. >>> >>> It has come out that deployment of the new IdM/Keystone is not >>> feasible as planned. Therefore, we have to define a new plan. >>> >>> This morning, the TID team (including me) have had the opportunity to >>> meet with the UPM team to understand the issue and we have come with an >>> alternative plan for the recovery of the FIWARE Lab than the one we defined >>> yesterday which sounds pretty reasonable and may help us to soon improve >>> the situation. >>> >>> Let me summarize the plan in this email so that we are all on the same >>> page. If you find some weakness/issue, please raise it. Otherwise, >>> let's stick to it. Fortunately, the first steps remain the same and they >>> have already been done, so we are on the right track. >>> >>> An important matter: I plan to send this plan to the EC tomorrow >>> morning at 11:00. If you have comments, you should provide them before >>> that deadline. I will also communicate this plan to FIWARE Accelerator >>> projects on Basecamp as well as to Use Case projects through the FI-PPP >>> mailing lists. Federico or Engineering should communicate this plan to >>> organizations operating the FIWARE Lab nodes also at that time. >>> >>> A very sensible matter: when you review step 6 you will see that we >>> cover the case in which some FIWARE Lab nodes may be put in quarantine. I >>> would like to propose to the EC that those FIWARE lab nodes which are put >>> into quarantine will be labeled as non-performance so they won't get the >>> grant they were assigned in the XiFi Open Call, at least for the remaining >>> of the XiFi project (until September). Maybe these funds can be given >>> away to other partners or launch another Open Call. I would like to know >>> your views on this. >>> >>> >>> *Step 1: reminder about new user account management policies >>> enforcement.* >>> >>> A first email aking existing FIWARE Lab users to accept the new user >>> account management policies, also covered in the new FIWARE Lab use terms >>> and conditions, was sent to all FIWARE Lab users several weeks ago. >>> >>> A reminder has been sent yesterday and today to current users of the >>> FIWARE Lab telling them that they have until April 15th 2015 19:00 CET. >>> This message will be disseminated through different means: >>> >>> - mailed to current users of the FIWARE Lab >>> - shown in a screen at login of users of the FIWARE Lab >>> - posted on Basecamp so that FIWARE accelerator projects get aware >>> and can forward the remainder to SMEs/startups under their respective >>> programmes >>> - mailed to the FI-PPP SB and the old FI-PPP AB members so that >>> coordinators/architects of the FIWARE Use Case projects can forward the >>> reminder to SMEs/startups under their respective Use Case projects >>> >>> >>> *Step 2: Increase of computing capacity in Spain-2 node* >>> In parallel and starting TODAY, activities to expand the capacity of >>> the recently launched Spain-2 node will be prioritized so that we reach a >>> capacity of aprox 500 cores in the datacenters located in both Sevilla and >>> Malaga. We expect this expansion be completed by April 20th if not >>> earlier. >>> >>> Additionally, additional capacity (close to 500 additional cores) will >>> be activated in the Spain-2 node with servers located in a new datacenter >>> located in Las Palmas. Conversations are ongoing with Red.es trying to >>> accelerate this process so that this additional 500 cores get available >>> closer to the end of next week. >>> >>> >>> *Step 3: New Trial users only allowed to work on Spain-2 node**. >>> Limitation of number of concurrent trial users.* >>> >>> Changes will be implemented in the Cloud portal and the user account >>> registration process/tool by UPM so that new Trial users will only see the >>> Spain-2 node. In addition, Trial users will be limited to 100 Trial users. >>> >>> Note that the "Trial Users", until the new IdM/Keystone component is >>> deployed, will need to be identified by considering the creation of their >>> user account. Actually, "Trial users" will be those users who have >>> created their account after April 16th. >>> >>> Most likely, the fact that Trial users will only be allowed to work on >>> Spain will remain. The number of Trial users allowed may increase (the EC >>> has shown its concern about keeping the number of Trial users too low) but >>> will see. >>> >>> Users who try to create an account when the limit on Trial users have >>> been reached, will receive a message indicating that the limit has been >>> reached, inviting them to try again in two weeks (Fernando to send the >>> wording for this message to UPM). >>> >>> This step should be implemented by this Wednesday April 15th. >>> >>> >>> *Step 4: Freeing resources on current nodes**, giving users the ability >>> to apply to become community users, asking users in Spain-1 and Prague to >>> migrate* >>> >>> Starting April 16th, current nodes will free resources on their nodes >>> (virtual infrastructure and public IP addresses allocated to users who >>> didn't accept the new user account management policies). >>> >>> They should complete this process before April 23rd. FIWARE Lab node >>> providers are aware of the current situation so they should accelerate this >>> process as much as possible, trying to complete the process the sooner the >>> better. Situation will be assessed on April 20th and April 23rd. It is >>> expected that the status of the FIWARE Lab will improve drastically during >>> the week and will become stable by April 23rd. >>> >>> In parallel, we will encourage legacy users (those who created their >>> account before April 16th and have accepted the new terms and conditions) >>> to apply for becoming community users. They should be able to submit >>> their application completing an application form that will be provided to >>> them and will be made available on the Cloud Portal. >>> >>> Those legacy users whose application is accepted and who were hosted >>> in the Spain-1 or the Prague nodes will be asked to migrate their >>> environments to any of the other nodes (a recommendation will be given). >>> The Spain-1 and the Prague nodes will not host community users. As a >>> result, no users will remain in these two nodes by May 1st. >>> >>> >>> *Step 5: Deployment of new IdM/Keystone component and upgrading of >>> Community Users*. * Migration of Spain-1 and Prague nodes to OpenStack >>> Juno.* >>> >>> This step will start May 1st. Then, we will deploy the new version >>> of the IdM/Keystone component. >>> >>> Users whose application to become Community Users has been approved >>> will become Community Users. Environments of those Trial users who has >>> overpass the 2 weeks trial period will be cleaned out. From then on, the >>> new user account management policies will be in place, with the new >>> IdM/keystone component supporting the ability to distinguish between kind >>> of users and the nodes each will be able to get access to. >>> >>> In parallel, Spain-1 and Prague nodes should start their migration to >>> Juno. Once they migrate, they will be made available as part of the >>> federation (maybe the physical resources allocated to the Spain-1 node will >>> be assigned to the Spain-2 node). >>> >>> >>> *Step 6: Assessment of nodes in the FIWARE Lab federation. Bringing >>> FIWARE Lab nodes into quarantine.* >>> >>> After April 23th, performance of the several nodes in the FIWARE Lab >>> federation will be weekly assessed. Those nodes who exhibit a bad >>> performance (instability, low response to request for help by users) will >>> be put into quarantine and their users (Community Users) will be asked to >>> migrate to the Spain-2 node. >>> >>> >>> 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 >>> >>> >>> ------------------------------ >>> >>> 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 >>> 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 > 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 > > _______________________________________________ > Fiware-lab-recovery-tf mailing list > Fiware-lab-recovery-tf at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-lab-recovery-tf > > -- -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From aalonsog at dit.upm.es Fri Apr 17 13:40:52 2015 From: aalonsog at dit.upm.es (=?utf-8?Q?=C3=81lvaro_Alonso?=) Date: Fri, 17 Apr 2015 13:40:52 +0200 Subject: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab In-Reply-To: References: <552D5D25.1060506@telefonica.com> <552E8A1E.30808@telefonica.com> Message-ID: <896B7FF4-64D7-4B3F-BDE1-657CE75D5214@dit.upm.es> Hi all, good news. During this morning Henar and I have made tests in Havana dev environment and we have succeeded in the configuration of the node with Keystone v3. The summary is that we can configure nodes' services with v2 and all the resources stored in Keystone v3 (in the default domain) are accesible. So according to that every node would work without changing the current configuration. Anyway in other to be sure and to have a definitively conclusion we prefer to perform more tests on Monday. So we will update with the final conclusion that day. BR -- ?lvaro > El 17 Apr 2015, a las 13:27, Federico Michele Facca escribi?: > > > > On Wed, Apr 15, 2015 at 5:56 PM, Juanjo Hierro > wrote: > Dear Federico, > > User type management indeed depends on the deployment of the new IdM, but a) this doesn't prevent that we start taking note about who is willing to become a Community User in May 1st, b) in some cases, eventually assign them the requested quota before May 1st (even though they would not yet ticketed as "Community Users" yet in the system). > > > sure, i was asking only to be sure what information to pass to coaches and we will be able to close the consider close the community request processes. > > > Cheers, > > -- Juanjo > > > On 15/04/15 06:11, Federico Michele Facca wrote: >> Ps: i forgot to mention that in my understanding user type management was depending on the deployment of the new idm, but maybe upm has in mind a solution that does not require that. >> >> ----------------------------------------- >> Apologizes for mispellings. My thumb is not compatible with Android >> >> On Apr 15, 2015 5:58 AM, "Federico Michele Facca" > wrote: >> Dear Juanjo, >> some comments from my side: >> >> 1) Maurizio as XIFI coordinator, needs to be in the loop. While I agree that some nodes - probably like some GEs developers btw - don't deserve ths money they have been granted for the service given, any action and decision in this direction within XIFI is beyond my role. Not sure if and how saved money could be employed. Moved to FI-CORE? >> >> 2) According to a short discussion I had with Alvaro, Migration to new IDM my affect as well other nodes still using Grizzly, this needs to be clarified asap in order to take proper actions (i.e. Accelerate migration plan). >> >> 3) It is very important to agree on fair, objective and not arguable metrics to define performance. As early mentioned errors from tests due to finished resources do not mean "bad performance" (if not this would be the case as well for spain), this case is a more general issue related to the tools and functions provided on top of nodes, for which we cannot account them. >> >> 4) There are nodes operating for "free", what should we do in such cases? I would keep possibility fir user with proper role to use them, regardeless, no financial penality can be passed over to them. >> >> when the message is finalized and agreed, i can inform lab nodes. >> >> Best, >> Federico >> >> ----------------------------------------- >> Apologizes for mispellings. My thumb is not compatible with Android >> >> On Apr 14, 2015 8:32 PM, "Juanjo Hierro" > wrote: >> Dear all, >> >> I have added Thierry Nagellen from Orange to this mailing list because despite he is not involved in the Task Force "per se", we are synchronized also with Orange overall with respect to messages to pass to the EC and rest of FI-PPP projects. If you believe someone else has to be in this list, please let me know. >> >> It has come out that deployment of the new IdM/Keystone is not feasible as planned. Therefore, we have to define a new plan. >> >> This morning, the TID team (including me) have had the opportunity to meet with the UPM team to understand the issue and we have come with an alternative plan for the recovery of the FIWARE Lab than the one we defined yesterday which sounds pretty reasonable and may help us to soon improve the situation. >> >> Let me summarize the plan in this email so that we are all on the same page. If you find some weakness/issue, please raise it. Otherwise, let's stick to it. Fortunately, the first steps remain the same and they have already been done, so we are on the right track. >> >> An important matter: I plan to send this plan to the EC tomorrow morning at 11:00. If you have comments, you should provide them before that deadline. I will also communicate this plan to FIWARE Accelerator projects on Basecamp as well as to Use Case projects through the FI-PPP mailing lists. Federico or Engineering should communicate this plan to organizations operating the FIWARE Lab nodes also at that time. >> >> A very sensible matter: when you review step 6 you will see that we cover the case in which some FIWARE Lab nodes may be put in quarantine. I would like to propose to the EC that those FIWARE lab nodes which are put into quarantine will be labeled as non-performance so they won't get the grant they were assigned in the XiFi Open Call, at least for the remaining of the XiFi project (until September). Maybe these funds can be given away to other partners or launch another Open Call. I would like to know your views on this. >> >> >> Step 1: reminder about new user account management policies enforcement. >> >> A first email aking existing FIWARE Lab users to accept the new user account management policies, also covered in the new FIWARE Lab use terms and conditions, was sent to all FIWARE Lab users several weeks ago. >> >> A reminder has been sent yesterday and today to current users of the FIWARE Lab telling them that they have until April 15th 2015 19:00 CET. This message will be disseminated through different means: >> mailed to current users of the FIWARE Lab >> shown in a screen at login of users of the FIWARE Lab >> posted on Basecamp so that FIWARE accelerator projects get aware and can forward the remainder to SMEs/startups under their respective programmes >> mailed to the FI-PPP SB and the old FI-PPP AB members so that coordinators/architects of the FIWARE Use Case projects can forward the reminder to SMEs/startups under their respective Use Case projects >> >> Step 2: Increase of computing capacity in Spain-2 node >> >> In parallel and starting TODAY, activities to expand the capacity of the recently launched Spain-2 node will be prioritized so that we reach a capacity of aprox 500 cores in the datacenters located in both Sevilla and Malaga. We expect this expansion be completed by April 20th if not earlier. >> >> Additionally, additional capacity (close to 500 additional cores) will be activated in the Spain-2 node with servers located in a new datacenter located in Las Palmas. Conversations are ongoing with Red.es trying to accelerate this process so that this additional 500 cores get available closer to the end of next week. >> >> >> Step 3: New Trial users only allowed to work on Spain-2 node. Limitation of number of concurrent trial users. >> >> Changes will be implemented in the Cloud portal and the user account registration process/tool by UPM so that new Trial users will only see the Spain-2 node. In addition, Trial users will be limited to 100 Trial users. >> >> Note that the "Trial Users", until the new IdM/Keystone component is deployed, will need to be identified by considering the creation of their user account. Actually, "Trial users" will be those users who have created their account after April 16th. >> >> Most likely, the fact that Trial users will only be allowed to work on Spain will remain. The number of Trial users allowed may increase (the EC has shown its concern about keeping the number of Trial users too low) but will see. >> >> Users who try to create an account when the limit on Trial users have been reached, will receive a message indicating that the limit has been reached, inviting them to try again in two weeks (Fernando to send the wording for this message to UPM). >> >> This step should be implemented by this Wednesday April 15th. >> >> >> Step 4: Freeing resources on current nodes, giving users the ability to apply to become community users, asking users in Spain-1 and Prague to migrate >> >> Starting April 16th, current nodes will free resources on their nodes (virtual infrastructure and public IP addresses allocated to users who didn't accept the new user account management policies). >> >> They should complete this process before April 23rd. FIWARE Lab node providers are aware of the current situation so they should accelerate this process as much as possible, trying to complete the process the sooner the better. Situation will be assessed on April 20th and April 23rd. It is expected that the status of the FIWARE Lab will improve drastically during the week and will become stable by April 23rd. >> >> In parallel, we will encourage legacy users (those who created their account before April 16th and have accepted the new terms and conditions) to apply for becoming community users. They should be able to submit their application completing an application form that will be provided to them and will be made available on the Cloud Portal. >> >> Those legacy users whose application is accepted and who were hosted in the Spain-1 or the Prague nodes will be asked to migrate their environments to any of the other nodes (a recommendation will be given). The Spain-1 and the Prague nodes will not host community users. As a result, no users will remain in these two nodes by May 1st. >> >> >> Step 5: Deployment of new IdM/Keystone component and upgrading of Community Users. Migration of Spain-1 and Prague nodes to OpenStack Juno. >> >> This step will start May 1st. Then, we will deploy the new version of the IdM/Keystone component. >> >> Users whose application to become Community Users has been approved will become Community Users. Environments of those Trial users who has overpass the 2 weeks trial period will be cleaned out. From then on, the new user account management policies will be in place, with the new IdM/keystone component supporting the ability to distinguish between kind of users and the nodes each will be able to get access to. >> >> In parallel, Spain-1 and Prague nodes should start their migration to Juno. Once they migrate, they will be made available as part of the federation (maybe the physical resources allocated to the Spain-1 node will be assigned to the Spain-2 node). >> >> >> Step 6: Assessment of nodes in the FIWARE Lab federation. Bringing FIWARE Lab nodes into quarantine. >> >> After April 23th, performance of the several nodes in the FIWARE Lab federation will be weekly assessed. Those nodes who exhibit a bad performance (instability, low response to request for help by users) will be put into quarantine and their users (Community Users) will be asked to migrate to the Spain-2 node. >> >> >> 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 >> >> >> 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 >> 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 > 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 > > _______________________________________________ > Fiware-lab-recovery-tf mailing list > Fiware-lab-recovery-tf at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-lab-recovery-tf > > > > > -- > -- > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From fernando.lopezaguilar at telefonica.com Fri Apr 17 15:18:08 2015 From: fernando.lopezaguilar at telefonica.com (FERNANDO LOPEZ AGUILAR) Date: Fri, 17 Apr 2015 13:18:08 +0000 Subject: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab In-Reply-To: <896B7FF4-64D7-4B3F-BDE1-657CE75D5214@dit.upm.es> References: <552D5D25.1060506@telefonica.com> <552E8A1E.30808@telefonica.com> <896B7FF4-64D7-4B3F-BDE1-657CE75D5214@dit.upm.es> Message-ID: Well, keep in mind that in order to be fully compatible you need to assing the value default to hte domain of the user previously defined in v2 or defined in v2 in order that it can work properly. Fernando De: ?lvaro Alonso > Fecha: Friday 17 April 2015 13:40 Para: Federico Michele Facca > CC: "fiware-lab-recovery-tf at lists.fiware.org" > Asunto: Re: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab Hi all, good news. During this morning Henar and I have made tests in Havana dev environment and we have succeeded in the configuration of the node with Keystone v3. The summary is that we can configure nodes' services with v2 and all the resources stored in Keystone v3 (in the default domain) are accesible. So according to that every node would work without changing the current configuration. Anyway in other to be sure and to have a definitively conclusion we prefer to perform more tests on Monday. So we will update with the final conclusion that day. BR -- ?lvaro El 17 Apr 2015, a las 13:27, Federico Michele Facca > escribi?: On Wed, Apr 15, 2015 at 5:56 PM, Juanjo Hierro > wrote: Dear Federico, User type management indeed depends on the deployment of the new IdM, but a) this doesn't prevent that we start taking note about who is willing to become a Community User in May 1st, b) in some cases, eventually assign them the requested quota before May 1st (even though they would not yet ticketed as "Community Users" yet in the system). sure, i was asking only to be sure what information to pass to coaches and we will be able to close the consider close the community request processes. Cheers, -- Juanjo On 15/04/15 06:11, Federico Michele Facca wrote: Ps: i forgot to mention that in my understanding user type management was depending on the deployment of the new idm, but maybe upm has in mind a solution that does not require that. ----------------------------------------- Apologizes for mispellings. My thumb is not compatible with Android On Apr 15, 2015 5:58 AM, "Federico Michele Facca" > wrote: Dear Juanjo, some comments from my side: 1) Maurizio as XIFI coordinator, needs to be in the loop. While I agree that some nodes - probably like some GEs developers btw - don't deserve ths money they have been granted for the service given, any action and decision in this direction within XIFI is beyond my role. Not sure if and how saved money could be employed. Moved to FI-CORE? 2) According to a short discussion I had with Alvaro, Migration to new IDM my affect as well other nodes still using Grizzly, this needs to be clarified asap in order to take proper actions (i.e. Accelerate migration plan). 3) It is very important to agree on fair, objective and not arguable metrics to define performance. As early mentioned errors from tests due to finished resources do not mean "bad performance" (if not this would be the case as well for spain), this case is a more general issue related to the tools and functions provided on top of nodes, for which we cannot account them. 4) There are nodes operating for "free", what should we do in such cases? I would keep possibility fir user with proper role to use them, regardeless, no financial penality can be passed over to them. when the message is finalized and agreed, i can inform lab nodes. Best, Federico ----------------------------------------- Apologizes for mispellings. My thumb is not compatible with Android On Apr 14, 2015 8:32 PM, "Juanjo Hierro" > wrote: Dear all, I have added Thierry Nagellen from Orange to this mailing list because despite he is not involved in the Task Force "per se", we are synchronized also with Orange overall with respect to messages to pass to the EC and rest of FI-PPP projects. If you believe someone else has to be in this list, please let me know. It has come out that deployment of the new IdM/Keystone is not feasible as planned. Therefore, we have to define a new plan. This morning, the TID team (including me) have had the opportunity to meet with the UPM team to understand the issue and we have come with an alternative plan for the recovery of the FIWARE Lab than the one we defined yesterday which sounds pretty reasonable and may help us to soon improve the situation. Let me summarize the plan in this email so that we are all on the same page. If you find some weakness/issue, please raise it. Otherwise, let's stick to it. Fortunately, the first steps remain the same and they have already been done, so we are on the right track. An important matter: I plan to send this plan to the EC tomorrow morning at 11:00. If you have comments, you should provide them before that deadline. I will also communicate this plan to FIWARE Accelerator projects on Basecamp as well as to Use Case projects through the FI-PPP mailing lists. Federico or Engineering should communicate this plan to organizations operating the FIWARE Lab nodes also at that time. A very sensible matter: when you review step 6 you will see that we cover the case in which some FIWARE Lab nodes may be put in quarantine. I would like to propose to the EC that those FIWARE lab nodes which are put into quarantine will be labeled as non-performance so they won't get the grant they were assigned in the XiFi Open Call, at least for the remaining of the XiFi project (until September). Maybe these funds can be given away to other partners or launch another Open Call. I would like to know your views on this. Step 1: reminder about new user account management policies enforcement. A first email aking existing FIWARE Lab users to accept the new user account management policies, also covered in the new FIWARE Lab use terms and conditions, was sent to all FIWARE Lab users several weeks ago. A reminder has been sent yesterday and today to current users of the FIWARE Lab telling them that they have until April 15th 2015 19:00 CET. This message will be disseminated through different means: * mailed to current users of the FIWARE Lab * shown in a screen at login of users of the FIWARE Lab * posted on Basecamp so that FIWARE accelerator projects get aware and can forward the remainder to SMEs/startups under their respective programmes * mailed to the FI-PPP SB and the old FI-PPP AB members so that coordinators/architects of the FIWARE Use Case projects can forward the reminder to SMEs/startups under their respective Use Case projects Step 2: Increase of computing capacity in Spain-2 node In parallel and starting TODAY, activities to expand the capacity of the recently launched Spain-2 node will be prioritized so that we reach a capacity of aprox 500 cores in the datacenters located in both Sevilla and Malaga. We expect this expansion be completed by April 20th if not earlier. Additionally, additional capacity (close to 500 additional cores) will be activated in the Spain-2 node with servers located in a new datacenter located in Las Palmas. Conversations are ongoing with Red.es trying to accelerate this process so that this additional 500 cores get available closer to the end of next week. Step 3: New Trial users only allowed to work on Spain-2 node. Limitation of number of concurrent trial users. Changes will be implemented in the Cloud portal and the user account registration process/tool by UPM so that new Trial users will only see the Spain-2 node. In addition, Trial users will be limited to 100 Trial users. Note that the "Trial Users", until the new IdM/Keystone component is deployed, will need to be identified by considering the creation of their user account. Actually, "Trial users" will be those users who have created their account after April 16th. Most likely, the fact that Trial users will only be allowed to work on Spain will remain. The number of Trial users allowed may increase (the EC has shown its concern about keeping the number of Trial users too low) but will see. Users who try to create an account when the limit on Trial users have been reached, will receive a message indicating that the limit has been reached, inviting them to try again in two weeks (Fernando to send the wording for this message to UPM). This step should be implemented by this Wednesday April 15th. Step 4: Freeing resources on current nodes, giving users the ability to apply to become community users, asking users in Spain-1 and Prague to migrate Starting April 16th, current nodes will free resources on their nodes (virtual infrastructure and public IP addresses allocated to users who didn't accept the new user account management policies). They should complete this process before April 23rd. FIWARE Lab node providers are aware of the current situation so they should accelerate this process as much as possible, trying to complete the process the sooner the better. Situation will be assessed on April 20th and April 23rd. It is expected that the status of the FIWARE Lab will improve drastically during the week and will become stable by April 23rd. In parallel, we will encourage legacy users (those who created their account before April 16th and have accepted the new terms and conditions) to apply for becoming community users. They should be able to submit their application completing an application form that will be provided to them and will be made available on the Cloud Portal. Those legacy users whose application is accepted and who were hosted in the Spain-1 or the Prague nodes will be asked to migrate their environments to any of the other nodes (a recommendation will be given). The Spain-1 and the Prague nodes will not host community users. As a result, no users will remain in these two nodes by May 1st. Step 5: Deployment of new IdM/Keystone component and upgrading of Community Users. Migration of Spain-1 and Prague nodes to OpenStack Juno. This step will start May 1st. Then, we will deploy the new version of the IdM/Keystone component. Users whose application to become Community Users has been approved will become Community Users. Environments of those Trial users who has overpass the 2 weeks trial period will be cleaned out. From then on, the new user account management policies will be in place, with the new IdM/keystone component supporting the ability to distinguish between kind of users and the nodes each will be able to get access to. In parallel, Spain-1 and Prague nodes should start their migration to Juno. Once they migrate, they will be made available as part of the federation (maybe the physical resources allocated to the Spain-1 node will be assigned to the Spain-2 node). Step 6: Assessment of nodes in the FIWARE Lab federation. Bringing FIWARE Lab nodes into quarantine. After April 23th, performance of the several nodes in the FIWARE Lab federation will be weekly assessed. Those nodes who exhibit a bad performance (instability, low response to request for help by users) will be put into quarantine and their users (Community Users) will be asked to migrate to the Spain-2 node. 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 ________________________________ 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 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 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 _______________________________________________ Fiware-lab-recovery-tf mailing list Fiware-lab-recovery-tf at lists.fiware.org https://lists.fiware.org/listinfo/fiware-lab-recovery-tf -- -- 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 ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From juanjose.hierro at telefonica.com Fri Apr 17 17:12:12 2015 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Fri, 17 Apr 2015 17:12:12 +0200 Subject: [Fiware-lab-recovery-tf] Fwd: HelpDesk Dashboard In-Reply-To: References: Message-ID: <553122CC.2040505@telefonica.com> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Attached Message Part Type: text/calendar Size: 2214 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: HELPDESK-DASHBOARD.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 350295 bytes Desc: not available URL: From juanjose.hierro at telefonica.com Sun Apr 19 19:14:42 2015 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Sun, 19 Apr 2015 19:14:42 +0200 Subject: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab In-Reply-To: References: <552D5D25.1060506@telefonica.com> <552E8A1E.30808@telefonica.com> <896B7FF4-64D7-4B3F-BDE1-657CE75D5214@dit.upm.es> Message-ID: <5533E282.6010203@telefonica.com> An HTML attachment was scrubbed... URL: From fernando.lopezaguilar at telefonica.com Mon Apr 20 01:22:27 2015 From: fernando.lopezaguilar at telefonica.com (FERNANDO LOPEZ AGUILAR) Date: Sun, 19 Apr 2015 23:22:27 +0000 Subject: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab In-Reply-To: <5533E282.6010203@telefonica.com> References: <552D5D25.1060506@telefonica.com> <552E8A1E.30808@telefonica.com> <896B7FF4-64D7-4B3F-BDE1-657CE75D5214@dit.upm.es> <5533E282.6010203@telefonica.com> Message-ID: Inline De: JUAN JOSE HIERRO SUREDA > Fecha: Sunday 19 April 2015 19:14 Para: fla >, ?lvaro Alonso >, Federico Michele Facca > CC: "fiware-lab-recovery-tf at lists.fiware.org" > Asunto: Re: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab Folks, I'm a bit confused about what this means. This means that the UPM thought that the keystone does not work with v2 and v3, thing that it is wrong and we had test last week in order to secure it. The only thing is that it is necessary to define the domain value of v2 field to default and there will be no problem using them in v3. Current version of keystone introduce, as you know, the domain field besides project and user but v2 of the API do not have this value. So the previous data of the Keystone-Proxy just have to make sure that in the migration procedure assign the value ?default? to domain in order that they can work properly. What release of OpenStack is then the release below which we will ask nodes to update and community users to migrate? Icehouse or Juno, preferably Juno but some node just Just as a reminder, besides compatiblity with the new IdM/Keystone, we wanted to have Neutron supported, don't we? On the other hand, I see that "EOL - End of Life" is marked for the Havana release and older releases here: https://wiki.openstack.org/wiki/Releases We know it, only the last two releases are available. I have been always the same since beginning of the project. This means that on 30th Abril the Security-supported will be Juno and Kilo will be the current stable version beside starting the development of Liberty. Therefore, I would say that we should force all nodes to be either on IceHouse or Juno ... shouldn't we? Agree, it is what we are saying to the nodes in Grizzly. I'm telling this because, tomorrow (monday) we should: * Send a message to nodes with OpenStack older than the defined release, asking them to migrate to the defined release or even more recent (should we ask them to migrate to Juno)? Federico has contact with them in order to clarify the status of the migration to Icehouse or Juno and He has planned the next XIFI TM on Tuesday to clarify the status of this task per each node. * Send a message to those users who had accepted the new policies and were hosted in the nodes of the previous point, asking them to migrate to the Spain-2 node @Nacho/@Fernando: how did the planned action on Sevilla-Malaga nodes work yesterday? Any issue? There was a serious issue some of the components of the storage rack and they had to change the component in order to work again. Till Saturday midnight Red.es could not resolve the issue and Sunday he switch on the machine again. @Nacho/@Fernando: did we start cleaning user accounts in the Spain-1 node? You wanted to make some checks because of the large number of users ... but I wonder where we are ... We have a delay in the operation to delete this VMs that we hope recover during Monday due to this problem. Previously we need to check that the Spain and Spain2 are working properly after the power supply intervention and then we make the cleaning. Regarding the check of the user, we were making some aleatory test over de user last week in order to secure the process but we have no time to analyse the resources of 1000 people. On Monday, in the FIWARE Lab Recovery Task Force PhC, we give you more details about in which step we will be. Cheers, -- Juanjo On 17/04/15 15:18, FERNANDO LOPEZ AGUILAR wrote: Well, keep in mind that in order to be fully compatible you need to assing the value default to hte domain of the user previously defined in v2 or defined in v2 in order that it can work properly. Fernando De: ?lvaro Alonso > Fecha: Friday 17 April 2015 13:40 Para: Federico Michele Facca > CC: "fiware-lab-recovery-tf at lists.fiware.org" > Asunto: Re: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab Hi all, good news. During this morning Henar and I have made tests in Havana dev environment and we have succeeded in the configuration of the node with Keystone v3. The summary is that we can configure nodes' services with v2 and all the resources stored in Keystone v3 (in the default domain) are accesible. So according to that every node would work without changing the current configuration. Anyway in other to be sure and to have a definitively conclusion we prefer to perform more tests on Monday. So we will update with the final conclusion that day. BR -- ?lvaro El 17 Apr 2015, a las 13:27, Federico Michele Facca > escribi?: On Wed, Apr 15, 2015 at 5:56 PM, Juanjo Hierro > wrote: Dear Federico, User type management indeed depends on the deployment of the new IdM, but a) this doesn't prevent that we start taking note about who is willing to become a Community User in May 1st, b) in some cases, eventually assign them the requested quota before May 1st (even though they would not yet ticketed as "Community Users" yet in the system). sure, i was asking only to be sure what information to pass to coaches and we will be able to close the consider close the community request processes. Cheers, -- Juanjo On 15/04/15 06:11, Federico Michele Facca wrote: Ps: i forgot to mention that in my understanding user type management was depending on the deployment of the new idm, but maybe upm has in mind a solution that does not require that. ----------------------------------------- Apologizes for mispellings. My thumb is not compatible with Android On Apr 15, 2015 5:58 AM, "Federico Michele Facca" > wrote: Dear Juanjo, some comments from my side: 1) Maurizio as XIFI coordinator, needs to be in the loop. While I agree that some nodes - probably like some GEs developers btw - don't deserve ths money they have been granted for the service given, any action and decision in this direction within XIFI is beyond my role. Not sure if and how saved money could be employed. Moved to FI-CORE? 2) According to a short discussion I had with Alvaro, Migration to new IDM my affect as well other nodes still using Grizzly, this needs to be clarified asap in order to take proper actions (i.e. Accelerate migration plan). 3) It is very important to agree on fair, objective and not arguable metrics to define performance. As early mentioned errors from tests due to finished resources do not mean "bad performance" (if not this would be the case as well for spain), this case is a more general issue related to the tools and functions provided on top of nodes, for which we cannot account them. 4) There are nodes operating for "free", what should we do in such cases? I would keep possibility fir user with proper role to use them, regardeless, no financial penality can be passed over to them. when the message is finalized and agreed, i can inform lab nodes. Best, Federico ----------------------------------------- Apologizes for mispellings. My thumb is not compatible with Android On Apr 14, 2015 8:32 PM, "Juanjo Hierro" > wrote: Dear all, I have added Thierry Nagellen from Orange to this mailing list because despite he is not involved in the Task Force "per se", we are synchronized also with Orange overall with respect to messages to pass to the EC and rest of FI-PPP projects. If you believe someone else has to be in this list, please let me know. It has come out that deployment of the new IdM/Keystone is not feasible as planned. Therefore, we have to define a new plan. This morning, the TID team (including me) have had the opportunity to meet with the UPM team to understand the issue and we have come with an alternative plan for the recovery of the FIWARE Lab than the one we defined yesterday which sounds pretty reasonable and may help us to soon improve the situation. Let me summarize the plan in this email so that we are all on the same page. If you find some weakness/issue, please raise it. Otherwise, let's stick to it. Fortunately, the first steps remain the same and they have already been done, so we are on the right track. An important matter: I plan to send this plan to the EC tomorrow morning at 11:00. If you have comments, you should provide them before that deadline. I will also communicate this plan to FIWARE Accelerator projects on Basecamp as well as to Use Case projects through the FI-PPP mailing lists. Federico or Engineering should communicate this plan to organizations operating the FIWARE Lab nodes also at that time. A very sensible matter: when you review step 6 you will see that we cover the case in which some FIWARE Lab nodes may be put in quarantine. I would like to propose to the EC that those FIWARE lab nodes which are put into quarantine will be labeled as non-performance so they won't get the grant they were assigned in the XiFi Open Call, at least for the remaining of the XiFi project (until September). Maybe these funds can be given away to other partners or launch another Open Call. I would like to know your views on this. Step 1: reminder about new user account management policies enforcement. A first email aking existing FIWARE Lab users to accept the new user account management policies, also covered in the new FIWARE Lab use terms and conditions, was sent to all FIWARE Lab users several weeks ago. A reminder has been sent yesterday and today to current users of the FIWARE Lab telling them that they have until April 15th 2015 19:00 CET. This message will be disseminated through different means: * mailed to current users of the FIWARE Lab * shown in a screen at login of users of the FIWARE Lab * posted on Basecamp so that FIWARE accelerator projects get aware and can forward the remainder to SMEs/startups under their respective programmes * mailed to the FI-PPP SB and the old FI-PPP AB members so that coordinators/architects of the FIWARE Use Case projects can forward the reminder to SMEs/startups under their respective Use Case projects Step 2: Increase of computing capacity in Spain-2 node In parallel and starting TODAY, activities to expand the capacity of the recently launched Spain-2 node will be prioritized so that we reach a capacity of aprox 500 cores in the datacenters located in both Sevilla and Malaga. We expect this expansion be completed by April 20th if not earlier. Additionally, additional capacity (close to 500 additional cores) will be activated in the Spain-2 node with servers located in a new datacenter located in Las Palmas. Conversations are ongoing with Red.es trying to accelerate this process so that this additional 500 cores get available closer to the end of next week. Step 3: New Trial users only allowed to work on Spain-2 node. Limitation of number of concurrent trial users. Changes will be implemented in the Cloud portal and the user account registration process/tool by UPM so that new Trial users will only see the Spain-2 node. In addition, Trial users will be limited to 100 Trial users. Note that the "Trial Users", until the new IdM/Keystone component is deployed, will need to be identified by considering the creation of their user account. Actually, "Trial users" will be those users who have created their account after April 16th. Most likely, the fact that Trial users will only be allowed to work on Spain will remain. The number of Trial users allowed may increase (the EC has shown its concern about keeping the number of Trial users too low) but will see. Users who try to create an account when the limit on Trial users have been reached, will receive a message indicating that the limit has been reached, inviting them to try again in two weeks (Fernando to send the wording for this message to UPM). This step should be implemented by this Wednesday April 15th. Step 4: Freeing resources on current nodes, giving users the ability to apply to become community users, asking users in Spain-1 and Prague to migrate Starting April 16th, current nodes will free resources on their nodes (virtual infrastructure and public IP addresses allocated to users who didn't accept the new user account management policies). They should complete this process before April 23rd. FIWARE Lab node providers are aware of the current situation so they should accelerate this process as much as possible, trying to complete the process the sooner the better. Situation will be assessed on April 20th and April 23rd. It is expected that the status of the FIWARE Lab will improve drastically during the week and will become stable by April 23rd. In parallel, we will encourage legacy users (those who created their account before April 16th and have accepted the new terms and conditions) to apply for becoming community users. They should be able to submit their application completing an application form that will be provided to them and will be made available on the Cloud Portal. Those legacy users whose application is accepted and who were hosted in the Spain-1 or the Prague nodes will be asked to migrate their environments to any of the other nodes (a recommendation will be given). The Spain-1 and the Prague nodes will not host community users. As a result, no users will remain in these two nodes by May 1st. Step 5: Deployment of new IdM/Keystone component and upgrading of Community Users. Migration of Spain-1 and Prague nodes to OpenStack Juno. This step will start May 1st. Then, we will deploy the new version of the IdM/Keystone component. Users whose application to become Community Users has been approved will become Community Users. Environments of those Trial users who has overpass the 2 weeks trial period will be cleaned out. From then on, the new user account management policies will be in place, with the new IdM/keystone component supporting the ability to distinguish between kind of users and the nodes each will be able to get access to. In parallel, Spain-1 and Prague nodes should start their migration to Juno. Once they migrate, they will be made available as part of the federation (maybe the physical resources allocated to the Spain-1 node will be assigned to the Spain-2 node). Step 6: Assessment of nodes in the FIWARE Lab federation. Bringing FIWARE Lab nodes into quarantine. After April 23th, performance of the several nodes in the FIWARE Lab federation will be weekly assessed. Those nodes who exhibit a bad performance (instability, low response to request for help by users) will be put into quarantine and their users (Community Users) will be asked to migrate to the Spain-2 node. 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 ________________________________ 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 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 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 _______________________________________________ Fiware-lab-recovery-tf mailing list Fiware-lab-recovery-tf at lists.fiware.org https://lists.fiware.org/listinfo/fiware-lab-recovery-tf -- -- 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 ________________________________ 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.orghttps://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 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From federico.facca at create-net.org Mon Apr 20 11:52:51 2015 From: federico.facca at create-net.org (Federico Michele Facca) Date: Mon, 20 Apr 2015 11:52:51 +0200 Subject: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab In-Reply-To: References: <552D5D25.1060506@telefonica.com> <552E8A1E.30808@telefonica.com> <896B7FF4-64D7-4B3F-BDE1-657CE75D5214@dit.upm.es> <5533E282.6010203@telefonica.com> Message-ID: On Mon, Apr 20, 2015 at 1:22 AM, FERNANDO LOPEZ AGUILAR < fernando.lopezaguilar at telefonica.com> wrote: > Inline > > De: JUAN JOSE HIERRO SUREDA > Fecha: Sunday 19 April 2015 19:14 > Para: fla , ?lvaro Alonso < > aalonsog at dit.upm.es>, Federico Michele Facca < > federico.facca at create-net.org> > CC: "fiware-lab-recovery-tf at lists.fiware.org" < > fiware-lab-recovery-tf at lists.fiware.org> > Asunto: Re: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of > the FIWARE Lab > > Folks, > > I'm a bit confused about what this means. > > This means that the UPM thought that the keystone does not work with v2 > and v3, thing that it is wrong and we had test last week in order to secure > it. The only thing is that it is necessary to define the domain value of v2 > field to default and there will be no problem using them in v3. Current > version of keystone introduce, as you know, the domain field besides > project and user but v2 of the API do not have this value. So the previous > data of the Keystone-Proxy just have to make sure that in the migration > procedure assign the value ?default? to domain in order that they can work > properly. > > What release of OpenStack is then the release below which we will ask > nodes to update and community users to migrate? > > Icehouse or Juno, preferably Juno but some node just > > Just as a reminder, besides compatiblity with the new IdM/Keystone, we > wanted to have Neutron supported, don't we? On the other hand, I see that > "EOL - End of Life" is marked for the Havana release and older releases > here: > > https://wiki.openstack.org/wiki/Releases > > We know it, only the last two releases are available. I have been always > the same since beginning of the project. This means that on 30th Abril the > Security-supported will be Juno and Kilo will be the current stable version > beside starting the development of Liberty. > > Therefore, I would say that we should force all nodes to be either on > IceHouse or Juno ... shouldn't we? > > Agree, it is what we are saying to the nodes in Grizzly. > +1 on fernando comments, the only additional meaning i see is that upgrade plan does not need to be rushed out, but we can proceed more smoothly minimizing nodes down at the same time for end-users. cheers, federico -- -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From juanjose.hierro at telefonica.com Mon Apr 20 17:39:55 2015 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Mon, 20 Apr 2015 17:39:55 +0200 Subject: [Fiware-lab-recovery-tf] Feedback from Peter Fatelnig on statistics regarding resolution of tickets In-Reply-To: <6C981BE2-E7F3-442E-A2F6-59906F976C8E@ec.europa.eu> References: <6C981BE2-E7F3-442E-A2F6-59906F976C8E@ec.europa.eu> Message-ID: <55351DCB.1090207@telefonica.com> An HTML attachment was scrubbed... URL: From aalonsog at dit.upm.es Wed Apr 22 12:15:27 2015 From: aalonsog at dit.upm.es (=?utf-8?Q?=C3=81lvaro_Alonso?=) Date: Wed, 22 Apr 2015 12:15:27 +0200 Subject: [Fiware-lab-recovery-tf] Email for the users Message-ID: <1FB196F5-C3AF-4686-8F74-02319CD93C4C@dit.upm.es> Hi all, this is the draft of the email I?m going to send to the users regarding actions 16, 29 and 31 of our document. Please, if you have a minute to review if and provide feedback. Many thanks -- ?lvaro Reminders regarding new Terms and Conditions Dear FIWARE lab user, as you know we are going to introduce some changes in the behaviour of the Lab as a consequence of the new Terms and Conditions. This email is a reminder of few things you have to take into account to continue enjoying FIWARE Lab. 1. Spain1 and Prague regions will not be available anymore so if you have cloud resources deployed there and your Community Account request has been accepted, please, migrate those resources to Spain2 region. 2. If you have created your account before April 15th and you have accepted the new T&C, from May 1st you will be a Trial user and you will be able to operate only in Spain2 region. So if you have resources in other regions, please, migrate them to Spain2 region. From May 1st and as a Trial user, you will have a 14 days period to continue using the platform in Spain2 region. Then you can apply for a Community Account to have a longer term environment for working on FIWARE Cloud following the application process. 3. In the cloud environment only organizations linked to the FIWARE accounts could be used. Organizations that you create ?by hand? using the Account Portal interface, could not be used in the cloud scope. But don?t worry, you will be able to share access to that organization by authorizing other users in it. The default name of the organization linked to your account will be ?your_email cloud? (for instance ?example at domain.com cloud?) but you will be able to modify it. Take into account that other organizations will not be accesible from the Cloud Portal anymore so, please, migrate all the resources to your account-linked organization before May 1st. The current name of that organization fits with your user name. After May 1st and as a consequence of these 3 points, FIWARE Lab providers will not be responsible for the loss of any data. If you have not applied for a Community account and your Trial period has expired, you will be able to continue using all FIWARE Lab capacities except cloud environment. Using the Account Portal you will be able to manage your organizations, your users and your applications in order to provide authentication and authorization in your services as you are doing now, via OAuth2 protocol and GEs such as Wilma PEP Proxy or AuthZForce. You have only to take into account two updates when the new FIWARE Account release is deployed the first week of May: - If you are using organizations ids in your application or GE you have to convert them adding as many zeros as necessary to make them 32 chars length. For instance, the organization ?241? now will be ?00000000000000000000000000000241?. - If you are using users ids in your application or GE you have to take into account that the new unique identifier will be the one that now is retrieved as ?nickName? field. Please, take the opportune actions to update your environments according this. -------------- next part -------------- An HTML attachment was scrubbed... URL: From aalonsog at dit.upm.es Wed Apr 22 16:45:57 2015 From: aalonsog at dit.upm.es (=?utf-8?Q?=C3=81lvaro_Alonso?=) Date: Wed, 22 Apr 2015 16:45:57 +0200 Subject: [Fiware-lab-recovery-tf] audio today? Message-ID: <1E9C9325-46E2-4A65-8802-3DE9F28A65A9@dit.upm.es> Hi, Silvio Joaquin and I are connected? -- ?lvaro -------------- next part -------------- An HTML attachment was scrubbed... URL: From federico.facca at create-net.org Thu Apr 23 18:13:14 2015 From: federico.facca at create-net.org (Federico Michele Facca) Date: Thu, 23 Apr 2015 18:13:14 +0200 Subject: [Fiware-lab-recovery-tf] FI-PPP projects and community accounts Message-ID: Dear All, there are a number of Phase II projects that are hosting applications / demos in the Lab. I think it is fair to grant them the community account and the resources (especially for already deployed applications). Then, as with accellertor applicatns, we can argue if they want too many resources. Let me know if you think differently. Federico -- -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From juanjose.hierro at telefonica.com Thu Apr 23 19:31:30 2015 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Thu, 23 Apr 2015 19:31:30 +0200 Subject: [Fiware-lab-recovery-tf] FI-PPP projects and community accounts In-Reply-To: References: Message-ID: <55392C72.4040903@telefonica.com> An HTML attachment was scrubbed... URL: From juanjose.hierro at telefonica.com Thu Apr 23 19:34:04 2015 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Thu, 23 Apr 2015 19:34:04 +0200 Subject: [Fiware-lab-recovery-tf] Confcall with the EC to track progress TOMORROW Message-ID: <55392D0C.1010106@telefonica.com> Folks, We have been asked by the EC (JV and Peter Fatelning) to run a confcall tomorrow to follow-up overall progress. Can someone summarize the status? Is the Action Plan table up to date? Thanks in advance, -- 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 ________________________________ 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 From federico.facca at create-net.org Thu Apr 23 22:16:06 2015 From: federico.facca at create-net.org (Federico Michele Facca) Date: Thu, 23 Apr 2015 22:16:06 +0200 Subject: [Fiware-lab-recovery-tf] FI-PPP projects and community accounts In-Reply-To: <55392C72.4040903@telefonica.com> References: <55392C72.4040903@telefonica.com> Message-ID: Hi Juanjo, yesterday there was the call and we progressed in the reporting who was in the call (silvio replaced me). Today - apparently it was holiday in Spain? - it was only me and Alvaro, we discussed some points in relation to the new idm. Best, Federico On Thu, Apr 23, 2015 at 7:31 PM, Juanjo Hierro < juanjose.hierro at telefonica.com> wrote: > > I agree ... but they have to issue their request to become Community > Users. > > Let's be strick with the rules. > > BTW, I guess you were aware of that, but Stefano and me were yesterday, > today and tomorrow unable to join our daily meeting. I hope you have > proceed anyway and actually make progress. Please confirm. > > Best regards, > > -- Juanjo > > > On 23/04/15 18:13, Federico Michele Facca wrote: > > Dear All, > there are a number of Phase II projects that are hosting applications / > demos in the Lab. I think it is fair to grant them the community account > and the resources (especially for already deployed applications). Then, as > with accellertor applicatns, we can argue if they want too many resources. > > Let me know if you think differently. > Federico > > -- > -- > 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 listFiware-lab-recovery-tf at lists.fiware.orghttps://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 > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From juanjose.hierro at telefonica.com Mon Apr 27 00:21:16 2015 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Mon, 27 Apr 2015 00:21:16 +0200 Subject: [Fiware-lab-recovery-tf] Cannot we provide a better look&feel? Message-ID: <553D64DC.4080605@telefonica.com> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cjbcahcg.png Type: image/png Size: 375116 bytes Desc: not available URL: From juanjose.hierro at telefonica.com Mon Apr 27 00:25:14 2015 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Mon, 27 Apr 2015 00:25:14 +0200 Subject: [Fiware-lab-recovery-tf] Cannot we provide a better look&feel? In-Reply-To: <553D64DC.4080605@telefonica.com> References: <553D64DC.4080605@telefonica.com> Message-ID: <553D65CA.40809@telefonica.com> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 375116 bytes Desc: not available URL: From aalonsog at dit.upm.es Mon Apr 27 10:56:01 2015 From: aalonsog at dit.upm.es (=?utf-8?Q?=C3=81lvaro_Alonso?=) Date: Mon, 27 Apr 2015 10:56:01 +0200 Subject: [Fiware-lab-recovery-tf] Cannot we provide a better look&feel? In-Reply-To: <553D65CA.40809@telefonica.com> References: <553D64DC.4080605@telefonica.com> <553D65CA.40809@telefonica.com> Message-ID: Hi Juanjo, we have just deployed a new version with all the fixes. BR -- ?lvaro > El 27 Apr 2015, a las 00:25, Juanjo Hierro escribi?: > > > BTW, the messages ends abruptly as follows "please contact our Technical Support Team sending an email to ." an no email address is provided ... > > Had someone tested that the message that we were providing? > > Come on! > > -- Juanjo > > > On 27/04/15 00:21, Juanjo Hierro wrote: >> Hi, >> >> I wanted to try myself the experience when a user tries to sign up on the FIWARE Lab and the number of trial users has reached the limit. >> >> Check below a screenshot of the screen I get. Isn't it feasible to get a better (more profesional) look&feel? >> Why the "here" associated to the link to the application form for upgrading of the accounts is splitted into two lines? >> Wouldn't it be feasible that the word "here" appears with another color (or at least underlined) so that people can find out easily it is an URL link? >> Couldn't we choose a font for the message in line with the style guides we defined for user interfaces? >> Cannot we position the box with the message at the left of the box with the title "Sign Up" on the left upper corner? >> Sincerely, it doesn''t cost that much to make the things look more professional ... >> Best regards, >> -- 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 > _______________________________________________ > Fiware-lab-recovery-tf mailing list > 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: From aalonsog at dit.upm.es Mon Apr 27 10:57:08 2015 From: aalonsog at dit.upm.es (=?utf-8?Q?=C3=81lvaro_Alonso?=) Date: Mon, 27 Apr 2015 10:57:08 +0200 Subject: [Fiware-lab-recovery-tf] Cannot we provide a better look&feel? In-Reply-To: References: <553D64DC.4080605@telefonica.com> <553D65CA.40809@telefonica.com> Message-ID: <8FA4D850-0A38-4859-BCCD-63E305D79172@dit.upm.es> This is the new screen: -- ?lvaro > El 27 Apr 2015, a las 10:56, ?lvaro Alonso escribi?: > > Hi Juanjo, > > we have just deployed a new version with all the fixes. > > BR > -- > ?lvaro > >> El 27 Apr 2015, a las 00:25, Juanjo Hierro > escribi?: >> >> >> BTW, the messages ends abruptly as follows "please contact our Technical Support Team sending an email to ." an no email address is provided ... >> >> Had someone tested that the message that we were providing? >> >> Come on! >> >> -- Juanjo >> >> >> On 27/04/15 00:21, Juanjo Hierro wrote: >>> Hi, >>> >>> I wanted to try myself the experience when a user tries to sign up on the FIWARE Lab and the number of trial users has reached the limit. >>> >>> Check below a screenshot of the screen I get. Isn't it feasible to get a better (more profesional) look&feel? >>> Why the "here" associated to the link to the application form for upgrading of the accounts is splitted into two lines? >>> Wouldn't it be feasible that the word "here" appears with another color (or at least underlined) so that people can find out easily it is an URL link? >>> Couldn't we choose a font for the message in line with the style guides we defined for user interfaces? >>> Cannot we position the box with the message at the left of the box with the title "Sign Up" on the left upper corner? >>> Sincerely, it doesn''t cost that much to make the things look more professional ... >>> Best regards, >>> -- 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 >> _______________________________________________ >> Fiware-lab-recovery-tf mailing list >> 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: Captura de pantalla 2015-04-27 a las 10.56.29.png Type: image/png Size: 251628 bytes Desc: not available URL: From federico.facca at create-net.org Mon Apr 27 19:13:17 2015 From: federico.facca at create-net.org (Federico Michele Facca) Date: Mon, 27 Apr 2015 19:13:17 +0200 Subject: [Fiware-lab-recovery-tf] Fwd: [Fiware-lab-help] Move from FI-LAB to other host In-Reply-To: References: Message-ID: we need to elaborate a faq for this type of questions, i would suppose. of course, if you meant to have a running commercial instance of fiware, this is the time to step-in, of your company will lose potential customers :) federico ---------- Forwarded message ---------- From: Jon Vadillo Date: Mon, Apr 27, 2015 at 3:45 PM Subject: [Fiware-lab-help] Move from FI-LAB to other host To: fiware-lab-help at lists.fi-ware.org Dear FIWARE team, We have a question about FIWARE hosting alternatives. After using Filab and when it is time to move a comercial version of our application to a private hosting solution (e.g. Amazon Cloud Services), which are the most choosen solutions by developers? Our requirements are quite simple (we are using Orion Context Broker, COSMOS and Application Mashup-Wirecloud) but we don't know wich providers could satisfy our needs. Help you very much for your attention, Jon _______________________________________________ Fiware-lab-help mailing list Fiware-lab-help at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-lab-help -- -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefano.depanfilis at eng.it Tue Apr 28 07:33:08 2015 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Tue, 28 Apr 2015 07:33:08 +0200 Subject: [Fiware-lab-recovery-tf] Fwd: [Fiware-lab-help] Move from FI-LAB to other host In-Reply-To: References: Message-ID: Well, the engineering platform is already available Ciao Stefano Il 27/Apr/2015 19:13, "Federico Michele Facca" < federico.facca at create-net.org> ha scritto: > we need to elaborate a faq for this type of questions, i would suppose. of > course, if you meant to have a running commercial instance of fiware, this > is the time to step-in, of your company will lose potential customers :) > > federico > > ---------- Forwarded message ---------- > From: Jon Vadillo > Date: Mon, Apr 27, 2015 at 3:45 PM > Subject: [Fiware-lab-help] Move from FI-LAB to other host > To: fiware-lab-help at lists.fi-ware.org > > > Dear FIWARE team, > > We have a question about FIWARE hosting alternatives. After using Filab > and when it is time to move a comercial version of our application to a > private hosting solution (e.g. Amazon Cloud Services), which are the most > choosen solutions by developers? Our requirements are quite simple (we are > using Orion Context Broker, COSMOS and Application Mashup-Wirecloud) but we > don't know wich providers could satisfy our needs. > > Help you very much for your attention, > Jon > > _______________________________________________ > Fiware-lab-help mailing list > Fiware-lab-help at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-lab-help > > > > > -- > -- > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From federico.facca at create-net.org Tue Apr 28 07:53:45 2015 From: federico.facca at create-net.org (Federico Michele Facca) Date: Tue, 28 Apr 2015 07:53:45 +0200 Subject: [Fiware-lab-recovery-tf] Fwd: [Fiware-lab-help] Move from FI-LAB to other host In-Reply-To: References: Message-ID: nice! but still we need to make this visible and provide reference to users like Jon ! On Tue, Apr 28, 2015 at 7:33 AM, stefano de panfilis < stefano.depanfilis at eng.it> wrote: > Well, the engineering platform is already available > > Ciao > Stefano > Il 27/Apr/2015 19:13, "Federico Michele Facca" < > federico.facca at create-net.org> ha scritto: > >> we need to elaborate a faq for this type of questions, i would suppose. >> of course, if you meant to have a running commercial instance of fiware, >> this is the time to step-in, of your company will lose potential customers >> :) >> >> federico >> >> ---------- Forwarded message ---------- >> From: Jon Vadillo >> Date: Mon, Apr 27, 2015 at 3:45 PM >> Subject: [Fiware-lab-help] Move from FI-LAB to other host >> To: fiware-lab-help at lists.fi-ware.org >> >> >> Dear FIWARE team, >> >> We have a question about FIWARE hosting alternatives. After using Filab >> and when it is time to move a comercial version of our application to a >> private hosting solution (e.g. Amazon Cloud Services), which are the most >> choosen solutions by developers? Our requirements are quite simple (we are >> using Orion Context Broker, COSMOS and Application Mashup-Wirecloud) but we >> don't know wich providers could satisfy our needs. >> >> Help you very much for your attention, >> Jon >> >> _______________________________________________ >> Fiware-lab-help mailing list >> Fiware-lab-help at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-lab-help >> >> >> >> >> -- >> -- >> 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 >> > -- -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From juanjose.hierro at telefonica.com Tue Apr 28 12:04:55 2015 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Tue, 28 Apr 2015 12:04:55 +0200 Subject: [Fiware-lab-recovery-tf] Daily meetings? Message-ID: <553F5B47.70302@telefonica.com> An HTML attachment was scrubbed... URL: From stefano.depanfilis at eng.it Tue Apr 28 13:51:39 2015 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Tue, 28 Apr 2015 13:51:39 +0200 Subject: [Fiware-lab-recovery-tf] Daily meetings? In-Reply-To: <553F5B47.70302@telefonica.com> References: <553F5B47.70302@telefonica.com> Message-ID: dear juanjo, as said during the call on last wednesday, we announced that alfonso was having internal training courses till friday and that also i was with you ad the adv board. thing are now and should be regularly back. ciao, stefano 2015-04-28 12:04 GMT+02:00 Juanjo Hierro : > Dear all, > > I was informed that participation in Daily meetings has gone down > dramatically since Wednesday last week (actually, when I stopped attending > because my attendance to the FI-PPP Advisory Board meeting) ... > > I rather do not understand this ... Wasn't Engineering supposed to run > these meetings from a point on? Come on! I don't believe it is a good > idea that we assume that everything is fixed and we can relax ! Yes, > it's true we have made very good progress and we are probably starting to > get things under control, but there are still a lot of things to get done > even discuss how to solve. > > This week I'm again not able to get involved in the Daily meetings > because I'm attending the FI-WARE project final review. However, I expect > that you continue dealing with it. > > If there is any action that has to be assigned to me, don't hesitate to > assign it to me. Although I'll try to keep an eye, it would be nice if > you let me know. I count on Fernando to give me a signal that there is > something on my plate. Actually, if there is something currently on my > plate, please let me know. > > Some feedback on topics that I believe you should address (again, let me > know if there is something about which it is expected that I have to do > something): > > - Reminders to users of Spain and Prague nodes about migrating to > Spain-2 > - Assignment of the right roles (Community, Trial) to existing users > on May 1st > - Being able to deal with users that require an environment more > stable than the one assigned to Trial Users but may not need, on the other > hand, an environment for 9 months (e.g., users who are submitting > applications to some Open Call and are required to setup some demo on the > FIWARE Lab using FIWARE technologies regarding their proposal) ... should > we define another category of users ... or define an attribute linked to > Trial Users kind of "expiration time" that can be managed by administrators > of nodes? > - ... > > > Best regards, > > -- 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 > > > ------------------------------ > > 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 > 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: From stefano.depanfilis at eng.it Tue Apr 28 15:04:09 2015 From: stefano.depanfilis at eng.it (stefano de panfilis) Date: Tue, 28 Apr 2015 15:04:09 +0200 Subject: [Fiware-lab-recovery-tf] Daily meetings? In-Reply-To: References: <553F5B47.70302@telefonica.com> Message-ID: dear juanjo, got confirmation from alfonoso that yesterday the call was regular with 6 attendees, which means everybody but you and i. so i do not see any problem here. ciao, stefano 2015-04-28 13:51 GMT+02:00 stefano de panfilis : > dear juanjo, > > as said during the call on last wednesday, we announced that alfonso was > having internal training courses till friday and that also i was with you > ad the adv board. > thing are now and should be regularly back. > > ciao, > stefano > > 2015-04-28 12:04 GMT+02:00 Juanjo Hierro : > >> Dear all, >> >> I was informed that participation in Daily meetings has gone down >> dramatically since Wednesday last week (actually, when I stopped attending >> because my attendance to the FI-PPP Advisory Board meeting) ... >> >> I rather do not understand this ... Wasn't Engineering supposed to run >> these meetings from a point on? Come on! I don't believe it is a good >> idea that we assume that everything is fixed and we can relax ! Yes, >> it's true we have made very good progress and we are probably starting to >> get things under control, but there are still a lot of things to get done >> even discuss how to solve. >> >> This week I'm again not able to get involved in the Daily meetings >> because I'm attending the FI-WARE project final review. However, I expect >> that you continue dealing with it. >> >> If there is any action that has to be assigned to me, don't hesitate to >> assign it to me. Although I'll try to keep an eye, it would be nice if >> you let me know. I count on Fernando to give me a signal that there is >> something on my plate. Actually, if there is something currently on my >> plate, please let me know. >> >> Some feedback on topics that I believe you should address (again, let >> me know if there is something about which it is expected that I have to do >> something): >> >> - Reminders to users of Spain and Prague nodes about migrating to >> Spain-2 >> - Assignment of the right roles (Community, Trial) to existing users >> on May 1st >> - Being able to deal with users that require an environment more >> stable than the one assigned to Trial Users but may not need, on the other >> hand, an environment for 9 months (e.g., users who are submitting >> applications to some Open Call and are required to setup some demo on the >> FIWARE Lab using FIWARE technologies regarding their proposal) ... should >> we define another category of users ... or define an attribute linked to >> Trial Users kind of "expiration time" that can be managed by administrators >> of nodes? >> - ... >> >> >> Best regards, >> >> -- 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 >> >> >> ------------------------------ >> >> 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 >> 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 > > -- 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: From depa at eng.it Wed Apr 22 16:58:53 2015 From: depa at eng.it (Stefano De Panfilis) Date: Wed, 22 Apr 2015 15:58:53 +0100 Subject: [Fiware-lab-recovery-tf] R: audio today? Message-ID: Dear Alvaro and all, as said yesterday alfonso Till friday is attending company training. I'm abroad unfortunately now in a noicy airport... I thought juanjo or fede or Fernando to be there. Isn't It?? CiaoStefano? Inviato dal mio dispositivo Samsung -------- Messaggio originale -------- Da: ?lvaro Alonso Data: 22/04/2015 15:45 (GMT+00:00) A: fiware-lab-recovery-tf at lists.fiware.org Oggetto: [Fiware-lab-recovery-tf] audio today? Hi, Silvio Joaquin and I are connected?? --??lvaro -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsalvachua at dit.upm.es Thu Apr 23 20:20:45 2015 From: jsalvachua at dit.upm.es (=?utf-8?Q?Joaqu=C3=ADn_Salvach=C3=BAa?=) Date: Thu, 23 Apr 2015 20:20:45 +0200 Subject: [Fiware-lab-recovery-tf] FI-PPP projects and community accounts In-Reply-To: <55392C72.4040903@telefonica.com> References: <55392C72.4040903@telefonica.com> Message-ID: <89C2179F-0E4D-4AA9-A116-36AFACF4415B@dit.upm.es> Hello, Yesterday all the task where reviewed and all was done or on track. Today just Create Net and UPM was on the call and all our task where done or On Track. Best Regards Joaqu?n > El 23/4/2015, a las 19:31, Juanjo Hierro escribi?: > > > I agree ... but they have to issue their request to become Community Users. > > Let's be strick with the rules. > > BTW, I guess you were aware of that, but Stefano and me were yesterday, today and tomorrow unable to join our daily meeting. I hope you have proceed anyway and actually make progress. Please confirm. > > Best regards, > > -- Juanjo > > On 23/04/15 18:13, Federico Michele Facca wrote: >> Dear All, >> there are a number of Phase II projects that are hosting applications / demos in the Lab. I think it is fair to grant them the community account and the resources (especially for already deployed applications). Then, as with accellertor applicatns, we can argue if they want too many resources. >> >> Let me know if you think differently. >> Federico >> >> -- >> -- >> 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 > > -- > > ______________________________________________________ > > 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 > _______________________________________________ > Fiware-lab-recovery-tf mailing list > 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: From jsalvachua at dit.upm.es Fri Apr 24 16:47:40 2015 From: jsalvachua at dit.upm.es (=?utf-8?Q?Joaqu=C3=ADn_Salvach=C3=BAa?=) Date: Fri, 24 Apr 2015 16:47:40 +0200 Subject: [Fiware-lab-recovery-tf] FI-PPP projects and community accounts In-Reply-To: References: <55392C72.4040903@telefonica.com> Message-ID: Hello, After some waiting Jose Ignacio and Me decided to close the call. From UPM side all the task assigned with deadline end to close are on the DONE. Best Regards and have a nice weekend Joaquin > El 23/4/2015, a las 22:16, Federico Michele Facca escribi?: > > Hi Juanjo, > yesterday there was the call and we progressed in the reporting who was in the call (silvio replaced me). Today - apparently it was holiday in Spain? - it was only me and Alvaro, we discussed some points in relation to the new idm. > > Best, > Federico > > On Thu, Apr 23, 2015 at 7:31 PM, Juanjo Hierro >wrote: > > I agree ... but they have to issue their request to become Community Users. > > Let's be strick with the rules. > > BTW, I guess you were aware of that, but Stefano and me were yesterday, today and tomorrow unable to join our daily meeting. I hope you have proceed anyway and actually make progress. Please confirm. > > Best regards, > > -- Juanjo > > > On 23/04/15 18:13, Federico Michele Facca wrote: >> Dear All, >> there are a number of Phase II projects that are hosting applications / demos in the Lab. I think it is fair to grant them the community account and the resources (especially for already deployed applications). Then, as with accellertor applicatns, we can argue if they want too many resources. >> >> Let me know if you think differently. >> Federico >> >> -- >> -- >> 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 > > -- > > ______________________________________________________ > > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From juanjose.hierro at telefonica.com Thu Apr 30 06:24:22 2015 From: juanjose.hierro at telefonica.com (Juanjo Hierro) Date: Thu, 30 Apr 2015 06:24:22 +0200 Subject: [Fiware-lab-recovery-tf] Cannot we provide a better look&feel? In-Reply-To: <8FA4D850-0A38-4859-BCCD-63E305D79172@dit.upm.es> References: <553D64DC.4080605@telefonica.com> <553D65CA.40809@telefonica.com> <8FA4D850-0A38-4859-BCCD-63E305D79172@dit.upm.es> Message-ID: <5541AE76.5070407@telefonica.com> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 251628 bytes Desc: not available URL: From aalonsog at dit.upm.es Thu Apr 30 08:54:19 2015 From: aalonsog at dit.upm.es (=?utf-8?Q?=C3=81lvaro_Alonso?=) Date: Thu, 30 Apr 2015 08:54:19 +0200 Subject: [Fiware-lab-recovery-tf] Cannot we provide a better look&feel? In-Reply-To: <5541AE76.5070407@telefonica.com> References: <553D64DC.4080605@telefonica.com> <553D65CA.40809@telefonica.com> <8FA4D850-0A38-4859-BCCD-63E305D79172@dit.upm.es> <5541AE76.5070407@telefonica.com> Message-ID: <81853E0F-4F6F-4AAC-8B81-A8F162707311@dit.upm.es> Hi Juanjo, yes, I agree with you. In fact in the new IdM the check is done before filling the form. BR -- ?lvaro > El 30 Apr 2015, a las 06:24, Juanjo Hierro escribi?: > > > Obviously, much better. > > One point though ... currently this screen is shown only after (s)he has completed the form to create the user account ... why should we let him fill the form and only show this message after (s)he clicks on the "accept" button ? I understand that whenever the user clicks on "sign-up" in the FIWARE Lab home page, you should be able to verify whether the limit on number of Trial Users have been reached ... why don't we display the screen below at that moment, without asking the user to complete the form? > > Thanks, > > -- Juanjo > > On 27/04/15 10:57, ?lvaro Alonso wrote: >> This is the new screen: >> >> >> -- >> ?lvaro >> >>> El 27 Apr 2015, a las 10:56, ?lvaro Alonso > escribi?: >>> >>> Hi Juanjo, >>> >>> we have just deployed a new version with all the fixes. >>> >>> BR >>> -- >>> ?lvaro >>> >>>> El 27 Apr 2015, a las 00:25, Juanjo Hierro > escribi?: >>>> >>>> >>>> BTW, the messages ends abruptly as follows "please contact our Technical Support Team sending an email to ." an no email address is provided ... >>>> >>>> Had someone tested that the message that we were providing? >>>> >>>> Come on! >>>> >>>> -- Juanjo >>>> >>>> >>>> On 27/04/15 00:21, Juanjo Hierro wrote: >>>>> Hi, >>>>> >>>>> I wanted to try myself the experience when a user tries to sign up on the FIWARE Lab and the number of trial users has reached the limit. >>>>> >>>>> Check below a screenshot of the screen I get. Isn't it feasible to get a better (more profesional) look&feel? >>>>> Why the "here" associated to the link to the application form for upgrading of the accounts is splitted into two lines? >>>>> Wouldn't it be feasible that the word "here" appears with another color (or at least underlined) so that people can find out easily it is an URL link? >>>>> Couldn't we choose a font for the message in line with the style guides we defined for user interfaces? >>>>> Cannot we position the box with the message at the left of the box with the title "Sign Up" on the left upper corner? >>>>> Sincerely, it doesn''t cost that much to make the things look more professional ... >>>>> >>>>> Best regards, >>>>> >>>>> -- 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 >>>> _______________________________________________ >>>> Fiware-lab-recovery-tf mailing list >>>> 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 > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From federico.facca at create-net.org Thu Apr 30 09:49:23 2015 From: federico.facca at create-net.org (Federico Michele Facca) Date: Thu, 30 Apr 2015 09:49:23 +0200 Subject: [Fiware-lab-recovery-tf] R: audio today? In-Reply-To: References: Message-ID: silvio replaced me and covered my parts. On Wed, Apr 22, 2015 at 4:58 PM, Stefano De Panfilis wrote: > Dear Alvaro and all, > > as said yesterday alfonso Till friday is attending company training. I'm > abroad unfortunately now in a noicy airport... > > I thought juanjo or fede or Fernando to be there. Isn't It? > > Ciao > Stefano > > > > Inviato dal mio dispositivo Samsung > > > -------- Messaggio originale -------- > Da: ?lvaro Alonso > Data: 22/04/2015 15:45 (GMT+00:00) > A: fiware-lab-recovery-tf at lists.fiware.org > Oggetto: [Fiware-lab-recovery-tf] audio today? > > Hi, Silvio Joaquin and I are connected? > -- > ?lvaro > > > _______________________________________________ > Fiware-lab-recovery-tf mailing list > Fiware-lab-recovery-tf at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-lab-recovery-tf > > -- -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From aalonsog at dit.upm.es Thu Apr 30 11:48:05 2015 From: aalonsog at dit.upm.es (=?utf-8?Q?=C3=81lvaro_Alonso?=) Date: Thu, 30 Apr 2015 11:48:05 +0200 Subject: [Fiware-lab-recovery-tf] VERY IMPORTANT! FIWARE Lab User Categories In-Reply-To: References: Message-ID: Hi all, I?ve prepared a document explaining the model of users that we have created in IdM according the things decided during this weeks (attached). Please, read it carefully and send me any comments. ------ On the other hand and thinking in the migration of current users, the day of the migration: - Users created before April 16th will be Trial users (Spain 2 region) during 14 days. Obviously the amount is higher than 100. Once the 14 days period expires, we will set the limit to 100 again. - 100 first users created after April 16th will be Basic users. - Other new users (community accounts created after April 16th) will be community. In this case I need the region that I have to assign to them. Who can provide me this??? Is this correct? Please correct me if I?m wrong. BR -- ?lvaro -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARELab_accountCategories.pdf Type: application/pdf Size: 136861 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: