Page MenuHomePhabricator

Netbox: use Provider Networks
Closed, ResolvedPublic


The upgrade to Netbox 3.2 brings Provider Networks objects:

I don't see a huge benefit for this feature (eg. for automation), but it's easy to implement and will help documenting our infrastructure properly (eg. it allows adding X-connect and patch panel on the Z-side if needed)

Event Timeline

ayounsi triaged this task as Lowest priority.Jun 14 2022, 10:24 AM
ayounsi created this task.
Restricted Application added a subscriber: Aklapper. · View Herald Transcript
ayounsi renamed this task from NEtbox use Provider Networks to Netbox: use Provider Networks.Jun 14 2022, 10:25 AM

Assiging a provider network to a circuit causes:

Traceback (most recent call last):
  File "/srv/deployment/homer/venv-1655301229/lib/python3.9/site-packages/homer/", line 46, in __getitem__[key] = getattr(self, method_name)()
  File "/srv/deployment/homer/venv-1655301229/lib/python3.9/site-packages/homer_plugins/", line 412, in _get_junos_interfaces
    interface_config['description'] = self.interface_description(interface_name)
  File "/srv/deployment/homer/venv-1655301229/lib/python3.9/site-packages/homer_plugins/", line 358, in interface_description
    vc = termination.link_peer.device.virtual_chassis
AttributeError: 'NoneType' object has no attribute 'device'

As so far the code assumes that if there is a link_peer, there is a device.

Change 805898 had a related patch set uploaded (by Ayounsi; author: Ayounsi):

[operations/software/homer/deploy@master] wmf-netbox: don't crash with "provider network"

Change 805898 merged by Ayounsi:

[operations/software/homer/deploy@master] wmf-netbox: simplify interface description for circuits