Anxible points for those who want to introduce Ansible

This is my first participation in the Advent Calendar. It's jerky. ((((； ﾟ Д ﾟ)))) Gakugaku Bull Bull

Ansible that can be started relatively softly in the provisioning framework But if you're a Dev, you need to persuade Ops to get started. In such a case, I would like to introduce some of the tricks that can be humbled by introducing Ansible.

Target person

I want to introduce a recently popular provisioning framework! !! How is it?

However, that is often disliked by the person in charge of infrastructure.

Well, for people who don't usually write programs

"You can write a program and automate it !!"

Even if I argue

(＇Ε＇) Fun

I feel like

"I already manage it with kickstart" "The installation procedure has already been shelled."

Well, there is always a backlash against new things. I understand. It should be painful at first to learn new things even though you are busy with your daily work.

Here are some tips for introducing Ansible to such people.

[Part 1] Installation only needs to be done on the Host side! !! !!

This is a difference from Chef.

Chef targets

• Host side
• Guest side

Both require Chef installation (Ruby and Gem) You don't need Ansible.

Depending on where you work, even one middleware installation is for the infrastructure

(ﾟ Д ﾟ) Gol'!! What do you do with things that aren't necessary for the production environment? !! !!

There is a place to get angry.

But the basic concept of Ansible is

Good luck with SSH! !!

is.

Why if it ’s a place that seems to get angry

"There is a convenient tool that can be used in the production environment without putting any middleware, but ぉ ぉ ぉ ぉ ぉ"

Let's say it while ((((; ﾟ Д ﾟ)))) jerky bull bull.

[Part 2] The document is simple

Documents are simpler than Chef !!

Chef isn't the only one who has a hard time finding documentation! !!

But Ansible

Documentation is simple

This is in the missionary activity

"I don't have much to remember. ぉ ぉ ぉ ぉ

Let's say it while ((((; ﾟ Д ﾟ)))) jerky bull bull.

[Part 3] You can start for the time being

For Chef's recent epidemic, use the source from the opscode-cookbooks repository. It seems to be fashionable, but (I tried and was frustrated on the way) You can see it if you look at the source

• It feels pretty apt. .. .. (Oh, just me ...)
• You have to follow the definition of attibute a lot. .. .. ..

It takes some time to understand and master the contents of the cookbook, which is easy to frustrate at first.

• Not applicable unless you use the opscode source. However, since the purpose is to introduce Ansible, let's lie down (･ д ･).

Ansible doesn't have such a trend, so it feels like you can write freely.

So

"It's easy to call for the time being."

Let's say it while ((((; ﾟ Д ﾟ)))) jerky bull bull.

(I don't understand what I want to say ...)

[Part 4] About 5000 units can be connected.

Introduction to Ansible ...? It was written that about 5000 units can be used per 35 pages. (I haven't verified it myself)

I think that it is a limited place to handle the number of units of this scale, so

"I can manage about 5000 units at the same time."

Let's say it while ((((; ﾟ Д ﾟ)))) jerky bull bull.

Finally

I like the loose and fluffy feeling, and even people who can not use python (I can not use it) can introduce it relatively easily Ansible 。 here we go,

When do you argue?

"Now!" (Old ...)