Comment by jira-help-desk@fi-ware.org :
Spam detection software, running on the system "fiware-forge-01", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
@@CONTACT_ADDRESS@@ for details.

Content preview: From FIWARE JIRA - Main Help Desk ---- Comments: Lannion Node
Helpdesk - Today 9:30 AM Project migrated... ticket closed. BR, Cristian
[...]

Content analysis details: (4.7 points, 4.5 required)

pts rule name description
---- ---------------------- --------------------------------------------------
2.3 FSL_HELO_BARE_IP_1 FSL_HELO_BARE_IP_1
0.0 TVD_RCVD_IP4 TVD_RCVD_IP4
0.0 TVD_RCVD_IP TVD_RCVD_IP
1.2 RCVD_NUMERIC_HELO Received: contains an IP address used for HELO
0.0 T_FRT_BELOW2 BODY: ReplaceTags: Below (2)
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
2.3 FM_IS_IT_OUR_ACCOUNT Is it our account?
0.8 RDNS_NONE Delivered to internal network by a host with no rDNS

Project migrated... ticket closed.
BR,
Cristian

Comment by jira-help-desk@fi-ware.org :
Spam

Hi Dimitrios,

Did you solved the problem about starting the your VM which used an old image of orion-psb-image ?
Please inform us ... to close this ticket.

BR,
Cristian

Comment by d.amaxilatis@gmail.com :
Any updates?

Should I fall back to the old VMs in Lannion2?

Dimitrios Amaxilatis
http://amaxilatis.com

Comment by d.amaxilatis@gmail.com :
Those 2 are the only CentOS VMs so probably there is a problem with that ?

It seems like I cannot access them from the internal network as well so
there may be a problem with spawning them?

Dimitrios Amaxilatis
http://amaxilatis.com

Comment by d.amaxilatis@gmail.com :
I have an issue with the following vms :

In the first Tenant :
4ff8777f-eef1-4e25-a297-6d33c0266cae

And in the second Tenant:
ad9a60dd-5e49-437e-b558-f97d550d3903

The vms seem to be Active but when I associate the external IPs and try to
connect via SSH I get ssh: connect to host 195.220.224.132 port 22: No
route to host

ports are correctly configured, as I can connect to the other vms if I
associate the external IP to them.

Any ideas?

Dimitrios Amaxilatis
http://amaxilatis.com

On Wed, Sep 7, 2016 at 11:53 AM, Cristian CMECIU <
ccmeciu@images-et-reseaux.com> wrote:

