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" <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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-lab-recovery-tf/attachments/20150415/69080c43/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy