Please find migration details of a INCENSe user.

Regards,
P.

Hi Luciano,

Can you please demand an extension of your accout? It is expired from 19/04/2016.
Also please specify the project that you will continue in Fiware?

BR,
Cristian

Migration scheduled for 22/09/2016
BR,
Cristian

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

The migration process of your VMS is started.
I will inform you when you can start your VMs on the new node.

After migration you'll need to start your VMs on the new node Lannion3 following 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/ :
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

Migration on Lannion3 done.
For other problems, please contact us.

BR,
Cristian

Comment by luciano.rosa@zenup.eu :

I'm sorry but I'm not sure that migration is done.. When I select Lannion3 from region menu, I have no instances allocated in this node.
The instances seems to be remained on Lannion 2 node

Best regards,
Luciano Rosa

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

Dear Luciano,

I have explained before that after migration, you will need to start the VMs on Lannion3 node.

Here is the procedure:

After migration you'll need to start your VMs on the new node Lannion3 following 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/ :
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

----Message d'origine----
De : Luciano Rosa luciano.rosa@zenup.eu
Envoyé : vendredi 23 septembre 2016 12:52
À : jira-help-desk@fi-ware.org; Cristian CMECIU
Objet : R: [FIWARE-JIRA] (HELP-7307) [Fiware-incense-coaching] Lannion3 migration - ZenUp s.r.l.

I'm sorry but I'm not sure that migration is done.. When I select Lannion3 from region menu, I have no instances allocated in this node.
The instances seems to be remained on Lannion 2 node

Best regards,
Luciano Rosa

----Messaggio originale----
Da: Help-Desk jira-help-desk@fi-ware.org
Inviato: venerdì 23 settembre 2016 10:57
A: ccmeciu@images-et-reseaux.com
Cc: luciano.rosa@zenup.eu
Oggetto: [FIWARE-JIRA] (HELP-7307) [Fiware-incense-coaching] Lannion3 migration - ZenUp s.r.l.

From FIWARE JIRA - Main Help Desk ----

-------------------------------------------------------------------------------
Comments:

Lannion Node Helpdesk - Today 10:56 AM
------------------
Migration on Lannion3 done.
For other problems, please contact us.

BR,
Cristian

FW External User - Yesterday 11:46 AM
------------------
Comment by ccmeciu@images-et-reseaux.com :
Dear user,

The migration process of your VMS is started.
I will inform you when you can start your VMs on the new node.

After migration you'll need to start your VMs on the new node Lannion3 following 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/ :
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

Lannion Node Helpdesk - Tuesday 9:32 AM
------------------
Migration scheduled for 22/09/2016
BR,
Cristian

Lannion Node Helpdesk - Monday 11:52 AM
------------------
Hi Luciano,

Can you please demand an extension of your accout? It is expired from 19/04/2016.
Also please specify the project that you will continue in Fiware?

BR,
Cristian

Pasquale Andriani - Monday 11:19 AM
------------------
Please find migration details of a INCENSe user.

Regards,
P.

------------------------
Issue id: HELP-7307
Description:
Hello, I'm Luciano Rosa from ZenUp s.r.l.

In last days I have received a message about the migration from Lannion2 to
Lannnion3

I report your requests:

You said:

In order to schedule the migration, you will need to inform us about ( please fill the lines bellow):

. Your project ID (tenant):
zenup cloud (ID ee6abf6aa7e54a0c97403c7df3e96167)

. VMs id's or names to migrate:

Name: Accumulator
ID: 2339cac9-1cee-4290-8529-10b84dff0d16

Name: KeyRock - IdM
ID: 4bb60c19-a117-41f9-9f7b-872bcac3793f

Name: MQTT Agent
ID: d45db07e-8d98-46df-8670-647d83a81375

Name: Orion Context Broker
ID: 65e6eac2-7b3a-476c-bcb9-2908882c0765

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

September, 22, 2016

Thank you,

Best regards,

Luciano Rosa

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-incense-coaching@lists.fiware.org) instead of the old one.

Comment by luciano.rosa@zenup.eu :

