Documentation ¶
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
This section is empty.
Types ¶
type Linux ¶
type Linux struct { IfPlugin *linux_ifplugin.IfPlugin L3Plugin *linux_l3plugin.L3Plugin NSPlugin *linux_nsplugin.NsPlugin IPTablesPlugin *linux_iptablesplugin.IPTablesPlugin }
Linux contains all Linux plugins.
type VPP ¶
type VPP struct { ABFPlugin *abfplugin.ABFPlugin ACLPlugin *aclplugin.ACLPlugin IfPlugin *ifplugin.IfPlugin IPSecPlugin *ipsecplugin.IPSecPlugin L2Plugin *l2plugin.L2Plugin L3Plugin *l3plugin.L3Plugin NATPlugin *natplugin.NATPlugin PuntPlugin *puntplugin.PuntPlugin STNPlugin *stnplugin.STNPlugin SRPlugin *srplugin.SRPlugin }
VPP contains all VPP plugins.
type VPPAgent ¶
type VPPAgent struct { infra.PluginName LogManager *logmanager.Plugin // VPP & Linux (and other plugins with descriptors) are first to ensure that // all their descriptors are registered to KVScheduler // before orchestrator that starts watch for their NB key prefixes. VPP Linux Netalloc *netalloc.Plugin Orchestrator *orchestrator.Plugin ETCDDataSync *kvdbsync.Plugin ConsulDataSync *kvdbsync.Plugin RedisDataSync *kvdbsync.Plugin Configurator *configurator.Plugin RESTAPI *restapi.Plugin Probe *probe.Plugin StatusCheck *statuscheck.Plugin Telemetry *telemetry.Plugin }
VPPAgent defines plugins which will be loaded and their order. Note: the plugin itself is loaded after all its dependencies. It means that the VPP plugin is first in the list despite it needs to be loaded after the linux plugin.
Click to show internal directories.
Click to hide internal directories.