Network: Meraki

Ansible modules for managing Meraki equipment

News

Ansible v2.7 now ships with 11 Meraki modules !
Feedback is very much appreciated.

Community

Name	GitHub (+ IRC)	Role	Affiliation
Kevin Breit	kbreit / mrproper	Lead
Dag Wieers	dagwieers / dag	Reviewer	Independent

Add yourself to this list as a Reviewer (help review PRs) or as a Member (discuss issues/roadmap).

Feedback

I am very much looking for feedback on how you use, or would use, these modules. Please submit issues on the Ansible New Issues page if you would like to see functionality changed or enhanced.

Open Issues

Modules do not respect Meraki’s rate limiting of 5 requests per second, per organization

API Issues

Using HTTP (no SSL) turns PUT/POST/DELETE in to GET requests (on purpose?)
API does not enforce Organizations to have unique names
API idempotency issues
- Requires POST for creating and PUT (id) for updating
- DELETE is not idempotent, only works when exists
VLANs are not enabled by default on a network. Ansible 2.8 or 2.9 will have support for enabling and disabling VLANs via the API. In the meantime, a network must have VLANs enabled via the Dashboard web interface.

Public Modules

Action Plan

2.8

Static route
Syslog server configuration
Enable/disable VLANs on network

Future

Develop Meraki connection plugin (uncertain)
Support for forthcoming BulkAction API, if appropriate
Create modules for the following categories:
- Clients
MX VPN firewall
MX cellular firewall
Network VPN settings
Wireless health facts
BLE
Webhook HTTP configuration
Service access controls
Add support for new features
- Network alert configuration

Integration Tests

Each Meraki module includes a suite of integration tests which help validate module functionality. Running the test is easy once you do a couple of setup steps.

Setup your development environment as described at the Ansible Module Development web page. If you've already done this, run $ . venv/bin/activate && . hacking/env-setup from the root directory of the Ansible code base.
Rename the template file located at /test/integration/inventory.networking.template to /test/integration/inventory.networking.
Edit the inventory.networking file with the following variables:

auth_key - Authentication key as provided by the Meraki Dashboard. Required for all modules.
test_org_name - Name of organization which your tests will be conducted in. Required for most modules.
test_org_id - ID number of the organization which your tests will be conducted in. Required for some modules. Use the meraki_organization module to find the ID for the organization as this information isn't available in the dashboard.
test_net_name - Name of the network which your tests will be conducted in. Required for most modules.
test_net_id - ID number of the network which your tests will be conducted in. Required for some modules. Use the meraki_network module to find the ID of the network as this information isn't available in the dashboard.