[Fiware-lab-federation-nodes] process for testing nodes prior to federation

[Sean Murphy]

Hi Fernando,

Thanks for that.

What we need is:
> - a way to add the node to the service registry temporarily
> - a way to access the node from the portal temporarily (I'm not
> sure if there is a difference between these two - given the mechanism
> to flag problematic nodes in the portal, I suspect there might be
> some difference between them)
> - a way to integrate the node with the health check temporarily (in
> such a way that we do not get penalized for underperformance - this
> is a tet period after all).
>
> Actually, the process to incorporate a new node is clearly defined. The
> first step
> should be the manual check of some functionalities (using the Horizon
> portal of
> the new node). If this process is ok, we start the federation of the node
> both in
> Keystone service and proper configuration services in that new node.
>

So, if I understand correctly, there is no gentle integration/staging -
either
a node is not federated or it is not and if it is federated it is (more or
less)
permanent and it is available for service.


> Afterthat, we configure the Sanity Checks to process the automatic
> execution of
> The tests on the new node. The reason of it is:
>
>    1. We do not want to put in the portal a new region that it is not
>    working properly
>    2. The Sanity Checks take all the information related to the service
>    endpoints from keystone.
>    3. The Sanity Checks take the authentication from the Keystone.
>
> I understand the sanity checks clearly - my point was that basically I can
envisage a scenario in which we are doing the federation of the new node,
we discover some problems/issues which may cause failure of the sanity
checks and we should not be penalized for this as (from our perspective),
the node is still under test.

Saying that, the only point that I can see here is the possibility that all
> the process can start
> except the configuration of the Cloud Portal in order that we do not show
> the new region. If
> it is possible *@Alvaro *we can start/move forward the rest of the
> procedure.
>

Ok, so we wait for instruction from Alvaro.

BR,
Seán.



> So, I'm wondering if there is any solution/guidelines/recommended
> practice for bringing up a new node, running it through some tests
> before putting it into production.
>
> Any thoughts/comments v appreciated.
>
> BR,
> Seán.
>
>
> ------------------------------
>
> 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-federation-nodes/attachments/20160212/4cba81e3/attachment.html>