[Fiware-lab-federation-nodes] Ficore : SophiaAntipolis Node - Upgrade

[Badia Philippe]

Hi Alvaro, Sean,

Thanks for the answer and the sharing.

So we understand that the upgraded will be seen as a new Fiware node.

2 comments here:

*#1* As the HW infrastructure will upgraded ( HDD/RAM) and merged with 
the new Ficore, we'll need at one moment to shut down the Xifi node 
before having the new node operational. Of course we will communicate on 
that with our users and we'll do our best to minimise this downtime time.

*#2* As stated by Sean, if our understanding is correct, we are able to 
migrate the data of the existing VMs but how can we allow  the users to 
retrieve their VM on their cloud portal account  account as the tenant 
will change ?
As it involves the Federation Keystone,  do you have a guideline or 
feedback from previous upgrade that could help us ?

Best regards,
Philippe


---------------------------------------------------------------------------------------------------------------------------------------------------------

Hi Philippe,

I think the best option is the first one. In fact that is more or less 
the procedure established but FIWARE Lab handbooks. Only few notes:

- Node name: you have to use SophiaAntipolis2 for the new node
- Users: you have to use the same admin and services users for the new node
- New node will be hidden in the cloud portal during federation tests
- Old node will be accesible in the cloud portal till the new one is ready

Anyway, Fernando (cc’ed) could tell you detailed information about the 
precess.

BR
--
Álvaro


Le 21/04/2016 à 15:10, Sean Murphy a écrit :
> Hi Philippe, all,
>
> In the spirit of sharing...
>
>     - Deploy Openstack Kilo on the New servers
>     - Check Openstack services
>     - Request new service endpoints with Federation keystone ( Nova,
>     Cinder, Neutron, Glance, Ceilometer)
>       Node name : Can we keep the same  : SophiaAntipolis ?
>       Admin user : Can we keep the same admin-c4 ?
>     - Check connection with the Federation
>     - Snapshots existing VMs
>     - Stop the Xifi node and migrate the servers to the new node
>     - Migrate VMs for the Xifi infrastructure to the new node
>
>
> There are a couple of non trivial points here (which we have not 
> solved yet)...
> - we don't think it is possible as admin to create a vm for a tenant 
> based on a snapshot
> - importing a snapshot is possible under the admin user and it can be 
> shared with a non-admin user
> - importing a volume for a specific tenant does not seem to be 
> directly possible right now.
>
> The solutions unfortunately seem to involve tampering with databases 
> which is super ugly and
> error prone...
>
> If anyone has any other thoughts on this, it would be much appreciated.
>
> BR,
> Seán.
>
>       How to handle the user impact on the cloud portal depending on
>     the changes above ?
>     - Ficore node fully operational
>
>
>     *_Solution 2
>     _*
>     We"ll keep the same service end point parameters for the upgraded
>     node.
>     The users might be more impacted with this solution as the
>     shutdown of the Xifi node will be done at the beginning of the plan.
>
>     - Deploy Openstack Kilo on the 5 New servers
>     - Snapshot of existing VMs
>     - Stop the Xifi node and migrate the servers to the new node
>     - Check Openstack services
>     - Use the existing service endpoints with Federation keystone (
>     Nova, Cinder, Neutron, Glance, Ceilometer)
>       Node name remains unchanged : SophiaAntipolis
>       Admin user remains unchanged  admin-c4
>     - Check connection with the Federation
>     - Migrate VMs for the Xifi infrastructure to the new node.
>     How to handle the existing VMs re-creation on the new nodes ?
>     - Ficore node fully operational
>
>
>     Let us know your thoughts and what would be your preferred solution.
>
>     Best regards,
>     Philippe
>     -- 
>     /Tel : +33 (0)4 89 86 69 37
>     <tel:%2B33%20%280%294%2089%2086%2069%2037>//
>     //Mob: +33 (0)6 16 31 63 04
>     <tel:%2B33%20%280%296%2016%2031%2063%2004>/
>     *www.com4innov.com <http://www.com4innov.com>*
>
>
>
>
>
> _______________________________________________
> Fiware-lab-federation-nodes mailing list
> Fiware-lab-federation-nodes at lists.fiware.org
> https://lists.fiware.org/listinfo/fiware-lab-federation-nodes


-- 
/Tel : +33 (0)4 89 86 69 37
Mob: +33 (0)6 16 31 63 04/
*www.com4innov.com*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-lab-federation-nodes/attachments/20160422/3233a1f9/attachment.html>