#268 Orchestration API
Closed: Won't fix 2 years ago by aday. Opened 3 years ago by aday.

As we've discussed how to improve the story for managed Workstation deployments, one proposal that's been raised is ensuring that we have an API for orchestration.


Can you elaborate on what you mean by orchestration? Running commands across multiple systems?

Maybe @ngompa can provide some details of what he had in mind.

We discussed this at today's working group meeting, and it's clear that there's a few aspects to it.

There are two potential aspects to an orchestration API:

  1. Reporting - for things like compliance with security policies, status of software updates and versions, etc
  2. Performing actions on the system, like changing settings or configuration

An initial action towards 1 would be to package and include osquery.

The other bigger question is what any future orchestration API would talk to. Options might include Cockpit, Ansible, something from the IoT space, or Microsoft Intune.

@ngompa said that he'd package osquery - setting pending-action for that.

Metadata Update from @aday:
- Issue untagged with: meeting-request
- Issue tagged with: pending-action

3 years ago

By the way, here are a couple of examples of OSQuery based systems:

Honestly I have no idea what this would look like. @ngompa could you elaborate more here please?

Is osquery packaging still WIP?

Metadata Update from @catanzaro:
- Issue assigned to ngompa

2 years ago

We discussed this ticket during today's meeting, and didn't feel that the working group can carry it forward. If someone wants to package osquery then they are free to do so.

Metadata Update from @aday:
- Issue close_status updated to: Won't fix
- Issue status updated to: Closed (was: Open)

2 years ago

Log in to comment on this ticket.

Metadata