Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Related Documentation


    Introduction to JunosV App Engine

    JunosV App Engine enables third-party applications—applications written to run in Linux—to run on a remote virtualized system called a guest OS. These applications, which can be control-plane, management-plane, or data-plane applications, are referred to as remote applications. JunosV App Engine enables remote applications to run in their native environment without requiring porting to Junos OS.

    JunosV App Engine provides a virtualized environment with a Kernel-based Virtual Machine (KVM) hypervisor, which runs on the host OS. The host OS controls the creation of virtual machines (VMs) on top of the hypervisor. The hypervisor and host OS run within a VSE device called a compute node. A JunosV App Engine compute node is in the form of an external device, provided by Juniper Networks, which runs CentOS, KVM, and Qemu. Compute nodes are used to spawn virtual machines (VMs), each of which runs either a Juniper Networks or third-party application within a guest OS. The external device is connected to a router using a Layer 2 or Layer 3 network. The compute node is connected to a device running Junos OS. This device can be a router, switch, or gateway.

    Multiple remote applications can communicate with Junos OS. Remote applications run in a VM on the external system and communicate through a Service Broker that runs on the Junos device. The Service Broker on the Junos device functions as a front end for services provided by Junos daemons such as rpd, mgd, and so forth, and relays information between the Junos daemons and the remote applications on the external system. The remote applications on the external system can access the Junos daemons on the Junos device.

    The JunosV App Engine Administration Guide provides CLI configuration information for configuring the compute node and provisioning the VMs. It also provides the operational commands that are available to monitor the compute node and VM settings. In the CLI configuration mode, there are two hierarchy levels to configure: the physical connection between the device running Junos OS and the hardware appliance (which is under the [edit services app-engine compute-cluster] hierarchy level) and the virtual machines VMs), where the applications run, each on its own guest OS (in the [edit services app-engine virtual-machines] hierarchy level).

    Currently, Linux and Ubuntu are the only supported guest OSes. The only device the compute node can connect to is a Juniper Networks M Series, MX Series, or T Series router. The type of connection is limited to a Layer 2 connection. Changes to the VM part of the CLI configuration are destructive and will cause the VM to reboot. In the compute cluster part of the CLI configuration, changes to management interfaces are destructive and require a reboot of the compute node.


    Related Documentation


    Published: 2014-03-31