51–56 of 56 posts
Earlier quoted context omitted.
http://www.nizkor.org/features/fallacies/straw-man.html
http://en.wikipedia.org/wiki/Non_sequitur_(logic)
Earlier quoted context omitted.
How do you create that initial AMI? CMs make answering that question simple. AMIs are nice - but they're merely snapshots of an end product. Being able to get to that end product in a repeatable, idempotant and self-documenting fashion is just as nice. So is being able to create a virtual image on your own machine with the same end product. FWIW, Vagrant lets you specify an AMI in its box description, so you get the…
>How do you create that initial AMI? CMs make answering that question simple. No, they make it slower and more complex. The idea being that after you have built a config, future clones will be easier. But you already get a better solution just setting up a server and then making an AMI from it. Cfengine and friends offer quite literally zero benefits for this sort of scenario.
Second, if you should move from AWS to (as an example of a second popular PAAS provider) Rackspace, how do you recreate that image? If you want to create a local VM to perform development on, how do you do that?
Now, if I were limited to just using one CMS, I might agree with you. There are some really obtuse ones out there that require a lot of learning. I don't think Ansible falls into this category. You're not writing python, you're not writing in some tool specific DSL, you're writing lists of packages, to be installed in-order. Simple and straightforward.
- yum: name=nginx
sudo yum -y install nginxEarlier quoted context omitted.
http://en.wikipedia.org/wiki/Non_sequitur_(logic)
Seriously? Read the thread. You responded to "Using config tools isn't helpful" with "but mine is python!!1". Nobody cares, it is a completely irrelevant detail. I simply said ruby because the two popular options are both ruby. It still applies to fucking cfengine, it doesn't matter the specific tool.
Earlier quoted context omitted.
>How do you create that initial AMI? CMs make answering that question simple. No, they make it slower and more complex. The idea being that after you have built a config, future clones will be easier. But you already get a better solution just setting up a server and then making an AMI from it. Cfengine and friends offer quite literally zero benefits for this sort of scenario.
You missed two points. How did you create that first image? Exactly what versions of packages, packages, configurations, etc were installed? Being unable to answer that question will hurt you more in the long run than you might expect. Second, if you should move from AWS to (as an example of a second popular PAAS provider) Rackspace, how do you recreate that image? If you want to create a local VM to perform developm…
Earlier quoted context omitted.
Seriously? Read the thread. You responded to "Using config tools isn't helpful" with "but mine is python!!1". Nobody cares, it is a completely irrelevant detail. I simply said ruby because the two popular options are both ruby. It still applies to fucking cfengine, it doesn't matter the specific tool.
The Ruby-based CMSes are very, very different from tools like Ansible. That's an important issue when you're bashing the entire range, seemingly without any thought for the situations that make them useful and without knowledge of other options than Puppet/Chef.
No they are not. I've probably been doing system administration longer than you have been alive. I've used everything from cfengine to salt. They all cause more problems than they solve.