This version is compatible with:
- Puppet Enterprise 2018.1.x, 2017.3.x, 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
- Puppet >= 4.7.0 < 6.0.0
Start using this module
- Setup - The basics of getting started with napalm
- Usage - Configuration options and additional functionality
- Release Notes
This module contains tasks that wrap the Network Automation and Programmability Abstraction Layer with Multivendor (NAPALM) framework.
The target machine running the tasks needs to be a Linux machine. It needs to have the following packages installed before you can run the task:
This module includes a
install_dependencies task that will install all the above requirements for you.
The very basic steps needed for a user to get the module up and running. This can include setup steps, if necessary, or it can be an example of the most basic use of the module.
This module contains 4 tasks:
- install_dependencies - this will install the system depdendencies
- call - make function calls to NAPALM
- configure - configure network devices using a supplied config file
- validate - validate network device configuration using a validation file
Do not run the task on the networking device itself. These tasks are meant to be run on a jump host. These tasks use virtualenv to create an isolated python environment. It will also put some files in the /tmp folder.
An example plan using all the tasks is included.
0.1.0 Initial Release
What are tasks?
Modules can contain tasks that take action outside of a desired state managed by Puppet. It’s perfect for troubleshooting or deploying one-off changes, distributing scripts to run across your infrastructure, or automating changes that need to happen in a particular order as part of an application deployment.
Tasks in this module release
Install napalm dependencies
What are plans?
Modules can contain plans that take action outside of a desired state managed by Puppet. It’s perfect for troubleshooting or deploying one-off changes, distributing scripts to run across your infrastructure, or automating changes that need to happen in a particular order as part of an application deployment.