junos_commit - Execute commit on device

Author:Rick Sherman, Juniper Networks


New in version 1.2.0.

Execute a Commit on a device running Junos independently of loading a configuration


parameter required default choices comments
check no None
    Do a commit check Can be used to confirm a `commit confirmed` without performing an actual commit
    comment no None
      Provide a comment to the commit of the configuration
      confirm no None
        Provide a confirm in minutes to the commit of the configuration
        host yes
          Set to {{ inventory_hostname }}
          logfile no None
            Path on the local server where the progress status is logged for debugging purposes
            mode no None
              mode of console connection (telnet/serial). If mode is not provided SSH connection is used.
              passwd no assumes ssh-key active
                Login password
                port no 830
                  port number to use when connecting to the device
                  ssh_private_key_file no None
                    This can be used if you need to provide a private key rather than loading the key into the ssh-key-ring/environment. if your ssh-key requires a password, then you must provide it via **passwd**
                    timeout no 0
                      Extend the NETCONF RPC timeout beyond the default value of 30 seconds. Set this value to accommodate commits that might take longer than the default timeout interval.
                      user no $USER
                        Login username


                        Requires junos-eznc >= 1.2.2


                        - junos_commit:
                           host: "{{ inventory_hostname }}"
                           comment="Non load commit"
                        # over console server connection using PyEZ >= 2.0
                        - name: junos commit
                            host={{ inventory_hostname }}
                            comment="commit with console connection via PyEZ"