You can open a Help ticket at Fiware-lab-help@lists.fiware.org
and the coach will redirect the ticket to the right person.
BR,
Cristian

Comment by dragomir@dragomirdimitrijevic.rs :

Which is their email?

DD

-

Dear Dragomir,
This is a migration ticket.
Please open a help ticket that concerns Orion Context Broker server. I cannot help you to fix this problem.
You need to contact the right person who is in charge to maintain Orion Context Broker Fiware generic enabler.
BR,
Cristian

Comment by dragomir@dragomirdimitrijevic.rs :
Hello:

I am using tokens to access Orion Broker and SSL certificate for token
server just expired. Can you fix it please?

URL I am using is

https://orion.lab.fiware.org/token

And Java error report is

more
Caused by: java.security.cert.CertificateExpiredException: NotAfter: Sun Oct
09 01:59:59 CEST 2016
at
sun.security.x509.CertificateValidity.valid(CertificateValidity.java:274)
at
sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:629)
at

Regards

Dr. Dragomir D. Dimitrijevic
CEO, CTO, Founder

Food and Agriculture Cloud Technology - FACT, Ltd.

Science Technology Park
Veljka Dugosevica 54,
11060 Belgrade
Serbia

Phone: +381-11-2400-589
Mobile: +381-63-101-8778
E-mail: dragomir@dragomirdimitrijevic.rs, dragomir@fact.rs
Skype: dragomirdimitrijevic
WWW: http://fact.rs, http://dragomirdimitrijevic.rs

Project migrated to Lannion3 node.
Ticket closed.
BR,
Cristian

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

Your VMs images are now available on Lannion3 node:
Orion_4.4 > image named: ansible-snapshot-00000000000000000000000000008608-12eccbbb-b46d-4571-952a-506627e48bc6
ubntuMySqlGlass > ansible-snapshot-OK_00000000000000000000000000008608-f3d4eb05-18ff-4098-b0b8-691187a9d7a7

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"

Please inform us when the migration will be finished on your side.
If you have other questions please contact us.

BR,
Cristian

Comment by ccmeciu@images-et-reseaux.com :
Hi Dragomir,
We have started the migration of your 2 concerned vms.
I will inform you when you can start them on the new Lannion3 node.
Meantime please check if your keypairs, security-groups and flavors, if they have been imported.
For the security groups i think you have to check it closely, cause we had encountered some errors in the migrations process.
Probably ou will need to recreate some rules.
BR,
Cristian

Hi Dragomir,
We have started the migration of your 2 concerned vms.
I will inform you when you can start them on the new Lannion3 node.
Meantime please check if your keypairs, security-groups and flavors, if they have been imported.
For the security groups i think you have to check it closely, cause we had encountered some errors in the migrations process.
Probably ou will need to recreate some rules.
BR,
Cristian

The vm_id 8048257b-ebc2-4eba-8184-16dc4b1bdd95 named Orion_4.2 will be deleted.

BR,
Cristian

Ok, for Thursday at 9:00AM UTC
you don't have any valumes ... i checked this.

BR,
Cristian

Comment by dragomir@dragomirdimitrijevic.rs :

Here is the data I got from the team:

• Your project ID (tenant):

Not sure... could be Fractals, FACT or FACTUAL

• VMs id's or names to migrate:

(Name: Orion_4.4, ID: 12eccbbb-b46d-4571-952a-506627e48bc6)
(Name: ubntuMySqlGlass, ID: f3d4eb05-18ff-4098-b0b8-691187a9d7a)

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

We believe we don't have it but please check out

• A date to schedule this migration (or multiple dates in the case we are
not available):
Let's say Thursday 15.09.2016

DD

-

Hi Dragomir,

We will proceed to snapshot your VMs and then to copy it on the new Node Lannion2.
In the time of migration the VMs on Lannion2 node will be paused.
If anything goes wrong we can start your old VMs again on Lannion2 node. We will not delete it till everithing is ok on the new node.

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

If you want us to DELETE a VM, we need the ID and the name of. Or simpliest you can do it yourself via the cloud portal https://account.lab.fiware.org/ .

Be aware that the public IP address will be changed on the new node Lannion3.

What will we migrate:

• flavors
• Keypairs
• Security lists
• Quotas

Here is the procedure that you will need to follow to start your VMs on the new platform:
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

Comment by dragomir@dragomirdimitrijevic.rs :

We have two instances active (web and Orion). You can delete the rest. How
will migration proceed? As I mentioned earlier, I am terrified of changes
since we expect to demo the system to potential customers/investors. When
are you going to migrate and how long it will take?

DD

-

Comment by dragomir@dragomirdimitrijevic.rs :

OK I will check with the team.

We are in the process of demonstrating our product to potential customers
and investors and the last thing we need now is some changes of the system
that might cause a crash during demonstration. How long it will take and
what is our involvement in the process?

DD

-

Dear Dragomir,

I saw that you have an Vm which is stopped.
If you are not using anymore this vm, please delete it before migration.

BR,
Cristian

Dear Dragomir,

We announced the migration of all vms of Lannion2 node to Lannion3 node till the end of Septembre.

Here is the mail, where you need to tell us which vms to migrate.

===
Dear Lannion FIWARE Lab user,
 
As you are aware, during theese last months, Lannion FIWARE Lab node has undergone significant maintenance, in order to perform an upgrade to the Openstack Kilo version.
In this moment we have two nodes active: Lannion2 (in Juno version) and Lannion3 (in Kilo version).
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.
 
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:
• After 30 Septembre we will shutdown Lannion2 Node and all your data will be errased on this node. To avoid this, please be so kind to schedule the migration of your ressources in time.
• Your public IP addresses will be changed during this process. So please make the necessary changes before migration (DNS, etc).

If you are not concerned or you don't want to continue on Lannion nodes after 30 Septembre, please ignore this message.
 
Best regards,
Fiware-Lab/ Lannion Region
ImaginLab Support