![Page 1: Journey Map Approach - ansible.com ATL Slide... · Increment 1 Increment 1 Little to no network automation with Ansible Team has little to no exposure to Ansible playbook No configuration](https://reader034.vdocuments.us/reader034/viewer/2022050217/5f62cd1a72f4a91bfa014d79/html5/thumbnails/1.jpg)
Journey Map ApproachTo Implementing Network Automation with Ansible
Piyush PatelManaging Architect, Automation PracticeWalter BentleySenior Manager, Automation Practice
![Page 2: Journey Map Approach - ansible.com ATL Slide... · Increment 1 Increment 1 Little to no network automation with Ansible Team has little to no exposure to Ansible playbook No configuration](https://reader034.vdocuments.us/reader034/viewer/2022050217/5f62cd1a72f4a91bfa014d79/html5/thumbnails/2.jpg)
Share your automation story
1. How did you get started with Ansible?
2. How long have you been using it?
3. What's your favorite thing to do when you Ansible?
![Page 3: Journey Map Approach - ansible.com ATL Slide... · Increment 1 Increment 1 Little to no network automation with Ansible Team has little to no exposure to Ansible playbook No configuration](https://reader034.vdocuments.us/reader034/viewer/2022050217/5f62cd1a72f4a91bfa014d79/html5/thumbnails/3.jpg)
This WILL be an interactive session…
Please register here to take part in the interactive parts of the session:
PollEV.com/walterbentley
![Page 4: Journey Map Approach - ansible.com ATL Slide... · Increment 1 Increment 1 Little to no network automation with Ansible Team has little to no exposure to Ansible playbook No configuration](https://reader034.vdocuments.us/reader034/viewer/2022050217/5f62cd1a72f4a91bfa014d79/html5/thumbnails/4.jpg)
AGENDA
● Identify the Ask
● Embrace the Need for a Framework
● What is the MVP?
● Identify What Phase You Are In
![Page 5: Journey Map Approach - ansible.com ATL Slide... · Increment 1 Increment 1 Little to no network automation with Ansible Team has little to no exposure to Ansible playbook No configuration](https://reader034.vdocuments.us/reader034/viewer/2022050217/5f62cd1a72f4a91bfa014d79/html5/thumbnails/5.jpg)
Identify the Ask
![Page 6: Journey Map Approach - ansible.com ATL Slide... · Increment 1 Increment 1 Little to no network automation with Ansible Team has little to no exposure to Ansible playbook No configuration](https://reader034.vdocuments.us/reader034/viewer/2022050217/5f62cd1a72f4a91bfa014d79/html5/thumbnails/6.jpg)
IDENTIFY THE ASK
Why are we here? What are the
business drivers and what does success
look like?
Define the Strategy
End State, Current State & MVP
ECM
Discussion focused on how automation will impact people,
process and technology
Impact of Automation
![Page 7: Journey Map Approach - ansible.com ATL Slide... · Increment 1 Increment 1 Little to no network automation with Ansible Team has little to no exposure to Ansible playbook No configuration](https://reader034.vdocuments.us/reader034/viewer/2022050217/5f62cd1a72f4a91bfa014d79/html5/thumbnails/7.jpg)
DEFINE THE STRATEGY
● Current business & IT landscape● Ongoing and planned projects● Business objectives● Focus / Problem areas● Constraints● Security Considerations
![Page 8: Journey Map Approach - ansible.com ATL Slide... · Increment 1 Increment 1 Little to no network automation with Ansible Team has little to no exposure to Ansible playbook No configuration](https://reader034.vdocuments.us/reader034/viewer/2022050217/5f62cd1a72f4a91bfa014d79/html5/thumbnails/8.jpg)
END STATE, CURRENT STATE AND MVP
What is the desired END STATE?
What does the CURRENT STATE look
like?
Determine what an acceptable MVP
looks like
![Page 9: Journey Map Approach - ansible.com ATL Slide... · Increment 1 Increment 1 Little to no network automation with Ansible Team has little to no exposure to Ansible playbook No configuration](https://reader034.vdocuments.us/reader034/viewer/2022050217/5f62cd1a72f4a91bfa014d79/html5/thumbnails/9.jpg)
IMPACT OF AUTOMATION
![Page 10: Journey Map Approach - ansible.com ATL Slide... · Increment 1 Increment 1 Little to no network automation with Ansible Team has little to no exposure to Ansible playbook No configuration](https://reader034.vdocuments.us/reader034/viewer/2022050217/5f62cd1a72f4a91bfa014d79/html5/thumbnails/10.jpg)
Embrace the Need
![Page 11: Journey Map Approach - ansible.com ATL Slide... · Increment 1 Increment 1 Little to no network automation with Ansible Team has little to no exposure to Ansible playbook No configuration](https://reader034.vdocuments.us/reader034/viewer/2022050217/5f62cd1a72f4a91bfa014d79/html5/thumbnails/11.jpg)
THE JOURNEY MAPPrepare Initiate Expand Accelerate Optimize
Build out framework to
deliver network automation at
scale
Pilot with identified use
cases that would be MVP
Craft automation content to
support standard networking operations
Expand automation
adoption and engage the community
Refine processes in order to drive
increased network service efficiency.
Increment 1 Increment 2 Increment 3 Increment 4 Increment 5
![Page 12: Journey Map Approach - ansible.com ATL Slide... · Increment 1 Increment 1 Little to no network automation with Ansible Team has little to no exposure to Ansible playbook No configuration](https://reader034.vdocuments.us/reader034/viewer/2022050217/5f62cd1a72f4a91bfa014d79/html5/thumbnails/12.jpg)
PREPAREDesign Sprint 1* Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6
Project Management
Network assessment Configuration management
and role definition Workflow automation
Tool integration
Mentoring & Documentation
![Page 13: Journey Map Approach - ansible.com ATL Slide... · Increment 1 Increment 1 Little to no network automation with Ansible Team has little to no exposure to Ansible playbook No configuration](https://reader034.vdocuments.us/reader034/viewer/2022050217/5f62cd1a72f4a91bfa014d79/html5/thumbnails/13.jpg)
What is the MVP?
![Page 14: Journey Map Approach - ansible.com ATL Slide... · Increment 1 Increment 1 Little to no network automation with Ansible Team has little to no exposure to Ansible playbook No configuration](https://reader034.vdocuments.us/reader034/viewer/2022050217/5f62cd1a72f4a91bfa014d79/html5/thumbnails/14.jpg)
MVP (Most Valuable Player)Minimum Viable Product
Keywords:
MINIMUM means that the product is so bad, that nobody wants to use it
MINIMUM+VIABLE means it’s a mix between those two; minimum enough to
solve the users problem
VIABLE means that the product is fast, reliable, optimised, well designed
and looks professional
![Page 15: Journey Map Approach - ansible.com ATL Slide... · Increment 1 Increment 1 Little to no network automation with Ansible Team has little to no exposure to Ansible playbook No configuration](https://reader034.vdocuments.us/reader034/viewer/2022050217/5f62cd1a72f4a91bfa014d79/html5/thumbnails/15.jpg)
MVP for Network Automation
MVP should be quantifiable and measurable. Team should be able to reach MVP within a deterministic timeframe. For example,
In network automation, MVP could be a production ready ansible tower deployment, a model to implement management configuration of network devices. This model should be the single source of truth used to configure and check compliance against for a vendor-specific class of devices, such as Cisco IOS. This should be implemented in increments 1 and 2.
![Page 16: Journey Map Approach - ansible.com ATL Slide... · Increment 1 Increment 1 Little to no network automation with Ansible Team has little to no exposure to Ansible playbook No configuration](https://reader034.vdocuments.us/reader034/viewer/2022050217/5f62cd1a72f4a91bfa014d79/html5/thumbnails/16.jpg)
Identify What Phase
![Page 17: Journey Map Approach - ansible.com ATL Slide... · Increment 1 Increment 1 Little to no network automation with Ansible Team has little to no exposure to Ansible playbook No configuration](https://reader034.vdocuments.us/reader034/viewer/2022050217/5f62cd1a72f4a91bfa014d79/html5/thumbnails/17.jpg)
Prepare
Build out framework to
deliver network automation at
scale
Increment 1
Increment 1
● Little to no network automation with Ansible● Team has little to no exposure to Ansible playbook● No configuration management of network devices● No centralized source for network device information
Start your journey here if you have:
![Page 18: Journey Map Approach - ansible.com ATL Slide... · Increment 1 Increment 1 Little to no network automation with Ansible Team has little to no exposure to Ansible playbook No configuration](https://reader034.vdocuments.us/reader034/viewer/2022050217/5f62cd1a72f4a91bfa014d79/html5/thumbnails/18.jpg)
Initiate
Pilot with identified use
cases that would be MVP
Increment 2
Increment 2
● Some automation with Ansible playbooks● Team is familiar with Ansible playbook syntax and execution● No centralized repository for storing playbooks and artifacts● No templates for configuration
Start your journey here if you have:
![Page 19: Journey Map Approach - ansible.com ATL Slide... · Increment 1 Increment 1 Little to no network automation with Ansible Team has little to no exposure to Ansible playbook No configuration](https://reader034.vdocuments.us/reader034/viewer/2022050217/5f62cd1a72f4a91bfa014d79/html5/thumbnails/19.jpg)
Expand
Craft automation content to
support standard networking operations
Increment 3
Increment 3
● Template based configuration of devices, certain attributes● Devices organized by type and function● Use of inventory to capture device attributes that are part of
automation● Tiger team implementing network automation
Start your journey here if you have:
![Page 20: Journey Map Approach - ansible.com ATL Slide... · Increment 1 Increment 1 Little to no network automation with Ansible Team has little to no exposure to Ansible playbook No configuration](https://reader034.vdocuments.us/reader034/viewer/2022050217/5f62cd1a72f4a91bfa014d79/html5/thumbnails/20.jpg)
Increment 4Accelerate
Expand automation
adoption and engage the community
Increment 4
● Complete network device automation using Ansible● Integration with tools such as ticketing ● Use of CI/CD to migrate configuration changes from
Dev/Test to Production● Minimal configuration drift that can be remediated using
inventory sources
![Page 21: Journey Map Approach - ansible.com ATL Slide... · Increment 1 Increment 1 Little to no network automation with Ansible Team has little to no exposure to Ansible playbook No configuration](https://reader034.vdocuments.us/reader034/viewer/2022050217/5f62cd1a72f4a91bfa014d79/html5/thumbnails/21.jpg)
Increment 5Optimize
Refine processes in order to drive
increased network service efficiency.
Increment 5
● Tiger(COE) team using Ansible best practices and extending network automation to other teams
● Role based access for identified classes of automation users and developers
● Single source of truth implemented and utilized to eliminate configuration drift
![Page 22: Journey Map Approach - ansible.com ATL Slide... · Increment 1 Increment 1 Little to no network automation with Ansible Team has little to no exposure to Ansible playbook No configuration](https://reader034.vdocuments.us/reader034/viewer/2022050217/5f62cd1a72f4a91bfa014d79/html5/thumbnails/22.jpg)