Page MenuHomePhabricator

Use the same logic in "bin/drydock lease" and LeaseUpdateWorker to identify candidate blueprints
ClosedPublic

Authored by epriestley on May 3 2022, 9:28 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Mar 23, 7:58 PM
Unknown Object (File)
Tue, Mar 19, 5:19 PM
Unknown Object (File)
Sat, Mar 16, 11:47 AM
Unknown Object (File)
Sun, Mar 10, 4:49 PM
Unknown Object (File)
Feb 13 2024, 8:20 PM
Unknown Object (File)
Feb 12 2024, 1:25 AM
Unknown Object (File)
Feb 4 2024, 1:51 AM
Unknown Object (File)
Feb 4 2024, 1:51 AM
Subscribers
Restricted Owners Package

Details

Summary

Ref T13676. Currently, "bin/drydock lease" just creates a lease that permits any blueprint.

To prepare for "use specific blueprint X", unify the logic between this workflow and LeaseUpdateWorker so we select only blueprints which at least have coarse compatibility (e.g., if we're leasing a host, only select enabled blueprints of classes that can allocate hosts).

Test Plan

Used bin/drydock lease to try to lease a nonsense type, got sensible error. Leased a host.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable