spcl/serverless-benchmarks

Cleaning up inactive resources

Open

#209 opened on Jul 10, 2024

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Python (99 forks)auto 404
good first issue

Repository metrics

Stars
 (196 stars)
PR merge metrics
 (PR metrics pending)

Description

SeBS keeps a list of cached cloud resources. However, the cache entries can become stale and invalid - this primarily applies to local deployment, where containers will be easily removed. Right now, a cached but removed container will throw an exception and force users to manually fix cache entries. We should be able to do it automatically.

  • Detect old containers and reject them, issuing a warning.
  • Add option to sebs resources to clean up local containers.
  • Add option to sebs resources to look for and stop remove orphaned containers, e.g., Azure CLI after crash; a complete killswitch.

Contributor guide

Research direction
Investigate how SeBS manages cached cloud resources and container lifecycles. Look into using container runtime APIs (e.g., Docker SDK) to detect stale containers and implement automated cleanup. Add CLI subcommands under `sebs resources` for removal and orphaned container detection.
Tech stack
python
Domain
backenddevopscloud
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitPythonDocker
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70