Adding a pair of Proxy and Execution modules for managing Cisco Nexus switches via the NX-API #48541
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mirceaulinic
force-pushed
the
nxos-api-mod
branch
4 times, most recently
from
bdb7944
to
075cfcf
Compare
mirceaulinic
force-pushed
the
nxos-api-mod
branch
from
075cfcf
to
e69877e
Compare
rallytime
approved these changes
Jul 16, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Adds the initial version of two new modules: one Proxy and one Execution module for managing Cisco Nexus switches via via NX-API. Well, the NX-API is not the most reliable API in this world, but it's there and it can be used up to some extent.
The execution module is flexible enough to execute the commands on the (remote) device without necessarily requiring to be running inside the
nxos_apiProxy Minion. This goes well with its SSH-based counterpart https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.nxos.html providing good coverage for NXOS switches.The most important side of these modules is the fact that it has no external dependencies, as everything is HTTP-based. Not only that it's easier to get it up and running, but that also means it's straight forward to have it running under a regular Minion: on Nexus switches it is possible to install the Salt Minion under a container running in a what-is-called OAC (why keep it simple when can you make it awkward, right?). Anyway, the idea is that the user only has to execute
yum install salt-minionin that OAC, then can start using:salt-call --local nxos_api.show 'show bgp sessions'without any further headache.If, for whatever reasons, the user can't / is not allowed / the hardware does not support the OAC thing, can always fallback to using the
nxos_apiProxy instead.