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

[Sean Murphy]

Hi all,

As some of you may know, we are working on migrating our system
to Kilo.

Our solution to this involves keeping the Icehouse node operational
while ramping up a new Kilo node (with limited resources initially)
and then gradually moving the VMs, snapshots and physical servers
from Icehouse to Kilo. (Our particular case is made more complex by the
fact that we are split across physical data centres with Icehouse in
one location and Kilo in another - this does cause some logistical issues
and makes things slower, but these are not the focus of this mail).

We have just set up the Kilo deployment and it has passed local
tests. We would like to have a managed process of integration into the
federation (which I suspect all the new nodes will also want), but I
fear that this is not there at present.

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).

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-lab-federation-nodes/attachments/20160210/4f5aa932/attachment.html>