Skip to content

sealingtech/EDCOP-CONFIGURESENSORS

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

17 Commits
 
 
 
 

Repository files navigation

EDCOP Configure Sensors

Table of Contents

Configuration Guide

Within this configuration guide, you will find instructions for modifying Host-Setup. Host-Setup is designed to utilize SR-IOV networks for SR-IOV enabled cards, or host networking for direct interface, exposure while also optimizing performance across all sensors. In gerneral, VMs should use host networking.

WARNING: While Host-setup doesn't require a reboot, there should be no sensors deployed before running this tool. Delete all sensors utilizing either of the inline or passive networks. Once this has been run it is possible to re-run this.

Image Repository

This points to the location of the Docker container registry. If you're changing these values, make sure you include the full repository name.

images:
    host-setup: gcr.io/edcop-public/host-setup:3

Cluster Settings

Currently, the host-setup can be applied to physical or virtual clusters by using host networking instead of the SR-IOV plugin for virtual clusters. The useHostNetworking setting should be set to true or false depending on your environment. Additionally, if you do not wish to use inline capabilities, you can disable the inline NIC setup by setting inline to false.

cluster:
  useHostNetworking: false 
  inline: true

If you deployed EDCOP virtually, make sure your virtual network supports promiscuous mode and that your VMs will accept traffic.

Network Interfaces

Configure specific settings to define the network interface cards. The deviceName settings must the be the same across the cluster. The numOfVirtualFunctions setting will be the number of virtual functions that will be created on each physicalNIC. Each physical sensor will consume one SR-IOV virtual function. Host networking does not use SR-IOV, meaning the numOfVirtualFunctions settings are ignored. Finally, the irqCoreAssignment is the CPU core that will handle all interrupts for the Network Interface Card.

networkInterfaces: 
    inline1interface:
        #Configure the interface names
        deviceName: enp216s0f1
        #Configure the number of virtual functions to be created on the interface
        numOfVirtualFunctions: 4
        #Configure the core that will handle interrupts for the network interface
        irqCoreAssignment: 8
    inline2interface:
        deviceName: enp216s0f2
        numOfVirtualFunctions: 4
        irqCoreAssignment: 8
    passive1interface:
        deviceName: enp216s0f3
        numOfVirtualFunctions: 4
        irqCoreAssignment: 8    

NodeSelector

The worker option will configure which systems Configure Sensors will be applied to. This should only be systems which will carry sensors and should NEVER include the master node.

nodeSelector:
  label: sensor

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors 4

  •  
  •  
  •  
  •