Every time I need to automate something and I look at these solutions it becomes clear that I can put together a Ruby script to handle it much faster than getting one of these automation solutions up and running.
I agree that writing a ruby script is tempting. Where I disagree with you is that, when you have an organisation of 100s of devs, these scripts become tech debt. You need to have standard operating procedures delivered via one platform, that's when rundeck et al plays an important role.
Never have been able to get management buy in for automation.
I even had one manager tell me that there was value in having someone do it manually instead of automatic, I suspect part of their pay or career progression was based on the size of their team.
Ex-Rundeck engineer here. Would be very interested to here why you initially dropped it and why you are thinking about picking it back up!
It was just that we weren't using Rundeck very effectively. I set it up so that others could run a few Ansible jobs, and so that a slack bot could fire off one of those jobs. The Slack API changed a few years later and our old bot completely broke and I couldn't get it working again without rewriting. As far as other people running them, nobody else seemed to use it. So when it came time to upgrade the EOL OS that was hosting Rundeck, I just shut it down.
But, now we have some Jenkins jobs that would benefit from being isolated from Ansible runs, so Rundeck might be a good way to run those.
https://github.com/StackStorm/st2/blob/master/ADOPTERS.md includes a few more examples and use cases with the links.
Oh thanks, somehow I looked right at that and didn't process the fact that it was annotated with case studies and conference talks.
One of the maintainers here and I second that.
Other options available:
- deb/rpm packages - Vagrant - Docker-compose - Ansible/Puppet - Kubernetes/Helm
...probably better idea to adveritse docker container, not everyone wants to have half-rotten corpse of python app spreading shit around your system forever (there is never an uninstall...) just to test something.
...or at least one that fucking works
I've tried to drop the check for distro only to be asked for fucking sudo which is like... WTF ?
zzz@hydra:~$ curl -sSL https://stackstorm.com/packages/install.sh | bash -s -- --user=st2admin --password=Ch@ngeMe *** Detected Distro is Debian *** *** Detected flavor bookworm *** Unsupported ubuntu codename bookworm. Please use 16.04 (xenial) or Ubuntu 18.04 (bionic) or Ubuntu 20.04 (focal) as base system!
curl|sh that downloads more curl|sh is also interesting choice.
zzz@hydra:/tmp$ ./install.sh --user=st2admin --password=Ch@ngeMe *** Detected Distro is Debian *** *** Detected flavor bookworm *** Downloading deployment script from: https://raw.githubusercontent.com/StackStorm/st2-packages/v3.8/scripts/st2bootstrap-deb.sh... Running deployment script for st2 ... OS specific script cmd: bash st2bootstrap-deb.sh --stable --user=st2admin --password=**** [sudo] password for zzz:
`curl | sh` "installs" are not a good look on any package, and should be dropped -- you are absolutely right -- there is never an "uninstall" process.
It's supporting a few OS platforms and require a clean server for installation: https://docs.stackstorm.com/install/system_requirements.html
Expect to get MongoDB, RabbitMQ and Redis installed as dependencies.
I wouldn't recommend it as a security tool
Works well for DevOps and SRE operations and like K8s, needs a whole team to run it
I've tried on clean account
It is curl|sh that also requires sudo
StackStorm was an open-core project with a paid enterprise offering on top of it, belonging to a single vendor. In 2019 the project was donated to the Linux Foundation as a neutral umbrella, also open-sourcing the enterprise features like RBAC, LDAP, UI Workflow Designer.
Today StackStorm has an open-source ecosysem with several partner companies (5) providing consulting, commercial support, custom solutions or training for the clients that may need it: https://stackstorm.com/partners/
These partners also contribute back to the core and help supporting the project together with the other maintainers.
Prefect and Apache Airflow defines logic in a pure Python code, while StackStorm uses a YAML-structured Workflow called Orquesta  supporting different logic patterns (parallel, merge, concurrency, join, retries, pause, ask, nested subworkflows, etc)  with Jinja and YAQL  support. YAQL is especially interesting one where Jinja is not enough.
There's also a bi-directional ChatOps framework you can tie with the workflows to make the experience more interactive.
So you can listen on events (could be a chat command) from 3rd party services, do some rule filtering & matching (all in YAML), and trigger workflows with the logic that runs actions in other tool(s) and service(s).
StackStorm has Exchange , - a collection of 100+ plugin integrations with different tools and services contributed and supported by community to make that building blocks juggling easier.
Interesting. I saw this tweet (https://twitter.com/RobustaDev/status/1595767655687913473) last night, and I'm not sure that the image of people falling out of an airplane is in particularly good taste. It put me off your company and product immediately.
One of the maintainers during EU late night here.
* The release management team is preparing the v3.8.0 release right now, - coming out soon next week.
* There are 15 Maintainers (https://github.com/StackStorm/st2/blob/master/OWNERS.md) in the Technical Steering Committee (TSC), a very diverse group, but I'd say only 1/3 or half are really active.
* There are monthly TSC meetings and we invite curious to join us: https://github.com/StackStorm/community/issues/33 (next meeting is on 6th Dec).
* Past Meetings: https://github.com/StackStorm/community/issues?q=is%3Aissue+...
* The project is under the neutral Linux Foundation umbrella with no single commercial owner, so probably why less marketing. We have blog/twitter/linkedin with the mostly engineering updates for engineers.
But I agree with the sentiment overall, - the development velocity could be higher and we definitely welcome new contributors and interested folks. The tool is written in Python if someone is willing to join, play with it and start contributing.
In what sense?
The repo linked here appears to have contributions merged in that last month and it has a bunch of active pull requests.