D4Science Infrastructure

Roberto, it seems the endpoint we added yesterday for the db is not e enough https://support.d4science.org/issues/5393

I had already added the serviceEndpoint named SimulFishGrowth also present in the preVRE VRE.
This is the only serviceEndpoint for SimulFish present in preproduction environment.
If you need another ServiceEndpoint, you should specify more details in order to understand what you need and how I have to fill the new resource. The service Endpoint that I've added is the following:

<Profile>
      <Category>Database</Category>
      <Name>SimulFishGrowth</Name>
      <Description>Data supporting what-if analyses regarding fish growth</Description>
      <Platform>
         <Name>PostgreSQL</Name>
         <Version>9</Version>
         <MinorVersion>4</MinorVersion>
         <RevisionVersion>0</RevisionVersion>
         <BuildVersion>0</BuildVersion>
      </Platform>
      <RunTime>
         <HostedOn>db-sfg-pre.d4science.org</HostedOn>
         <GHN UniqueID="" />
         <Status>READY</Status>
      </RunTime>
      <AccessPoint>
         <Description>Database supporting what-if analyses regarding fish growth</Description>
         <Interface>
            <Endpoint EntryName="SimulFishGrowth_pre">db-sfg-pre.d4science.org:5432</Endpoint>
         </Interface>
         <AccessData>
            <Username>sfguser</Username>
            <Password>qdg7ap2ePyTai0WhP+dL7A==</Password>
         </AccessData>
      </AccessPoint>
   </Profile>

Is it right or you need another one?

Denis Pyriochos wrote:

This resource is available to preVRE and Dorne. Please make it available to preECO, as well. There is no need to change anything else as @k.kakaletris@cite.gr will take it from there :)

<Resource version="0.4.x">
   <ID>53cdcc71-cbde-4871-9448-f7a04357dda8</ID>
   <Type>RunningInstance</Type>
   <Scopes>
      <Scope>/gcube/preprod/Dorne</Scope>
      <Scope>/gcube/preprod/preVRE</Scope>
   </Scopes>
   <Profile>
      <Description>Access Simulation Fish Growth Data using a RESTfull Json API</Description>
      <Version>0.0.2-SNAPSHOT</Version>
      <GHN UniqueID="0ac4f93b-68a8-4726-8b99-0bbd560a8c13" />
      <Service UniqueID="SimulFishGrowthDataSearch0.0.2-SNAPSHOT" />
      <ServiceName>SimulFishGrowthData</ServiceName>
      <ServiceClass>Search</ServiceClass>
      <DeploymentData>
         <ActivationTime value="2017-05-29T11:08:42+02:00" />
         <Status>ready</Status>
      </DeploymentData>
      <AccessPoint>
         <RunningInstanceInterfaces>
            <Endpoint EntryName="API REST Service">http://dl20.di.uoa.gr:8080/simul-fish-growth-data/api</Endpoint>
            <Endpoint EntryName="SimulFishGrowthData-remote-management">http://dl20.di.uoa.gr:8080/simul-fish-growth-data/gcube/resource</Endpoint>
            <Endpoint EntryName="StartupServicesServlet">http://dl20.di.uoa.gr:8080/simul-fish-growth-data/StartupServicesServlet</Endpoint>
         </RunningInstanceInterfaces>
      </AccessPoint>
   </Profile>
</Resource>

This is a Running Instance resource. This kind of resource is automatically added to preECO VRE if your service is running in preEco VRE. So we need to run the service to preECO VRE @k.kakaletris@cite.gr, could you add the preECO VO scope to the service, please?

@denispyr@i2s.gr I do not think that the current preproduction resource (dl20) should be added to that new preproduction VRE. If I'm not mistaken this VRE was created for testing/development of a community app, because it was affected by the parallel development of enabling components.
In my understanding preVRE is the same as the production or at last releases that are to go to production and not for development.

Because of the above I preferred to change the current development resources of simulefish and technoeconomics (dl015.amadgik.di.uoa.gr) to the new pre-production VRE. This VM is the one that was on development and can be accessed by the developers that had access to it as before (in contrary, to the preVRE resources the access is granted per incident)

The services are up and running on the preprod/preECO vre. Please verify that it is OK and close the ticket.

• @roberto.cirillo@isti.cnr.it , by the way, would it be OK if the same resource was belonging to both development and preproduction VREs(e.g. smartgear tokens for preprod/preECO, devsec/devVRE)

Kind Regards,
Kostas