The project migrated to Lannion3 Node.
Ticket closed.

BR,
Cristian

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

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

We are waiting the user to start the VMs on the new node.

BR,
Cristian

Hi,
I have not tried yet.
----------------------------------
Sent from my smartphone (I won't
tell you the brand)

On Sep 13, 2016 9:47 AM, "Cristian CMECIU" <ccmeciu@images-et-reseaux.com> wrote:
Hi Hichem,

Have you succeeded to start your VMs on Lannion3 node ?

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

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

Your VMs are migrated. The corresponding images are:

Kurento > ansible-snapshot-353d9df6040146d99a9b48077b9ae2d0-6251ef5e-2f1f-4b29-8769-3b29ba585511
Memo24 > ansible-snapshot-353d9df6040146d99a9b48077b9ae2d0-3f9bdbe8-324e-4a1c-8d93-11c813f99e47

I extender the account expiration date for 2 weeks till you will make the demand to Help desk.

Please follow next procedure to start them 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:

· Create a new keypair

· Create a new security list(s)

· 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:

· You will find the snapshoted image named ansible-snapshot-<tenant_id>-<vm_id> in (look in Compute>Images), then click Launch button

· Rename your vm and chose the flavor in "1.Details"

· Select keypair and security groups in "2. Access & Security"

· Chose node-int-net-01 network in "3. Networking"

· Then "Launch instance" in "5. Summary"

BR,
Cristian

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

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

Your VMs are migrated. The corresponding images are:

Kurento > ansible-snapshot-353d9df6040146d99a9b48077b9ae2d0-6251ef5e-2f1f-4b29-8769-3b29ba585511
Memo24 > ansible-snapshot-353d9df6040146d99a9b48077b9ae2d0-3f9bdbe8-324e-4a1c-8d93-11c813f99e47

I extender the account expiration date for 2 weeks till you will make the demand to Help desk.

Please follow next procedure to start them 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

Comment by ccmeciu@images-et-reseaux.com :
Ok I will inform you when you can start the vms.

Have you made the request for the expiration date of your account?

BR,
Cristian

De : Hichem Boudali hichem.boudali@gmail.com
Envoyé : lundi 12 septembre 2016 12:01
À : Cristian CMECIU
Cc : FW External User (JIRA); support-lannion@imaginlab.fr
Objet : Re: [FIWARE-JIRA] (HELP-7236) [Fiware-lab-help] Migration Lannion2 to Lannion3

Fine with me.

Hichem.
https://track.mixmax.com/api/track/v2/VXrh3WuDtc9kbodwq/ISbvNmLslWYtdGQpxWYkV3bi5Sblh2YphmI/gIt92YugXdhV2clJXL0VWLzV2Zh1WaAVXajVWbjNmI/ISVJNURNNEIuFWa0NXayNkI?sc=false

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

Hi Hichem,

Of you want we can schedule the migration this afternoon 12/09/2016 at 14:00 UTC.

After migration you’ll need to start your VMs on the new node.

Please also create a ticket to extend your account. It is expired from 22/03/2016.

BR,

Cristian

Comment by hichem.boudali@gmail.com :
Fine with me.
Hichem.

On Mon, Sep 12, 2016 11:53 AM, Cristian CMECIU ccmeciu@images-et-reseaux.com
wrote:
Hi Hichem,

Of you want we can schedule the migration this afternoon 12/09/2016 at 14:00
UTC.

After migration you’ll need to start your VMs on the new node.

Please also create a ticket to extend your account. It is expired from
22/03/2016.

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 11:52 AM Comment by ccmeciu@images-et-reseaux.com : Hi Hichem,
[...]

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 Hichem,

Of you want we can schedule the migration this afternoon 12/09/2016 at 14:00 UTC.
After migration you’ll need to start your VMs on the new node.

Please also create a ticket to extend your account. It is expired from 22/03/2016.

BR,
Cristian

Comment by hichem.boudali@gmail.com :
Hi,
Here are the VMs for migration:
Your project ID (tenant): 353d9df6040146d99a9b48077b9ae2d0VMs id's or names to
migrate: 3f9bdbe8-324e-4a1c-8d93-11c813f99e47  and
 6251ef5e-2f1f-4b29-8769-3b29ba585511Volume(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): any day in Sept.
Thank you,
Hichem.

On Mon, Sep 12, 2016 11:43 AM, Cristian CMECIU ccmeciu@images-et-reseaux.com
wrote:
Hi Hichem,

Can you send please the mail to support-lannion@imaginlab.fr

Can you specify a convenient date and hour to migrate your VMs?

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

IMPORTANT: Your public IP addresses will be changed during this process. So
please make the necessary changes before migration (DNS, etc).

After the migration, you will need to start your VMs on Lannion3 Node following
the next 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 please re-create it:

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"

For other questions please contact us.

BR,

Cristian CMECIU

Fiware-Lab/ Lannion Region

ImaginLab Support Engineer

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

Can you send please the mail to support-lannion@imaginlab.fr
Can you specify a convenient date and hour to migrate your VMs?

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

IMPORTANT: Your public IP addresses will be changed during this process. So please make the necessary changes before migration (DNS, etc).

After the migration, you will need to start your VMs on Lannion3 Node following the next 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 please re-create it:
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"

For other questions please contact us.

BR,
Cristian CMECIU
Fiware-Lab/ Lannion Region
ImaginLab Support Engineer

Hi,
I can send your request to the Lannion support team.
They will ask you all the details in order to proceed to the migration.

Regards,
Giuseppe