Some servers do not have a remote control. Our duty shift could perform necessary power actions and connect external IP KVM to the server. This could be done via API, which will create tickets in our Service desk software (Remote Hand Request - RHR).

Remote hands actions:

ResourceActionDescription
jira.phprequest_ponOpen RHR to power on the server
jira.phprequest_poffOpen RHR to power down the server
jira.phprequest_rebootOpen RHR to reboot the server
jira.phprequest_PXEbootOpen RHR to boot the server from PXE
jira.phprequest_kvmOpen RHR to connect IP KVM to the server
jira.phprequest_checkOpen RHR to check and load the server into OS

Each action will create JIRA ticket TICKET_ID accessible via https://my.hostkey.com/servicedesk/customer/portal/1/TICKET_ID with subject and message on behalf of the user. The user will receive an email message with confirmation. After the requested action was performed, the duty shift will communicate with the customer via this ticket.

Jira/Request_pon


HTTP Method - POST


ParameterRequiredType Value/defaultDescription
action    *        stringrequest_ponMain action - Open RHR to power on the server
token     *        string              Your session token
id     *        int              Your server ID
curl -s "https://invapi.hostkey.com/jira.php" -X POST \
--data "action=request_pon" \
--data "token=" \
--data "id="


Jira/Request_poff


HTTP Method - POST


ParameterRequiredType Value/defaultDescription
action    *        stringrequest_poffMain action - Open RHR to power down the server
token     *        string              Your session token
id     *        int              Your server ID
curl -s "https://invapi.hostkey.com/jira.php" -X POST \
--data "action=request_poff" \
--data "token=" \
--data "id="


Jira/Request_reboot


HTTP Method - POST


ParameterRequiredType Value/defaultDescription
action    *        stringrequest_rebootMain action - Open RHR to reboot the server
token     *        string              Your session token
id     *        int              Your server ID
curl -s "https://invapi.hostkey.com/jira.php" -X POST \
--data "action=request_reboot" \
--data "token=" \
--data "id="


Jira/Request_PXEboot


HTTP Method - POST


ParameterRequiredType Value/defaultDescription
action    *        stringrequest_PXEbootMain action - Open RHR to boot the server from PXE. This request is required during the reinstall process when the server without remote control unit should be booted from PXE to start the reinstall process.
token     *        string              Your session token
id     *        int              Your server ID

curl -s "https://invapi.hostkey.com/jira.php" -X POST \
--data "action=request_PXEboot" \
--data "token=" \
--data "id="


Jira/Request_kvm


HTTP Method - POST


ParameterRequiredType Value/defaultDescription
action    *        stringrequest_kvmMain action - Open RHR to connect IP KVM to the server. The duty shift will connect the IP KVM device to the server
token     *        string              Your session token
id     *        int              Your server ID
curl -s "https://invapi.hostkey.com/jira.php" -X POST \
--data "action=request_kvm" \
--data "token=" \
--data "id="


Jira/Request_check


HTTP Method - POST


ParameterRequiredType Value/defaultDescription
action    *        stringrequest_checkMain action - Open RHR to check and load the server into OS. The duty shift will check the server and try to bring it back online.
token     *        string              Your session token
id     *        int              Your server ID
curl -s "https://invapi.hostkey.com/jira.php" -X POST \
--data "action=request_check" \
--data "token=" \
--data "id="


Tags: