Files
pipelines/docs/notes/android-target-pool-allocation.md
T

1.5 KiB
Raw Blame History

Android target pool allocation — 2026-10-18, phase one not activated

This item adds a reusable store contract only. Pool declarations are not activated in live jobs, runner handoff, server configuration, Android maps, shared documentation, or deployment.

Store.ConfigureResourcePool(ctx, protocol.ResourcePool) replaces a bounded pool declaration. Each member has a unique 1–128 byte resource key, an enabled flag, quarantine state, and at most 16 bounded ASCII-keyed metadata values (each value is at most 128 bytes). A pool has 1–32 explicit members. Invalid, empty, duplicate, unknown, or malformed declarations are rejected. Updating a pool never transfers a live owner; queued requests use the new declaration on the next eligible release.

Store.RequestResourcePool(ctx, pool, visit) atomically returns a lease for one free eligible concrete member, or a FIFO wait channel. The lease's Target contains only the concrete member and bounded non-secret metadata. Capability tokens remain private to the store and are never protocol/model metadata. Direct concrete-resource leases and pool leases share the owner table, so they cannot overlap. Disabled or quarantined members are skipped; if none are eligible, the request queues without inference. Release, cancellation, stale credentials, recovery, and restart retain the existing no-expiry semantics.

This is scheduler coordination only: no device probing, emulator creation, credentials, activation, or live job changes are included.