[Fiware-lab-recovery-tf] URGENT remediation action

FERNANDO LOPEZ AGUILAR fernando.lopezaguilar at telefonica.com
Tue May 12 10:47:22 CEST 2015


For sure, issues about copy&paste, you know :)

De: JUAN JOSE HIERRO SUREDA <juanjose.hierro at telefonica.com<mailto:juanjose.hierro at telefonica.com>>
Fecha: Tuesday 12 May 2015 09:56
Para: fla <fernando.lopezaguilar at telefonica.com<mailto:fernando.lopezaguilar at telefonica.com>>, "fiware-lab-recovery-tf at lists.fiware.org<mailto:fiware-lab-recovery-tf at lists.fiware.org>" <fiware-lab-recovery-tf at lists.fiware.org<mailto:fiware-lab-recovery-tf at lists.fiware.org>>
Asunto: Re: [Fiware-lab-recovery-tf] URGENT remediation action


  I guess minimum was maximum and maximum was minimum in the data you provided ...

On 12/05/15 09:35, FERNANDO LOPEZ AGUILAR wrote:
What I wanted to say is that the decision to move Community users to Spain2 will decide the priority actions that we have to take in order to cope with the demand of new resources.

Regarding the assignation of resources to every community user, we have decided to proceed in the following way. We have only two options, minimum and maximum, if the request can fix with the minimum we assign it (it is the default value). By contrast, if they requires more resources we assign the maximum one:
* Minimum
VM Instances: 5
VCPUs: 10
Hard Disk: 100 GB
Memory: 10240 MB
Public IP: 1

* Maximum
VM Instances:2
VCPUs: 2
Hard Disk: 40 GB
Memory: 4096 MB
Public IP: 1

The reason, currently we have 7x tickets in Spain regarding the process to migrate to community users, and this number for sure will increase next days. We do not have resources to attend all the jira tickets and we decide to automate the process in some way in order to resolve it as fast as we can do it.

De: JUAN JOSE HIERRO SUREDA <juanjose.hierro at telefonica.com<mailto:juanjose.hierro at telefonica.com>>
Fecha: Tuesday 12 May 2015 09:06
Para: fla <fernando.lopezaguilar at telefonica.com<mailto:fernando.lopezaguilar at telefonica.com>>, "fiware-lab-recovery-tf at lists.fiware.org<mailto:fiware-lab-recovery-tf at lists.fiware.org>" <fiware-lab-recovery-tf at lists.fiware.org<mailto:fiware-lab-recovery-tf at lists.fiware.org>>
Asunto: Re: [Fiware-lab-recovery-tf] URGENT remediation action


  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<mailto:juanjose.hierro at telefonica.com>>
Fecha: Tuesday 12 May 2015 06:37
Para: "fiware-lab-recovery-tf at lists.fiware.org<mailto:fiware-lab-recovery-tf at lists.fiware.org>" <fiware-lab-recovery-tf at lists.fiware.org<mailto: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<mailto: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<mailto: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/b1f2ee2f/attachment.html>


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

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