3 ms·

I really want to use ansible (currently using salt), but I'm still waiting for the apt_repository pr[0] to get merged. [0] https://github.com/ansible/ansible/p

by dschep 13y ago

I really want to use ansible (currently using salt), but I'm still waiting for the apt_repository pr[0] to get merged. [0] https://github.com/ansible/ansible/pull/3783 https://github.com/ansible/ansible/pull/3783

borplk 13y ago
can you elaborate on why you are moving away form salt?
- BozeWolf 13y ago
  Would like to hear that as well. In my current project, vagrant is being provisioned with ansible. We chose ansible because it's easy to extend and its written in python. This project runs on freelancers, so its important the next django developer understands the provisioning system and custom modules as well. For some reason I tend to prefer the idea of being more "abstract" like Salt is. So my private project (server+vagrant) is being provisioned with Salt. Like borplk i'm interested in opinions of people which have experience with both.
  - mpdehaan2 13y ago
    I'd be interested in hearing what you mean about being more abstract, but I think you'll like the simplicity angle. In general, we build things with the goal of readability by diverse levels of skill and busy-ness -- to make things readable like a book and easy so you don't forget something in Ansible 6 months after you wrote it, and so you can dive in, get something done, and dive out. We've got some IT managers saying they can tell employees to do X, Y, and Z, and not knowing Ansible, can still read the playbook. So, it should be fine for your freelancer case I'm sure. This is also why there is no graph dependency system, just handlers and notifies, so you can read things top to bottom.
- liyanage 13y ago
  Same here, I'd be interested to hear why you're moving in that direction. I heard great things about Ansible and would love to try it, but in some of the environments I work in, using GPL software (especially v3) is not possible (in other environments it is perfectly fine). Because I'd like to use the same system in all environments I work in, and because I strongly prefer a Python-based system, I'll probably go with Salt. If there were a different licensing option than GPL, I'd look into Ansible first, based on all the comments I read about it so far.
  - mixmastamyk 13y ago
    Could you give a few details on why gpl software is not acceptable in those environments? I understand the part about GPL libraries forcing it on linked applications. However, not sure why it matters regarding stand-alone apps.
mpdehaan2 13y ago
Looks like this got merged an hour ago :) (Thanks James!)
bostonvaulter2 13y ago
That was only opened 6 days ago. Seems premature to be complaining about it.

by dschep 13y ago

borplk 13y ago

can you elaborate on why you are moving away form salt?

BozeWolf 13y ago
Would like to hear that as well. In my current project, vagrant is being provisioned with ansible. We chose ansible because it's easy to extend and its written in python. This project runs on freelancers, so its important the next django developer understands the provisioning system and custom modules as well. For some reason I tend to prefer the idea of being more "abstract" like Salt is. So my private project (server+vagrant) is being provisioned with Salt. Like borplk i'm interested in opinions of people which have experience with both.
- mpdehaan2 13y ago
  I'd be interested in hearing what you mean about being more abstract, but I think you'll like the simplicity angle. In general, we build things with the goal of readability by diverse levels of skill and busy-ness -- to make things readable like a book and easy so you don't forget something in Ansible 6 months after you wrote it, and so you can dive in, get something done, and dive out. We've got some IT managers saying they can tell employees to do X, Y, and Z, and not knowing Ansible, can still read the playbook. So, it should be fine for your freelancer case I'm sure. This is also why there is no graph dependency system, just handlers and notifies, so you can read things top to bottom.
liyanage 13y ago
Same here, I'd be interested to hear why you're moving in that direction. I heard great things about Ansible and would love to try it, but in some of the environments I work in, using GPL software (especially v3) is not possible (in other environments it is perfectly fine). Because I'd like to use the same system in all environments I work in, and because I strongly prefer a Python-based system, I'll probably go with Salt. If there were a different licensing option than GPL, I'd look into Ansible first, based on all the comments I read about it so far.
- mixmastamyk 13y ago
  Could you give a few details on why gpl software is not acceptable in those environments? I understand the part about GPL libraries forcing it on linked applications. However, not sure why it matters regarding stand-alone apps.

mpdehaan2 13y ago

Looks like this got merged an hour ago :) (Thanks James!)

bostonvaulter2 13y ago

That was only opened 6 days ago. Seems premature to be complaining about it.