> Dimitros, you can proceed for your last tenant too to migrate.
> Hera are the image id to start your vm.
> | 9021152a-cff6-4361-a710-a7cb647d546c | ansible-snapshot-
> 00000000000000000000000000010699-2ce0849d-9e6d-4301-a4e8-14b5f47bd95f
>
> For other questions please contact us.
>
> BR,
> Cristian
> ----Message d'origine----
> De : Cristian CMECIU ccmeciu@images-et-reseaux.com
> Envoyé : mercredi 7 septembre 2016 10:23
> À : FW External User (JIRA)
> Cc : support-lannion@imaginlab.fr; Dimitrios Amaxilatis
> Objet : RE: [FIWARE-JIRA] (HELP-7192) [Fiware-lab-help] Lannion FIWARE
> Lab-Migration Lannion2 to Lannion3
>
> Hi Dimitros the migration of your vms is done fot your tenant
> 00000000000000000000000000010601.
> After you will finish to install all vms please inform us to disable your
> account (max Monday 12 September).
>
> Here you will find the images that were created on Lannion3 node.
> | 343825a8-33be-4d95-bacf-445a4e68a78a |
> | ansible-snapshot-00000000000000000000000000010601-890954a7-4043-4aaa-b
> | be9-09aef74e51ee
> | fb6125bb-0f30-4a7c-be77-7fc526c3ee14 |
> | ansible-snapshot-00000000000000000000000000010601-a491db8b-fcd7-436a-b
> | 742-14bd26390d36 f2b9dddf-340b-4a6e-bfc0-0093720305fb |
> | ansible-snapshot-00000000000000000000000000010601-b4dd63c5-8819-407a-a
> | 7cf-3e60b6c6d776 911f4a3c-d40d-4c53-bc1d-b1b48914c56a |
> | ansible-snapshot-00000000000000000000000000010601-bc301b89-848b-4bbe-a
> | 603-5692beb7a9db
>
> Your vm_id correspondence on Lannion2 is:
> VM id VM name
> bc301b89-848b-4bbe-a603-5692beb7a9db ehr
> a491db8b-fcd7-436a-b742-14bd26390d36 orion
> 890954a7-4043-4aaa-bbe9-09aef74e51ee patriot_ehr
> b4dd63c5-8819-407a-a7cf-3e60b6c6d776 www
> Please follow the next procedure to start your vms on Lannion3 node:
>
> 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 (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
>

Comment by jira-help-desk@fi-ware.org :
Spam detection software, running on the system "fiware-forge-01", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
@@CONTACT_ADDRESS@@ for details.

Content preview: From FIWARE JIRA - Main Help Desk ---- Comments: FW External
User - Today 10:51 AM Comment by ccmeciu@images-et-reseaux.com : Dimitros,
you can proceed for your last tenant too to migrate. Hera are the image id
to start your vm. | 9021152a-cff6-4361-a710-a7cb647d546c | ansible-snapshot-00000000000000000000000000010699-2ce0849d-9e6d-4301-a4e8-14b5f47bd95f
[...]

Content analysis details: (4.7 points, 4.5 required)

pts rule name description
---- ---------------------- --------------------------------------------------
2.3 FSL_HELO_BARE_IP_1 FSL_HELO_BARE_IP_1
0.0 TVD_RCVD_IP4 TVD_RCVD_IP4
0.0 TVD_RCVD_IP TVD_RCVD_IP
1.2 RCVD_NUMERIC_HELO Received: contains an IP address used for HELO
0.0 T_FRT_BELOW2 BODY: ReplaceTags: Below (2)
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
2.3 FM_IS_IT_OUR_ACCOUNT Is it our account?
0.8 RDNS_NONE Delivered to internal network by a host with no rDNS

Comment by ccmeciu@images-et-reseaux.com :
Dimitros, you can proceed for your last tenant too to migrate.
Hera are the image id to start your vm.

For other questions please contact us.

BR,
Cristian
----Message d'origine----
De : Cristian CMECIU ccmeciu@images-et-reseaux.com
Envoyé : mercredi 7 septembre 2016 10:23
À : FW External User (JIRA)
Cc : support-lannion@imaginlab.fr; Dimitrios Amaxilatis
Objet : RE: [FIWARE-JIRA] (HELP-7192) [Fiware-lab-help] Lannion FIWARE Lab-Migration Lannion2 to Lannion3

Hi Dimitros the migration of your vms is done fot your tenant 00000000000000000000000000010601.
After you will finish to install all vms please inform us to disable your account (max Monday 12 September).

Here you will find the images that were created on Lannion3 node.

Your vm_id correspondence on Lannion2 is:
VM id VM name
bc301b89-848b-4bbe-a603-5692beb7a9db ehr
a491db8b-fcd7-436a-b742-14bd26390d36 orion
890954a7-4043-4aaa-bbe9-09aef74e51ee patriot_ehr
b4dd63c5-8819-407a-a7cf-3e60b6c6d776 www
Please follow the next procedure to start your vms on Lannion3 node:

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 (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

Comment by jira-help-desk@fi-ware.org :
Spam detection software, running on the system "fiware-forge-01", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
@@CONTACT_ADDRESS@@ for details.

Content preview: From FIWARE JIRA - Main Help Desk ---- Comments: FW External
User - Today 10:21 AM Comment by ccmeciu@images-et-reseaux.com : Hi Dimitros
the migration of your vms is done fot your tenant 00000000000000000000000000010601.
After you will finish to install all vms please inform us to disable your
account (max Monday 12 September). [...]

Content analysis details: (4.7 points, 4.5 required)

pts rule name description
---- ---------------------- --------------------------------------------------
2.3 FSL_HELO_BARE_IP_1 FSL_HELO_BARE_IP_1
0.0 TVD_RCVD_IP4 TVD_RCVD_IP4
0.0 TVD_RCVD_IP TVD_RCVD_IP
1.2 RCVD_NUMERIC_HELO Received: contains an IP address used for HELO
0.0 T_FRT_BELOW2 BODY: ReplaceTags: Below (2)
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
2.3 FM_IS_IT_OUR_ACCOUNT Is it our account?
0.8 RDNS_NONE Delivered to internal network by a host with no rDNS

Comment by ccmeciu@images-et-reseaux.com :
Hi Dimitros the migration of your vms is done fot your tenant 00000000000000000000000000010601.
After you will finish to install all vms please inform us to disable your account (max Monday 12 September).

Here you will find the images that were created on Lannion3 node.

Your vm_id correspondence on Lannion2 is:
VM id VM name
bc301b89-848b-4bbe-a603-5692beb7a9db ehr
a491db8b-fcd7-436a-b742-14bd26390d36 orion
890954a7-4043-4aaa-bbe9-09aef74e51ee patriot_ehr
b4dd63c5-8819-407a-a7cf-3e60b6c6d776 www
Please follow the next procedure to start your vms on Lannion3 node:

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 (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

Comment by jira-help-desk@fi-ware.org :
Spam detection software, running on the system "fiware-forge-01", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
@@CONTACT_ADDRESS@@ for details.

Content preview: From FIWARE JIRA - Main Help Desk ---- Comments: FW External
User - Today 9:47 AM Comment by ccmeciu@images-et-reseaux.com : I found your
account d.amaxilatis@gmail.com<d.amaxilatis@gmail.com> ☺ [...]

Content analysis details: (4.7 points, 4.5 required)

pts rule name description
---- ---------------------- --------------------------------------------------
2.3 FSL_HELO_BARE_IP_1 FSL_HELO_BARE_IP_1
0.0 TVD_RCVD_IP4 TVD_RCVD_IP4
0.0 TVD_RCVD_IP TVD_RCVD_IP
1.2 RCVD_NUMERIC_HELO Received: contains an IP address used for HELO
0.0 T_FRT_BELOW2 BODY: ReplaceTags: Below (2)
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
2.3 FM_IS_IT_OUR_ACCOUNT Is it our account?
0.8 RDNS_NONE Delivered to internal network by a host with no rDNS

Comment by ccmeciu@images-et-reseaux.com :
I found your account d.amaxilatis@gmail.com<d.amaxilatis@gmail.com> ☺

Cristian

Comment by d.amaxilatis@gmail.com :
The mail is d.amaxilatis@gmail.com not amaxilatis@gmail.com

Dimitrios Amaxilatis
http://amaxilatis.com

On Wed, Sep 7, 2016 at 10:41 AM, Cristian CMECIU <
ccmeciu@images-et-reseaux.com> wrote:

> Ok,
> The migration is in progress. I will inform you when it will end.
>
> About your other tenant ... do you want to migrate your vm orion-www?
> The problem is that you don' t have an active account on Cloud portal. I'm
> talking about amaxilatis@gmail.com account.
>
> BR,
> Cristian
>
>

Comment by jira-help-desk@fi-ware.org :
Spam detection software, running on the system "fiware-forge-01", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
@@CONTACT_ADDRESS@@ for details.

Content preview: From FIWARE JIRA - Main Help Desk ---- Comments: FW External
User - Today 9:39 AM Comment by ccmeciu@images-et-reseaux.com : Ok, The migration
is in progress. I will inform you when it will end. [...]

Content analysis details: (4.7 points, 4.5 required)

pts rule name description
---- ---------------------- --------------------------------------------------
2.3 FSL_HELO_BARE_IP_1 FSL_HELO_BARE_IP_1
0.0 TVD_RCVD_IP4 TVD_RCVD_IP4
0.0 TVD_RCVD_IP TVD_RCVD_IP
1.2 RCVD_NUMERIC_HELO Received: contains an IP address used for HELO
0.0 T_FRT_BELOW2 BODY: ReplaceTags: Below (2)
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
2.3 FM_IS_IT_OUR_ACCOUNT Is it our account?
0.8 RDNS_NONE Delivered to internal network by a host with no rDNS

Comment by ccmeciu@images-et-reseaux.com :
Ok,
The migration is in progress. I will inform you when it will end.

About your other tenant ... do you want to migrate your vm orion-www?
The problem is that you don' t have an active account on Cloud portal. I'm talking about amaxilatis@gmail.com account.

BR,
Cristian

Comment by d.amaxilatis@gmail.com :
yes, go for it

Dimitrios Amaxilatis
http://amaxilatis.com

On Wed, Sep 7, 2016 at 10:31 AM, Cristian CMECIU <
ccmeciu@images-et-reseaux.com> wrote:

> Hi Dimitros,
>
> Can I start the migration for the tenant 00000000000000000000000000010601
> - mail account: admin@sparkworks.net?
>
> BR,
> Cristian
>
>

Comment by jira-help-desk@fi-ware.org :
Spam detection software, running on the system "fiware-forge-01", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
@@CONTACT_ADDRESS@@ for details.

Content preview: From FIWARE JIRA - Main Help Desk ---- Comments: FW External
User - Today 9:30 AM Comment by ccmeciu@images-et-reseaux.com : Hi Dimitros,
[...]

Content analysis details: (4.7 points, 4.5 required)

pts rule name description
---- ---------------------- --------------------------------------------------
2.3 FSL_HELO_BARE_IP_1 FSL_HELO_BARE_IP_1
0.0 TVD_RCVD_IP4 TVD_RCVD_IP4
0.0 TVD_RCVD_IP TVD_RCVD_IP
1.2 RCVD_NUMERIC_HELO Received: contains an IP address used for HELO
0.0 T_FRT_BELOW2 BODY: ReplaceTags: Below (2)
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
2.3 FM_IS_IT_OUR_ACCOUNT Is it our account?
0.8 RDNS_NONE Delivered to internal network by a host with no rDNS

Comment by ccmeciu@images-et-reseaux.com :
Hi Dimitros,

Can I start the migration for the tenant 00000000000000000000000000010601 - mail account: admin@sparkworks.net?

BR,
Cristian

Comment by d.amaxilatis@gmail.com :
Ok,

done, I move the rules that we will need in the Lannion3 region.

Best,
Dimitris

Dimitrios Amaxilatis
http://amaxilatis.com

On Tue, Sep 6, 2016 at 6:39 PM, Cristian CMECIU <
ccmeciu@images-et-reseaux.com> wrote:

> Hi,
>
> You will need to look on Lannion2 and see the rules, and then to re-create
> it on Lannion3.
> Or if you want, you can create new rules on Lannion3 directly.
>
> BR,
> Cristian
>

Comment by jira-help-desk@fi-ware.org :
Spam detection software, running on the system "fiware-forge-01", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
@@CONTACT_ADDRESS@@ for details.

Content preview: From FIWARE JIRA - Main Help Desk ---- Comments: FW External
User - Today 5:37 PM Comment by ccmeciu@images-et-reseaux.com : Hi, [...]

Content analysis details: (4.7 points, 4.5 required)

pts rule name description
---- ---------------------- --------------------------------------------------
2.3 FSL_HELO_BARE_IP_1 FSL_HELO_BARE_IP_1
0.0 TVD_RCVD_IP4 TVD_RCVD_IP4
0.0 TVD_RCVD_IP TVD_RCVD_IP
1.2 RCVD_NUMERIC_HELO Received: contains an IP address used for HELO
0.0 T_FRT_BELOW2 BODY: ReplaceTags: Below (2)
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
2.3 FM_IS_IT_OUR_ACCOUNT Is it our account?
0.8 RDNS_NONE Delivered to internal network by a host with no rDNS

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

You will need to look on Lannion2 and see the rules, and then to re-create it on Lannion3.
Or if you want, you can create new rules on Lannion3 directly.

BR,
Cristian

Comment by d.amaxilatis@gmail.com :
I cannot delete the "default" security lists because they are being used.
What should I do?

Dimitrios Amaxilatis
http://amaxilatis.com

On Tue, Sep 6, 2016 at 5:24 PM, Cristian CMECIU <
ccmeciu@images-et-reseaux.com> wrote:

> Hi Dimitros,
>
> Can you make changes for your two tenants concerning the security list
> rules.... I cannot migrate them because are named "default"
>
> I gived you access on Lannion3 node for the 2 tenants:
> 00000000000000000000000000010699
> 00000000000000000000000000010601
>
> BR,
> Cristian
>

Comment by jira-help-desk@fi-ware.org :
Spam detection software, running on the system "fiware-forge-01", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
@@CONTACT_ADDRESS@@ for details.

Content preview: From FIWARE JIRA - Main Help Desk ---- Comments: FW External
User - Today 4:22 PM Comment by ccmeciu@images-et-reseaux.com : Hi Dimitros,
[...]

Content analysis details: (4.7 points, 4.5 required)

pts rule name description
---- ---------------------- --------------------------------------------------
2.3 FSL_HELO_BARE_IP_1 FSL_HELO_BARE_IP_1
0.0 TVD_RCVD_IP4 TVD_RCVD_IP4
0.0 TVD_RCVD_IP TVD_RCVD_IP
1.2 RCVD_NUMERIC_HELO Received: contains an IP address used for HELO
0.0 T_FRT_BELOW2 BODY: ReplaceTags: Below (2)
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
2.3 FM_IS_IT_OUR_ACCOUNT Is it our account?
0.8 RDNS_NONE Delivered to internal network by a host with no rDNS

Comment by ccmeciu@images-et-reseaux.com :
Hi Dimitros,

Can you make changes for your two tenants concerning the security list rules.... I cannot migrate them because are named "default"

I gived you access on Lannion3 node for the 2 tenants:
00000000000000000000000000010699
00000000000000000000000000010601

BR,
Cristian

Comment by d.amaxilatis@gmail.com :

I have deleted the VM and requested the extension to the account.

Best,
Dimitrios

Dimitrios Amaxilatis
http://amaxilatis.com

spam

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

Hi,

Can you delete the other vm that you don't want to migrate?

Also your account for the tenant 00000000000000000000000000010699 is expired. Can you request a extension of tis account on Jira Help desk ?

BR,
Cristian

Comment by d.amaxilatis@gmail.com :
Hi Cristian,

Wednesday 7 Septembre is ok.

For the project with the second tenant 00000000000000000000000000010699

we will need to migrate the 2ce0849d-9e6d-4301-a4e8-14b5f47bd95f | orion-www

You can schedule this for Wednesday as well.

Best Regards,
Dimitris

Dimitrios Amaxilatis
http://amaxilatis.com

Comment by ccmeciu@images-et-reseaux.com :
Hi Dimitros,

Actually we will be able to start the migration from Wednesday 7 Septembre.

Regarding the tenant id 00000000000000000000000000010601 “constantinos-anagnostopoulos cloud » VMs we will migrate it Wednesday , in the morning.
Concerning the Object Storage, you will need to recreate it on the new node Lannion3.

Concerning the project with tenant id : 00000000000000000000000000010699, do you need anymore these vms?
----------------------------------------------------------------------------------------------------------------------+

----------------------------------------------------------------------------------------------------------------------+

Can you please confirm the migration for the first tenant, and the migration/deletion of the second one?

BR,
Cristian

De : Dimitrios Amaxilatis d.amaxilatis@gmail.com
Envoyé : jeudi 1 septembre 2016 16:17
À : Cristian CMECIU
Objet : Re: [FIWARE-JIRA] (HELP-7192) [Fiware-lab-help] Lannion FIWARE Lab-Migration Lannion2 to Lannion3

Dear Cristian,

The details are the following.

project id : "constantinos-anagnostopoulos cloud"

VM ids:
890954a7-4043-4aaa-bbe9-09aef74e51ee
bc301b89-848b-4bbe-a603-5692beb7a9db
a491db8b-fcd7-436a-b742-14bd26390d36
b4dd63c5-8819-407a-a7cf-3e60b6c6d776

Object Storage Containers:
HeartContainer

You can schedule the migration for tomorrow if that works for you.

Let me know if the information is ok.

Best,
Dimitrios Amaxilatis

Dimitrios Amaxilatis
http://amaxilatis.com

On Thu, Sep 1, 2016 at 4:42 PM, Cristian CMECIU <ccmeciu@images-et-reseaux.com<ccmeciu@images-et-reseaux.com>> wrote:
Hi Dimitros,

As i specified in the mail, we will schedule a migration during the month of September:
"During the month of september, we will proceed to migrate all VMs from Lannion2 to Lannion3 node, in order to clear Lannion2 node.
So, we kindly ask users that want to continue to use their ressouces, to demand us the migration of their VMs till 30 Septembre 2016."

It is up to you to choose a date for migration.

In order to schedule the migration, you will need to inform us about ( please fill the lines bellow):
• Your project ID (tenant):
• VMs id's or names to migrate:
• Volume(s) to migrate and their Ids (if you have) :
• A date to schedule this migration (or multiple dates in the case we are not available):

BR,
Cristian

Comment by ccmeciu@images-et-reseaux.com :
Hi Dimitros,

As i specified in the mail, we will schedule a migration during the month of September:
"During the month of september, we will proceed to migrate all VMs from Lannion2 to Lannion3 node, in order to clear Lannion2 node.
So, we kindly ask users that want to continue to use their ressouces, to demand us the migration of their VMs till 30 Septembre 2016."

It is up to you to choose a date for migration.

In order to schedule the migration, you will need to inform us about ( please fill the lines bellow):
• Your project ID (tenant):
• VMs id's or names to migrate:
• Volume(s) to migrate and their Ids (if you have) :
• A date to schedule this migration (or multiple dates in the case we are not available):

BR,
Cristian

Dear Dimitrios,
I've just forwarded your request to the Lannion node support team.
They'll get back to you soon.

Best regards
Marco