Thanassis Zografos
-- description --
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
My name is Thanassis Zografos
I sysadmin @imgzine
I own a company; Ultraweb4U
Earned a living using VB6 (do not say a word)
and i love ... ansible
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
Developers develop
Status quo
Sys Admins administer
Users use
Managers manage
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
Things change...watch out !!
DevOps is coming to an
IT {{ schema }}
near you!!
coming soon...
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
DevOps
is a term for a group of concepts that,
while not all new,
have catalyzed into a movement
and is rapidly spreading throughout the technical community.
They say about it:
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
Born of the need to improve IT service delivery agility,
the DevOps movement
emphasizes communication, collaboration and integration between
software developers
and
IT operations
what it does
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
DevOps
is a series of
actions, changes, procedures, and tools
that make
operations and development engineers
participate together
in the entire service lifecycle,
from design
through the development process
to production support.
in other words
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
When developers begin
to think of infrastructure as part of their application
When developers choose stability and performance as normal procedures.
When sysadmins work tightly with developers to understand modern application methodologies
When procedures are enforced in order to communicate
in other words
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
When tools help the cause and
do not overrun it
so what ?
When tools are used
then...
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
You are a step
"May the force be with you"
closer into
understanding and practising
DevOps
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
What DevOps is not
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
Next steps
Ok I see that
but
what can the tools do for me ?
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
Things we do for love...apps
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
Things we do for love...apps
use the cloud or use baremetal
have the ability to change providers
deliver infrastructure fast and safely
allow this not to bottleneck your pipeline
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
Things we do for love...apps
running a “/usr/sbin/reboot” command
against tens, hundreds, or thousands of servers
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
Things we do for love...apps
manage your environment uniformely
describe your infra and build it
do that fast
do it again
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
Things we do for love...apps
enforce security across the board
implement changes securely
never miss upgrades
be compliant
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
Things we do for love...apps
repeat deployments
reliable deployments
simple methods
easy to maintain
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
Things we do for love...apps
update often
zero downtime
multi step, push based methodology
gain control and keep it that way
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
The TOOLS
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
The TOOLS too
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
The TOOLS more too
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
ooooh no ... more tools
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
The TOOLS more too
It is not about the tools...
Focus on why and how..
Use best practices.
Try this at home
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
The fight of the century
Ansible vs Puppet vs Chef vs Salt vs ...
There can not be only one !!
I like Ansible ...
you must choose what you like
choose the one that fits your project best
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
Ansible
SSH based, no clients no servers
Easy learning, YAML syntax
Playbook structure simple
Register variables for later tasks
No pulling ... just push
Performance upgrades in later versions
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
Ansible
Simple Playbook structure
---
- hosts: all
tasks:
- shell: echo "hello world"
helloworld.yml
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
Ansible
Simple Playbook structure
ansible-playbook -i "localhost" -c local helloworld.yml
execute it like this
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
Ansible
PLAY [all] *********
GATHERING FACTS *********
ok: [localhost]
TASK: [shell echo "hello world"] ********* changed: [localhost]
PLAY RECAP *********
localhost : ok=2 changed=1 unreachable=0 failed=0
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
Ansible
Even simpler Ansible script
ansible localhost -m shell -a 'echo hello world'
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
Thanassis Zografos | tzografos@gmail.com | DevStaff.gr
By Thanassis Zografos
from concept to movement to implementation