Hello, thank you for all informations. I have a real problem now.
when I try to associate public IP to an Instance, I have this error message:

{"badRequest": {"message": "Unable to associate floating ip 10.0.51.45 to fixed ip 192.168.3.196 for instance a10c5a1f-8dda-4362-9f17-85df5c961574. Error: External network 34287647-4771-4b66-bc0f-6328498b75ba is not reachable from subnet 395b0573-47a9-4738-b2af-df38d49d7fda. Therefore, cannot associate Port 31e75457-0b03-42e2-be13-012d512db22f with a Floating IP.", "code": 400}}

Thank you
Best regards,

Luciano Rosa

----Messaggio originale----
Da: Help-Desk jira-help-desk@fi-ware.org
Inviato: venerdì 23 settembre 2016 14:26
A: luciano.rosa@zenup.eu
Cc: luciano.rosa@zenup.eu
Oggetto: [FIWARE-JIRA] (HELP-7307) FIWARE.Request.Lab.Lannion3 migration - ZenUp s.r.l..

From FIWARE JIRA - Main Help Desk ----

-------------------------------------------------------------------------------
Comments:

FW External User - Today 2:25 PM
------------------
Comment by ccmeciu@images-et-reseaux.com :

Dear Luciano,

I have explained before that after migration, you will need to start the VMs on Lannion3 node.

Here is the procedure:

After migration you'll need to start your VMs on the new node Lannion3 following 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/ :
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

----Message d'origine----
De : Luciano Rosa luciano.rosa@zenup.eu Envoyé : vendredi 23 septembre 2016 12:52 À : jira-help-desk@fi-ware.org; Cristian CMECIU Objet : R: [FIWARE-JIRA] (HELP-7307) [Fiware-incense-coaching] Lannion3 migration - ZenUp s.r.l.

I'm sorry but I'm not sure that migration is done.. When I select Lannion3 from region menu, I have no instances allocated in this node.
The instances seems to be remained on Lannion 2 node

Best regards,
Luciano Rosa

----Messaggio originale----
Da: Help-Desk jira-help-desk@fi-ware.org
Inviato: venerdì 23 settembre 2016 10:57
A: ccmeciu@images-et-reseaux.com
Cc: luciano.rosa@zenup.eu
Oggetto: [FIWARE-JIRA] (HELP-7307) [Fiware-incense-coaching] Lannion3 migration - ZenUp s.r.l.

From FIWARE JIRA - Main Help Desk ----

-------------------------------------------------------------------------------
Comments:

Lannion Node Helpdesk - Today 10:56 AM
------------------
Migration on Lannion3 done.
For other problems, please contact us.

BR,
Cristian

FW External User - Yesterday 11:46 AM
------------------
Comment by ccmeciu@images-et-reseaux.com :
Dear user,

The migration process of your VMS is started.
I will inform you when you can start your VMs on the new node.

After migration you'll need to start your VMs on the new node Lannion3 following 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/ :
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

Lannion Node Helpdesk - Tuesday 9:32 AM
------------------
Migration scheduled for 22/09/2016
BR,
Cristian

Lannion Node Helpdesk - Monday 11:52 AM
------------------
Hi Luciano,

Can you please demand an extension of your accout? It is expired from 19/04/2016.
Also please specify the project that you will continue in Fiware?

BR,
Cristian

Pasquale Andriani - Monday 11:19 AM
------------------
Please find migration details of a INCENSe user.

Regards,
P.

------------------------
Issue id: HELP-7307
Description:
Hello, I'm Luciano Rosa from ZenUp s.r.l.

In last days I have received a message about the migration from Lannion2 to
Lannnion3

I report your requests:

You said:

In order to schedule the migration, you will need to inform us about ( please fill the lines bellow):

. Your project ID (tenant):
zenup cloud (ID ee6abf6aa7e54a0c97403c7df3e96167)

. VMs id's or names to migrate:

Name: Accumulator
ID: 2339cac9-1cee-4290-8529-10b84dff0d16

Name: KeyRock - IdM
ID: 4bb60c19-a117-41f9-9f7b-872bcac3793f

