Details
-
Type:
extRequest
-
Status: Closed
-
Priority:
Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-LAB-HELP
-
Labels:None
-
Sender Email:
-
HD-Node:PiraeusU
Description
Dear Mr/Mrs,
my name is Thomai Giotopoulou and i am currently working under mermix
project, that has been funded from Fractals Consortium.
mermix's account on Fi Lab, includes 3 virtual machine instances, but for
the projects' needs its necessary to have 2 more instances in order to
complete it successfully.
Could you please advise us on how we can have 5 vm instances into our
account?
Thank you in advance.
mermix team
26, Agias Paraskevis str,
PS 35100, Lamia, GREECE
t. +30 22310 54040
www.mermix.gr
[image: Lobo_300x81]
Access Nearby Tools
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-lab-help@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: mermix Access Nearby Tools <info@mermix.gr>]
Activity
Dear Team,
Could you please help the user with this migration?
Thanks kr
Omer
Dear user,
for the migration process, as far as we known, it is implemented by the current host node towards the new node. We as PiraeusU node we do not have access rights to the node where the user is currently hosted.
Consequently, the migration request should be served by the current hos node. Since the VMs of the user/tenant/project will be migrated to our node (PiraeusU) then we will be able to manipulate any request with respect ot resources allocation, under a new FLUA request.
The current ticket is unassigned by PiraeusU since there is no further action from our side with respect to migration. For the allocation of new resources, please issue a new resource request @ https://account.lab.fiware.org/, by clicking on button request a community account.
Best Regards,
PirauesU node team
The VM's have been transfered to PiraeusU. When the new node has finished the migration process on their side (which may take a while since most of our users migrated there) the user will have to cooperate with them to ask for their added requirements. As far as PiraeusN is concerned there is nothing else to do.
Dear all,
after a synchronization with PiraeusN node, the migration process has started. PiraeusU has now the VM snapshots of tenants' VMs and proceed with the deployment of the VM instances.
We will do our best so as to complete the process the soonest possible, whereas will inform by email the users, when the VM instances will be deployed in our node. We will give access to the node through the cloud portal by enabling them into keyrock, as well.
Best Regards,
PiraeusU node team
Dear all,
we have completed the migration process of the project VMs in collaboration with PiraeusN node. We have authorized the user to use PiraeusU node, and we have informed the user with the below email.
User do not send some particular problem. The current ticket could be considered as closed. In case there is some additional problem please raise a new ticket.
Best Regards,
PiraeusU node team
-----------------
_Dear user,
with this email we would like to inform you that your VMs have been migrated from PiraeusN node to PiraeusU node and there are available as private image snapshots in the image list, that you can directly launch them and have back your VM instance.
Please follow the guidelines in the attached file and of course feel free to contact us for any further clarification and/or help.
Best Regards,
Dimitris Kelaidonis, on behalf of PiraeusU Openstack node team_
-----------------
Dear Team,
Could you please help us with the extra 2 VM creation?
Thanks kr
Omer