#187 Dogtag 10: Port 'systemd' logic from pkicreate to pkideploy . . .
Closed: Fixed Opened by mharmsen.

Since 'pkicreate' utilizes 'systemd' to create per PKI subsystem instances, it will be necessary to port the following functions to create a 'systemd' which launch a single PKI Tomcat instance which may house a CA, KRA, OCSP, and/or TKS:

    * pki-<subsystem>d.target --> pki-tomcatd.target
    * pki-<subsystem>d@.service --> pki-tomcatd@.service
    * pki-<subsystem>d.target.wants/ --> pki-tomcatd.target.wants/
    * <subsystem> registry_instance --> <common> pkidaemon_registry
    * pkisetup pkicontrol --> pkideploy pkidaemon
    * pkisetup functions --> pkideploy operations

Fixed in:

commit 4a263b8db27208413acd0f038ea67629d5ee27bb
Author: Matthew Harmsen mharmsen@redhat.com
Date: Wed May 23 18:59:06 2012 -0700

PKI Deployment Scriptlets
- Integration of Tomcat 7
- Addition of centralized 'pki-tomcatd' systemd functionality to the
  PKI Deployment strategy
- Removal of 'pki_flavor' attribute

Metadata Update from @mharmsen:
- Issue assigned to mharmsen
- Issue set to the milestone: Dogtag 10.0 - Phase 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/759

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