Name: MQTT Agent
ID: d45db07e-8d98-46df-8670-647d83a81375

Name: Orion Context Broker
ID: 65e6eac2-7b3a-476c-bcb9-2908882c0765

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

September, 22, 2016

Thank you,

Best regards,

Luciano Rosa

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-incense-coaching@lists.fiware.org) instead of the old one.

FW External User - Today 12:54 PM
------------------
Comment by luciano.rosa@zenup.eu :

I'm sorry but I'm not sure that migration is done.. When I select Lannion3 from region menu, I have no instances allocated in this node.
The instances seems to be remained on Lannion 2 node

Best regards,
Luciano Rosa

Lannion Node Helpdesk - Today 10:56 AM
------------------
Migration on Lannion3 done.
For other problems, please contact us.

BR,
Cristian

FW External User - Yesterday 11:46 AM
------------------
Comment by ccmeciu@images-et-reseaux.com :
Dear user,

The migration process of your VMS is started.
I will inform you when you can start your VMs on the new node.

After migration you'll need to start your VMs on the new node Lannion3 following 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/ :
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

Lannion Node Helpdesk - Tuesday 9:32 AM
------------------
Migration scheduled for 22/09/2016
BR,
Cristian

Lannion Node Helpdesk - Monday 11:52 AM
------------------
Hi Luciano,

Can you please demand an extension of your accout? It is expired from 19/04/2016.
Also please specify the project that you will continue in Fiware?

BR,
Cristian

Pasquale Andriani - Monday 11:19 AM
------------------
Please find migration details of a INCENSe user.

Regards,
P.

------------------------
Issue id: HELP-7307
Description:
Hello, I'm Luciano Rosa from ZenUp s.r.l.

In last days I have received a message about the migration from Lannion2 to
Lannnion3

I report your requests:

You said:

In order to schedule the migration, you will need to inform us about (
please fill the lines bellow):

. Your project ID (tenant):
zenup cloud (ID ee6abf6aa7e54a0c97403c7df3e96167)

. VMs id's or names to migrate:

Name: Accumulator
ID: 2339cac9-1cee-4290-8529-10b84dff0d16

Name: KeyRock - IdM
ID: 4bb60c19-a117-41f9-9f7b-872bcac3793f

Name: MQTT Agent
ID: d45db07e-8d98-46df-8670-647d83a81375

Name: Orion Context Broker
ID: 65e6eac2-7b3a-476c-bcb9-2908882c0765

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

September, 22, 2016

Thank you,

Best regards,

Luciano Rosa

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-incense-coaching@lists.fiware.org) instead of the old one.

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

The problem is that you need to choose "public-ext-net-01" to allocate a floating IP in the range 195.220.224.X.
I'm sure that you have chosen an IP from federation-etc-net-01. You don't have access to this network.
Thank you to reminding me to inform the other users.

BR,
Cristian

----Message d'origine----
De : FW External User (JIRA) jira-help-desk@fi-ware.org
Envoyé : lundi 26 septembre 2016 09:10
À : support-lannion@imaginlab.fr
Objet : [FIWARE-JIRA] (HELP-7307) FIWARE.Request.Lab.Lannion3 migration - ZenUp s.r.l..

[ https://jira.fiware.org/browse/HELP-7307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

FW External User updated HELP-7307:
-----------------------------------

Comment by luciano.rosa@zenup.eu :

Hello, thank you for all informations. I have a real problem now.
when I try to associate public IP to an Instance, I have this error message:

{"badRequest": {"message": "Unable to associate floating ip 10.0.51.45 to fixed ip 192.168.3.196 for instance a10c5a1f-8dda-4362-9f17-85df5c961574. Error: External network 34287647-4771-4b66-bc0f-6328498b75ba is not reachable from subnet 395b0573-47a9-4738-b2af-df38d49d7fda. Therefore, cannot associate Port 31e75457-0b03-42e2-be13-012d512db22f with a Floating IP.", "code": 400}}

Thank you
Best regards,

Luciano Rosa