ISTI Open Access

There's no difference between dev and production machines, but I agree that the hostname is misleading and it should be better to split the services (and use a diffferent mongodb instance).

I'm of the opinion that such a service should live on the ISTI servers, but your choice.

There is also a solr instance.

@andrea.dellamico@isti.cnr.it I'm fine with ISTI servers if (a) we already have them, (b) the machine we have are suitable for the service(s).

@tommaso.piccioli@isti.cnr.it can answer. He knows better than me the hypervisors that could host the service (the same one where social-isti is running, FYI).

I think that 3 machines are necessary for the production deployment:

1. dnet.openportal.isti.cnr.it (java 8 + tomcat 7 + dnet): 2 cpus, 8GB Ram, ~12GB diskspace

2. backend.openportal.isti.cnr.it (solr 5.5.x + mongo + mysql)): 4 cpus, 16GB Ram, ~64GB diskspace

3. openportal.isti.cnr.it, beta.openportal.isti.cnr.it, ftp.openportal.isti.cnr.it (php 7 + apache + mysql + joomla + ftp server): 4 cpus, 16GB Ram, ~512GB diskspace

The third machine should hosts 2 web sites (openportal.isti.cnr.it and beta.openportal.isti.cnr.it) and an ftp server; the ftp users should write in a particular directory and this directory should be visible by the web users.

NB. The modification of the openportal.isti.cnr.it DNS entry should be performed after the migration of the current portal.

Vm created (and now running):

dnet-openportal.isti.cnr.it (146.48.87.206), alias dnet.openportal.isti.cnr.it
2 cpus, 8GB Ram, 12GB diskspace

backend-openportal.isti.cnr.it (146.48.87.207), alias  backend.openportal.isti.cnr.it
4 cpus, 16GB Ram, 12GB + 64GB (/data) diskspace

portal-openportal.isti.cnr.it (146.48.87.208), aliases beta.openportal.isti.cnr.it, ftp.openportal.isti.cnr.it 
4 cpus, 16GB Ram, 12 Gb + 500GB (/data) diskspace

All the SW must be installed yet and /data mount-point can be changed

• mysql should only on the backend server
  mysql is used by d-net and by the portals; if you prefer a single installation, it is OK.

• the reverse proxy of the running instance is nginx, I'd stick with it
  If you prefer nginx it is OK, I proposed Apache because some features have a better documentation using Apache.

• beta and openportal are two distinct installations of joomla, each one with its database, correct?
  yes

dnet-openportal.isti.cnr.it has been deployed. The dnet application will answer at https://dnet.openportal.isti.cnr.it/is when installed.
Michele has access as michele.artini, with write permissions under the tomcat webapps directory.

We had the OK to switch the official hostname so that it points to the new frontend: just done.