Embed Size (px)
Citation preview
ChatOps Making complex processes accessible
Marian Knotek
2
ChatOps• What is ChatOps• Benefits of ChatOps• How it works• Use Case – Employee Onboarding• Use Case – Third Party access • Whats Next
3
Who’s heard of ChatOps?
4MULTI-TASKING
5
@hubot deploy APPLICATION to PRODUCTION
6
What is ChatOps• The natural evolution to Instant Messaging
• Makes complex processes accessible to everyday users
• The chat window enables the breakdown of silos, everyone can see the actions taking place
7
What is ChatOps• Principle : Make the chat smart by automating task via
a scriptable chat bot or hidden logic.
• From day-to-day tasks to application deployment, If it can be scripted it can be automated.
8http://www.statista.com/statistics/258749/most-popular-global-mobile-messenger-apps/
January 2016
9
Benefits of ChatOps• Giving access for non-technical personnel to complete
technical tasks
• Removes bottlenecks
• One of the lesser known benefits for DevOps
10
Benefits of ChatOps• Creates Transparency
• Increases Speed
• Easily accessible – who doesn’t check their phones at least once every hour!
11
How it works?• A number of different variations
• One of the most popular setups is using Hubot and Slack (both free!)
• Other integrations could include HipChat, Jabber, IRC, Yammer etc.
12
How it works?
13
How it works?
and many more….
14
Use Case – Employee OnBoarding
15
Employee OnBoarding• In a DevOps organisation many new tools, processes
and people are added frequently.
• Every time a new employee joined we would have to set up Exchange, Slack, Confluence etc..
• This process involved many users with different privileges and a total elapsed time around 3 hours
16
Employee OnBoarding - Process• Review of our processes
• Analysis of tools and integrations
• Implemented a subset
• Next steps and improvements
17
Employee OnBoarding - Results
18
Employee OnBoarding - Benefits• Time saved to on board new employees
• Enabled all users to do complex tasks
• Learning!
• Innovate – eat our own dog food!
19
Use Case – Third Party Access
20
Third Party Access• We provide customers access to dedicated AWS
environments
• There was a need to stop/start when needed
• Needed to keep cost low as these instances were large
• Did not want a operations engineer to manage something so simple
21
Third Party Access - Results
22
Third Party Access - Benefits• Setup access control so users would only have access to
their own regions
• Starting or stopping instances become almost instant
• Provides access to external customers to our internal systems without the need to provide passwords or complex setup
23
What’s Next?• Expand our ChatOps capabilities, automate more back
office tasks
• Enable the dynamic creation/destruction of AWS instances
• Promote and further educate others in the world of ChatOps
24
Want to try for yourself?• We have a monthly DevOps Playground meetup in
London which gives users Hands On DevOps experience
• Try implementing a ChatOps solution yourself with our step-by-step guide on GitHub:
• https://github.com/ForestTechnologiesLtd/Devops-Playground-Chatops-Intro
25
The potential is limitless!
26
Summary • ChatOps is a practice which can enable a greater level
of collaboration
• Enable ease of use for every user
• The integrations to every day tasks is limitless
27
28
“Failure is an option here. If things are not failing, you are not innovating enough.” – Elon Musk
