Skip to content
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

Add functionality for recording Rack Types for netbox 4.1.0+ #2618

Open
justin-davisibm opened this issue Jan 8, 2025 · 5 comments
Open
Assignees
Labels
status: gathering feedback Further discussion is needed to determine this issue's scope and/or implementation

Comments

@justin-davisibm
Copy link

I suppose this is more of a discussion on formatting as any logic would likely live in https://github.com/netbox-community/Device-Type-Library-Import, but I'd like to propose the following:

  • Add new top level folder rack-types
  • Children folders will follow the same {{ manufacturer_name }} format as device-types and module-types does today.
  • Add new schema that supports the allowed field options for rack types in Netbox:
    • manufacturer (required)
    • model (required)
    • slug (required)
    • width (required)
    • u_height (required)
    • form_factor (2-post-frame, 4-post-frame, 4-post-cabinet, wall-frame, wall-frame-vertical, wall-cabinet, wall-cabinet-vertical)
    • starting_unit
    • desc_units (boolean)
    • outer_width
    • outer_depth
    • outer_unit (mm, in)
    • mounting_depth
    • weight
    • max_weight
    • weight_unit (kg, g, lb, oz)
    • description
    • comments
    • tags
    • id

This will allow a feature request to Device-Type-Library-Import to support Rack types as an importable object.

@BCurrell
Copy link
Contributor

If this gets approved / added, I have access to the following 2 rack types I'd be willing to add files for:

@phillf
Copy link
Contributor

phillf commented Jan 25, 2025

@harryajc, is this possible in current state devicetype-library or is this something that has to come down from upstream netbox?

@danner26
Copy link
Member

danner26 commented Feb 1, 2025

Hey all, could you submit an example file built out for this? Attach it here and I will review. This might work well and if so we would be happy to help build it out/review what you build out

@danner26 danner26 added the status: gathering feedback Further discussion is needed to determine this issue's scope and/or implementation label Feb 1, 2025
@danner26 danner26 self-assigned this Feb 1, 2025
@BCurrell
Copy link
Contributor

BCurrell commented Feb 1, 2025

Example / actual file for Startech 42U 4 poster:

---
manufacturer: Startech
model: 4 Post 42U
slug: startech-4postrack42
width: 19
u_height: 42
form_factor: 4-post-frame
description: Startech 4 Post 42U 19in rack with optional casters
starting_unit: 1
outer_width: 600
outer_unit: mm
# Adjustable depth, do we want the minimum or maximum depth?
# Minimum adjusted depth
mounting_depth: 560
# Maximum adjusted depth
# mounting_depth: 1017
weight: 38.5
# Different weights between stationary and on casters, which one?
# Stationary
# max_weight: 600
# Rolling
max_weight: 360
weight_unit: kg

Couple of possible options for mounting_depth and max_weight, not sure which option would be best. And I'm not sure if I need to add a manufacturer somewhere, or if it handles that automatically?

There's no field for this currently, but maybe somewhere we could also put a URL to the product page / specs? Could add that to comments I guess.

@phillf
Copy link
Contributor

phillf commented Feb 2, 2025

Adding a field for spec sheet/datasheet is a good idea.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: gathering feedback Further discussion is needed to determine this issue's scope and/or implementation
Projects
None yet
Development

No branches or pull requests

4 participants