Provisioning

Question 1

What is provisioning?

Answer 1

Automatic configuration of a server.

Question 2

What criteria should a good provisioning script respect?

Answer 2

• Work from the first try.
• Work when launched several times.
• Be easy to understand, so be simple.

Question 3

What is the purpose of a provisioning script?

Answer 3

• Configure servers faster.
• Avoid human errors.
• Have a maintanable and reusable script.

Question 4

Where do we use a provisiong script?

Answer 4

On local VMs and remote servers hosting our applications.

Question 5

What is Ansible? Are there alternatives?

Answer 5

Ansible is software that automates software provisioning, configuration management, and application deployment. Basically: write code to configure servers. Existing alternatives: Puppet, Chef, Bash scripts…

Question 6

Why Ansible does not require any additional software to be installed on client computers?

Answer 6

Because Ansible communicates over normal SSH channels in order to retrieve information from remote machines, issue commands, and copy files.

Question 7

Which computers can be administered through Ansible?

Answer 7

Any computer (server) that has an SSH port exposed can be brought under Ansible’s configuration umbrella, regardless of what stage it is at in its life cycle.

Question 8

How does Ansible work?

Answer 8

Ansible works by configuring client machines from an computer with Ansible components installed and configured.

Question 9

How does Ansible interact?

Answer 9

Ansible can interact with clients through either command line tools or through its configuration scripts called Playbooks.

Question 10

How are written Ansible modules and configuration files?

Answer 10

• Modules can be written in any language and communicate in standard JSON.
• Configuration files are mainly written in the YAML data serialization format due to its expressive nature and its similarity to popular markup languages.

Question 11

What is the best way to install Ansible on Ubuntu 16.04?

Answer 11

• $ sudo apt-add-repository ppa:ansible/ansible
• $ sudo apt-get update
• $ sudo apt-get install ansible

Question 12

How does Ansible keep track of all the servers?

Answer 12

Through a hosts file (in /etc/ansible/hosts) that need to be set up before computers can communicate.

Question 13

How to configure the hosts file so that Ansible can communicate with the servers via ssh?

Answer 13

Write in etc/ansible/hosts:

[group_name]

[alias] ansible_host=[server_IP] ansible_port=[port_number] ansible_user=[user]

For Ansible > 2.2: add ansible_python_interpreter=/usr/bin/python3

Optionally: use group specific variables by creating the group_vars directory in etc/ansible and then creating files with the format:

etc/ansible/group_vars/[group_name]

Question 14

How to make sure that Ansible has a connection to its hosts?

Answer 14

• One host: $ ansible -m ping [server_alias]
• Multiple hosts: $ ansible -m ping [server_alias]:[server_alias]
• Group of hosts: $ ansible -m ping [group_name]
• All hosts: $ ansible -m ping all

Question 15

What are Ansible playbooks?

Answer 15

• Ansible playbooks are a way to send commands to remote computers in a scripted way. That is, you can configure entire complex environments by passing a script to one or more systems.
• Ansible playbooks are written in the YAML data serialization format.
• Each playbook contains one or more plays, which map hosts to a certain function. Ansible does this through something called tasks, which are basically module calls.

Question 16

What is the difference between a standard YAML file and an Ansible YAML file?

Answer 16

YAML allows multiple “documents” to exist in one file, each seperated by —, but Ansible only wants one per file, present at the top of the file.

Question 17

What are the characteristics of YAML files?

Answer 17

• YAML documents basically define a hierarchical tree structure with the containing elements further to the left.
• A document starts with —.
• YAML is very-sensitive to white-space:
  
  • Use only spaces.
  • The spacing should be consistent.
• Items that begin with a - are considered list items.
• Items with the format key: value operate as hashes or dictionaries.

Question 18

What are Ansible plays?

Answer 18

YAML items at the left-most level. Plays are groups of tasks performed on a certain set of hosts to allow them to fulfill the function you assign them.

Basic format:

• hosts: [hostname_or_group]

tasks:

• task 1
• task 2

Question 19

What is the structure of an Ansible task?

Answer 19

• name: [task_description]

[ansible_module]

[ansible_module]

…

Question 20

Simple description of the apt module.

Answer 20

​apt: pkg=[package] state=[state] update_cache=[true/false]

• [state] can be present.
• update-cache=true tells the remote computer to update its package cache prior to the state action.

Question 21

Simple description of the notify module.

Answer 21

The notify item can contain a list of references to handlers, which can perform certain functions when called from within a task.

Format:

notify:

• [handler_name]

Question 22

What are Ansible handlers?

Answer 22

• The “handlers” section exists at the same level as “hosts” and “tasks”.
• Handlers are tasks that only run when they have been told to by task that changes have occured on the client system.

Question 23

How to run an Ansible playbook?

Answer 23

• Only on the defined hosts:
  
  • $ ansible-playbook [playbook]
• Filtering to specific hosts:
  
  • $ ansible-playbook -l [host_subset] [playbook]
    *

Question 24

How to check whether an Ansible action was successful or not?

Answer 24

• Use the register module to register a task result (failure or success) in a variable that we can check later on.
• When using this functionality, we also have to tell Ansible to ignore errors for that task, otherwise it will abort the playbook execution in case of an error.
• Format:
• name: …

command

register: [var]

ignore_errors: True

• name: …

command

when: [var] | success
- name: …

command

when: [var] | failed

Question 25

How to execute a task or playbook as another user?

Answer 25

* Use "become", which can be set from play to task level, but is overridden by connection variables as they can be host specific. * become: true ==\> activite privilege escalation. * become\_user=[username] ==\> defines the user used for privilege escalation. Default is root. become\_user is useless if become is not set to true.