No Downtime Deployment of Packs
Open
Nobody has claimed this yet.
feature
status:under discussion
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
Background
One of the goals i have for our StackStorm deployment is to implement Continuous Delivery (CD) of our custom packs without having to schedule downtime of our StackStorm servers.
Requirements
- Upgrades can be performed without taking downtime
- No race conditions exist that could cause errors of ongoing workings during a deployment
- External systems, that may be polling for status/completion of ongoing workflows, should not be affected
- Packs may need to deploy/update virtualenvs
- Pack configs may need to be loaded
- Key/value pairs may need to be added to the datastore
- Custom content may need to be installed on the box (deploy additional non-pack content)
- Custom scripts may need to be run on the box (install system level dependencies)
Conclusion
This issue is to simply start the conversation and brainstorm ideas of how to implement such a feature/process.
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 entry points and is framed as a brainstorming discussion. Start by mapping StackStorm pack deployment, virtualenv, configuration, datastore, and workflow lifecycle processes; a complete proposal would need to define a safe no-downtime process and validate each listed deployment requirement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100