Saravanan666/pypi-org huggingface dataset:
Package: netbox-circuitmaintenance
Netbox Circuit Maintenance PluginDocumentation:https://jasonyates.github.io/netbox-circuitmaintenance/A NetBox plugin built to track circuit maintenance events, the plugin itself is agnostic in that it is only built to store data surrounding maintenance events and provide an overview of historical, active and upcoming circuit and provider maintenance events. The plugin tracks maintenance events at the provider level and associates impact from each event at the circuit level.The plugin does not directly provide an automated approach to ingesting provider notifications, instead it extends NetBox's extensive REST API and provides GET/POST/PUT/PATCH methods to manage maintenance events. The plugin is intended to be coupled with an automated parser to handle the parsing of provider notifications and the delivery of the maintenance events to the plugin's REST API. Several example parsers have been documentedhere.FeaturesTrack provider maintenance eventsTrack circuit impact from provider maintenanceProvides a consolidated view of active, upcoming and historical maintenance events at the provider and circuit levelConsolidated notifications (coming soon)Maintenance overlap detection (coming soon)CompatibilityThis plugin is only supported on NetBox 3.4 or higher, for exact compatibility information, see the table below.NetBox VersionPlugin Version3.50.3.03.40.2.2InstallingA working installation of Netbox 3.4+ is required -see official documentation.Package InstallationActivate your virtual env and install via pip::$source/opt/netbox/venv/bin/activate(venv)$pipinstallnetbox-circuitmaintenanceTo ensure the Netbox Documents plugin is automatically re-installed during future upgrades, add the package to yourlocal_requirements.txt:# echo netbox-circuitmaintenance >> local_requirements.txtEnable the PluginIn the Netboxconfiguration.pyconfiguration file add or update the PLUGINS parameter, addingnetbox_documents:PLUGINS=['netbox_circuitmaintenance']PLUGINS_CONFIG={"netbox_circuitmaintenance":{},}Apply Database MigrationsApply database migrations with Netboxmanage.py:(venv) $ python manage.py migrateRestart NetboxRestart the Netbox service to apply changes:sudo systemctl restart netboxScreenshotsCreditsBased on the NetBox plugin tutorial:demo repositorytutorialThis package was created withCookiecutterand thenetbox-community/cookiecutter-netbox-pluginproject template.
Package: netbox-cloud-pilot
NetBox Cloud PilotNetBox Cloud Pilotis a specialized plugin tailored for
NetBox, offering enhanced functionality for users on theCloudMyDC public Cloud platform (VAP). This plugin simplifies the management of
various NetBox components and infrastructure, streamlining processes and offering a more integrated experience.NetBox Cloud Pilot, developed and maintained byOnemind Services LLC, introduces an
exclusive plugin store for NetBox. It caters to users with a diverse range of both free and paid plugins, enhancing the
NetBox experience.FeaturesNetBox Cloud Pilot integrates several key features:Management of NetBox Settings: Control settings for Database (DB), Redis, System, and security and much more.Infrastructure Log Viewing: Access and monitor logs from different nodes within the infrastructure.Node Restart Capabilities: Remotely restart nodes within the infrastructure.Database Backup and Restoration: Manage and restore DB backups.Plugin Management: Install, uninstall, and configure other NetBox plugins.CompatibilityNetBox VersionPlugin Versionv3.5.xv0.0.xv3.6.xv0.1.xInstallationFor updates, visitNetBox Cloud Pilot releases.SupportFor support, questions, or feedback, please file an issue on ourGitHub issue tracker.ContributingContributions to NetBox Cloud Pilot are welcome! If you'd like to contribute, please fork the repository and submit a
pull request. For more detailed information, refer to our contributing guidelines in the repository.
Package: netbox-config-diff
NetBox Config Diff PluginNetBoxplugin for Config Diff.Free software: Apache-2.0Documentation:https://miaow2.github.io/netbox-config-diff/AboutCollecting diffsWith this plugin you can find diff between the rendered configuration for a device to its actual configuration, retrieved from the device itself, or stored in DataSource.
Read aboutDataSourcesfor further details.Device configuration renders natively in NetBox. Thisfeaturewas introduced in 3.5 version.
NetBox Labsblogpost about it.Plugin supports a wide list of vendors (Cisco, Juniper, Huawei, MicroTik etc.) with the help of Scrapli. ReadScrapliandscrapli-communitydocumentations to find full list of vendors.Pushing configurationAlso you can push rendered configuration from NetBox to device and apply it.Supported platforms:arista_eoscisco_iosxecisco_iosxrcisco_nxosjuniper_junosThis is possible thanks to the scrapli_cfg. ReadScraplidocumentation for more info.CompatibilityNetBox VersionPlugin Version3.5, 3.6=>0.1.0InstallingFor adding to a NetBox Docker setup seethe general instructions for using netbox-docker with plugins.Install with pip:pipinstallnetbox-config-diffAdd tolocal_requirements.txt:echonetbox-config-diff>>local_requirements.txtEnable the plugin in/opt/netbox/netbox/netbox/configuration.py,
or if you use netbox-docker, your/configuration/plugins.pyfile,
and define credentials for devices connection:PLUGINS=["netbox_config_diff",]PLUGINS_CONFIG={"netbox_config_diff":{"USERNAME":"foo","PASSWORD":"bar","AUTH_SECONDARY":"foobar",# define here password for accessing Privileged EXEC mode, this variable is optional},}Run database migrations:pythonmanage.pymigrateCollect static from the plugin:pythonmanage.pycollectstatic--noinputRestart NetBox service:systemctlrestartnetboxnetbox-rqUsageRead thisdocabout collecting diffs, for configuration management readthisVideoMy presention about plugin at October NetBox community call (19.10.2023).ScreenshotsCompliance finished with errorRender diff between configurationsNo diffConfiguration requestCompleted Configuration requestCreditsBased on the NetBox plugin tutorial:demo repositorytutorialThis package was created withCookiecutterand thenetbox-community/cookiecutter-netbox-pluginproject template.
Package: netbox-counterparties
Netbox Software PluginA plugin designed to faciliate the storage of site, circuit, device type and device specific software withinNetBoxFeaturesStore software against the following NetBox models:CircuitsDevicesDevice TypesSitesUpload software to your NetBox media/ folder or other Django supported storage method e.g. S3Supports a wide array of common file types (bmp, gif, jpeg, jpg, png, pdf, txt, doc, docx, xls, xlsx, xlsm)Store links to external URL's to save duplication of remote softwareCompatibilityNetBox VersionPlugin Version3.2+0.2.4InstallationA working installation of Netbox 3.2+ is required. 3.4+ is recommended.Package Installation from PyPiActivate your virtual env and install via pip:$ source /opt/netbox/venv/bin/activate
(venv) $ pip install netbox-systemsTo ensure the Netbox software plugin is automatically re-installed during future upgrades, add the package to yourlocal_requirements.txt:# echo netbox-systems >> local_requirements.txtEnable the PluginIn the Netboxconfiguration.pyconfiguration file add or update the PLUGINS parameter, addingnetbox_systems:PLUGINS=['netbox_systems',](Optional) Add or update a PLUGINS_CONFIG parameter inconfiguration.pyto configure plugin settings. Options shown below are the configured defaults:PLUGINS_CONFIG={'netbox_systems':{# Enable the management of device specific software (True/False)'enable_device_software':True,# Location to inject the software widget in the device view (left/right'device_software_location':'left',}}(Optional) Add or replace the built-in software Type choices via Netbox'sFIELD_CHOICESconfiguration parameter:The colours that can be used are listed in the Netbox CSS netbox-light.css:(https://github.com/netbox-community/netbox/blob/develop/netbox/project-static/dist/netbox-light.css)The bg- must not be specified in the configuration.
Here are a few examples from the CSS:bg-indigo = #6610f2 --> 'indigo'bg-blue = #0d6efd --> 'blue'bg-purple = #6f42c1 --> 'purple'bg-pink = #d63384 --> 'pink'bg-red = #dc3545 --> 'red'bg-orange = #fd7e14 --> 'orange'bg-yellow = #ffc107 --> 'yellow'bg-green = #198754 --> 'green'bg-teal = #20c997 --> 'teal'bg-cyan = #0dcaf0 --> 'cyan'bg-gray = #adb5bd --> 'gray'bg-black = #000 --> 'black'bg-white --> 'white'FIELD_CHOICES={'netbox_systems.DocTypeChoices.device+':(('mysoftware','My Custom Device software Type','green'),)}Apply Database MigrationsApply database migrations with Netboxmanage.py:(venv) $ python manage.py migrateRestart NetboxRestart the Netbox service to apply changes:sudo systemctl restart netboxRe-index Netbox search index (Upgrade to 3.4 only)If you are upgrading from Netbox 3.2 or above to Netbox 3.4, any previously inserted software may not show up in the new search feature. To resolve this, re-index the plugin:(venv) $ python manage.py reindex netbox_systems
Package: netbox-ddns
Dynamic DNS Connector for NetBoxThis plugin lets you define DNS servers that supportRFC3007 Dynamic DNS Updates.
For each server you specify which domains and reverse DNS domains it is responsible for, and after that NetBox will
automatically send DNS Updates to those servers whenever you change the DNS name of an IP Address in NetBox.Updates are sent from the worker process in the background. You can see their progress either by configuring Django
logging or by looking at the Background Tasks in the NetBox admin back-end.For now all configuration is done in the NetBox admin back-end. A later version will provide a nicer user interface.CompatibilityThis plugin in compatible withNetBoxv3.0.0 and greater, support for Netbox v2.11.0 is dropped in v1.1.4 due to UI implementation.InstallationFirst, addnetbox-ddnsto your/opt/netbox/local_requirements.txtfile. Create it if it doesn't exist.Then enable the plugin in/opt/netbox/netbox/netbox/configuration.py, like:PLUGINS=['netbox_ddns',]And finally run/opt/netbox/upgrade.sh. This will download and install the plugin and update the database when
necessary. Don't forget to runsudo systemctl restart netbox netbox-rqlikeupgrade.shtells you!
Package: netbox-demo
NetBox Demo PluginWARNING:This plugin is purposefully insecure. Do not install it.This plugin serves to ease the administration of the public NetBox demo instance athttps://demo.netbox.dev. It performs the following tasks:Facilitate the automatic creation of new superuser accountsPrevent manipulation or deletion of the default admin userChange Logv0.4Implement the automatic creation of unique user accountsv0.3Protect against changes to the admin user's name, password, or statusv0.2Separatepre_saveandpre_deletesignal handlersv0.1Initial release
Package: netbox-device-groups
A netbox plugin for managing multiple device group types by siteInstalling the Plugin in NetboxPrerequisitesThe plugin is compatible with Netbox 3.5.0 and higher.Databases supported: PostgreSQLPython supported : Python3 >= 3.10Install GuideNOTE: Plugins can be installed manually or using Python'spip. See thenetbox documentationfor more details. The pip package name for this plugin isnetbox-device-groups.The plugin is available as a Python package via PyPI and can be installed withpip:pipinstallnetbox-device-groupsTo ensure the device cluster plugin is automatically re-installed during future upgrades, create a file namedlocal_requirements.txt(if not already existing) in the Netbox root directory (alongsiderequirements.txt) and list thenetbox_device_groupspackage:echonetbox-device-groups>>local_requirements.txtOnce installed, the plugin needs to be enabled in your Netbox configuration. The following block of code below shows the additional configuration required to be added to your$NETBOX_ROOT/netbox/configuration.pyfile:Append"netbox_device_groups"to thePLUGINSlist.Append the"netbox_device_groups"dictionary to thePLUGINS_CONFIGdictionary and override any defaults.PLUGINS=["netbox_device_groups",]Post Install StepsOnce the Netbox configuration is updated, run the post install steps from theNetbox Hometo run migrations and clear any cache:# Apply any database migrationspython3netbox/manage.pymigrate# Trace any missing cable paths (not typically needed)python3netbox/manage.pytrace_paths--no-input# Collect static filespython3netbox/manage.pycollectstatic--no-input# Delete any stale content typespython3netbox/manage.pyremove_stale_contenttypes--no-input# Rebuild the search cache (lazily)python3netbox/manage.pyreindex--lazy# Delete any expired user sessionspython3netbox/manage.pyclearsessions# Clear the cachepython3netbox/manage.pyclearcacheThen restart the Netbox services:sudosystemctlrestartnetboxnetbox-rq
Package: netbox-devicetype-importer
Netbox DeviceType Import PluginNetBoxplugin for easy import DeviceType fromNetBox Device Type LibraryDescriptionThe plugin usesGitHub GraphQL APIto load DeviceType fromNetBox Device Type Library. The plugin loads only file tree representation from github repo and shows it as a table with vendor and model columns. DeviceType definitions files are loaded when you try to import selected models.
To use GraphQL API you need to set GitHub personal access token in plugin settings.  You don't need to grant any permissions to the token.How to create the token, see"Creating a personal access token."CompatibilityThis plugin in compatible withNetBox3.0 and laterInstallationThe plugin is available as a Python package in pypi and can be installed with pippip install netbox-devicetype-importerEnable the plugin inNetBox ConfigurationPLUGINS = ['netbox_devicetype_importer']ConfigurationPut your GitHub personal access token toNetBox plugins configPLUGINS_CONFIG = {
    'netbox_devicetype_importer': {
        'github_token': '<YOUR-GITHUB-TOKEN>'
    }
}ScreenshotsFutureImport device images from GitHub repoAdd a GitHub REST API client that allows this plugin to be used without the GitHub token
Package: netbox-device-view
Netbox Device View PluginInstallThe plugin is available as a Python package and can be installed with pip.Runpip install netbox-device-viewin your virtual env.To ensure NetBox Device View plugin is automatically re-installed during future upgrades, create a file namedlocal_requirements.txt(if not already existing) in the NetBox root directory (alongsiderequirements.txt) and list thenetbox-device-viewpackage:# echo netbox-device-view >> local_requirements.txtOnce installed, the plugin needs to be enabled in yourconfiguration.pyand optionally theshow_on_device_tabsetting enabled.# In your configuration.pyPLUGINS=["netbox_device_view"]PLUGINS_CONFIG={'netbox_device_view':{'show_on_device_tab':True,},}First runsource /opt/netbox/venv/bin/activateto enter the Python virtual environment.Then runcd/opt/netbox/netbox
pip3installnetbox-device-view
python3manage.pymigratenetbox_device_view
python3manage.pycollectstatic--no-inputHow To UseFor each Device Type you need to add a DeviceView.It is based on a CSS grid view with 32 columns and 2 rows.
You need to specify the grid-template-areas.Interface positions will use the following format: {interfacename}{module}-{port}
or fallback to all lower case + [^.a-zA-Z\d] changed to "-"leading "empties" can be specified as xtrailing "empties" can be specified as zbetween "empties" can be named s{0-99}numeric only ports have to be prefixed with "p" e.g. "p1"Example for Cisco C9300-24T with 8x 10G module ( more inexamplesfolder )/* C9300-24T */
.deviceview.area {
	grid-template-areas:
	"x x x x x x x x x x x x x x gigabitethernet0-1 gigabitethernet0-3 gigabitethernet0-5 gigabitethernet0-7 gigabitethernet0-9 gigabitethernet0-11 s0 gigabitethernet0-13 gigabitethernet0-15 gigabitethernet0-17 gigabitethernet0-19 gigabitethernet0-21 gigabitethernet0-23 z z z z z"
	"x x x x x x x x x x x x x x gigabitethernet0-2 gigabitethernet0-4 gigabitethernet0-6 gigabitethernet0-8 gigabitethernet0-10 gigabitethernet0-12 s0 gigabitethernet0-14 gigabitethernet0-16 gigabitethernet0-18 gigabitethernet0-20 gigabitethernet0-22 gigabitethernet0-24 z z z z z";
}

/* C9300-24T with C9300-NM-8X */
.deviceview.moduleC9300-NM-8X.area {
	grid-template-areas:
	"x x x x x x x x x x x x x x gigabitethernet0-1 gigabitethernet0-3 gigabitethernet0-5 gigabitethernet0-7 gigabitethernet0-9 gigabitethernet0-11 s0 gigabitethernet0-13 gigabitethernet0-15 gigabitethernet0-17 gigabitethernet0-19 gigabitethernet0-21 gigabitethernet0-23 s1 tengigabitethernet1-1 tengigabitethernet1-3 tengigabitethernet1-5 tengigabitethernet1-7"
	"x x x x x x x x x x x x x x gigabitethernet0-2 gigabitethernet0-4 gigabitethernet0-6 gigabitethernet0-8 gigabitethernet0-10 gigabitethernet0-12 s0 gigabitethernet0-14 gigabitethernet0-16 gigabitethernet0-18 gigabitethernet0-20 gigabitethernet0-22 gigabitethernet0-24 s1 tengigabitethernet1-2 tengigabitethernet1-4 tengigabitethernet1-6 tengigabitethernet1-8";
}It will look like
Package: netbox-disk
Directory structure+- api - The API type
+- filters - Filters of the models
+- forms - The ModelForm, ModelFilterForm, ModelImportForm, ModelBulkEditForm
+- migrations - DB Django Migration
+- tables - The ModelBaseTable, ModelTable, RelatedModelTable
+- templates
  +- netbox_disk - The detail view of each model
    +- disk - The template content box in the Virtual Machine Model
+- views - PhysicalvolumeListView, PhysicalvolumeView, PhysicalvolumeEditView, PhysicalvolumeDeleteView, 
           PhysicalvolumeBulkImportView, PhysicalvolumeBulkEditView, PhysicalvolumeBulkDeleteViewModelsERMDriveThe drive has 4 parameter:NameExample ValueVirtualmachinetest-vm (Link zu virtual machine)IdentiferFestplatte 1ClusterSTOR2000000 (Link zu cluster)Size50GBSystemNoFilesystemThe filesystem has 1 parameter:NameExample ValuefsEXT4Linux VolumeThe linux volume has 1 parameter:NameExample Valuevg_namedockerlv_namedockerPath/var/lib/dockerFilesystemNTFS (Link zu Filesystem)Windows VolumeThe linux volume has 1 parameter:NameExample Valuedrive_name(D, E, F)FilesystemNTFS (Link zu Filesystem)Basis:pv:sizeStorage Clustervirtual_machineWindows Form:drive_name (D, E, F)filesystem (ntfs)Linux Form:vg namelv namepathfilesystemExtra Filesystem Model & als ChoiceField ausgebenBuildpoetry publish --builddocker-compose build --no-cache && docker-compose build --no-cache && docker-compose up -dgit add . && git commit -m "0.0.7.6.5.66" && git push
Package: netbox-dns
NetBox DNSNetBox DNS is a NetBox plugin for managing DNS data.FeaturesManage name serversManage DNS zone information, automatically generating SOA and NS recordsAutomatically create and update PTR records for A and AAAA recordsOptionally organize zones in views to cater for split horizon DNS and multi site deploymentsNetBox DNS is using the standardized NetBox plugin interface, so it also takes advantage of the NetBox tagging and change log features.RequirementsNetBox 3.4 or higherPython 3.8 or higherInstallation & ConfigurationInstallation$ source /opt/netbox/venv/bin/activate
(venv) $ pip install netbox-dnsConfigurationAdd the plugin to the NetBox config.~/netbox/configuration.pyPLUGINS=["netbox_dns",]To permanently mount the plugin when updating NetBox:echo netbox-dns >> ~/netbox/local_requirements.txtTo add the required netbox_dns tables to your database run the following command from your NetBox directory:./manage.py migrateFull reference:Using Plugins - NetBox DocumentationScreenshotsContributeContributions are always welcome! Please see:contributing guideLicenseMIT
Package: netbox-exporter
Netbox-ExporterNetbox-Exporteris a Python package and CLI utility for fetching a Netbox inventory and dumping it to a local directory in YAML format for human consumption.Getting startedInstallationpip install netbox_exporterUsage# netbox_exporter --help

# netbox_export \
    --dir ./netbox \
    --url https://netbox \
    --apikey 0123456789abcdefDevelopmentpipenv install --dev
Package: netbox-floorplan-plugin
netbox floorplandemosummaryA netbox plugin providing floorplan mapping capability for locations and sitesprovides graphical ability to draw racks & unracked devices on a floorplansupport for metadata such as labels, areas, walls, coloringfloorplan object mapped to sites or locations and click through rack/deviceskeyboard controls supportedexport to svginstallingInstall the package, apply migrations, then add the plugin toPLUGINS = ["netbox_floorplan"]in/opt/netbox/netbox/netbox/configuration.py:then collectstaticmentionsSpecial thanks to Ziply Fiber network automation team for helping originally helping to conceive this during the NANOG hackathon
Package: netbox-fusioninventory-plugin
netbox-fusioninventory-pluginThis plugin can add devices from fusioninventory-agent or ocsinventory-agent.fusioninventory-agent -s http://netbox.local/plugins/fusion-inventory/what working:add device nameDevice TypeSerial NumberAsset Tagtodoadd componentsadd configadd interfacesadd ipInstallationFirst, add netbox-fusioninventory-plugin to your/opt/netbox/local_requirements.txtfile. Create it if it doesn't exist.Then enable the plugin in/opt/netbox/netbox/netbox/configuration.py, like:PLUGINS=['netbox_fusioninventory_plugin',]And finally run/opt/netbox/upgrade.sh. This will download and install the plugin and update the database when necessary. Don't forget to run sudo systemctl restart netbox netbox-rq like upgrade.sh tells you!configurationYou can overwrite fields with xml content or use internal objects.PLUGINS_CONFIG={'netbox_fusioninventory_plugin':{"name":"xml:request.content.hardware.name","device_role":"object:DeviceRole:unknow","tenant":None,"manufacturer":"xml:request.content.bios.mmanufacturer","device_type":"xml:request.content.bios.mmodel","platform":"xml:request.content.hardware.osname","serial":"xml:request.content.bios.msn","asset_tag":"xml:request.content.bios.assettag","status":"str:active","site":"object:Site:unknow","location":None,"rack":None,"position":None,"face":None,"virtual_chassis":None,"vc_position":None,"vc_priority":None,"cluster":None,"comments":None,}}
Package: netbox-ged
Netbox GEDA plugin designed to faciliate the storage of documents withinNetBoxRe-written from the originalNetbox DocumentsWARNINGTHIS PLUGIN IS NOT COMPATIBLE WITHNETBOX DOCUMENTSI don't want to break your existing documents, so please don't install this plugin if you have documents stored in the original plugin.A migration script will, perhaps one day, made available, but for now you will need to manually migrate your documents.FeaturesStore documents against all NetBox modelsSort documents with tags and customisable typesSupports a wide array of common file typesCompatibilityNetBox VersionPlugin Version3.2+0.2.1InstallationA working installation of Netbox 3.2+ is required. 3.4+ is recommended.Package Installation from PyPiActivate your virtual env and install via pip:$ source /opt/netbox/venv/bin/activate
(venv) $ pip install netbox-gedTo ensure the Netbox Documents plugin is automatically re-installed during future upgrades, add the package to yourlocal_requirements.txt:# echo netbox-ged >> local_requirements.txtEnable the PluginIn the Netboxconfiguration.pyconfiguration file add or update the PLUGINS parameter, addingnetbox_documents:PLUGINS=['netbox_ged',]Apply Database MigrationsApply database migrations with Netboxmanage.py:(venv) $ python manage.py migrateRestart NetboxRestart the Netbox service to apply changes:sudo systemctl restart netboxScreenshotsComing soon