Future sprints¶

• Feature #17751: [arvados-dispatch-cloud] expose rate-limiting condition in metrics
  • help diagnose underutilized cluster resources / slow queue progress
• Bug #22967: "use of closed network connection" and "read: connection reset by peer" log messages from crunch-run while running processes with local dispatcher
  • reduce log spam / red herrings (note this is not just a local-dispatcher thing)
• Bug #21658: `arvados-client logs` shows no logs then exits zero
• Feature #21279: cloudtest command should test connectivity to crunch-run gateway
• Feature #21133: Add diagnostics checks for container log API
• Bug #20516: Diagnostics command should recommend using cloudtest to diagnose further if test container does not succeed
• Bug #20857: numerous errors "Cost cannot be modified in state 'Locked'"
• Feature #21599: _inspect/requests endpoint should reveal whether each request is queued or active
• Bug #21618: cloudtest should give up if test instance disappears from listing before probe succeeds
• Idea #21581: Crunch saves compute node journals to collections readable only by administrators
• Idea #21424: Way to run a diagnostic container that captures all system logs, not just Crunch's
• Idea #21542: Improved visibility on cloud instance (and maybe other resources?) quotas
• Bug #21527: lib/service Suite.TestRequestLimitsAndDumpRequests_Controller fails intermittently
• Feature #20220: Dispatcher uses live logs endpoint on crunch-run to fetch logs and store a backup locally
• Feature #18944: [controller] should log the user uuid used for the request
• Feature #18897: [go services] should log the uuid of the token used for each request (and if available, the uuid of the associated user)