3 ms·

This is ansible for people who like Python. It's kind of sad because I feel I've invested 5 years into Ansible but now Michael releases something equally impre

This is ansible for people who like Python. It's kind of sad because I feel I've invested 5 years into Ansible but now Michael releases something equally impressive seemingly based on experiences and lessons learned while building ansible. So it's very hard not to just abandon Ansible and go with this new shiny tool.

jvehent 8y ago
They are just tools. People will come up with better ones every other year, and we'll abandon the old stuff. That's ok, components should be replaceable without having to reinvent the whole thing.
- dvtrn 8y ago
  That's ok, components should be replaceable without having to reinvent the whole thing. A fine, admirable and accurate (IMO) mindset. Things get weird when recruiters find out about these new tools and suddenly we're having that time honored discussion about how 'tech hiring is broken' because the people screening resumes don't realize OpsMop hasn't been out for 4 years and no one has 4 years experience with OpsMop. Everyone scrambles to learn OpsMops-so they can get a job where OpsMop ends up being abandoned and the DevOps team goes back to ansible, other teams start adding it to their tool chains because someone got hired who fiddled with it once and becomes an OpsMop house, a few engineers get very good at it, realize they can probably write a better version, three years later someone's posted "Show HN: OpsBroom" to the front page. Repeat.
mpdehaan2 8y ago
I suspect people will probably adopt it if they like it mostly for new projects. We still do have a lot of modules to write yet, so if you are interested in that, stop by talk.msphere.io - I'm open to a lot of enhancements there, but also want to keep it somewhat controlled. A lot of the early adoption is no doubt going to be folks doing CM-based builds for images (EC2, docker, whatever), where everything remains pretty disconnected. A mid-way adoption stage might be using opsmop to run existing ansible content, though ... that's really pointing towards wanting to add something like rsync, which is easy, but... I need to think about that a little bit.
nineteen999 8y ago
> So it's very hard not to just abandon Ansible and go with this new shiny tool. Huh? No it's not, not yet. It's clearly marked as alpha software.
- INTPenis 8y ago
  I'd say it's already ready to be adopted by some personal or PoC project. And I'm finding the Python DSL very attractive in theory. At least I'm assuming I'll be able to use it just like I use Python. So I'm not restricted by opsmop if I want to lookup secrets in secrets management API of my choice for example. Or connect the inventory methods to whatever asset mgmt API I might be using. Possible with Ansible too of course but using Python as DSL gets rid of the entire necessity of ansiblelib and following along with its API.

jvehent 8y ago

They are just tools. People will come up with better ones every other year, and we'll abandon the old stuff. That's ok, components should be replaceable without having to reinvent the whole thing.

dvtrn 8y ago
That's ok, components should be replaceable without having to reinvent the whole thing. A fine, admirable and accurate (IMO) mindset. Things get weird when recruiters find out about these new tools and suddenly we're having that time honored discussion about how 'tech hiring is broken' because the people screening resumes don't realize OpsMop hasn't been out for 4 years and no one has 4 years experience with OpsMop. Everyone scrambles to learn OpsMops-so they can get a job where OpsMop ends up being abandoned and the DevOps team goes back to ansible, other teams start adding it to their tool chains because someone got hired who fiddled with it once and becomes an OpsMop house, a few engineers get very good at it, realize they can probably write a better version, three years later someone's posted "Show HN: OpsBroom" to the front page. Repeat.

mpdehaan2 8y ago

I suspect people will probably adopt it if they like it mostly for new projects. We still do have a lot of modules to write yet, so if you are interested in that, stop by talk.msphere.io - I'm open to a lot of enhancements there, but also want to keep it somewhat controlled. A lot of the early adoption is no doubt going to be folks doing CM-based builds for images (EC2, docker, whatever), where everything remains pretty disconnected. A mid-way adoption stage might be using opsmop to run existing ansible content, though ... that's really pointing towards wanting to add something like rsync, which is easy, but... I need to think about that a little bit.

nineteen999 8y ago

> So it's very hard not to just abandon Ansible and go with this new shiny tool. Huh? No it's not, not yet. It's clearly marked as alpha software.

INTPenis 8y ago
I'd say it's already ready to be adopted by some personal or PoC project. And I'm finding the Python DSL very attractive in theory. At least I'm assuming I'll be able to use it just like I use Python. So I'm not restricted by opsmop if I want to lookup secrets in secrets management API of my choice for example. Or connect the inventory methods to whatever asset mgmt API I might be using. Possible with Ansible too of course but using Python as DSL gets rid of the entire necessity of ansiblelib and following along with its API.