This is a tool to sync data from different sources to a NetBox instance.
Available source types:
- VMware vCenter Server
- bb-ricardo/check_redfish inventory files
IMPORTANT: READ INSTRUCTIONS CAREFULLY BEFORE RUNNING THIS PROGRAM
A BIG thank-you goes out to Raymond Beaudoin for creating vcenter-netbox-sync which served as source of a lot of ideas for this project.
copied from Raymond Beaudoin
The NetBox documentation makes it clear the tool is intended to act as a "Source of Truth". The automated import of live network state is strongly discouraged. While this is sound logic we've aimed to provide a middle-ground solution for those who desire the functionality.
All objects collected from vCenter have a "lifecycle". Upon import, for supported object types,
they are tagged NetBox-synced to note their origin and distinguish them from other objects.
Using this tagging system also allows for the orphaning of objects which are no longer detected in vCenter.
This ensures stale objects are removed from NetBox keeping an accurate current state.
- python >= 3.6
- packaging
- urllib3==1.26.9
- wheel
- requests==2.27.1
- pyvmomi==7.0.3
- aiodns==2.0.0
- setuptools>=62.00.0
- pyyaml==6.0
- NetBox >= 2.9
- VMWare vCenter >= 6.0
- check_redfish >= 1.2.0
- here we assume we install in
/opt
- on RedHat/CentOS 7 you need to install python3.6 and pip from EPEL first
- on RedHat/CentOS 8 systems the package name changed to
python3-pip
yum install python36-pipapt-get update && apt-get install python3-venv- If you need to use python 3.6 then you would need
requirements_3.6.txtto install requirements - download and setup of virtual environment
cd /opt
git clone https://github.com/bb-Ricardo/netbox-sync.git
cd netbox-sync
python3 -m venv .venv
. .venv/bin/activate
pip3 install --upgrade pip || pip install --upgrade pip
pip3 install wheel || pip install wheel
pip3 install -r requirements.txt || pip install -r requirements.txtThe vsphere-automation-sdk must be installed if tags should be synced from vCenter to NetBox
- assuming we are still in an activated virtual env
pip install --upgrade git+https://github.com/vmware/vsphere-automation-sdk-python.gitIn order to updated data in NetBox you need a NetBox API token.
- API token with all permissions (read, write) except:
- auth
- secrets
- users
A short description can be found here
usage: netbox-sync.py [-h] [-c settings.ini [settings.ini ...]] [-g]
[-l {DEBUG3,DEBUG2,DEBUG,INFO,WARNING,ERROR}] [-n] [-p]
Sync objects from various sources to NetBox
Version: 1.6.1 (2024-05-14)
Project URL: https://github.com/bb-ricardo/netbox-sync
options:
-h, --help show this help message and exit
-c settings.ini [settings.ini ...], --config settings.ini [settings.ini ...]
points to the config file to read config data from
which is not installed under the default path
'./settings.ini'
-g, --generate_config
generates default config file.
-l {DEBUG3,DEBUG2,DEBUG,INFO,WARNING,ERROR}, --log_level {DEBUG3,DEBUG2,DEBUG,INFO,WARNING,ERROR}
set log level (overrides config)
-n, --dry_run Operate as usual but don't change anything in NetBox.
Great if you want to test and see what would be
changed.
-p, --purge Remove (almost) all synced objects which were create
by this script. This is helpful if you want to start
fresh or stop using this script.
It is recommended to set log level to DEBUG2 this way the program should tell you what is happening and why.
Also use the dry run option -n at the beginning to avoid changes directly in NetBox.
There are two ways to define configuration. Any combination of config file(s) and environment variables is possible.
- config files (the default config file name is set to
./settings.ini.) - environment variables
The config from the environment variables will have precedence over the config file definitions.
Following config file types are supported:
- ini
- yaml
There is also more than one config file permitted. Example (config file names are also just examples):
/opt/netbox-sync/netbox-sync.py -c common.ini all-sources.yaml additional-config.yamlAll files are parsed in order of the definition and options will overwrite the same options if defined in a previous config file.
To get config file examples which include descriptions and all default values, the -g can be used:
# this will create an ini example
/opt/netbox-sync/netbox-sync.py -g -c settings-example.ini
# and this will create an example config file in yaml format
/opt/netbox-sync/netbox-sync.py -g -c settings-example.yaml Each setting which can be defined in a config file can also be defined using an environment variable.
The prefix for all environment variables to be used in netbox-sync is: NBS
For configuration in the common and netbox section a variable is defined like this
<PREFIX>_<SECTION_NAME>_<CONFIG_OPTION_KEY>=value
Following example represents the same configuration:
# yaml config example
common:
log_level: DEBUG2
netbox:
host_fqdn: netbox-host.example.com
prune_enabled: true# this variable definition is equal to the yaml config sample above
NBS_COMMON_LOG_LEVEL="DEBUG2"
NBS_netbox_host_fqdn="netbox-host.example.com"
NBS_NETBOX_PRUNE_ENABLED="true"This way it is possible to expose for example the NBS_NETBOX_API_KEY only via an env variable.
The config definitions for sources need to be defined using an index. Following conditions apply:
- a single source needs to use the same index
- the index can be number or a name (but contain any special characters to support env var parsing)
- the source needs to be named with
_NAMEvariable
Example of defining a source with config and environment variables.
; example for a source
[source/example-vcenter]
enabled = True
type = vmware
host_fqdn = vcenter.example.com
username = vcenter-readonly# define the password on command line
# here we use '1' as index
NBS_SOURCE_1_NAME="example-vcenter"
NBS_SOURCE_1_PASSWORD="super-secret-and-not-saved-to-the-config-file"
NBS_SOURCE_1_custom_dns_servers="10.0.23.23, 10.0.42.42"Even to just define one source variable like NBS_SOURCE_1_PASSWORD the NBS_SOURCE_1_NAME needs to be defined as
to associate to the according source definition.
In Order to sync all items regularly you can add a cron job like this one
# NetBox Sync
23 */2 * * * /opt/netbox-sync/.venv/bin/python3 /opt/netbox-sync/netbox-sync.py >/dev/null 2>&1
Run the application in a docker container. You can build it yourself or use the ones from docker hub.
Available here: bbricardo/netbox-sync
- The application working directory is
/app - Required to mount your
settings.ini
To build it by yourself just run:
docker build -t bbricardo/netbox-sync:latest .To start the container just use:
docker run --rm -it -v $(pwd)/settings.ini:/app/settings.ini bbricardo/netbox-sync:latestRun the containerized application in a kubernetes cluster
- Create a config map with the default settings
- Create a secret witch only contains the credentials needed
- Adjust the provided cronjob resource to your needs
- Deploy the manifest to your k8s cluster and check the job is running
config example saved as settings.yaml
netbox:
host_fqdn: netbox.example.com
source:
my-vcenter-example:
type: vmware
host_fqdn: vcenter.example.com
permitted_subnets: 172.16.0.0/12, 10.0.0.0/8, 192.168.0.0/16, fd00::/8
cluster_site_relation: Cluster_NYC = New York, Cluster_FFM.* = Frankfurt, Datacenter_TOKIO/.* = Tokiosecrets example saved as secrets.yaml
netbox:
api_token: XYZXYZXYZXYZXYZXYZXYZXYZ
source:
my-vcenter-example:
username: vcenter-readonly
password: super-secretCreate resource in your k8s cluster
kubectl create configmap netbox-sync-config --from-file=settings.yaml
kubectl create secret generic netbox-sync-secrets --from-file=secrets.yaml
kubectl apply -f k8s-netbox-sync-cronjob.yamlREAD CAREFULLY
The program operates mainly like this
- parsing and validating config
- instantiating all sources and setting up connection to NetBox
- read current data from NetBox
- read data from all sources and add/update objects in memory
- Update data in NetBox based on data from sources
- Prune old objects
Request all current NetBox objects. Use caching whenever possible. Objects must provide "last_updated" attribute to support caching for this object type.
Actually perform the request and retry x times if request times out. Program will exit if all retries failed!
Check out the documentations for the different sources
If you have multiple vCenter instances or check_redfish folders just add another source with the same type in the same file.
Example:
[source/vcenter-BLN]
enabled = True
host_fqdn = vcenter1.berlin.example.com
[source/vcenter-NYC]
enabled = True
host_fqdn = vcenter2.new-york.example.com
[source/redfish-hardware]
type = check_redfish
inventory_file_path = /opt/redfish_inventoryIf different sources overwrite the same attribute for ex. a host then the order of the sources should be considered. The last source in order from top to bottom will prevail.
Prune objects in NetBox if they are no longer present in any source. First they will be marked as Orphaned and after X (config option) days they will be deleted from NetBox.
Objects subjected to pruning:
- devices
- VMs
- device interfaces
- VM interfaces
- IP addresses
All other objects created (i.e.: VLANs, cluster, manufacturers) will keep the source tag but will not be deleted. Theses are "shared" objects might be used by different NetBox objects
You can check out the full license here
This project is licensed under the terms of the MIT license.
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent