←back to thread

261 points dban | 2 comments | | HN request time: 0.42s | source
Show context
jdoss ◴[] No.42744258[source]
This is a pretty decent write up. One thing that comes to mind is why would you write your own internal tooling for managing a rack when Netbox exists? Netbox is fantastic and I wish I had this back in the mid 2000s when I was managing 50+ racks.

https://github.com/netbox-community/netbox

replies(4): >>42744318 #>>42744734 #>>42745234 #>>42745416 #
1. matt-p ◴[] No.42744734[source]
It is not that difficult to build it into your app, if you're already storing information about hosts, networking etc. All you're really doing is expanding the scope, netbox is a fine starting point if you're willing to start there and build your systems around it, but if you've already got a system (or you need to do anything that doesn't fit netbox logic) you're probably better off just extending it.

In this case railway will need to care about a lot of extra information beyond just racks, IP addresses and physical servers.

replies(1): >>42744989 #
2. ca508 ◴[] No.42744989[source]
correct; I think the first version of our tool sprung up in the space of a couple of weekends. It wasn't planned, my colleague Pierre who wrote it just had a lot of fun building it.