Saravanan666/pypi-org huggingface dataset:
Package: nautobot-device-resources
Nautobot Device Resources pluginPlugin forNautobotto provide device resources info (CPU, RAM, ...) to Nautobot (IPPlan) Device detail view.This works by extending or replacing several core views to inject device resources information to various places with a goal of seamless integration and behaving as close to part of Nautobot Core as possible. It allows a user to interact with aDeviceand itsResourceslike it is a single model, completely removing any layering betweenDeviceandDeviceResourcesmodels.The goal is to store data on Device HW configuration directly with a Device and to allow answers to questions like:WhichDeviceshave this CPU model?How manyDevicesI have with more than 512GB RAM?WhichDeviceshave more than 16 cores?When did we change disks configuration of thisDevice?Please check theScreenshots sectionfor detailed information on this plugin capabilities.View replacementsThis plugin replaces some core views. If there is another plugin with core view replacement, please check if there is not a conflict. Replacing same view from multiple sources does not work!Views replaced:dcim:device_adddcim:device_editdcim:device_listdcim:device_importextras:objectchangeScreenshotsDevice view is extended to show resources on the right side. If any field (for exampleGPUis empty, it does not show at all).Adding or editing device form is replaced to contain DeviceResources model fields at the very bottom.ObjectChangeview shows any change toDeviceor itsDeviceResourcesdirectly, behaving like single core model. Here is a change to both Device (status) and itsDeviceResourcesshowing like single change. In reality those are 2 changes but to user it looks like this in UI:Each CPU has its own model, directly linked from Device. There is direct link to a parent Manufacturer of the CPU and all Devices with this CPU (Instancescount is direct link to Device list with a filter for this CPU).Manufacturer detail is extended to show CPUsonlywhen any CPU has this manufacturer (hidden otherwise). TheInstancescount is direct link to CPu list with this Manufacturer filter.CPUs can be added through UI, the form is accessible from Device menu underDevice Components.Device list view is replaced to have columns for all the resources fields plus it supports filtering by the resources.All CPUs can be listed and filtered in a new separate CPU model view.Accessing all this data is possible via GraphQL and REST API too, but it is not merged to the coreDevicemodel APIs as Nautobot does not allow replacing API views. In GraphQL there is a link directly fromDevicecalledresourceswhich provides the information in nested way. In REST API there is a separate endpointresourcesunder the installed plugin.DevelopmentHave running Nautobot instance (preferably in Docker) with this plugin installed.
Make sure you haveTEST_USE_FACTORIES = Truein younautobot_config.py.pipinstall-e.[all]pre-commitrun--all-files
nautobot-servermigrate
nautobot-servertestnautobot_device_resourcesBuild packagepipinstallbuild
python-mbuild--sdist--wheel
twinecheckdist/*
Package: nautobot-evpn
Nautobot EVPNThis represents a Nautobot plugin for EVPN management. This creates some resources to fully document a EVPN-based setup in Nautobot.IntegrationTo integrate this plugin, please addnautobot-changeto PLUGINS in your Nautobot settings.Migration fromnautobot-changeWe seperatednautobot-changeandnautobot-evpnat some point in time. Data is not migrated automagically due to Django restrictions.
This means some manual steps to migrate the data.Migratenautobot-changeto the latest point. We just ignore the EVPN tables at some point.Migratenautobot-vpnto 0001. This creates the basic tables.Movenautobot_change_{anycastdummyip,anycastip,ethernetsegment,ethernetsegmentmembership,vlanvrf,vlanvrflist}tonautobot_evpn_{anycastdummyip,anycastip,ethernetsegment,ethernetsegmentmembership,vlanvrf,vlanvrflist}:insertintonautobot_evpn_anycastdummyipselect*fromnautobot_change_anycastdummyip;insertintonautobot_evpn_anycastipselect*fromnautobot_change_anycastip;insertintonautobot_evpn_ethernetsegmentselect*fromnautobot_change_ethernetsegment;insertintonautobot_evpn_ethernetsegmentmembershipselect*fromnautobot_change_ethernetsegmentmembership;insertintonautobot_evpn_vlanvrfselect*fromnautobot_change_vlanvrf;insertintonautobot_evpn_vlanvrflistselect*fromnautobot_change_vlanvrflist;dropnautobot_change_anycastdummyip;dropnautobot_change_anycastip;dropnautobot_change_ethernetsegment;dropnautobot_change_ethernetsegmentmembership;dropnautobot_change_vlanvrf;dropnautobot_change_vlanvrflist;Do a full migration.Have Fun!
Package: nautobot-firewall-models
Nautobot Firewall ModelsAnAppforNautobot.OverviewA plugin forNautobotthat is meant to model layer 4 firewall policies and/or extended access control lists.ScreenshotsMore screenshots can be found in theUsing the Apppage in the documentation. Here's a quick overview of some of the app's added functionality:Try it out!This App is installed in the Nautobot Community Sandbox found over atdemo.nautobot.com!For a full list of all the available always-on sandbox environments, head over to the main page onnetworktocode.com.DocumentationFull documentation for this App can be found over on theNautobot Docswebsite:User Guide- Overview, Using the App, Getting Started.Administrator Guide- How to Install, Configure, Upgrade, or Uninstall the App.Developer Guide- Extending the App, Code Reference, Contribution Guide.Release Notes / Changelog.Frequently Asked Questions.Contributing to the DocumentationYou can find all the Markdown source for the App documentation under thedocsfolder in this repository. For simple edits, a Markdown capable editor is sufficient: clone the repository and edit away.If you need to view the fully-generated documentation site, you can build it withMkDocs. A container hosting the documentation can be started using theinvokecommands (details in theDevelopment Environment Guide) onhttp://localhost:8001. Using this container, as your changes to the documentation are saved, they will be automatically rebuilt and any pages currently being viewed will be reloaded in your browser.Any PRs with fixes or improvements are very welcome!QuestionsFor any questions or comments, please check theFAQfirst. Feel free to also swing by theNetwork to Code Slack(channel#nautobot), sign uphereif you don't have an account.
Package: nautobot-floor-plan
Nautobot Floor PlanAnAppforNautobot.OverviewThis App aids in data center management by providing the ability to create a gridded representation of the floor plan of a Nautobot Location and indicate the relative location of each Nautobot Rack within that floor plan.ScreenshotsMore screenshots can be found in theUsing the Apppage in the documentation.DocumentationFull documentation for this App can be found over on theNautobot Docswebsite:User Guide- Overview, Using the App, Getting Started.Administrator Guide- How to Install, Configure, Upgrade, or Uninstall the App.Developer Guide- Extending the App, Code Reference, Contribution Guide.Release Notes / Changelog.Frequently Asked Questions.Contributing to the DocumentationYou can find all the Markdown source for the App documentation under thedocsfolder in this repository. For simple edits, a Markdown capable editor is sufficient: clone the repository and edit away.If you need to view the fully-generated documentation site, you can build it withMkDocs. A container hosting the documentation can be started using theinvokecommands (details in theDevelopment Environment Guide) onhttp://localhost:8001. Using this container, as your changes to the documentation are saved, they will be automatically rebuilt and any pages currently being viewed will be reloaded in your browser.Any PRs with fixes or improvements are very welcome!QuestionsFor any questions or comments, please check theFAQfirst. Feel free to also swing by theNetwork to Code Slack(channel#nautobot), sign uphereif you don't have an account.
Package: nautobot-lunch
Nautobot LunchAnAppforNautobot.OverviewThis app queries Yelp to find lunch (or breakfast or dinner, we don't discriminate) near a location. The goal of this is to make it easier for field personel to find food near the site they are at. Or to re-arrange the order you want to visit sites so that you actually end up eating a good lunch.ScreenshotsMore screenshots can be found in theUsing the Apppage in the documentation. Here's a quick overview of some of the app's added functionality:DocumentationFull documentation for this App can be found over on theNautobot Docswebsite:User Guide- Overview, Using the App, Getting Started.Administrator Guide- How to Install, Configure, Upgrade, or Uninstall the App.Developer Guide- Extending the App, Code Reference, Contribution Guide.Release Notes / Changelog.Frequently Asked Questions.Contributing to the DocumentationYou can find all the Markdown source for the App documentation under thedocsfolder in this repository. For simple edits, a Markdown capable editor is sufficient: clone the repository and edit away.If you need to view the fully-generated documentation site, you can build it withMkDocs. A container hosting the documentation can be started using theinvokecommands (details in theDevelopment Environment Guide) onhttp://localhost:8001. Using this container, as your changes to the documentation are saved, they will be automatically rebuilt and any pages currently being viewed will be reloaded in your browser.Any PRs with fixes or improvements are very welcome!QuestionsFor any questions or comments, please check theFAQfirst. Feel free to also swing by theNetwork to Code Slack(channel#nautobot), sign uphereif you don't have an account.
Package: nautobot-move
Nautobot MoveNautobot Move enables you to move a device by replacing a planned device. It works best in
connection withnautobot_deepcopyto enable you to plan a move and then switch it on once you’re ready to go.
Cables and connections will be preserved from the planned device.Please note that this plugin uses internal Nautobot components, which is
explicitly discouraged by the documentation. We promise to keep the plugin up
to date, but the latest version might break on unsupported Nautobot version.
Your mileage may vary.IntegrationTo integrate the plugin, you will have to provide add it to yourPLUGINSconfiguration to yourconfiguration.py:PLUGINS = [
  "nautobot_move",
  # my other plugins
]TheNautobot plugins guideshould help you get started!UsageOnce the plugin is installed, a button labelledMovewill appear on the
detail page of devices.Once you click that button, you will be directed to a form that allows you to
choose any planned device to move this device to, preserving any connections.
When submitting, the backend will make sure the connections actually match up,
and emit a form error otherwise.The planned device that is superseded will be deleted.Have fun!
Package: nautobot-plugin-builder
draw.io-nautobot-workThere is a demo here, sadly it's a little out of date:https://youtu.be/ZwiIgBtmoMUThe goal is to making building a Nautobot plugin much easier.  The idea is you bulid the database in draw.io, then use that file to build out the plugin.the project name should be the same as the file name, but without the drawio part.   So for the filetest.drawiofile the project name would betestRunpython3 build_db_with_class.pyto build the info about the drawio file, it will prompt you for the name of the project (the name of the file minus the .drawio part)There are 2 ways to build the project:This will build out the basics of the pluginproject=BuildNautobotProject(project_name)project.build_project()This will build out:[name of the project]_plugin_filesplugin[name of the project]admin.pyfilters.pyjobs.pymodels.pyapi__init__.pyserilizers.pyurls.pyviews.pyThis way will build out everythingbuild_project()does,plus give instructions on how to install it, and build out some other needed files.project=BuildNautobotProject(project_name)project.full_build_project_with_help()In addition to everything that build_projects build this will also build:[name of the project]_plugin_filespluginsetup.py[name of the project]__init__.py
Package: nautobot-plugin-ip-services
Nautobot IP Services PluginNautobot natively provides the ability to add Services such as TCP/UDP ports that are exposed on an Interface of a Device using the "Assign service" button on the Device view. The Services can also optionally be assigned to an IP address from the Device view.  This plugin forNautobotextends the functionality by adding the ability to view and add Services from the IP Address view in IPAM.With the plugin installed, users can see the list of services associated with an IP address in IPAM.In addition, users can also use theAssign servicebutton to define new Services associated with the IP Address.  The IP address from the previous IP Address view is automatically programmed into theIP Addressesfield on the form.SetupInstall the package on the Nautobot server:pipinstallnautobot-plugin-ip-servicesAdd plugin toPLUGINSinnautobot_config.py:PLUGINS=["nautobot_plugin_ip_services",]Restart the Nautobot services:sudosystemctlrestartnautobotnautobot-workernautobot-scheduler
Package: nautobot-plugin-nornir
Nautobot Plugin NornirAn App forNautobot.OverviewA plugin forNautobot, that intends to be a small shim layer betweennornir-nautobotand other plugins. The primary abilities that the plugin provides is a native Nornir ORM based inventory and a credential manager.As of the writing of this readme, the only plugin leveraging this plugin is thegolden-config. However, future plugins are planned, such as the "network importer".That being said, there is currently little reason to install this plugin by itself, without an enabler, which can be seen represented as the white rectangles inside the yellow rectangle in the diagram above. An enabler could be a Plugin, Job, or another piece of code like a Chatops command.ScreenshotsAs previously mentioned, the plugin is mostly a shim layer, here is an example of how Nautobot Golden Config uses a Nornir Job.Try it out!This App is installed in the Nautobot Community Sandbox found over atdemo.nautobot.com! This is used within the Nautobot Golden Config plugin, when the tasks of generating config, running backup of configs, or comparing configs.For a full list of all the available always-on sandbox environments, head over to the main page onnetworktocode.com.DocumentationFull web-based HTML documentation for this app can be found over on theNautobot Docswebsite:User Guide- Overview, Using the App, Getting Started.Administrator Guide- How to Install, Configure, Upgrade, or Uninstall the App.Developer Guide- Extending the App, Code Reference, Contribution Guide.Release Notes / Changelog.Frequently Asked Questions.Contributing to the DocsYou can find all the Markdown source for the App documentation under thedocsfolder in this repository. For simple edits, a Markdown capable editor is sufficient - clone the repository and edit away.If you need to view the fully generated documentation site, you can build it withmkdocs. A container hosting the docs will be started using the invoke commands (details in theDevelopment Environment Guide) onhttp://localhost:8001. As your changes are saved, the live docs will be automatically reloaded.Any PRs with fixes or improvements are very welcome!QuestionsFor any questions or comments, please check theFAQfirst. Feel free to also swing by theNetwork to Code Slack(channel#nautobot), sign uphereif you don't have an account.
Package: nautobot-ssot-aci
Nautobot SSoT ACI - Nautobot plugin for synchronizing with Cisco ACINautobot SSoT ACI is a plugin forNautobotallowing synchronization of data from Cisco ACI into Nautobot.This plugin is built on top of theNautobot Single Source of Truth (SSoT)plugin. SSoT plugin enables Nautobot to be the aggregation point for data coming from multiple systems of record (SoR).To accomplish the synchronization of data, the SSoT ACI plugin communicates with the Cisco ACI controller, the Application Policy Infrastructure Controller (APIC). The APIC provides a central point of administration for the ACI fabric via a web dashboard or REST API.The SSoT ACI plugin eliminates the need for manually adding objects to Nautobot that have been automatically discovered by the Cisco APIC controller.  This includes information such as device model/serial numbers, node management IP addressing, and more.In addition any changes to the ACI fabric are reflected in Nautobot when the synchronization process is executed.Examples of ACI changes synchronized into Nautobot:New devices that were registered to the fabric are added to Nautobot.Devices decommissioned from the fabric are removed from Nautobot.Management IP addresses of devices added to the ACI fabric are created in Nautobot.Subnets and gateway addresses of bridge domains created in ACI are added to Nautobot as prefixes and IP addresses.Prefixes and IP addresses associated with removed ACI bridge domains are deleted from Nautobot.ACI interface description additions and updates are carried over to interface descriptions in Nautobot.The below list shows object types that are currently synchronized and how they map between systems.ACINautobotTenantTenantNode (Leaf/Spine/Controller)DeviceModelDevice TypeManagement IP address (Leaf/Spine/Controller)IP AddressBridge Domain SubnetPrefix, IP AddressInterfacesInterfaceVRFsVRFsDocumentationDocumentation is hosted on ReadTheDocs atNautobot SSoT for Cisco ACI Documentation.ScreenshotsContributingPull requests are welcomed and automatically built and tested against multiple version of Python and multiple version of Nautobot through TravisCI.The project is packaged with a light development environment based ondocker-composeto help with the local development of the project and to run the tests within TravisCI.The project is following Network to Code software development guideline and is leveraging:Black, Pylint, Bandit and pydocstyle for Python linting and formatting.Django unit test to ensure the plugin is working properly.QuestionsFor any questions or comments, please check theFAQfirst and feel free to swing by theNetwork to Code slack channel(channel #networktocode).
Sign uphere
Package: nautobot-ssot-servicenow
Nautobot Single Source of Truth -- ServiceNow Data TargetA plugin forNautobot, building atop thenautobot-ssotplugin.This plugin provides the ability to synchronize basic data from Nautobot into ServiceNow. Currently the following data is mapped and synchronized:Nautobot Manufacturer table to ServiceNow Company tableNautobot DeviceType table to ServiceNow Hardware Product Model tableNautobot Region and Site tables to ServiceNow Location tableNautobot Device table to ServiceNow IP Switch tableNautobot Interface table to ServiceNow Interface tableFor more information about general usage of the Nautobot SSoT plugin, refer toits documentation.Installation and ConfigurationThe plugin is available as a Python package in PyPI and can be installed withpipinto an existing Nautobot installation:pipinstallnautobot-ssot-servicenowThe plugin is compatible with Nautobot 1.2.0 and higherOnce installed, the plugin needs to be enabled in yournautobot_config.pyand configured appropriately:# nautobot_config.pyPLUGINS=["nautobot_ssot","nautobot_ssot_servicenow",]PLUGINS_CONFIG={"nautobot_ssot":{"hide_example_jobs":True,},"nautobot_ssot_servicenow":{"instance":os.getenv("SERVICENOW_INSTANCE"),"username":os.getenv("SERVICENOW_USERNAME"),"password":os.getenv("SERVICENOW_PASSWORD"),},}The plugin behavior can be controlled with the following list of settings:instance: The ServiceNow instance to point to (as in<instance>.servicenow.com)username: Username to access this instancepassword: Password to access this instanceThere is also the option of omitting these settings fromPLUGINS_CONFIGand instead defining them through the UI at/plugins/ssot-servicenow/config/(reachable by navigating toPlugins > Installed Pluginsthen clicking the "gear" icon next to theNautobot SSoT ServiceNowentry) using Nautobot's standard UI andsecretsfunctionality.If you configure the plugin's settings inPLUGINS_CONFIG, those values will take precedence over any configuration in the UI.Depending on the amount of data involved, and the performance of your ServiceNow instance, you may need to increase the Nautobot job execution time limits (CELERY_TASK_SOFT_TIME_LIMITandCELERY_TASK_TIME_LIMIT) so that the job can execute to completion without timing out.QuestionsFor any questions or comments, please check theFAQfirst and feel free to swing by theNetwork to Code slack channel(channel #networktocode).
Sign uphereUsageOnce the plugin is installed and configured, from the Nautobot SSoT dashboard view (/plugins/ssot/), ServiceNow will be shown as a Data Target. You can click theSyncbutton to access a form view from which you can run the Nautobot-to-ServiceNow synchronization Job. Running the job will redirect you to a NautobotJob Resultview, from which you can access theSSoT Sync Detailsview to see detailed information about the outcome of the sync Job.
Package: nautobot-ssot-vsphere
Nautobot SSoT vSphereA plugin forNautobotthat leverages the SSoT plugin to create Virtual Machines, VMInterfaces, IPAddresses, Clusters, and Cluster Groups from VMWare vSphere.The future of Virtual Machine In NautobotThere is discussion in place to that will bring big changes to VirtualMachine and VMInterface targeted for release 2.0. See theissueWhen that time comes, this application will need to be updated to handle the new core model structureInstallationThe plugin is available as a Python package in pypi and can be installed with pippipinstallnautobot-ssot-vsphereThe plugin is compatible with Nautobot 1.2.0 and higherTo ensure Nautobot SSoT vSphere is automatically re-installed during future upgrades, create a file namedlocal_requirements.txt(if not already existing) in the Nautobot root directory (alongsiderequirements.txt) and list thenautobot-ssot-vspherepackage:# echo nautobot-ssot-vsphere >> local_requirements.txtOnce installed, the plugin needs to be enabled in yournautobot_config.py# In your nautobot_config.pyPLUGINS=["nautobot_ssot_vsphere"]PLUGINS_CONFIG={"nautobot_ssot_vsphere":{"VSPHERE_URI":os.getenv("VSPHERE_URI"),"VSPHERE_USERNAME":os.getenv("VSPHERE_USERNAME"),"VSPHERE_PASSWORD":os.getenv("VSPHERE_PASSWORD"),"VSPHERE_VERIFY_SSL":is_truthy(os.getenv("VSPHERE_VERIFY_SSL",False)),},}The plugin behavior can be controlled with additional configuration settings-`VSPHERE_TYPE`Defaultsto`VMWarevSphere`-`ENFORCE_CLUSTER_GROUP_TOP_LEVEL`DefaultstoTrue
-`VSPHERE_VM_STATUS_MAP`Defaultsto{"POWERED_OFF":"Offline","POWERED_ON":"Active","SUSPENDED":"Suspended"}-`VSPHERE_IP_STATUS_MAP`Defaultsto{"PREFERRED":"Active","UNKNOWN":"Reserved"}-`VSPHERE_VM_INTERFACE_MAP`Defaultsto{"NOT_CONNECTED":False,"CONNECTED":True}-`PRIMARY_IP_SORT_BY`Defaultsto"Lowest"-`DEFAULT_USE_CLUSTERS`Defaultsto`True`-`DEFAULT_CLUSTER_NAME`Defaultsto"vSphere Default Cluster"-`DEFAULT_IGNORE_LINK_LOCAL`Defaultsto`True`To get a detailed description on each configuration setting, head over to theOverviewdocumentation.
Package: nautobot-type-reapply
Nautobot Type Re-ApplyThis plugin inserts a button to re-apply device types on a device on demand.Please note that this plugin uses internal Nautobot components, which is
explicitly discouraged by the documentation. We promise to keep the plugin up
to date, but the latest version might break on unsupported Nautobot version.
Your mileage may vary.InstallationThe plugin can be found onpypi.
You should therefore be able to install it usingpip:pip install nautobot-type-reapplyMake sure to use the same version ofpipthat manages Nautobot, so if you’ve
set up a virtual environment, you will have to use<venv>/bin/pipinstead.After that, you should be able to install the plugin as described inthe
Nautobot documentation. No
change toPLUGINS_CONFIGis necessary.UsageOnce this plugin is installed, a button will appear on devices that allows you
to reapply the device type, which will add and delete device components
according to the definition of the type.You will be asked for confirmation and all changes that will be applied will be
listed before the actual operation.Have fun!