Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Cable and switch management under data center #2225
Ralph NG is a very good project. I love it.
But i miss under data center a management for switch and cable documentation.
Thank you for your amazing work.
Have any update about this feature ? Clearly, in term of datacenter management, it would be great to have this feature developed. In order to help or test, is there an available branch to pull/push some fix/feature ?
We are currently testing Ralph 'ng' branch but we can checkout another one for testing purpose.
Keep up the good work,
In fact, we are thinking about switch from racktable to ralph-ng. We already setup it for testing purposes and we find it great. But there are some missing features that we would like to help to develop or specify. For us there are 3 missing features that blocks our final decision:
So, for cable path management:
We manage every day a lot of racks/cabinets and we need a tool that reference cable plug between devices in order to see the cable path. Typically, we would like to be able to get setup cables on a patch panel and see where each cable go (another patch panel ? switch ? router ? server ? etc). I think that other providers like us could be interested with this feature. As cable can be referenced into Ralph like servers or switch are, it could be easier to 'map' a physical architecture with these informations. Moreover, for physical parts (bare metal servers, switch, routers, etc) we can imagine that could replace the 'parent' information taht we find into assets (but it introduce the multi-parent topic).
I'm only slightly familiar with Ralph at this point. I had been looking into using Racktables to replace our cobbled-together spreadsheets and text configs, but ran across Ralph and like that it's more active and has a real API. The ability to model network connections well is the only major "missing" feature
I would mostly follow Racktables' example for this:
I think few people are crazy enough to track individual cables, so mostly it would just need cable type, optionally color, and length.
Bonus points for: having an actual port/connector type on each end and for the cable. This mostly makes sense for environments with interconnections among switches where there can be a variety of connections and cables. 10Gbase-T, 1Gbase-T, 40GBase-SR4, TwinAX, etc.