Consolidate pkidaemon into pki-server.

[pki-bot]

This issue was migrated from Pagure Issue #1496. Originally filed by edewata (@edewata) on 2015-07-17 18:57:42:

• Closed at 2019-06-14 15:13:16 as fixed
• Assigned to edewata (@edewata)
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=1248216

---

The pkidaemon is currently used to start of PKI instances and check their statuses. This tool should be consolidated into pki-server CLI, so the server startup can be managed using:

$ pki-server <start|stop|restart|status> [instance name]

The start/stop/restart commands should work with regular instances as well as nuxwdog-enabled instances.

The status command should be implemented by reading the instance's actual configuration settings instead of pre-formatted message in server.xml (see ticket 1260).

[pki-bot]

Comment from mharmsen (@mharmsen) at 2015-07-17 23:57:17

Per IRC discussions between alee, edewata, and mharmsen: 10.3 (critical)

[pki-bot]

Comment from mharmsen (@mharmsen) at 2016-02-01 21:47:54

Per discussions in CS/DS meeting of 02/01/2016: 10.3 Backlog - major

[pki-bot]

Comment from mharmsen (@mharmsen) at 2016-04-22 00:24:29

Per CS Bug/Ticket Triage held 04/19/2016: 10.4

While it is highly desired to eliminate 'pkidaemon', it was determined that this would need to
wait until 10.4, as we simply have too many other higher priorities.

[pki-bot]

Comment from mharmsen (@mharmsen) at 2016-12-01 20:27:36

Per Offline Triage of 11/30/2016-12/01/2016: 10.4 - major

[pki-bot]

Comment from edewata (@edewata) at 2017-02-27 14:09:55

Metadata Update from @edewata:

• Issue assigned to mharmsen
• Issue set to the milestone: 10.4

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-08-09 16:44:19

Per CS/DS Meeting of August 7, 2017, it was determined to move this issue from 10.4 ==> FUTURE.

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-08-09 16:44:19

Metadata Update from @mharmsen:

• Custom field component adjusted to None (was: Process Management)
• Custom field feature adjusted to None
• Custom field proposedmilestone adjusted to None
• Custom field proposedpriority adjusted to None
• Custom field reviewer adjusted to None
• Custom field version adjusted to None
• Issue close_status updated to: None
• Issue set to the milestone: FUTURE (was: 10.4)

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-08-30 22:35:25

Metadata Update from @mharmsen:

• Issue set to the milestone: 10.5 (was: FUTURE)

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-10-25 18:22:53

[20171025] - Offline Triage ==> 10.6

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-10-25 18:22:54

Metadata Update from @mharmsen:

• Issue set to the milestone: 10.6 (was: 10.5)

[pki-bot]

Comment from edewata (@edewata) at 2018-03-19 12:57:08

Metadata Update from @edewata:

• Issue set to the milestone: FUTURE (was: 10.6)

[pki-bot]

Comment from mharmsen (@mharmsen) at 2018-04-13 18:28:38

Per 10.5.x/10.6 Triage: FUTURE

mharmsen: pkidaemon has been proposed to be replaced

[pki-bot]

Comment from cipherboy (@cipherboy) at 2019-03-14 13:57:28

pkidaemon and pki-server can both be used to start/stop instances, with the caveat that they display different information under status operations. These should be consolidated prior to removal.

[pki-bot]

Comment from edewata (@edewata) at 2019-06-14 15:13:16

Fixed in master branch:

• b97f19c
• d09bb7d
• 07e6a9d
• bc48fa6

Docs:

• https://www.dogtagpki.org/wiki/PKI_Server_Start_CLI
• https://www.dogtagpki.org/wiki/PKI_Server_Stop_CLI
• https://www.dogtagpki.org/wiki/PKI_Server_Restart_CLI
• https://www.dogtagpki.org/wiki/PKI_Server_Status_CLI

[pki-bot]

Comment from edewata (@edewata) at 2019-06-14 15:13:17

Metadata Update from @edewata:

• Issue close_status updated to: fixed
• Issue status updated to: Closed (was: Open)

[pki-bot]

Comment from edewata (@edewata) at 2019-06-14 15:13:53

Metadata Update from @edewata:

• Issue assigned to edewata (was: mharmsen)

[pki-bot]

Comment from edewata (@edewata) at 2019-06-14 15:14:53

Metadata Update from @edewata:

• Issue set to the milestone: 10.7.2 (was: FUTURE)