Project

General

Profile

Idea #6429

Updated by Tom Clegg over 8 years ago

See [[Containers API]] and [[Crunch2 migration]] 

 For this initial implementation, focus on implementing and testing a minimal feature set with 
 * Access controls (e.g., users cannot modify Container records) 
 * Validations (e.g., container state cannot change from Completed to Queued; repositories and inputs must be readable by the submitter) 
 * Locking mechanism for use by scheduler 
 * Apply cascading effects of state changes 
 ** When a Container exits, cancel all active ContainerRequests that it initiated 
 ** When a ContainerRequest cancels, and this leaves a Container running without any active requests, cancel that container 

 Definition of "minimal Minimal feature set" TBD. Possibilities: set 
 * No container re-use: create a new Container to satisfy each ContainerRequest with @priority>0@. 
 * No support for expires_at, filters, container_count_max (but don't ignore them -- just reject submissions that specify anything but the one supported null/easy value for each respective feature) Tests 

Back