Skip to content

Log Insight 4.0: Supported Deployment API

Log Insight 4.0 includes more supported APIs. Read on to learn more!
li-logo

Deployment APIs

Deployment APIs are now fully supported. Just like in the UI, you have two options:

1. Start New Deployment

The new API can only be used on a freshly deployed LI instance.

IMPORTANT: You must use port 9543 with the request (not 443)

POST /api/v1/deployment/new
Authorization: Bearer {session_id}
Content-type: application/json
{
  "user": {
     "userName": "admin",
     "password": "Password123!",
     "email": "[email protected]" # optional
   }
}

2. Join an Existing Cluster

If you are looking to join a freshly deployed LI instance to an existing cluster then you can use the join API.

IMPORTANT: You must use port 9543 with the request (not 443)

POST /api/v1/deployment/join
Authorization: Bearer {session_id}
Content-type: application/json
{
  "masterFQDN": "li.example.com"
}

After you issue a join request, you then must leverage the approve API on the master node to accept the request.

POST /api/v1/deployment/approve
Authorization: Bearer {session_id}
Content-type: application/json
{
  "workerAddress": "10.0.0.124",
  "workerPort": 16520,
  "workerToken": "85867eeb-3461-4dff-9294-e60f69467ab1",
  "approved": true
}

Checking Status

In addition to the deployment APIs, you can also check the status of the deployment.

POST /api/v1/deployment/waitUntilStarted

A 200 HTTP status request means success, while a 500 means not yet or some kind of failure.

Documentation

As always, the latest API documentation is available here.

© 2016, Steve Flanders. All rights reserved.

Published inVMware

Be First to Comment

Leave a Reply

Your email address will not be published. Required fields are marked *