Not sure if I should break these up, the first one is the one I plan on working on, and the others are ideas for whomever.

File Uploading

I worked on this last hackathon, but there was not a consensus on the methods. Since then @ktbyers has a demo here: https://github.com/ktbyers/napalm-ios/tree/file_copy

My plan for the hackathon is to finally work on this.

Documentation

Documentation could always be updated and it is a great place to start if you do not have a ton of programming experience.

Config Replace/Merge Methods

What goes on "under the hood" is not well understood to the audience abroad. It would be great to have a manual example of what is happening. As an example, show archive config differences <base_file> <new_file> and show common pitfalls associated.

Driver Overview

Build out https://napalm.readthedocs.io/en/latest/support/index.html#general-support-matrix to include the backend connection mechanism and additional caveats.

Writing Output of Commands/Offline mode

I think it would be helpful to be able to save the configuration of the command output (api or ssh), to be usable later. Once that is done, it would be equally helpful to run in an offline mode.

This has been brought up here: napalm-automation/napalm-base#296 but there has not been final consensus on what the final method should be. (would be good to define this)

Normalize Interface

I currently do this in post-processing, but would be nice to have an option to return an normalized interface. This is essentially what I do: https://github.com/itdependsnetworks/Scripts/blob/master/normalize_interface/normalize_interface.py

Supported Getters

Always good to update the supported getters: https://napalm.readthedocs.io/en/latest/support/index.html#getters-support-matrix

Anywhere there is an X, a method is missing, and could use an update.

Supported Getters

Always good to update the supported getters: https://napalm.readthedocs.io/en/latest/support/index.html#getters-support-matrix

Anywhere there is an X, a method is missing, and could use an update.

I want to work on implementing a web interface to NAPALM (and netmiko too).
It can be a showcase of napalm for network engineers who are not familiar with python / ansible.

What I will use: Flask, SQLalchemy, Bootstrap, jQuery and maybe some other javascript libraries if need be.

Main functionnalities:

• a web page to manage devices.
  Device = IP address + operating system + username + password (credentials to log in to the device) and optionally, hostname + secret password.
  A device can be created from a form manually, or by importing an excel file that contains those data, or by importing a .csv file.
  Devices can be deleted as well.

• a web page for sending script with netmiko
  The user can choose a driver, choose the global_delay_factor, and a protocol (SSH or telnet).
  Then, he writes the script in a text area and the script is sent to the device. A script can be a Jinja2 template, and it will be possible for the user to import a .yaml file to turn the j2 template into a real script.

• a web page for napalm getters
  the user selects a device and one or more getters, the request is sent to the device and the result is displayed in the webinterface by pretty printing the dictionnary.

• a web page for napalm configuration functions
  just like with netmiko, the user can write a script (possibly a j2 template along with a yaml file) and send it to the device by using configure_merge or configure_replace. It will also be possible to rollback.

• a web page to configure a "napalm daemon", that will give the possibility to do certain things on a regular basis, for instance retrieve the configuration of the device every day, or retrieve a given set of getters every hour and store the result somewhere, that sort of things.

the project will be available here: https://github.com/afourmy/e-napalm (I started two days ago as the whole things takes a few days)

Any comment / feedback / ideas on how to improve it or what else can be done is more than welcome !

Note: it won't be finished before Monday as I don't have access to my lab this we, which I need to test it on real devices.

Create a parser nxos configs to yang models. Starting with the interface model

relates to #9

• I created a web interface to Netmiko and NAPALM: https://github.com/afourmy/e-napalm

• I updated the model for get_interfaces to support MTU, and added MTU support to IOS and NXOS in napalm-automation/napalm#529 and napalm-automation/napalm#539, both of which were merged into the dedicated feature branch

Write a proxy service that implements a northbound grpc API and leverages on napalm-yang as southbound API to interact with the network.

Note: Probably too big of a project but would be cool to have some POC working. Also, I might write this one in golang* if I find an easy way to leverage napalm-yang from a go application.

* Reasons for golang are: better coroutines support, better grpc/protobuf support, I like it more than python.

Writing Output of Commands/Offline mode

