ISTI Open Access

I add some details about the components of the current machines:

dnet.openportal.isti.cnr.it

• Java (OpenJDK 1.8.0_171)
• Tomcat7 (7.0.52-1ubuntu0.16)
• dnet application (it manages 2 embedded databases, the files are stored in /var/lib/dnet/)

backend.openportal.isti.cnr.it

• MySQL (5.5.62):
  • Joomla databases: op_beta_joomla, op_ismar_joomla, op_prod_joomla
  • dnet databases: isti_affiliations
• Solr (5.5.5): the index can be automatically regenerated by dnet
• Mongo (3.6.9): relevant databases are dnet_logs_isti, mdstore_isti, oaistore_isti

openportal.isti.cnr.it

• Apache 2, it hosts the Joomla sites, it exposes the content of the /data directory and redirect the calls to https://openportal.isti.cnr.it/oai to the dnet application
• PHP with modules for mongo and solr
• FTP server, it permits to manipulate the file under /data, it must be accessible also by the dnet application
• Joomla (3 instances)
  

Michele Artini wrote in #note-5:

• Tomcat7 (7.0.52-1ubuntu0.16)

Tomcat's version will be 8.5

There are also some shell scripts under /etc/cron.hourly of openportal.isti.cnr.it . These scripts keep the totals updated on the main page of the portals.

It's time to manage everything inside the ansible playbook, I hate having to search servers and find all the manual tweaks.

Michele Artini wrote in #note-7:

There are also some shell scripts under /etc/cron.hourly of openportal.isti.cnr.it . These scripts keep the totals updated on the main page of the portals.

@michele.artini@isti.cnr.it those script should be provisioned by ansible. Where do we can find them?

Also: all the problems seems to have been solved.
Can we schedule the migration of the two other portals?

The scripts in /etc/cron.hourly are specific for each instance of portal. I need to edit them easily.

I still don't like manual editing in place, for whatever reason.
We could:

• Give you the ability to run the ansible playbook
• You put the cron entries into a git repository, and we use a cron job to pull from it.

@tommaso.piccioli@isti.cnr.it Could you permit the access to newbackend-openportal.isti.cnr.it (mysql, mongo and solr via https) from openportal.isti.cnr.it?

So, I will reconfigure all the portals to use the new backends and we could dismiss:

• dnet-openportal.isti.cnr.it (entire machine)
• backend-openportal.isti.cnr.it (for now only mongo and solr )

Michele Artini wrote in #note-21:

@tommaso.piccioli@isti.cnr.it Could you permit the access to newbackend-openportal.isti.cnr.it (mysql, mongo and solr via https) from openportal.isti.cnr.it?

done.

I reconfigured the ISTI, ISMAR and BETA portals to be managed by the services hosted on the new machines:

• newdnet-openportal.isti.cnr.it (dnet aggregator)
• newbackend.openportal.isti.cnr.it (mongo, solr and mysql)

Probably we could stop the old machines:

• dnet-openportal.isti.cnr.it
• backend.openportal.isti.cnr.it

Instead the portals are yet hosted on the old machine (Ubuntu 14.04, PHP 7.2.13) and need to be moved on the new server.

@tommaso.piccioli@isti.cnr.it @andrea.dellamico@isti.cnr.it
In the old server to enable the OAI exporter from the ISTI portal, according to the new mechanism, I commented the following line:

# ProxyPassMatch ^/oai(.*)$ https://dnet-openportal.isti.cnr.it/is/mvc/oai/oai.do$1

of file:

/etc/apache2/sites-enabled/openportal.isti.cnr.it.conf

That line is no longer necessary, you should remove it in the Ansible scripts.

dnet-openportal.isti.cnr.it and backend.openportal.isti.cnr.it switched off.

The ISTI portal was using the solr API, exposed by the backend.openportal.isti.cnr.it via https, to render some pages, for example: https://www.isti.cnr.it/en/research/publications

Could you reassign the name backend.openportal.isti.cnr.it to newbackend.openportal.isti.cnr.it and configure a proxy to expose the port 8983 via https?