Task #6015
closed
Provide a new VM for hosting the gCubeApps Registry service
Added by Roberto Cirillo almost 9 years ago. Updated over 8 years ago.
100%
Description
In order to upgrade the gCubeApps Registry service hosted on:
node65.p.d4science.research-infrastructures.eu
It's need to have another VM with the same resources of the previous one.
The switch will be done in the gCube 4.2 release planned for December 12th, 2016
Updated by Roberto Cirillo almost 9 years ago
I suggest to use the following hostname:
registry-gcubeapps.d4science.org
with alias :
node65.p.d4science.research-infrastructures.eu
Updated by Andrea Dell'Amico almost 9 years ago
- Status changed from New to In Progress
- Assignee changed from Tommaso Piccioli to Andrea Dell'Amico
Updated by Roberto Cirillo almost 9 years ago
It's need to have the following resources:
- 2 vcpu
- 5GB RAM
- 10GB HD
- java7
- an user called gcube
Updated by Andrea Dell'Amico almost 9 years ago
hostname and IP are going to be: registry-gcubeapps.d4science.org 146.48.122.99
Updated by Andrea Dell'Amico almost 9 years ago
The provisioning is running right now. Le me know when you want to move the hostname alias.
Updated by Andrea Dell'Amico almost 9 years ago
- Status changed from In Progress to Feedback
- % Done changed from 0 to 100
node65.p.d4science.research-infrastructures.eu is an alias for registry-gcubeapps.d4science.org.
registry-gcubeapps.d4science.org has address 146.48.122.99
Updated by Andrea Dell'Amico almost 9 years ago
- Status changed from Feedback to Closed
Updated by Roberto Cirillo almost 9 years ago
- Status changed from Closed to In Progress
- Priority changed from Normal to Urgent
- % Done changed from 100 to 80
I see a double registration of the gCubeApps Registry instance on monitor (https://services.d4science.org/infrastructure-monitor): the old one (node65.p) and the new one (registry-gcubeapps).
Both the container and both the service instances are currently registered and updated every minute on the IS.
How is it possible if the old node65.p has been dismissed? The new one VM is a new one VM as requested or it is recycled by the previous one?
I guess it is recycled by the previous one and maybe there is old stuff on the VM. Please could you check?
Updated by Roberto Cirillo almost 9 years ago
- Priority changed from Urgent to High
Updated by Andrea Dell'Amico almost 9 years ago
Roberto Cirillo wrote:
I see a double registration of the gCubeApps Registry instance on monitor (https://services.d4science.org/infrastructure-monitor): the old one (node65.p) and the new one (registry-gcubeapps).
node65.p.d4science.research-infrastructures.eu is an alias (CNAME) of registry-gcubeapps.d4science.org since when I wrote https://support.d4science.org/issues/6015#note-6
The old VM is still available at the old IP address: 146.48.122.145. Did you stop the service there?
Both the container and both the service instances are currently registered and updated every minute on the IS.
How is it possible if the old node65.p has been dismissed? The new one VM is a new one VM as requested or it is recycled by the previous one?
I guess it is recycled by the previous one and maybe there is old stuff on the VM. Please could you check?
You know that it's a new VM. Because we never recicle, and because you explicitly asked for a new one. You also know that the old and the new were running in parallel.
Updated by Roberto Cirillo almost 9 years ago
Andrea Dell'Amico wrote:
Roberto Cirillo wrote:
I see a double registration of the gCubeApps Registry instance on monitor (https://services.d4science.org/infrastructure-monitor): the old one (node65.p) and the new one (registry-gcubeapps).
node65.p.d4science.research-infrastructures.eu is an alias (CNAME) of registry-gcubeapps.d4science.org since when I wrote https://support.d4science.org/issues/6015#note-6
The old VM is still available at the old IP address: 146.48.122.145. Did you stop the service there?
I've stopped it but it was restarted tonight at 3.55 AM because there was a cronjob active.
I'm going to stop it now and to rename the start script in the user home to avoid this behavior.
Both the container and both the service instances are currently registered and updated every minute on the IS.
How is it possible if the old node65.p has been dismissed? The new one VM is a new one VM as requested or it is recycled by the previous one?
I guess it is recycled by the previous one and maybe there is old stuff on the VM. Please could you check?
You know that it's a new VM. Because we never recicle, and because you explicitly asked for a new one. You also know that the old and the new were running in parallel.
Perfect. Thanks.
Updated by Andrea Dell'Amico almost 9 years ago
Roberto Cirillo wrote:
I've stopped it but it was restarted tonight at 3.55 AM because there was a cronjob active.
I'm going to stop it now and to rename the start script in the user home to avoid this behavior.
Is it too early to dismiss the VM?
Updated by Roberto Cirillo almost 9 years ago
- Status changed from In Progress to Feedback
- Assignee changed from Andrea Dell'Amico to Roberto Cirillo
- % Done changed from 80 to 100
Andrea Dell'Amico wrote:
Roberto Cirillo wrote:
I've stopped it but it was restarted tonight at 3.55 AM because there was a cronjob active.
I'm going to stop it now and to rename the start script in the user home to avoid this behavior.Is it too early to dismiss the VM?
I think it's better to wait a couple of days before to dismiss it but we could shutdown it right now if you agree.
I'm going to assign this ticket to me and set it to feedback for reminder.
Updated by Roberto Cirillo over 8 years ago
- Assignee changed from Roberto Cirillo to _InfraScience Systems Engineer
I think the old vm "node65.p.d4science.research-infrastructures.eu" can be dismissed now.
After that, this ticket can be closed.
Updated by Tommaso Piccioli over 8 years ago
- Status changed from Feedback to Closed
