[Fiware-lab] Update on procedure for node migration / maintenance

[Federico Michele Facca]

Dear All,
recall and update on the node maintenance procedure, so to avoid nodes to
be visible during the process:

1. Ask Miguel and me approval before putting a node in planned maintenance
(one week upfront if planned, immediately for urgencies).
2. When this is approved, inform Alvaro that will make your node
“invisible” in the portal.
3. If for any “big issue” your node goes down, inform directly Alvaro so it
will be made not visible in the portal.
4. Once maintenance is completed, inform Alvaro that restore the node in
the portal.

Migration, when you need to have 2 nodes registered, for example, for
migration, proceed in the same way:
1. Inform Alvaro to add a new region with a temporary id (that then will be
replaced with the original one) to the catalogue.
2. Complete the registration of the new node.
3. Run tests from CLI
4. Migrate resources.
5. Inform Alvaro that he can remove the old node, and update the name of
the node to the old one.
6. Run tests from CLI.
7. Inform Alvaro he can make visible the new node.

Best,
Federico

--
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 408400 (1669)
M +39 334 6049758
E  federico.facca at create-net.org
T @chicco785
W  www.create-net.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-lab/attachments/20141218/69fe65dd/attachment.html>