I think it would be helpful to be able to save the configuration of the command output (api or ssh), to be usable later. Once that is done, it would be equally helpful to run in an offline mode.

This has been brought up here: napalm-automation/napalm-base#296 but there has not been final consensus on what the final method should be. (would be good to define this)

napalm-ansible documentation

Automatically generated configuration for the napalm-ansible modules which gets presented at the NAPALM ReadTheDocs site https://napalm.readthedocs.io

URL: https://napalm.readthedocs.io/en/latest/integrations/ansible/modules/index.html (Accessible once the PRs are merged)

PR:

• napalm-automation/napalm#535
• napalm-automation/napalm-ansible#106

Social:

• Twitter: networklore
• GitHub: @ogenstad
• Blog: https://networklore.com/

Google seems to have woken up with https://github.com/google/textfsm and that project is now more active than https://github.com/jonathanslenders/textfsm.

Perhaps NAPALM should move to the original module instead.

As you probably already knows napalm-yang is a framework to translate native configuration from a device to openconfig models and viceversa. Some examples:

• ios native config to interfaces model: https://github.com/napalm-automation/napalm-yang/blob/develop/napalm_yang/mappings/ios/parsers/config/openconfig-interfaces/interfaces.yaml
• interfaces model to native ios: https://github.com/napalm-automation/napalm-yang/blob/develop/napalm_yang/mappings/ios/translators/openconfig-interfaces/interfaces.yaml

There are plenty of models/vendors to implement so if you want to work on any of those just shout :D

https://napalm-automation.net/hackathon-2017-summary/

So, here are the candidate, just add a comment with the corresponding emoji to cast your vote:

• 👍 afourmy worked on e-napalm an awesome web UI for napalm and netmiko. I totally recommend this one.
• 💯 ogenstad worked on automating the process of turning ansible "docstrings" into actual documentation. You can see the result here
• 🔢 tcaiazza started working on a napalm-yang parser for NXOS. It's still WIP but I am sure he will finish it soon ;)
• 🥇 ktbyers started working on a testing environment to test config operations. Testing these operations has always been difficult so having this environment is certainly going to be useful.
• 🍆 itdependsnetworks worked on many things, most notably on bringing a set of helper functions to standardize interface names across commands.
• ✋ dbarrosop built a POC for an automation framework built on python to be used in python. You can find the project here

File Uploading

I worked on this last hackathon, but there was not a consensus on the methods. Since then @ktbyers has a demo here: https://github.com/ktbyers/napalm-ios/tree/file_copy

My plan for the hackathon is to finally work on this.

All of the modules in https://github.com/napalm-automation/napalm-ansible have documentation in the same way that the modules within Ansible does.

However unlike Ansible the documentation isn't available online outside of the source code. For the hackathon we could use this information to publish the documentation on https://napalm.readthedocs.io/en/latest/.

For this to happen we need to create tests to validate format of the current documentation and create a hook in Travis so that a new release of the Ansible modules would trigger a new build of the documentation for the https://github.com/napalm-automation/napalm repo.

Brigade

An automation framework in python for python

URL: https://github.com/napalm-automation/brigade
PR: none

Started napalm-yang nxos parser

PR: napalm-automation/napalm-yang#111

Normalize Interface

I currently do this in post-processing, but would be nice to have an option to return an normalized interface. This is essentially what I do: https://github.com/itdependsnetworks/Scripts/blob/master/normalize_interface/normalize_interface.py

Documentation

Documentation could always be updated and it is a great place to start if you do not have a ton of programming experience.

Config Replace/Merge Methods

What goes on "under the hood" is not well understood to the audience abroad. It would be great to have a manual example of what is happening. As an example, show archive config differences <base_file> <new_file> and show common pitfalls associated.

Driver Overview

Build out https://napalm.readthedocs.io/en/latest/support/index.html#general-support-matrix to include the backend connection mechanism and additional caveats.

This is something I'm interested in as it would be useful in my shop napalm-automation/napalm#525

I would need to get my head around napalm-yang first though I think. Ideally we should use the OpenConfig YANG model for IS-IS