#SALTSTACK CHANGE MINION NAME HOW TO#
#SALTSTACK CHANGE MINION NAME INSTALL#

#SALTSTACK CHANGE MINION NAME INSTALL#

install the latest Raspbian on an RPI from the -wheezy-raspbian image.

#SALTSTACK CHANGE MINION NAME HOW TO#

Interestingly enough, these junos state modules leverage the custom execution modules also.Īll in all, building some familiarity with the execution module will help you better understand the states that come with the minion and studying the execution modules in more detail will help you imagine how you can start writing you own custom execution modules and/or custom states to do things 100% your own way.The short version: How to get test.ping to work, after keys are -Added? And how to re-push a key if you -Deleted it from the master? When you get to writing states, the main thing you will use are the states that the Junos proxy minion comes with. Another way to see what is available is to check the execution module in github, right here.Īpart from applying the execution module functions directly like we have done here, the functions can be seen as ‘low-level’ building blocks. Using salt ar01-lab junos, you can see what other functions exists. Also note that we did not touch all execution module function. Add Salt’s 0MQ, and you have quite a powerful tool to instantly check what is going on in your network. Additionally, you can use them for ad-hoc information gathering leveraging CLI/RPCs you already know. First of all, they are great to play around with and will help you better understand the Junos proxy minion.

The execution module functions are great for several reasons. It gives some maturity to the proxy minion and it will give people that have worked with PyEZ a running start. I think it is pretty smart to tie the whole thing in with the PyEZ microframework. The proxy minion works really well and allows for a seamless interaction with the Juniper API. In this article we explored the Junos proxy minion and the functions that the junos execution module provides us with. The following Salt CLI command will render the template and apply show configuration system show system commit

Let’s take a different approach here and do everything in one go. Monitor of performing a rollback, we could have also used mit to commit the candidate configuration and make our changes take effect. To check the file we use for the proxy minion in our example, we use cat /srv/pillar/ar01_lab.sls monitor start interactive-commands | match interactive-commands ***Īug 11 20:13:55 ar01-lab mgd: UI_NETCONF_CMD: User 'admin' used NETCONF client to run command 'load-configuration action='set' format='text''Īug 11 20:14:00 ar01-lab mgd: UI_NETCONF_CMD: User 'admin' used NETCONF client to run command 'get-configuration compare='rollback' rollback='0' format='text''Īug 11 20:14:08 ar01-lab mgd: UI_NETCONF_CMD: User 'admin' used NETCONF client to run command 'commit-configuration check'Īug 11 20:14:16 ar01-lab mgd: UI_NETCONF_CMD: User 'admin' used NETCONF client to run command 'load-configuration compare='rollback' rollback='0'' Setting up the proxy minion requires that you create a file for the proxy minion where you specify the connection details. Sending a CLI command, issuing an RPC, changing the configuration, etc.īut before diving into all that, let’s get a proxy minion started first. These functions will enable you to get most of the basic things done. The proxy minion comes with an execution module that provides you several functions. The Junos proxy minion is leveraging PyEZ to communicate with the Junos API over NETCONF. This article is about the Junos proxy minion. When we want to have SaltStack control Juniper devices, we can choose from the following proxy minion software: netmiko, napalm or junos. In turn, the proxy minion controls a device through the API or through CLI commands. The proxy minion is a process that Salt controls as if it were a minion.

To enable SaltStack to control devices that cannot run standard salt-minion software, we turn to proxy minions.

Saltstack change minion name