spcl / spcl/serverless-benchmarks
IaaC-based deployment in the cloud
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 199
- Forks
- 105
- PR merge metrics
- No merged PRs in 30d
Description
Currently, we deploy all resources manually. However, we will likely need to deploy more than functions + immediate infrastructure, such as:
- VMs/containers for Redis-based handling of tracing data in SeBS-Flow.
- Caches and databases for state management and data in more complex workloads.
- Systems like Redis or ZeroMQ for communication.
- Kubernetes for running open-source platforms.
We should consider OpenTufu, and the deployment should be reproducible and pinned to specific versions. Our requirements are: reproducibility and portability; we want to support a wide range of clouds - AWS, Azure, GCP, Huawei, Oracle, Alibaba.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or deployment entry points; start by inventorying the current manual deployment process and the resources required by SeBS-Flow and complex workloads. Define the supported cloud scope, version-pinning approach, and reproducibility checks; done means deployments are reproducible and portable across the agreed providers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, azure, gcp, kubernetes, redis
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100