New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cable and switch management under data center #2225

Open
renki81 opened this Issue Feb 18, 2016 · 10 comments

Comments

Projects
None yet
6 participants
@renki81

renki81 commented Feb 18, 2016

Hi Developers

Ralph NG is a very good project. I love it.

But i miss under data center a management for switch and cable documentation.
Switch management is not so possible. But under datacenter > hardware > Generic components, would i find it great when i can here create a custom field. For example a new field for cable number and cable color or whatever.

@mkurek

This comment has been minimized.

Show comment
Hide comment
@mkurek

mkurek Feb 18, 2016

Member

Hi @renki81

About custom fields, we're now considering different options for that, check #2158 for details.
In terms of switch management, in Ralph 2.0 we had something called connections (between devices) and we'll probably expand this mechanism (definitely port it to Ralph NG).

Member

mkurek commented Feb 18, 2016

Hi @renki81

About custom fields, we're now considering different options for that, check #2158 for details.
In terms of switch management, in Ralph 2.0 we had something called connections (between devices) and we'll probably expand this mechanism (definitely port it to Ralph NG).

@renki81

This comment has been minimized.

Show comment
Hide comment
@renki81

renki81 Feb 18, 2016

Hi @mkurek

Thank you for your fast reply and information.

renki81 commented Feb 18, 2016

Hi @mkurek

Thank you for your fast reply and information.

@blacknon

This comment has been minimized.

Show comment
Hide comment
@blacknon

blacknon Aug 30, 2016

Hi Developers

I also have waiting for this functionality is implemented.
Is there progress anything?

blacknon commented Aug 30, 2016

Hi Developers

I also have waiting for this functionality is implemented.
Is there progress anything?

@vi4m

This comment has been minimized.

Show comment
Hide comment
@vi4m

vi4m Aug 30, 2016

Member

Yes, we have plans to start working on this feature in October.

Member

vi4m commented Aug 30, 2016

Yes, we have plans to start working on this feature in October.

@blacknon

This comment has been minimized.

Show comment
Hide comment
@blacknon

blacknon commented Sep 4, 2016

Thanks!

@PANZERBARON

This comment has been minimized.

Show comment
Hide comment
@PANZERBARON

PANZERBARON Jan 16, 2017

Hello,

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,

Tib

PANZERBARON commented Jan 16, 2017

Hello,

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,

Tib

@vi4m

This comment has been minimized.

Show comment
Hide comment
@vi4m

vi4m Jan 16, 2017

Member

We use one branch (ng) for the most recent changes, so it should be the base one for work.

Member

vi4m commented Jan 16, 2017

We use one branch (ng) for the most recent changes, so it should be the base one for work.

@vi4m

This comment has been minimized.

Show comment
Hide comment
@vi4m

vi4m Jan 16, 2017

Member

We're still waiting for some input, how this feature should be implemented in details. Any ideas / needs ?

Member

vi4m commented Jan 16, 2017

We're still waiting for some input, how this feature should be implemented in details. Any ideas / needs ?

@PANZERBARON

This comment has been minimized.

Show comment
Hide comment
@PANZERBARON

PANZERBARON Jan 20, 2017

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:

  • Cable path. Our current discussion topic.
  • Ip/Network range management (like racktable way of linking).
  • Hardcoded asset's components.

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

Tib

PANZERBARON commented Jan 20, 2017

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:

  • Cable path. Our current discussion topic.
  • Ip/Network range management (like racktable way of linking).
  • Hardcoded asset's components.

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

Tib

@SesquipedalianDefenestrator

This comment has been minimized.

Show comment
Hide comment
@SesquipedalianDefenestrator

SesquipedalianDefenestrator Jan 31, 2017

Contributor

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:
Each network connection has an optional "Remote Asset" and "Cable type". Remote Asset is a network port on another host/switch. So, host1's eth0 might have a remote asset of "switch1 ge1/1/", and switch1's ge1/1/1 now has a remote asset of "host1 eth0". In the UI, it should have a link to the remote asset.

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.

Contributor

SesquipedalianDefenestrator commented Jan 31, 2017

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:
Each network connection has an optional "Remote Asset" and "Cable type". Remote Asset is a network port on another host/switch. So, host1's eth0 might have a remote asset of "switch1 ge1/1/", and switch1's ge1/1/1 now has a remote asset of "host1 eth0". In the UI, it should have a link to the remote asset.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment