VM Creation #9874
closed
Provide new VM for hosting fhn-manager service in production environment
100%
Description
The new VM replace the old node65.d4science.org. The ansible role should be ready to use.
Updated by Roberto Cirillo over 7 years ago
- Copied from VM Creation #9726: Provide new VM for hosting fhn-manager service added
Updated by Roberto Cirillo over 7 years ago
- Copied from deleted (VM Creation #9726: Provide new VM for hosting fhn-manager service)
Updated by Roberto Cirillo over 7 years ago
- Priority changed from Normal to High
Updated by Tommaso Piccioli over 7 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 20
New VM host is fhn-manager.d4science.org
Updated by Andrea Dell'Amico over 7 years ago
@roberto.cirillo@isti.cnr.it do you need it provisioned?
Updated by Roberto Cirillo over 7 years ago
Andrea Dell'Amico wrote:
@roberto.cirillo@isti.cnr.it do you need it provisioned?
The provisioning for this VM should be ready to run. I've also update the service version and the inventory file with the new VM.
Updated by Roberto Cirillo over 7 years ago
- Assignee changed from _InfraScience Systems Engineer to Roberto Cirillo
- % Done changed from 20 to 100
The fhn-manager service has been installed
Updated by Roberto Cirillo over 7 years ago
- Status changed from In Progress to Feedback
- Assignee changed from Roberto Cirillo to Nunzio Andrea Galante
Updated by Nunzio Andrea Galante over 7 years ago
The FHNManager service works fine and the configuration is correct.
Just a thing: according to rOCCI guidelines, CRLs should have to be always up to date, otherwise a proxy generation fail could be produced.
In order to avoid this kind of problem, it is necessary to install, on the entire set of VMs hosting the service, a cronjob that run periodically (i guess once a week is enough) the following command: fetch-crl.
This should have to be added to the ansible-playbook then, in order to have a complete automatization of the deploy.
Updated by Roberto Cirillo over 7 years ago
- Status changed from Feedback to Closed
Nunzio Andrea Galante wrote:
The FHNManager service works fine and the configuration is correct.
Just a thing: according to rOCCI guidelines, CRLs should have to be always up to date, otherwise a proxy generation fail could be produced.
In order to avoid this kind of problem, it is necessary to install, on the entire set of VMs hosting the service, a cronjob that run periodically (i guess once a week is enough) the following command: fetch-crl.
This should have to be added to the ansible-playbook then, in order to have a complete automatization of the deploy.
DONE
