Well the problem is not so simple: often SMEs asked a community account on a node simple because they have already VMs on that node (a "trial" users), independently by the fact that the account has been approved or not. Migrating has a cost! It is exactly because we are aware of the delicate situation that we think that such a decision is not simple to take and must be carefully discussed: mixing different perspective (and problems) and taking a not deeply meditated decision is not good in this case. Saying that we are going to change a guideline circulated less than one month ago (as pointed out by Thierry) just because there are some problems on the federation caused by the migration to the new IDM, it the best way to state that the situation is not under control (and it is a symptom of surrender or failure). What happens in the future if we are experiencing problems on the Spain node? Are we proactively governing the problems or are we just reacting to them, suffering them? Again something should be put in place to solve the current problems, something different should be decided in order to "solve" the September issue (that btw is not a issue raised in the last week). Best regards silvio On Tue, May 12, 2015 at 10:05 AM, Juanjo Hierro < juanjose.hierro at telefonica.com> wrote: > > > If the user hadn't started to setup the VMs in the assigned node > (because the node was not working at the time the request was accepted, the > request had been assigned to the node but the node hadn't accept it yet or > the request arrived later than the new IdM was deployed) ... yes I would > rollback them and ask them to move to Spain-2. There is a good rationale > for that: the node you were assigned is not yet up and running so we don't > want to block you. > > If the user hadn't been assigned a node yet, I would simply assign them > to Spain-2. > > WE CANNOT KEEP HUNDRED OF USERS WITH NO SERVICE JUST WAITING FOR NODES > TO FIX THEIR CONFIGURATION WHEN WE DON'T KNOW WHERE THAT TASK WOULD > FINISH. I wonder if we are aware of the delicate situation. > > Best regards, > > -- Juanjo > > > On 12/05/15 09:40, Silvio Cretti wrote: > > Hi all, > I would say that we have to distinguish between a stretegic and a tactical > decision (please do not mix the two): > 1) Strategic: what happens after September? This is a question to be > discussed and answered independently from the temporary (hopefully) > problems we have at the moment. > 2) Tactical: how to solve the current instability and malfunctioning of > the federation. > > Said that, as a coach I want to know what to do with all the request > that have been already approved on nodes different to Spain-2. Do I have to > rollback them? > > > This has a cost for the SMEs because probably they have to "migrate" > their stuff (and we do not have any automatic procedure to do so). So a > change of "strategy" should be clearly motivated explaining also why we > decided to change it (new elements coming into account now that were not > know one month ago). > A telco is scheduled with the coaches this afternoon. Which is the message > we want to convey? > My 2 cents, > silvio > > On Tue, May 12, 2015 at 9:26 AM, Federico Michele Facca < > federico.facca at create-net.org> wrote: > >> hi, >> sorry to answer so late, but the email was in my spam inbox. >> >> i think we should evaluate which nodes have the problem resolved and >> consider them as well besides Spain-2. while for sure, we should not - >> unless users really insist - assign them to a node while it has not yet >> recovered (in which case they need to be patient - which is anyhow now the >> case, also in Spain-2). but this should be only a temporary thing till >> issues get resolved, not a permnanent one. >> >> i would take into consideration that what happened on thursday is not >> surely responsability of the nodes. so excluding them at this stage would >> sound like it's their fault, which I cannot support: it's not fair. some of >> them may be crap, as we identified and, should get excluded without any >> rethinking, others are not, and many of the issues they experienced are >> beyond their responsability. >> >> said so, today at 17, me and silvio have an info day here in trento (i >> am one of ther first speakers, so our presence in the afternoon call cannot >> last very long). >> >> cheers, >> federico >> >> On Tue, May 12, 2015 at 9:06 AM, Juanjo Hierro < >> juanjose.hierro at telefonica.com> wrote: >> >>> >>> Obviously, we will have to handle requests one by one and only accept >>> those who ask for a number of resources that sound reasonable. >>> >>> I understand that, given said this, Fernando you agreed on the >>> proposal (it was a little bit unclear with your wording, I have to say) >>> >>> Cheers, >>> >>> -- Juanjo >>> >>> On 12/05/15 09:02, FERNANDO LOPEZ AGUILAR wrote: >>> >>> Juanjo, >>> >>> Agree with consider the revision of the assigning Community and Trial >>> Users accounts, this should means what is the decision that we have to take >>> related to the amount of resources that everyone ask from Spain2. I mean, >>> it is important to know what is the policy that we want to follow in order >>> to assign resources to the Community Users if everyone will be moved to >>> Spain2. We will make this decision conditional on the efforts and place in >>> which we have to apply them if we want to give support to all the new users >>> that probably will come to Spain2. >>> >>> De: Juanjo Hierro <juanjose.hierro at telefonica.com> >>> Fecha: Tuesday 12 May 2015 06:37 >>> Para: "fiware-lab-recovery-tf at lists.fiware.org" < >>> fiware-lab-recovery-tf at lists.fiware.org> >>> Asunto: [Fiware-lab-recovery-tf] URGENT remediation action >>> >>> *IMHO, we should seriously consider to revise the "algorithm" for >>> assigning Community and Trial User accounts* so that Community User >>> accounts linked to FIWARE accelerator projects get assigned to the Spain-2 >>> node (unless serious requirements about hosting data in a given country) >>> and Trial User accounts or Community User accounts not linked to the FIWARE >>> accelerator projects are assigned to the rest of nodes (maybe some space to >>> be allocated in Spain if space remains). Trial Users are renewed every >>> two weeks, so the fact that in September may be other different nodes will >>> not be an issue with respect to them. Once the new nodes are federated, >>> they may host some Community Users. *I would like to seriously >>> discuss this matter in our daily confcall today. In the meantime until >>> then, I would welcome your feedback about this measure*. . >>> >>> >>> -- >>> >>> ______________________________________________________ >>> >>> 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 >> >> > > -- > > ______________________________________________________ > > 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: <https://lists.fiware.org/private/fiware-lab-recovery-tf/attachments/20150512/d159956f/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy