homer


Namehomer JSON
Version 0.6.5 PyPI version JSON
download
home_pagehttps://gerrit.wikimedia.org/r/plugins/gitiles/operations/software/homer
SummaryConfiguration manager for network devices
upload_time2023-12-18 11:18:34
maintainer
docs_urlNone
authorRiccardo Coccioli
requires_python>=3.9
licenseGPLv3+
keywords network switch router configuration deploy
VCS
bugtrack_url
requirements No requirements were recorded.
Travis-CI No Travis.
coveralls test coverage No coveralls.
            Homer - Configuration manager for network devices
-------------------------------------------------

Homer allows to manage the lifecycle of the configuration for network devices, generating and deploying their
configuration.

The configuration generation is based on ``YAML`` files to define variables and ``Jinja2`` templates.
The ``YAML`` files allow for hierarchical override of variables based on the device role, site or hostname.
Once generated, the configuration can be deployed to the selected devices.

The device list can either live hardcoded in the configuration files or be dynamically gathered from Netbox.
When using Netbox as inventory both the Virtual Chassis endpoint and the Device endpoint are used to select
all the devices that matches the configured whitelist of device roles and statuses.

Also when using Netbox as inventory for each device additional metadata is exposed to the templates, namely:

- ``role``: device role slug
- ``site``: device site slug
- ``type``: device type slug
- ``ip4``: primary IPv4 without netmask
- ``ip6``: primary IPv6 without netmask
- ``netbox_object``: the Netbox device object. Directly exposed data should always be preferred in templates.
  It is exposed to not be a blocker in case some additional data is needed that is not yet exposed by
  Homer explicitely. It could be removed in a future release.

If any metadata is present in the ``YAML`` inventory file when using Netbox as inventory, this additional metadata
ie exposed too to the templates, with the Netbox values having precedence in case of overlapping keys.

When using Netbox to gather dynamic configuration, it's also possible to write a custom plugin in the form of a
Python module that implements a class called ``NetboxDeviceDataPlugin`` that inherits from
`homer.netbox.BaseNetboxDeviceData` and is in the Python ``PATH``.
Assuming that the plugin class implements a method named ``_get_name``, it will be accessible within the templates
with ``netbox.device_plugin.name``.

            

Raw data

            {
    "_id": null,
    "home_page": "https://gerrit.wikimedia.org/r/plugins/gitiles/operations/software/homer",
    "name": "homer",
    "maintainer": "",
    "docs_url": null,
    "requires_python": ">=3.9",
    "maintainer_email": "",
    "keywords": "network,switch,router,configuration,deploy",
    "author": "Riccardo Coccioli",
    "author_email": "rcoccioli@wikimedia.org",
    "download_url": "https://files.pythonhosted.org/packages/44/7d/22cfeec52f16ad53af1551e34b3c818bb2ddeac89ba9dd8eda3250675a02/homer-0.6.5.tar.gz",
    "platform": "GNU/Linux",
    "description": "Homer - Configuration manager for network devices\n-------------------------------------------------\n\nHomer allows to manage the lifecycle of the configuration for network devices, generating and deploying their\nconfiguration.\n\nThe configuration generation is based on ``YAML`` files to define variables and ``Jinja2`` templates.\nThe ``YAML`` files allow for hierarchical override of variables based on the device role, site or hostname.\nOnce generated, the configuration can be deployed to the selected devices.\n\nThe device list can either live hardcoded in the configuration files or be dynamically gathered from Netbox.\nWhen using Netbox as inventory both the Virtual Chassis endpoint and the Device endpoint are used to select\nall the devices that matches the configured whitelist of device roles and statuses.\n\nAlso when using Netbox as inventory for each device additional metadata is exposed to the templates, namely:\n\n- ``role``: device role slug\n- ``site``: device site slug\n- ``type``: device type slug\n- ``ip4``: primary IPv4 without netmask\n- ``ip6``: primary IPv6 without netmask\n- ``netbox_object``: the Netbox device object. Directly exposed data should always be preferred in templates.\n  It is exposed to not be a blocker in case some additional data is needed that is not yet exposed by\n  Homer explicitely. It could be removed in a future release.\n\nIf any metadata is present in the ``YAML`` inventory file when using Netbox as inventory, this additional metadata\nie exposed too to the templates, with the Netbox values having precedence in case of overlapping keys.\n\nWhen using Netbox to gather dynamic configuration, it's also possible to write a custom plugin in the form of a\nPython module that implements a class called ``NetboxDeviceDataPlugin`` that inherits from\n`homer.netbox.BaseNetboxDeviceData` and is in the Python ``PATH``.\nAssuming that the plugin class implements a method named ``_get_name``, it will be accessible within the templates\nwith ``netbox.device_plugin.name``.\n",
    "bugtrack_url": null,
    "license": "GPLv3+",
    "summary": "Configuration manager for network devices",
    "version": "0.6.5",
    "project_urls": {
        "Homepage": "https://gerrit.wikimedia.org/r/plugins/gitiles/operations/software/homer"
    },
    "split_keywords": [
        "network",
        "switch",
        "router",
        "configuration",
        "deploy"
    ],
    "urls": [
        {
            "comment_text": "",
            "digests": {
                "blake2b_256": "09e70ea0dcf494ca1fa706a78a5c6b7d3f52470dca720c3f76d1a087bb3fbce0",
                "md5": "497179fb1dd036540c9e4cd546a26407",
                "sha256": "caa75074a92ac3f4d716c6a30df5343479950ab4ebe712c2bd14d8fb0de5ebbf"
            },
            "downloads": -1,
            "filename": "homer-0.6.5-py3-none-any.whl",
            "has_sig": false,
            "md5_digest": "497179fb1dd036540c9e4cd546a26407",
            "packagetype": "bdist_wheel",
            "python_version": "py3",
            "requires_python": ">=3.9",
            "size": 33095,
            "upload_time": "2023-12-18T11:18:32",
            "upload_time_iso_8601": "2023-12-18T11:18:32.141209Z",
            "url": "https://files.pythonhosted.org/packages/09/e7/0ea0dcf494ca1fa706a78a5c6b7d3f52470dca720c3f76d1a087bb3fbce0/homer-0.6.5-py3-none-any.whl",
            "yanked": false,
            "yanked_reason": null
        },
        {
            "comment_text": "",
            "digests": {
                "blake2b_256": "447d22cfeec52f16ad53af1551e34b3c818bb2ddeac89ba9dd8eda3250675a02",
                "md5": "5266cc893b293861825df319ac588857",
                "sha256": "08ca80053e56560d942f9dc840b4649eb841413671d5b1bc9f126de0a453b42a"
            },
            "downloads": -1,
            "filename": "homer-0.6.5.tar.gz",
            "has_sig": false,
            "md5_digest": "5266cc893b293861825df319ac588857",
            "packagetype": "sdist",
            "python_version": "source",
            "requires_python": ">=3.9",
            "size": 55899,
            "upload_time": "2023-12-18T11:18:34",
            "upload_time_iso_8601": "2023-12-18T11:18:34.207889Z",
            "url": "https://files.pythonhosted.org/packages/44/7d/22cfeec52f16ad53af1551e34b3c818bb2ddeac89ba9dd8eda3250675a02/homer-0.6.5.tar.gz",
            "yanked": false,
            "yanked_reason": null
        }
    ],
    "upload_time": "2023-12-18 11:18:34",
    "github": false,
    "gitlab": false,
    "bitbucket": false,
    "codeberg": false,
    "lcname": "homer"
}
        
Elapsed time: 0.15127s