Dear, I've just forwarded your request to the Lannion support team.

Best,
Daniele

Comment by ccmeciu@images-et-reseaux.com :

Dear Ioannis,

Can we schedule the migration on 26 sept 2016 ?
You will need to change your IP addresses.

Can you please make a Jira request to folow better the migration plan.

To start your vms you will need to follow the procedure:
To start your VM on Lannion3 node after migration, you will need to next steps in cloud portal https://cloud.lab.fiware.org/#nova/images/:
1. Chose Lannion3 Region

2. Normally the flavors , keypairs and the security groups were imported (look in Compute>Security), if not:
a. Create a new keypair
b. Create a new security list(s)
c. Allocate IP to your project (Important: Your IP will be changed, you will not be able to recover your old IP )

3. Start VM on Lannion3 node:
a. You will find the snapshoted image named ansible-snapshot-<tenant_id>-<vm_id> in c, then click Launch button
b. Rename your vm and chose the flavor in "1.Details"
c. Select keypair and security groups in "2. Access & Security"
d. Chose node-int-net-01 network in "3. Networking"
e. Then "Launch instance" in "5. Summary"

BR,
Cristian

Migration scheduled for 26/09/2016, see the mail bellow:
=============
Dear Cristian,
thank you very much for the prompt reply.
Yes, you can schedule the migration of the virtual machines on 26 September 2016.
Best regards,
Ioannis Stenos

Migration scheduled for 26/09/2016

Comment by ccmeciu@images-et-reseaux.com :

Dear Ioannis,

Can we start the migration for your VMs this morning as it was scheduled?

BR,
Cristian

De : Ioannis Stenos istenos@wings-ict-solutions.eu
Envoyé : lundi 5 septembre 2016 17:09
À : support-lannion@imaginlab.fr; Fiware-lab-help@lists.fiware.org
Cc : Aimilia Bantouna; Nelly Giannopoulou
Objet : Request for Migration of Lannion2 VMs to Lannion3 node

Dear Sir/Madame,
I am writing to you to request the migration of several virtual machines from Lannion2 to Lannion3 node. Below you can find the information concerning the migration as requested

Project ID (tenant): 9eb8b1d355084708899979a1c75139e0

VMs id's and names to migrate:

ID: 933d7156-d581-43c5-ad35-9bf17a17175b Name: HqseDevMgHadoopMasterHive
ID: 0304e4a2-f964-4c73-a75a-79e52f7a69f3 Name: MigraineNET_keyrock
ID: 64a61632-0084-44a5-a13e-ec87c6e87a0a Name: MigraineNET_proxyserver
ID: bde6092b-4497-4402-9064-ab810f7ce20c Name: MigraineNet_Poi
ID: 3d8f3753-b3f5-4bf5-a87c-f4db228d23dd Name: MigraineNet_orion_idas
ID: 067d274a-ca25-4dd9-85d5-463d65be9b00 Name: Migraine_objstore_slave

Volume(s) to migrate and their Ids (if you have) : None

A date to schedule this migration (or multiple dates in the case we are not available): 30 September is the preferred date for the migration. If 30 September is not possible, then any date between 26 and 30 of September will do.

Best regards,
Ioannis Stenos

Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one.

Comment by istenos@wings-ict-solutions.eu :

Dear Cristian,

you can proceed with the migration as scheduled.

BR,
Ioannis

2016-09-26 10:44 GMT+03:00 Cristian CMECIU <ccmeciu@images-et-reseaux.com>:

> Dear Ioannis,
>
>
>
> Can we start the migration for your VMs this morning as it was scheduled?
>
>
>
> BR,
>
> Cristian
>
>
>
> De : Ioannis Stenos istenos@wings-ict-solutions.eu
> Envoyé : lundi 5 septembre 2016 17:09
> À : support-lannion@imaginlab.fr; Fiware-lab-help@lists.fiware.org
> Cc : Aimilia Bantouna; Nelly Giannopoulou
> Objet : Request for Migration of Lannion2 VMs to Lannion3 node
>
>
>
> Dear Sir/Madame,
>
> I am writing to you to request the migration of several virtual machines
> from Lannion2 to Lannion3 node. Below you can find the information
> concerning the migration as requested
>
> Project ID (tenant): 9eb8b1d355084708899979a1c75139e0
>
> VMs id's and names to migrate:
>
> ID: 933d7156-d581-43c5-ad35-9bf17a17175b Name:
> HqseDevMgHadoopMasterHive
> ID: 0304e4a2-f964-4c73-a75a-79e52f7a69f3 Name: MigraineNET_keyrock
> ID: 64a61632-0084-44a5-a13e-ec87c6e87a0a Name: MigraineNET_proxyserver
> ID: bde6092b-4497-4402-9064-ab810f7ce20c Name: MigraineNet_Poi
> ID: 3d8f3753-b3f5-4bf5-a87c-f4db228d23dd Name:
> MigraineNet_orion_idas
> ID: 067d274a-ca25-4dd9-85d5-463d65be9b00 Name: Migraine_objstore_slave
>
> Volume(s) to migrate and their Ids (if you have) : None
>
> A date to schedule this migration (or multiple dates in the case we are
> not available): 30 September is the preferred date for the migration.
> If 30 September is not possible, then any date between *26 and 30 of
> September* will do.
>
>
> Best regards,
>
> Ioannis Stenos
>

Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one.

