Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Understanding Cloud Analytics Engine Architecture and Deployment

 

This topic describes the architecture and deployment of Cloud Analytics Engine.

This topic includes these sections:

Supported Topologies

Cloud Analytics Engine supports data center networks that use these topologies:

  • Bare metal application servers connected by a layer 3 IP fabric network. Figure 1 illustrates this type of topology.

    Figure 1: Bare Metal Application Servers Connected by a Layer 3 IP Fabric Network
    Bare Metal Application
Servers Connected by a Layer 3 IP Fabric Network
  • KVM virtual machine application servers connected by VxLAN tunnels overlaid on a layer 3 fabric network. Figure 2 illustrates this type of topology.

    Figure 2: KVM Virtual Machine Application Servers Connected by VxLAN Tunnels Overlaid on a layer 3 Fabric Network.
    KVM Virtual Machine
Application Servers Connected by VxLAN Tunnels Overlaid on a layer
3 Fabric Network.
  • KVM virtual machine application servers connected by a layer 3 IP fabric network. There is no overlay network. Figure 3 illustrates this type of topology.

    Figure 3: KVM Virtual Machine Application Servers Connected by a Layer 3 IP Fabric Network
    KVM Virtual Machine
Application Servers Connected by a Layer 3 IP Fabric Network

Software Components

Cloud Analytics Engine consists of the following software components:

  • Cloud Analytics Engine Junos component — A required component that is built into supported Junos releases. This component processes requests from Compute Agent to collect data. The collected data is sent to Compute Agent.

  • Compute Agent — A required software component that is installed on a compute node. The Compute Agent works with the Cloud Analytics Engine Junos component to configure cloud analytics data collection on network devices and collect the requested data. The Compute Agent is controlled by either an API or by the Data Learning Engine component.

  • Data Learning Engine — An optional software component that is installed on a compute node. It may not be installed on the same compute node as Compute Agent. It provides longer storage and additional processing of network analytics data. It provides a REST API for integrating with Network Director to allow Network Director to configure analytics data collection and visualize network analytics data. Other applications can also use the REST API to integrate with Cloud Analytics Engine.

Cloud Analytics Engine integrates with Junos Space Network Director to allow Network Director to configure analytics data collection and visualize network analytics data.

Support for Devices that Do Not Support Cloud Analytics Engine

Cloud Analytics Engine will work with devices that do not support Cloud Analytics Engine, including non-Juniper devices, in the application flow path, but the only data it will collect from them is their IP address and hop number.

It is recommended that network devices that connect to application servers (called penultimate hop devices) should be Juniper devices that support Cloud Analytics Engine. If you have penultimate hop devices that do not support Cloud Analytics Engine, ensure that your data collection requests specify an accurate hop count.

User Interfaces

Cloud Analytics Engine has several user interfaces:

  • On networking devices that support Cloud Analytics Engine, CLI statements allow you enable and disable cloud analytics data collection, and show commands allow you to view some of the collected cloud analytics data.

    Note

    In Junos OS Release 15.1X53, the Cloud Analytics Engine Junos component supports show commands that provide the same output but have different command names and hierarchies than the show commands supported in all other releases. Each operational command description provides a reference to its equivalent command in the other releases.

  • The Compute Agent API allows you to configure and collect cloud analytics data.

  • The Data Learning Engine REST API allows you to configure and collect cloud analytics data. It uses the Compute Agent API to collect data. Data Learning Engine performs some additional data processing, so it can provide more types of data than Compute Agent.

  • Network Director integrates with Data Learning Engine to allow you to configure, collect, and visualize cloud analytics data using the Network Director user interface. Network Director uses the Data Learning Engine REST API to configure and collect cloud analytics data, and it can perform additional data processing, so it can provide more types of data than Data Learning Engine.

Basic Workflow

This is the basic Cloud Analytics Engine workflow:

  1. You start generating cloud analytics data.

    You can use several methods to start generating cloud analytics data: Network Director, the Data Learning Engine REST API, or the Compute Agent API.

    You select what data to generate by specifying an application flow or a VxLAN tunnel to monitor. Each device in the path of a monitored application flow or tunnel that supports Cloud Analytics Engine generates cloud analytics data for that flow or tunnel.

  2. You view or collect the generated data.

    You can use show commands on networking devices to view some cloud analytics data. You can use several methods to collect cloud analytics data: Network Director, the Data Learning Engine REST API, or the Compute Agent API. You select what data to collect by specifying an application flow or a VxLAN tunnel.

  3. You visualize the collected data.

    You can use the Compute Agent API and the Data Learning Engine REST API to collect analytics data. Both APIs return analytics data in JSON format. If you use Network Director, it reads the data and provides features to visualize it.

Release History Table
Release
Description
In Junos OS Release 15.1X53, the Cloud Analytics Engine Junos component supports show commands that provide the same output but have different command names and hierarchies than the show commands supported in all other releases.