ocf_heartbeat_jira(7)

ocf_heartbeat_jira7

Jira ocf ra

Usage

jira [start | stop | monitor | meta-data | validate-all]

Overview

OCF Resource Agent to manage JIRA software

Supported parameters

statusurl

Status URL for JIRA monitoring

(optional, string, default "http://localhost:8080/status")

java_home

Java Home in the Linux instance

(optional, string, default "/usr/lib/jvm/jre")

jira_installation

JIRA installation directory (binaries, ... etc)

(required, string, no default)

jira_user

User to run Jira software with

(optional, string, default "jira")

Supported actions

This resource agent supports the following actions (operations):

start

Starts the resource. Suggested minimum timeout: 300s.

stop

Stops the resource. Suggested minimum timeout: 300s.

monitor

Performs a detailed status check. Suggested minimum timeout: 30s. Suggested interval: 10s.

meta-data

Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5s.

validate-all

Performs a validation of the resource configuration. Suggested minimum timeout: 20s.

Example CRM shell

The following is an example configuration for a jira resource using the crm(8) shell:

primitive p_jira ocf:heartbeat:jira \
  params \
    jira_installation=string \
  op monitor timeout="30s" interval="10s" depth="0" 

Example PCS

The following is an example configuration for a jira resource using pcs(8)

pcs resource create p_jira ocf:heartbeat:jira \
  jira_installation=string \
  op monitor timeout="30s" interval="10s" OCF_CHECK_LEVEL="0" 

Releases

4 releases since Debian 10 (Buster); the text changed 3 times.

  1. 10
  2. 11
  3. 12
  4. 13

Author

ClusterLabs contributors (see the resource agent source for information about individual authors)

From resource-agents 1:4.16.0-3+deb13u2 in Debian 13 (Trixie). Parsed by carta from the page's man source.