Comment by ccmeciu@images-et-reseaux.com :

Hi Ioannis,

I copied all VM images on the new Lannion3 Node, hereunder you can find the correspondence between the image and VM name :
MigraineNET_keyrock >> ansible-snapshot-9eb8b1d355084708899979a1c75139e0-0304e4a2-f964-4c73-a75a-79e52f7a69f3
Migraine_objstore_slave >> ansible-snapshot-9eb8b1d355084708899979a1c75139e0-067d274a-ca25-4dd9-85d5-463d65be9b00
MigraineNet_orion_idas >> ansible-snapshot-9eb8b1d355084708899979a1c75139e0-3d8f3753-b3f5-4bf5-a87c-f4db228d23dd
MigraineNET_proxyserver >> ansible-snapshot-9eb8b1d355084708899979a1c75139e0-64a61632-0084-44a5-a13e-ec87c6e87a0a
HqseDevMgHadoopMasterHive >> ansible-snapshot-9eb8b1d355084708899979a1c75139e0-933d7156-d581-43c5-ad35-9bf17a17175b
MigraineNet_Poi >> ansible-snapshot-9eb8b1d355084708899979a1c75139e0-bde6092b-4497-4402-9064-ab810f7ce20c

To start your VM on Lannion3 node after migration, you will need to next steps in cloud portal https://cloud.lab.fiware.org/ :
1. Chose Lannion3 Region

2. Normally the flavors , keypairs and the security groups were imported (look in Compute>Security), if not:
a. Create a new keypair
b. Create a new security list(s)
c. Allocate IP to your project (Important: Your IP will be changed, you will not be able to recover your old IP )
Also be aware to allocate IPs from “public-ext-net-01” network.

3. Start VM on Lannion3 node:
a. You will find the snapshoted image named ansible-snapshot-<tenant_id>-<vm_id> in (look in Compute>Images), then click Launch button
b. Rename your vm and chose the flavor in "1.Details"
c. Select keypair and security groups in "2. Access & Security"
d. Chose node-int-net-01 network in "3. Networking"
e. Then "Launch instance" in "5. Summary"

BR,
Cristian

De : Ioannis Stenos istenos@wings-ict-solutions.eu
Envoyé : lundi 26 septembre 2016 09:56
À : Cristian CMECIU
Cc : support-lannion@imaginlab.fr; Fiware-lab-help@lists.fiware.org; Aimilia Bantouna; Nelly Giannopoulou
Objet : Re: Request for Migration of Lannion2 VMs to Lannion3 node

Dear Cristian,
you can proceed with the migration as scheduled.
BR,
Ioannis

2016-09-26 10:44 GMT+03:00 Cristian CMECIU <ccmeciu@images-et-reseaux.com<ccmeciu@images-et-reseaux.com>>:
Dear Ioannis,

Can we start the migration for your VMs this morning as it was scheduled?

BR,
Cristian

De : Ioannis Stenos istenos@wings-ict-solutions.eu<mailto:istenos@wings-ict-solutions.eu>
Envoyé : lundi 5 septembre 2016 17:09
À : support-lannion@imaginlab.fr<support-lannion@imaginlab.fr>; Fiware-lab-help@lists.fiware.org<Fiware-lab-help@lists.fiware.org>
Cc : Aimilia Bantouna; Nelly Giannopoulou
Objet : Request for Migration of Lannion2 VMs to Lannion3 node

Dear Sir/Madame,
I am writing to you to request the migration of several virtual machines from Lannion2 to Lannion3 node. Below you can find the information concerning the migration as requested

Project ID (tenant): 9eb8b1d355084708899979a1c75139e0

VMs id's and names to migrate:

ID: 933d7156-d581-43c5-ad35-9bf17a17175b Name: HqseDevMgHadoopMasterHive
ID: 0304e4a2-f964-4c73-a75a-79e52f7a69f3 Name: MigraineNET_keyrock
ID: 64a61632-0084-44a5-a13e-ec87c6e87a0a Name: MigraineNET_proxyserver
ID: bde6092b-4497-4402-9064-ab810f7ce20c Name: MigraineNet_Poi
ID: 3d8f3753-b3f5-4bf5-a87c-f4db228d23dd Name: MigraineNet_orion_idas
ID: 067d274a-ca25-4dd9-85d5-463d65be9b00 Name: Migraine_objstore_slave

Volume(s) to migrate and their Ids (if you have) : None

A date to schedule this migration (or multiple dates in the case we are not available): 30 September is the preferred date for the migration. If 30 September is not possible, then any date between 26 and 30 of September will do.

Best regards,
Ioannis Stenos

Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one.

Migration done.
Ticket closed.

BR,
Cristian