Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replaces VirtualMachineFleetService with VirtualMachineFleet #7

Merged
merged 2 commits into from
May 8, 2023

Conversation

simonbs
Copy link
Contributor

@simonbs simonbs commented Apr 26, 2023

This PR simplifies the management of the fleet of virtual machines as a step in the right direction to fix #4. Specifically the PR makes the following changes:

  1. Deletes VirtualMachineFleetService.
  2. Deletes VirtualMachineFleetFactory.
  3. Deletes FleetParticipatingVirtualMachine.
  4. Rewrites VirtualMachineFleet to handle the need of all three above.

The VirtualMachineFleet creates a number of tasks that matches the number of virtual machines that the app has been configured to start. Each task will sequentially run a virtual machine until the task is cancelled, which will happen either when the user manually stops the fleet of virtual machines or the app is quit.

This provides for much simpler logic that is easier to debug.

@simonbs simonbs self-assigned this Apr 26, 2023
@simonbs
Copy link
Contributor Author

simonbs commented May 8, 2023

These changes seem to have resolved #4 for us.

@simonbs simonbs merged commit 418baed into main May 8, 2023
@simonbs simonbs deleted the bugfix/virtual-machine-is-not-started branch May 8, 2023 20:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Sometimes the second virtual machine is not started
1 participant