Network Automation - NANOG

2y ago
15 Views
2 Downloads
2.44 MB
23 Pages
Last View : 26d ago
Last Download : 2m ago
Upload by : Baylee Stein
Transcription

1Network Automation:Do I Need Expensive Vendor Tools To DoMeaningful Automation?P. MooreNANOG 72February 20, 2018

Agenda Orchestration Domains An Onramp To Automation Open Source Tools Use Cases Considered Case Studies Conclusions2

3Orchestration DomainsIT & OSSSystemsChangeManagement Service OrderManagement WFOperational ModelsService ManagementService StandardsDeviceTurn UpServicev1, v2, v3 Service ModelsServiceService LifecycleDeviceDay 0, Day 1 TemplatesDeviceDevice LifecycleConfig StandardsConfig DriftandCompliance

Domains Build Upon Each Other4. ServicesServices– Model-based ServiceManagement3. Policy– Model-based Policy Management2. Maintenance– Leverage Device Management toautomate MOPsPolicyMaintenance1. Device (Foundational)– Configuration ManagementDevice4

5Domains Build Upon Each OtherAutomation LevelYANGOpenStackVMWare CloudsStage 3Service & PolicyLifecycleStage 2OpenConfigStage 1Day 0, Day 1 TemplatesStage 0Manual / ScriptCLI/ScriptsVNF – VMsOrchestrationModelsMANOStage 4VNF – Cloud NativeService LifecycleKubernetesDockerService & PolicyManagementStage 5Device LifecycleYAMLOperations ActivitiesDeviceImagesTOSCAData Model

Automation Onramp Address this on 3 fronts:– People: who will own network automation?– Process: define how you will manage the automationwork– Platform: define the tools you will use Define your use cases thoroughly – “It is ALLabout the use case!” Crawl Walk Run – start simple and expand “Evolve and Accelerate!”6

7AUTOMATION CAPABILITIESEvolve then sModelsWorkflowPlaybooksRunbooksTIME

PeopleWho will own network automation? Dedicated Group? Not necessary unless you are looking to put avery formal program in placeRoles Required:– Network Automation Lead – owns the automation efforts and worksto remove roadblocks with other departments, vendors, etc.– Automation Designer – defines the work to be done, tools to use,workflow/steps of automation, and acts as technical lead– Engineer – works with the Designer to build the automation– Subject Matter Experts (SME) – provides knowledge in specifictechnology areas All roles may be filled by a single person in some cases, or may be4 or more people in larger operations8

Process: The Automation FactoryDefine how you will manage the automation work Submission of automation requests Prioritization of which efforts to undertake Execution of automation efforts9

PlatformDefine the tools you will use Use tools you already have Leverage open source tools– Ansible & AWX– OpenDaylight, ONAP, etc.– Puppet, Chef, Salt, etc. Leverage vendors where the value makes sense10

Examples: Tools Ansible, Salt, Chef, Puppet, OpenDaylight– Playbook scripting– YAML, YANG, NETCONF AWX, Tower, ONAP– Playbook Management– Workflow Bitbucket, Github, etc.– Playbook versioning– Config versioning (including diff)11

Use Cases for Examples Config Management– Backup– Config Diff MOP Automation– Sub interface turn up– OS Upgrade12

Examples: Tool ArchitectureAWX provides GUI based: Simple Workflow Playbook Management Job Management Simple InventoryAWXBitbucketPlaybooksConfigsAnsible is the executionengine underneath AWXto communicate withdevicesAnsibleDevice13Bitbucket manages: Playbooks Configs

Example: Config BackupLeveragingBitbucket: Repository forconfigs History ofchanges to configs Ability to viewprevious configs Ability to see diffsbetween currentversion andprevious versions14

15Example: Config DiffDiff examples showingitems removed fromconfig, as well as insertedor changed

Sub-interface Turn Up: PlaybookYour Playbooks should be: Variablized for reusepurposes Specific to a use case Broken into smallerexecutable “chunks” –even if you could combinemore functions into thesingle playbook – forreuse purposes16

Sub-interface Turn Up: Job TemplateAWX allows for: Definition of Templatesfor jobs Management ofcredentials for networkaccess Management of simpleinventory of devices17

Sub-interface Turn Up: WorkflowPost-ChecksPort Turn UpFalloutRollbackPre-ChecksFallout ActionUpdateSystems18

Device OS Upgrade: PlaybookExample of a Playbook for OS Upgrade: This Playbook leverages the NTC-Ansible modulethat can be found at: https://github.com/networktocode/ntcansible The example Playbook, and more detail, can befound at: des-with-ansible/19

Extensible Architecture20OSS & OtherNetwork Automation PlatformAPIsOrchestrators(NFV, DataCenter, ibleDevicesControllers(ODL, Contrail,etc.)

More Sophisticated WorkflowMore advanced automationplatforms allow for: Sophisticated workflows Cross tool workflows (e.g.Ansible, Puppet, Chef,Cisco NSO, etc.) Custom forms and appsto enable more complexautomations21

22Questions?

References Network to Code Slack Channel: https://networktocode.herokuapp.com/ Network To Code Ansible e Automating IOS Upgrades with ice-upgrades-with-ansible/23

Feb 20, 2018 · – Network Automation Lead – owns the automation efforts and works to remove roadblocks with other departments, vendors, etc. – Automation Designer – defines the work to be done, tools to use, workflow/steps of automation, and acts as technical lead – Engineer – works w

Related Documents:

Network automation at scale Mircea Ulinic Cloudflare, London NANOG 69 Washington, D.C. February 2017 1 Up and running in 60 minutes

Automation Journey! Reporting Most network engineers begin their automation journey by producing some simple reporting software. It is low-risk, has a positive useful impact, and a good introduction to network scripting and the many libraries that support network automation. 2

you can control how automation is deployed, and gain auditable knowledge about automation sources and outcomes. You can also use Red Hat Ansible Network Automation, a bundled offering tailored for network automation tasks. Read the Network automation for everyone e-book to learn more about Red Hat Ansible Network Automation. HOW TO USE THIS E-BOOK

programmable logic controller, is important for industrial engineer. Factory automation mainly covers; Machine level automation, Production line or work cell automation, Shop floor automation, and Plant level automation. The present manual focus on the 1st level of factory automation e.g. machine automation level. It provides an introduction .

Network Automation 101 Ivan Pepelnjak (ip@ipSpace.net) Network Architect . Lack of programming skills Lack of reliable automation tools and programmatic interfaces . NetworkAutomation 101 Network Programmability 101 Network Automation Tools Network Automation Use Cases.

CA Workload Automation Agent for Windows (CA WA Agent for Windows) CA Workload Automation Agent for z/OS (CA WA Agent for z/OS) CA Workload Automation CA 7 Edition (formerly named CA Workload Automation SE) CA Workload Automation ESP Edition (formerly named CA Workload Automation EE) CA Workload Control Center (CA WCC) Contact CA Technologies

NANOG 2006 13 Differentiated Services Model DiffServ Architecture – RFC 2475 Scales well with large flows through aggregation Creates a means for traffic conditioning (TC) Defines per-hop behavior (PHB) Edge nodes perform TC – Allows core routers to do more important processing tasks Tough to predict end-to

How to Transform your Basic Blues Riffs One of the features that makes the blues so fun to play is that the basic structure of a standard blues progression (the so-called ‘twelve bar’) isn’t all that complex. This simplicity makes this structure perfect to ‘embellish’ the chords and riffs we play. There are a lot of options to use these embellishments, but let’s first start with .