Move of BlueEconomy companies VREs from gCubeApps Virtual Organisation to FARM
|Status:||Closed||Start date:||Jun 27, 2017|
|Priority:||High||Due date:||Jun 30, 2017|
|Assignee:||Gerasimos Antzoulatos||% Done:|
Dear Gerasimos and Denis,
we plan to move the 3 VREs (Forkys, Ellenika and Alieia from the current Virtual Organisation to the FARM. This is to better distribute the work load of the infrastructure.
In practice this means that the VRE name (and groupid) will be maintained but the infrastructure scope (aka context) would change from e.g.
- /d4science.research-infrastructures.eu/gCubeApps/EllinikaPsariaVRE to /d4science.research-infrastructures.eu/FARM/EllinikaPsariaVRE
Before doing this we would need to know if the database serving the VREs (or any other WP6 service involved) uses the infrastructure scope (aka context) in any way that would make the VRE stop working.
Note that the content of the Workspace will remain as is, and the services deployed in the new scopes. So my concerns are about the DB used an or any other "stateful" storage you may use in these VREs.
#1 Updated by Denis Pyriochos over 2 years ago
Dear @firstname.lastname@example.org we are using the full scope name in order to identify each aqua farm in the database. As soon as you move them to the new infrastructure we should update their records. So please provide us with the new full scope names and we will do the database update.
#2 Updated by Massimiliano Assante over 2 years ago
- Status changed from New to In Progress
Thanks Denis, I think we should do this in a coordinate manner.
First I suggest to wait for the WP6 Services to be fully functional in the 2 new VRES (Markellos and Stratos), then we will perform the move in coordination. When would it be a suitable time for you this week?
#4 Updated by Massimiliano Assante over 2 years ago
The 3 VREs running on the following scopes, respectively:
Are going to be moved under FARM, the new scopes for the 3 VREs will be the following:
@email@example.com I suggest to do this Tomorrow, Friday 30th at 11.30 CEST You will need to apply the required changes in the DB while @firstname.lastname@example.org to make available the required services running on gCubeApps on FARM
is the plan ok with both of you?
#8 Updated by Kostas Kakaletris over 2 years ago
@email@example.com is it OK to do it at 09:00 CEST or you need to do changes on your side too and it is not convenient for you?
@firstname.lastname@example.org after fixing the time are you going to send a notification for downtime on this VREs? (I believe a one hour downtime is sufficient for changing and testing, is that correct @email@example.com ?)
#18 Updated by Kostas Kakaletris over 2 years ago
The service is started but not getting the VREs correct on all services. ie I see on IS that host is shown to be under all declared VREs but simulefish endpoint is shown under on;y the first one and not working correctly.
No errors in tomcat.
In Smatgears I see the following
14:43:13.851 [localhost-startStop-1] WARN Bootstrap: WELD-001208: Error when validating file:/home/gcube/apache-tomcat-7.0.72/webapps/data-transfer-service/WEB-INF/classes/META-INF/beans.xml@4 against xsd. cvc-complex-type.4: Attribute 'bean-discovery-mode' must appear on element 'beans'.
14:43:14.095 [localhost-startStop-1] WARN Interceptor: WELD-001700: Interceptor annotation class javax.ejb.PostActivate not found, interception based on it is not enabled
14:43:14.096 [localhost-startStop-1] WARN Interceptor: WELD-001700: Interceptor annotation class javax.ejb.PrePassivate not found, interception based on it is not enabled
14:43:14.399 [localhost-startStop-1] WARN Event: WELD-000411: Observer method [BackedAnnotatedMethod] private org.glassfish.jersey.gf.cdi.internal.CdiComponentProvider.processAnnotatedType(@Observes ProcessAnnotatedType
I will try to add VREs to the service one by one to see if the problem is because of a specific VRE
#20 Updated by Roberto Cirillo over 2 years ago
Some service on dewn05 were running only on a single scope but the container was running on more than one scope. This is not possible, I guess it could be a smartgears bug and I'm going to open a ticket about that.
I've resolved the problem on dewn05 adding the VO scope on the container and adding manually the VRE scopes on the GCoreEndpoint resources of the services. Now, the services are running on all the scope as expected.