#1183 Starting/stopping individual subsystems
Closed: Fixed Opened by edewata.

Currently to deploy/undeploy a subsystem the whole Tomcat has to be restarted. If a subsystem is having a problem, the entire server might need to be brought down or restarted in order to troubleshoot/fix the problem, which can be quite disruptive to the other subsystems running in the same instance. There should be a way to start/stop individual subsystems without affecting the others. This may be required to fix ticket #745.

One solution would be to use Tomcat auto deploy feature (see option 2 in comment #1 for ticket #745). For this to work, the web applications need to be moved out of the current appBase (i.e. /webapps) into the following folders:

  • subsystem webapps: //webapps
  • common webapps: /common/webapps

The deployment scriptlets need to be modified to use the new locations. An upgrade script can be written to relocate the webapps in existing instances automatically. Once this is implemented, it would be possible to create a tool to manage individual subsystem life-cycle as follows:

$ pki-server subsystem-stop pki-tomcat kra

Ideally changes like this should be done in 10.3. However, this ticket is required to fix ticket #745 which is targeted for 10.2.3. So the options are to fix both tickets in 10.2.x, or to postpone both tickets to 10.3.


Proposing milestone 10.2.1 since ticket #745 is a usability issue.

The pki-edewata-0530-Moved-web-application-deployment-locations.patch is obsolete.

After discussions with edewata and cfu, moving to proposed Milestone 10.2.2.

Additionally, per request of edewata, also moving PKI TRAC Ticket #1129 - Upgrade framework improvements back from 10.3 to 10.2.2.

master:

  • 2d574090ba49eec9647b78b44d841a6d6026dccf
  • a578cf649c0c41676677cf0a6ede03ea8d6fedb7
  • 3294ac64d9e71f76309d2cc12a2c256838fe8666

Metadata Update from @edewata:
- Issue assigned to edewata
- Issue set to the milestone: 10.2.2

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/1746

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata