starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Module Type Profiles for interfaces #11217

New Issue
Closed
opened 2025-12-29 21:42:03 +01:00 by adam · 5 comments
adam commented 2025-12-29 21:42:03 +01:00
Owner
Copy Link

Originally created by @harryajc on GitHub (May 24, 2025).

Originally assigned to: @harryajc on GitHub.

NetBox version

v.4.3.1

Feature type

Data model extension

Proposed functionality

My request is for an additional default module profile to be added for network interface cards, (not sure on the exact naming).

As part of the 4.3.0 module type profiles were added, however there doesn't seem to be a default defined profile that covers interface modules. Like linecard modules for routers or PCIE network interface cards for servers.

Use case

Should allow for most module types to be profiled under one of the default profiles, and allow for grouping all these types of modules by their module profile as can be done with the other module profiles.
We are also looking to added support for these new module profiles for modules that have been modelled within the devicetype-library by adding this as a default profile we can then enforce that modules defined within that repository have their module profiles defined.

Database changes

No response

External dependencies

No response

Originally created by @harryajc on GitHub (May 24, 2025). Originally assigned to: @harryajc on GitHub. ### NetBox version v.4.3.1 ### Feature type Data model extension ### Proposed functionality My request is for an additional default module profile to be added for network interface cards, (not sure on the exact naming). As part of the 4.3.0 module type profiles were added, however there doesn't seem to be a default defined profile that covers interface modules. Like linecard modules for routers or PCIE network interface cards for servers. ### Use case Should allow for most module types to be profiled under one of the default profiles, and allow for grouping all these types of modules by their module profile as can be done with the other module profiles. We are also looking to added support for these new module profiles for modules that have been modelled within the [devicetype-library](https://github.com/netbox-community/devicetype-library) by adding this as a default profile we can then enforce that modules defined within that repository have their module profiles defined. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: featurecomplexity: low labels 2025-12-29 21:42:03 +01:00
adam closed this issue 2025-12-29 21:42:03 +01:00
adam commented 2025-12-29 21:42:03 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (May 27, 2025):

@harryajc can you please expand upon this in your feature request writeup, it is not clear from this what exactly you are asking for.

The information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@arthanson commented on GitHub (May 27, 2025): @harryajc can you please expand upon this in your feature request writeup, it is not clear from this what exactly you are asking for. The information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.
adam commented 2025-12-29 21:42:04 +01:00
Author
Owner
Copy Link

@harryajc commented on GitHub (May 28, 2025):

Hi @arthanson

Hope that makes more sense.

@harryajc commented on GitHub (May 28, 2025): Hi @arthanson Hope that makes more sense.
adam commented 2025-12-29 21:42:04 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (May 29, 2025):

Can you please specify exactly what you would want to see in this interface profile, maybe even drafting the model fields you would want to see. This is currently not enough information to proceed with.

@arthanson commented on GitHub (May 29, 2025): Can you please specify exactly what you would want to see in this interface profile, maybe even drafting the model fields you would want to see. This is currently not enough information to proceed with.
adam commented 2025-12-29 21:42:05 +01:00
Author
Owner
Copy Link

@harryajc commented on GitHub (Jun 2, 2025):

Hi Arthanson,

Hope this works.

{
    "name": "Expansion card",
    "schema": {
        "properties": {
            "Connector type": {
                "type": "string",
                "description": "Connector type e.g. PCIe x4"
            },
            "bandwidth": {
                "type": "integer",
                "description": "Total Bandwidth for this module"
            }
        }
    }
}
@harryajc commented on GitHub (Jun 2, 2025): Hi Arthanson, Hope this works. ``` { "name": "Expansion card", "schema": { "properties": { "Connector type": { "type": "string", "description": "Connector type e.g. PCIe x4" }, "bandwidth": { "type": "integer", "description": "Total Bandwidth for this module" } } } } ```
adam commented 2025-12-29 21:42:05 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Jun 9, 2025):

This seems like a reasonable request for an example module type profile. We do not expect to be adding more of these in the future, however.

This should be placed in the dcim/migrations/initial_data/module_type_profiles directory, next to the other initial module type profiles where it will be picked up by the 0206_load_module_type_profiles data migration if it has not already been run. If the migration has already been run, then users will need to import or enter this manually.

@jnovinger commented on GitHub (Jun 9, 2025): This seems like a reasonable request for an example module type profile. We do not expect to be adding more of these in the future, however. This should be placed in the [`dcim/migrations/initial_data/module_type_profiles` directory](https://github.com/netbox-community/netbox/tree/main/netbox/dcim/migrations/initial_data/module_type_profiles), next to the other initial module type profiles where it will be picked up by the `0206_load_module_type_profiles` data migration if it has not already been run. If the migration has already been run, then users will need to import or enter this manually.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label complexity: low status: accepted type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#11217
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?