this post was submitted on 24 Mar 2025
17 points (100.0% liked)

Selfhosted

45653 readers
932 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] catloaf@lemm.ee 6 points 2 weeks ago

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