Details
-
Type:
extRequest
-
Status: Closed
-
Priority:
Critical
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-LAB-HELP
-
Labels:None
-
HD-Node:Budapest
Description
Dear node team,
FRACTALS accelerator team has contacted us for one fo their subgrantees (the EMPORIA project)
.
Mr. Ververidis has lost access to his instances since PireausN node has shutdown.
He has filled the migration form. It seems he requested to move to PireausU node. Could you kindly help this SME?
Thanks,
ilknur
Issue Links
- relates to
-
HELC-1313
FIWARE.Request.Coach.FRACTALS.Migration from PiraeusN node.
-
- Closed
-
Activity
Dear Christoper,
Regarding your statement about "not able to associate IP's to some instances", do you mean you can assign public IP to one of the VMs, but not to the others? or could you not assign IP to any of the VMs?
Normally, we allow only one public IP per community account. You can try the port forwarding solution recommended here if this is indeed the issue: http://joseignaciocarretero.blogspot.com
Regards,
ilknur
The issue has been emailed:
- Time sent: 28/Mar/16 11:21 AM
- To: c.ververidis@hypertech.gr
- with subject: floating IPs
Dear Christopher,
I see you have 5 floating IPs. Can you send us which VMs do you want to associate! Do you use the public-ext-net? Did you get any error message?
Best regards,
Gergő
Dear Gergő,
We do not use public-ext-net. We need one IP per instance in order for our
system to be functional.
The instances we need are the following:
emporia-idmemporia-authz
emporia-appemporia-poi
emporia-repo
Thank you!
Christopher
Christopher N. Ververidis, PhD
Innovation and Business Development Manager
Digital Life Unit
HYPERTECH S.A.
A 32 Perikleous St, 15232 Athens, GR
T (0030) 210 6179441
F (0030) 210 6179288
E c.ververidis@hypertech.gr
W http://www.hypertech.gr
The issue has been emailed:
- Time sent: 28/Mar/16 5:42 PM
- To: c.ververidis@hypertech.gr
- with subject: floating ips
Dear Christopher,
ok, i see the problem. I see you created floating ips from federation-ext-net-01, but the network of your VMs is in the public range. The openstack not allowed to associate different range of IPs. I suggest to release the floating IPs, and allocate new ones from the public-ext-net-01 and you can associate those IPs to the VM.
Best Regards,
Gergő
Dear Gergő,
It seems that releasing the IPs and allocating new ones from
public-ext-net-01 solved the problem.
We have managed to initialize the emporia-authz and the emporia-poi
instances successfully and are trying to connect via ssh to the others but
have not managed yet (it could be our internal issue and we are working to
figure it out now).
Best,
Christopher
Christopher N. Ververidis, PhD
Innovation and Business Development Manager
Digital Life Unit
HYPERTECH S.A.
A 32 Perikleous St, 15232 Athens, GR
T (0030) 210 6179441
F (0030) 210 6179288
E c.ververidis@hypertech.gr
W http://www.hypertech.gr
Dear ilknur,
the previous week we started the migration of the VMs from PiraeusN node to PiraeusU node. This process was implemented by using VM snapshots of the guest VMs that belong to the users. The snapshots were stored in our glance registry. We managed to store 8 different VM of 3 different user tenants. The node glance do not have further storage space and for this reason we have temporarily freeze the migration process.
The process could be gradually completed if:
In addition, we try to add a new VM that will support a NFS tha will be mounted on the existing glance store of our node. Till now we did not managed to achieve this extension. However, we are working so as to achieve it.
To our personal view a potential solution would be to migrate the rest of the VM snapshots that cannot be deployed on PiraeusU node, to another node with more available resources so as to avoid potential delays for the end-users/tenants. Would it be feasible?
Best Regards,
PiraeusU node team