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

feat: move runner scaling to the provisioner #3529

Merged
merged 3 commits into from
Nov 29, 2024

Conversation

stuartwdouglas
Copy link
Collaborator

@stuartwdouglas stuartwdouglas commented Nov 26, 2024

fixes #3483

This was referenced Nov 26, 2024
@stuartwdouglas stuartwdouglas added the run-all A PR with this label will run the full set of CI jobs in the PR rather than in the merge queue label Nov 27, 2024
@stuartwdouglas stuartwdouglas force-pushed the stuartwdouglas/provision-runners branch 15 times, most recently from 06b5022 to 0b0f22d Compare November 28, 2024 02:07
@stuartwdouglas stuartwdouglas marked this pull request as ready for review November 28, 2024 02:12
@stuartwdouglas stuartwdouglas requested review from wesbillman and removed request for a team November 28, 2024 02:12
@stuartwdouglas stuartwdouglas force-pushed the stuartwdouglas/provision-runners branch 3 times, most recently from 0aa9ae0 to ba315f2 Compare November 28, 2024 06:12
@stuartwdouglas stuartwdouglas force-pushed the stuartwdouglas/provision-runners branch 5 times, most recently from d36b8f2 to ae351a3 Compare November 28, 2024 23:12
@@ -149,6 +150,8 @@ func replaceOutputs(to []*provproto.Resource, from []*provproto.Resource) error
}
r.Subscription.Output = subscriptionFrom.Subscription.Output
}
case *provproto.Resource_Runner:
// Ignore
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why ignoring here? Should we not just set the outpus?

@@ -273,9 +276,18 @@ func ExtractResources(msg *ftlv1.CreateDeploymentRequest) (*ResourceGraph, error
to: dep.ResourceId,
})
}

runnerResource := &provisioner.Resource{
ResourceId: module.GetName() + "-runner",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we use deployment id here instead? I think that would fit better to the given model, given that each deployment has a separate runner as a resource.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually we don't really seem to have the deployment name here?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, yeah. I think it currently created after the provisioning, which is annoying. I suppose that is fine for now, though it breaks the model a bit.

@stuartwdouglas stuartwdouglas force-pushed the stuartwdouglas/provision-runners branch 2 times, most recently from 074deb9 to 7eb038e Compare November 29, 2024 00:10
@stuartwdouglas stuartwdouglas merged commit cecacf5 into main Nov 29, 2024
95 checks passed
@stuartwdouglas stuartwdouglas deleted the stuartwdouglas/provision-runners branch November 29, 2024 01:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
run-all A PR with this label will run the full set of CI jobs in the PR rather than in the merge queue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Refactor k8s provisioning to be a provisioner
2 participants