JCPA key terms

A property of an operation where applying it repeatedly produces the same end state as applying it once. Automation tools rely on this so reruns converge devices to the intended configuration without duplicating changes.

An approach where you describe the desired end state of a system rather than the step-by-step commands to reach it. The tool computes and applies whatever changes are needed to match that state.

An approach where you script the exact sequence of commands or actions to execute. It gives precise control but requires you to handle ordering, error checking, and repeat-run safety yourself.

The gradual divergence between a device's actual running configuration and the intended or source-controlled baseline. It typically results from manual changes, and automation is used to detect and correct it.

An authoritative repository or database holding the intended state of the network, such as device inventory, addressing, and policy. Automation reads from it so that generated configurations and audits share one consistent reference.

Managing network and compute infrastructure through machine-readable definition files kept in version control instead of manual CLI changes. It enables review, repeatability, testing, and rollback of infrastructure changes.

Core Python data structures: a list is an ordered, mutable sequence accessed by index; a dictionary is a collection of key-value pairs accessed by key. Both are heavily used to hold parsed device data and API responses.

The statement that loads a Python library or file so its functions and classes can be used. Automation scripts import libraries such as requests, lxml, or Junos PyEZ to gain their capabilities.

Using try, except, and related blocks to catch and respond to runtime errors instead of letting a script crash. In automation it allows graceful handling of timeouts, authentication failures, and unreachable devices.

Repeating a block of code over items such as a list of devices or interfaces. Automation scripts use loops to apply the same logic across many network elements without duplicating code.

Building text output by substituting values into a template string, for example with f-strings or the format method. It is commonly used to assemble CLI commands, URLs, and configuration snippets dynamically.

An interface style using HTTP methods such as GET, POST, PUT, PATCH, and DELETE on resource URLs, typically exchanging JSON or XML. Network devices and controllers expose REST APIs for programmatic configuration and monitoring.

A three-digit number in an HTTP response indicating the outcome, such as 200 for success, 401 for unauthorized, and 404 for not found. Automation code checks these codes to detect and handle failures.

A lightweight text data format built from objects (key-value pairs), arrays, strings, numbers, booleans, and null. It is the most common payload format for REST APIs and is easily parsed into Python dictionaries.

A markup format using nested elements with tags and attributes to represent structured data. NETCONF encodes its messages and configuration data in XML, and many legacy APIs also accept it.

A data modeling language that defines the structure, types, and constraints of configuration and state data for a device. Tools generate schemas and APIs from YANG models so changes can be validated before being applied.

A query syntax for selecting nodes within an XML document, for example by hierarchical path. It appears in NETCONF filters and in some XML-based APIs to narrow which data is returned.

A standards-based protocol that uses SSH transport and XML-encoded remote procedure calls to retrieve, edit, and validate device configuration. It supports candidate configurations and transactions, making changes more reliable than CLI scripting.

A protocol that maps YANG-modeled data onto HTTP methods and URLs, using JSON or XML payloads. It offers a REST-like alternative to NETCONF for reading and writing device configuration and state.

A working copy of device configuration that can be edited and validated before being committed to the active configuration. It allows changes to be staged and discarded without affecting running services.

A commit option that activates changes only if the change is explicitly confirmed within a time limit; otherwise the device automatically rolls back. It protects against configuration mistakes that could cut off management access.

A Python library for automating Junos devices, offering an object-oriented interface to retrieve configuration and operational data, load changes, and run remote procedure calls over NETCONF.

A YAML file describing an ordered set of tasks to run against managed hosts, often organized into roles. For network devices it typically runs on a control node and uses vendor-specific modules.

A declarative definition in Salt describing the desired state of a system, applied by the Salt master to managed minions. State files express outcomes and rely on the tool to determine required actions.

A structured list of network devices with attributes such as hostname, address, credentials reference, platform, and role. Automation tools and scripts read it to know which devices to target and how to connect.

A parameterized text file that generates device configuration by filling in variables for a specific device or role. Templating reduces duplication and keeps generated configurations consistent across the network.

A Python templating engine that supports variables, filters, conditionals, and loops inside text templates. It is widely used to render device configurations and is the default templating language in Ansible.

The rules determining which value wins when the same variable is defined in multiple places. Understanding it prevents unexpected rendered configurations when templates and inventories supply conflicting values.

Restoring a device or system to a previously known-good configuration or version after a failed or unwanted change. Automation platforms support it through stored configuration history or version-controlled baselines.

Streaming operational data from network devices to a collector at intervals or on change, rather than polling. It gives near-real-time visibility into interface, CPU, and flow metrics for monitoring and analysis.

A high-performance remote procedure call framework using HTTP/2 and protocol buffers. It is a common transport for model-driven telemetry and for programmatic interaction with network devices and controllers.

Automation triggered by a detected condition or message, such as a link-down syslog or telemetry threshold, rather than a fixed schedule. It shortens response time and can apply remediation automatically.

An HTTP callback that sends a payload to a configured URL when an event occurs. Automation platforms and chat tools use webhooks to notify or trigger workflows from external events.

A system such as Git that records changes to files over time, enabling history review, branching, and rollback. Automation code, templates, and inventories are stored in it so changes are auditable and reversible.

An automated sequence that builds, tests, and deploys changes after code is committed. For networks it can validate templates, run syntax and unit tests, and push approved configurations to devices.

Checking intended changes for syntax, policy, and impact before applying them to production. It includes rendering templates, linting, and simulation or lab testing to catch errors early.

Granting accounts and automation tools only the permissions needed for their tasks. It limits the blast radius of compromised credentials or faulty scripts and is a core security practice in automation.

Storing and retrieving credentials, keys, and tokens in a protected vault rather than hardcoding them in scripts or repositories. It supports rotation and auditing of sensitive automation access.

Assigning permissions according to a user's or system's role instead of individually. In network automation it restricts which devices and operations an account or tool can reach.

A limit on how long a client waits for a network connection or response before giving up. Proper timeout and retry settings keep automation from hanging when a device is slow or unreachable.