Task #12087
closedRemove services from Edison VO
100%
Description
It's needed to remove the Edison scope from the following services:
accounting-service1.d4science.org accounting-service2.d4science.org accounting-service3.d4science.org catalogue-ws.d4science.org resource-registry1.d4science.org resource-registry2.d4science.org node44.p.d4science.research-infrastructures.eu storagehub1.d4science.org workspace-repository-prod1.d4science.org (HL webbapp) socialnetworking1.d4science.org registry.d4science.org sdi.d4science.org thredds.d4science.org
In addition this scope should be removed from all the dataminer instances currently deployed in production
Related issues
Updated by Roberto Cirillo almost 7 years ago
- Blocks Task #11862: Dismiss EDISON Virtual Organisation and related enabling services added
Updated by Roberto Cirillo almost 7 years ago
- Blocks Task #12090: Remove Edison VO scope from infrastructure-monitor added
Updated by Roberto Cirillo almost 7 years ago
- Status changed from New to In Progress
On node44.p.d4science.research-infrastructures.eu (VREModeler service, not provisioned), the scope will be removed manually.
While, in the other services, the scope will be removed from ansible-playbook and the changes will be applied during the next downtime, planned for gCube 4.12.
Updated by Roberto Cirillo almost 7 years ago
- % Done changed from 0 to 10
node44.p.d4science.research-infrastructures.eu removed
Updated by Roberto Cirillo almost 7 years ago
- % Done changed from 10 to 40
scope removed from ansible-playbook.
We should also remove the Edison key from the playbook.
Updated by Roberto Cirillo almost 7 years ago
- Related to Upgrade #12019: D4Science Infrastructure Upgrade to gCube 4.12.0 added
Updated by Roberto Cirillo over 6 years ago
- Status changed from In Progress to Paused
- % Done changed from 80 to 90
Removed from Edison VO the following services:
socialnetworking1.d4science.org catalogue-ws.d4science.org
Now, only the dataminer instances are still running under Edison VO. The dataminer scopes will be updated when the new VO is active: the Edison VO will be replaced with a new VO. In this way, in one shot we could remove the old one and add the new one to the dataminer instances.
Updated by Roberto Cirillo over 6 years ago
- Blocks deleted (Task #11862: Dismiss EDISON Virtual Organisation and related enabling services)
Updated by Roberto Cirillo over 6 years ago
- Related to Task #11862: Dismiss EDISON Virtual Organisation and related enabling services added
Updated by Roberto Cirillo over 6 years ago
- Related to Task #12352: Add new VO scope D4OS to all the dataminer instances added
Updated by Roberto Cirillo over 6 years ago
- Status changed from Paused to Closed
- % Done changed from 90 to 100