- Remove PVC volume mount from k8s/deployment.yaml - Delete k8s/mib-pvc.yaml (no longer needed) - Update .gitignore to commit MIB files to git - Add mix import_mibs task to copy MIBs from LibreNMS - Add all MIB files from priv/mibs/ to git This fixes the multi-attach volume error in Kubernetes where new pods couldn't start because the RWO (ReadWriteOnce) PVC was attached to the old pod. MIBs are now part of the Docker image and can be used by all pods simultaneously.
42 lines
No EOL
1.4 KiB
Text
42 lines
No EOL
1.4 KiB
Text
-------------------------------
|
|
-- VeloCloud MIB Definitions --
|
|
-- --
|
|
-- Contains: --
|
|
-- .velocloud(45346) --
|
|
-- .orchestrator(1) --
|
|
-- .edge(2) --
|
|
-- .gateway(3) --
|
|
-------------------------------
|
|
|
|
VELOCLOUD-MIB DEFINITIONS ::= BEGIN
|
|
|
|
IMPORTS
|
|
MODULE-IDENTITY, enterprises FROM SNMPv2-SMI
|
|
;
|
|
|
|
velocloud MODULE-IDENTITY
|
|
LAST-UPDATED "201908020000Z"
|
|
ORGANIZATION "VMware Corporation"
|
|
CONTACT-INFO "postal: VMware Corporation
|
|
World Headquarters
|
|
3401 Hillview Avenue
|
|
Palo Alto, CA 943043
|
|
USA
|
|
|
|
web: www.velocloud.com
|
|
email: contact@velocloud.com"
|
|
DESCRIPTION "Top-level infrastructure of the VeloCloud enterprise MIB tree"
|
|
|
|
REVISION "201908020000Z"
|
|
DESCRIPTION "Implementation of VeloCloud Edge MIB Objects"
|
|
|
|
REVISION "201701180000Z"
|
|
DESCRIPTION "Implementation of VCO MIB Objects"
|
|
|
|
REVISION "201701130000Z"
|
|
DESCRIPTION "Inital definition of VeloCloud MIB Objects"
|
|
::= { enterprises 45346 }
|
|
|
|
modules OBJECT IDENTIFIER ::= { velocloud 1 }
|
|
|
|
END |