Parallels / Parallels/prl-devops-service

[PBI] Disk space sync and other config changes

Open
#403 0 comments 0 reactions 2 assignees View on GitHub

@sai-kumar-peddireddy is already working on this.

Since Mar 11, 2026.

pbi
Dominant language
Go
Stars
27
Forks
8
Avg merge
3h 13m
Merged PRs (30d)
4

Description

Description

We have a complex system for caching virtual machines in the host, we use logic to understand what we have and if we can create what we want to create. This requires some of our systems to keep an eye when something changes and emit that change for the orchestrator or UI.
The things we need to track, that change frequently are:

  • Disk Space available on the cache destination (this can be a external disk)
  • Disk Space on the default parallels destination for root (this will be a new thing that we were not tracking
  • Number of running macOS vms

On some of these it needs to be tracked also when other parts change, like vm state

User Story

As a user I want to have fully sync information about my host and it's capabilities

Acceptance Criteria
  • We have a new go routine that periodically checks the disk free space for the cache folder
  • We have a new go routine that periodically checks the disk free space for the default Parallels Location
  • We have a new message being sent through the event emitter with the changes, even if they are the same
  • We have a new endpoint to ask for disk space in real time for a specific user
  • We have updated the orchestrator to listen to these messages and update the internal database, for disk and number of macOS vms running
  • We have updated the orchestrator host selection to query in real time what is the disk space for each host and the target user
Definition of Done
  • Code implemented following best practices.
  • Unit tests written and passing.
  • Code reviewed and approved.
  • Merged into the main branch.
  • Documentation updated (if applicable).
  • Deployed to staging/production environment.
Assumptions and Constraints

No response

Dependencies

No response

Additional Notes

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.