workstation/tickets
13
0
Issues 25 Activity

Orchestration API #268

New issue
Closed
opened 2022-01-20 16:46:17 +00:00 by aday · 10 comments
aday commented 2022-01-20 16:46:17 +00:00
Owner
Copy link

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.

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.
otaylor commented 2022-01-20 17:04:48 +00:00
Contributor
Copy link

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

Can you elaborate on what you mean by orchestration? Running commands across multiple systems?
aday commented 2022-01-20 17:05:59 +00:00
Author
Owner
Copy link

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

Maybe @ngompa can provide some details of what he had in mind.
aday commented 2022-02-08 16:47:48 +00:00
Author
Owner
Copy link

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.

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.
aday commented 2022-02-09 17:23:28 +00:00
Author
Owner
Copy link

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

@ngompa said that he'd package osquery - setting pending-action for that.
aday commented 2022-02-09 17:23:28 +00:00
Author
Owner
Copy link

Metadata Update from @aday:

  • Issue untagged with: meeting-request
  • Issue tagged with: pending-action
**Metadata Update from @aday**: - Issue **un**tagged with: meeting-request - Issue tagged with: pending-action
ngompa commented 2022-03-01 01:41:05 +00:00
Owner
Copy link

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

By the way, here are a couple of examples of OSQuery based systems: * [Fleet](https://fleetdm.com/) * [Kolide](https://www.kolide.com/)
catanzaro commented 2023-01-11 21:57:07 +00:00
Owner
Copy link

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

Is osquery packaging still WIP?

Honestly I have no idea what this would look like. @ngompa could you elaborate more here please? Is osquery packaging still WIP?
catanzaro commented 2023-01-11 21:57:12 +00:00
Owner
Copy link

Metadata Update from @catanzaro:

  • Issue assigned to ngompa
**Metadata Update from @catanzaro**: - Issue assigned to ngompa
aday commented 2023-06-20 14:58:37 +00:00
Author
Owner
Copy link

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.

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.
aday commented 2023-06-20 14:58:38 +00:00
Author
Owner
Copy link

Metadata Update from @aday:

  • Issue close_status updated to: Won't fix
  • Issue status updated to: Closed (was: Open)
**Metadata Update from @aday**: - Issue close_status updated to: Won't fix - Issue status updated to: Closed (was: Open)
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
No results found.
Labels
Clear labels   
a11y

Issues related to Fedora GNOME accessibility

  
btrfs
  
Closed As
Can't fix
Closed with the reason of Can't fix

  
Closed As
Deferred to upstream
Closed with the reason of Deferred to upstream

  
Closed As
Fixed
Closed with the reason of Fixed

  
Closed As
Won't fix
Closed with the reason of Won't fix

  
default-apps

   
easyfix

Easy fixes for new contributors

  
experience

Issues related to the desktop experience

  
help-wanted

Volunteers wanted to help with this issue

  
installation

Issues related to the installer

  
meeting

For next Workstation working group meeting

  
meeting-request

Propose issue for a future meeting

  
nvidia

   
packaging

Requires packaging work

  
pending-action

Has an action that hasn't been completed

  
qa

Related to QA processes, infrastructure, policy. (Not for any issue which affects product quality.)

  
testing

Requires testing and validation

  
user-docs

Issues with the workstation user docs

  
wg-docs

Issues with the working group docs

  
wg-meta

For Workstation WG issues

No labels
a11y
btrfs
Closed As
Can't fix
Closed As
Deferred to upstream
Closed As
Fixed
Closed As
Won't fix
default-apps
easyfix
experience
help-wanted
installation
meeting
meeting-request
nvidia
packaging
pending-action
qa
testing
user-docs
wg-docs
wg-meta
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
workstation/tickets#268
No description provided.