In Polyspace Access R2020a, is it possible to autostart Access Cluster services on boot?

Polyspace Access has been installed on a Debian 9.13 machine according to the documentation.

After the cop-docker-agent is started, all child services (User Manager, Issue Tracker, Database, ETL, Web Server and Gateway) are in Stopped mode.

An administator has to log in to the Polyspace Access Cluster Operator website and start all the services manually.

Is it possible to configure the services to start automatically when cop-docker-agent is started?

Answer 1

[Anirban]

You can change the Docker restart policy so that the services restart automatically after a reboot. See more details in Configure Polyspace Access to Restart Automatically.

[Andrej Gantvorg]

Thank you very much for the answer!

However, I've got a follow-up question. In order to get the individual service images after the initial setup, one has to log in to the Cluster Operator website and click the "Provision" button.

Is it possible to trigger this initial image retrieval task using the command line or the like?

I would like to auto-provision the server using Ansible and this is the only step left that requires human interaction with the system.

[Anirban]

Thanks for asking the question!

Just to clarify in case there is a confusion, the provisioning is a one-time activity. Once you provision, on every restart, you should not need to do the provisioning again.

However, if you do not want to do the one-time provisioning through the Cluster Operator page, there is no documented command-line way as of now to trigger the provisioning. You can use Docker commands to do the provisioning, but it would require knowing the relevant environment variables and volumes to be mounted. Please contact MathWorks Technical Support to help you with the automation.