Project

General

Profile

Actions

Task #10838

closed

Alias for ckan-grsf-admin2.d4science.org machine

Added by Costantino Perciante over 7 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
High
Assignee:
_InfraScience Systems Engineer
Category:
Data Management
Target version:
Start date:
Jan 09, 2018
Due date:
% Done:

100%

Estimated time:
Infrastructure:
Production

Description

We currently have two machines for the management activities of the GRSF community:

The older one can be shut down but we need to keep it for a while (I will alert you as soon as we can destroy it)

To let things be as transparent as possible I would like to have an alias for redirecting call addressed at ckan-grsf-admin.d4science.org to ckan-grsf-admin2.d4science.org

Actions #1

Updated by Pasquale Pagano over 7 years ago

  • Tracker changed from Support to Task
Actions #2

Updated by Costantino Perciante over 7 years ago

  • Priority changed from Normal to High
Actions #3

Updated by Tommaso Piccioli over 7 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 10

new letsencrypt certificate requested.

Actions #4

Updated by Tommaso Piccioli over 7 years ago

  • Status changed from In Progress to Feedback
  • % Done changed from 10 to 100

we must wait for the new letsencrypt certificate, no way to obtain it immediately due to the limit to the number of request.

Actions #5

Updated by Costantino Perciante over 7 years ago

Tommaso Piccioli wrote:

we must wait for the new letsencrypt certificate, no way to obtain it immediately due to the limit to the number of request.

Thanks! I'm wondering how long it would take: are we talking about days or more (weeks)?

Actions #6

Updated by Andrea Dell'Amico over 7 years ago

Usually we have to wait 2/3 days at maximum. The last big batch of updates was run Jan 2nd, so the certificate could be issued tomorrow (the cap lasts a week).

Actions #7

Updated by Pasquale Pagano over 7 years ago

I am wondering the following can be implemented instead

a) shut down ckan-grsf-admin.d4science.org
b) rename ckan-grsf-admin2.d4science.org in ckan-grsf-admin.d4science.org

In this way, we don't need to wait for the new certificate and we do not need to add a DNS redirection.

Actions #8

Updated by Andrea Dell'Amico over 7 years ago

renaming is always a bit awkward but it's doable.
I assumed that ckan-grsf-admin2.d4science.org was already in use.

Actions #9

Updated by Tommaso Piccioli over 7 years ago

  • Status changed from Feedback to Closed

Certificate was OK this morning:

Certificate Subject Alt Name:
DNS Name: ckan-grsf-admin.d4science.org
DNS Name: ckan-grsf-admin2.d4science.org

I will destroy the old ckan-grsf-admin.d4science.org VM.

Actions #10

Updated by Costantino Perciante over 7 years ago

Tommaso Piccioli wrote:

Certificate was OK this morning:

Certificate Subject Alt Name:
DNS Name: ckan-grsf-admin.d4science.org
DNS Name: ckan-grsf-admin2.d4science.org

I will destroy the old ckan-grsf-admin.d4science.org VM.

Perfect! Let's just keep the old one for a while (i.e. few days)

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 8.91 MB)