Which process is responsible for JET automation requests?

The JET Service Daemon (jsd) is the core process responsible for handling all Junos Extension Toolkit (JET) automation requests. It functions as the gRPC server on the Junos device, listening for incoming API calls from external JET applications. The jsd process manages the lifecycle of these applications and facilitates their communication and interaction with other essential Junos processes, such as the routing protocol process (rpd) and the management process (mgd), to perform the requested operations on the device.

A. jsrpd: This is the Junos Services Redundancy Protocol process, which is primarily used for state synchronization and failover in high-availability configurations like chassis clusters, not for JET automation.

B. mgd: This is the Management Process, which handles traditional management interfaces such as the CLI, NETCONF, and the Junos XML protocol. It does not process the gRPC-based requests used by JET.

C. rpd: This is the Routing Protocol Process, responsible for managing all routing protocols (e.g., BGP, OSPF) and maintaining the routing tables. While JET applications can interact with rpd, rpd itself does not handle the initial JET API requests.

1. Juniper Networks TechLibrary, Junos OS, Automation Scripting Feature Guide. In the "Junos Extension Toolkit (JET) Overview" section, it describes the architecture where applications communicate with Junos OS processes. The "JET Service Process (jsd)" subsection explicitly states: "The JET service process (jsd) is the daemon that is responsible for all JET applications. The jsd process is also the gRPC server."

2. Juniper Networks TechLibrary, Junos OS, CLI User Guide. The "Junos OS Processes" section provides a list of daemons. It defines jsd as the "JET service process," mgd as the "Management process," and rpd as the "Routing protocol process," clearly distinguishing their roles.