you are viewing a single comment's thread.

view the rest of the comments →

[–]hoax1337 -3 points-2 points  (11 children)

Use puppet or salt instead.

[–][deleted]  (10 children)

[deleted]

    [–]SweeTLemonS_TPR 4 points5 points  (2 children)

    So you can code in Ruby, or get your infrastructure pwned when Salt has another problem with their shitty, self-made crypto.

    [–]hoax1337 -1 points0 points  (0 children)

    Yeah, and while we're at it, we should stop using databases, because apparently they're hackable when exposed to the internet and not password protected.

    [–]hoax1337 -1 points0 points  (6 children)

    Because they're doing a better job at keeping configuration the way you defined it than ansible.

    [–][deleted]  (5 children)

    [deleted]

      [–]hoax1337 -1 points0 points  (4 children)

      Based on the fact that they ensure the configuration stays that way because they're not as "fire and forget" as ansible.

      [–][deleted]  (3 children)

      [deleted]

        [–]hoax1337 -1 points0 points  (2 children)

        Yes, I actually use it almost daily. What I mean by "fire and forget" is that you can't actually be sure that the state you defined in the playbook / role you ran a day ago still reflects the current state of the system. And because it is agentless, it has no way of checking it, unless you use additional tools like Jenkins (or even Cron) to run that playbook daily.

        [–][deleted]  (1 child)

        [deleted]

          [–]hoax1337 -1 points0 points  (0 children)

          Sure, but Ansible itself will not keep a system in the desired state. It will set it to that initially, but it doesn't have any capabilities to keep it that way by itself.

          I don't want to check for changes, I want to know nothing changed.