Selfhosted

45450 readers

246 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

[email protected]

Combining Netbox and Ansible (feddit.org)

submitted 1 week ago* (last edited 1 week ago) by [email protected] to c/[email protected]

3 comments fedilink hide all child comments

I'm new to netbox and as far as I can tell there are two ways to combine Netbox with ansible.

Automate network and Netbox with ansible. A playbook would configure a switch port and then use the Netbox ansible collection to modify Netbox to reflect the change. All changes go through Ansible.
Use Netbox as the data source for ansible. A playbook pulls the switch configuration from Netbox and applies it to the switch using ansible. All changes go through Netbox.

What would be preferred? Both solve the Problem of having to change everything twice.

top 3 comments

sorted by: hot top controversial new old

[–] [email protected] 6 points 1 week ago

The latter. Ansible isn't for storing configs, it's for applying them.

[–] [email protected] 5 points 1 week ago

Go with the second option.

Having Netbox as your source of truth is what we do and we can easily track changes

[–] [email protected] 1 points 1 week ago

Depending on what you need either first or second solution may be better. In my company we use Netbox fork Nautobot along with Ansible. It's Ansible that initiates the change and fills all the data properties in Nautobot. This way Ansible can also raise and close relevant change ticket at the right time. With your second solution it would be more difficult for us to properly work with change tickets in compliant way. If you ever intend to take compliance and ticketing system into account, then I would recommend going with first solution, otherwise both solutions are fine to me.