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

Config Context assignment based on Device Type #4833

Closed
robertpenz opened this issue Jul 8, 2020 · 3 comments
Closed

Config Context assignment based on Device Type #4833

robertpenz opened this issue Jul 8, 2020 · 3 comments
Assignees
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Milestone

Comments

@robertpenz
Copy link

robertpenz commented Jul 8, 2020

Environment

  • Python version: 3.6.9
  • NetBox version: 2.8.5

Proposed Functionality

Add a dropdown box for device type for config context assignment.

Use Case

We've switches/routers from multiple vendors and use config context based on platform heavily, but some devices types of the same platform don't support a feature. We now want to override the config context for them based on that. So the platform has the feature enable and then platform + device types does disable it. Also enabling the feature only for platform + device types does not work current as we can't select device types.

Database Changes

no

External Dependencies

no

@robertpenz robertpenz changed the title Config Context Assignment based on Device Type Config Context assignment based on Device Type Jul 8, 2020
@stale
Copy link

stale bot commented Jul 22, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@stale stale bot added the pending closure Requires immediate attention to avoid being closed for inactivity label Jul 22, 2020
@jeremystretch jeremystretch added needs milestone Awaiting prioritization for inclusion with a future NetBox release type: feature Introduction of new functionality to the application and removed pending closure Requires immediate attention to avoid being closed for inactivity labels Jul 24, 2020
@jeremystretch jeremystretch added status: under review Further discussion is needed to determine this issue's scope and/or implementation and removed needs milestone Awaiting prioritization for inclusion with a future NetBox release labels Oct 14, 2020
@netbox-community netbox-community deleted a comment from ledgley Oct 22, 2020
@netbox-community netbox-community deleted a comment from kilker12 Oct 22, 2020
@jeremystretch
Copy link
Member

A reminder, per the contributing guide:

Note that comments with no substance other than a "+1" will be deleted. Please use GitHub's reactions feature to indicate your support.

@jqueuniet
Copy link

I'd like to add my support to this enhancement, with a different use case.

  • Serial console configuration. Some hardware needs COM2/ttyS1, other needs COM1/ttyS0, many of our devices don't support changing the serial port and thus, we can't standardize over one or the other.
  • Installation devices for unattended installs, especially for storage servers with loads of block devices. /dev/sda might not always be the answer and the specifics are going to be very tied to hardware parameters (number of controllers, PCI slot usage, etc).

Of course, we could use tags for this, but as this use cases are very common this means handing thousands of tags based on device types and basically duplicating the information of the latter. We can't use the platform for this either, as it is already used to store the operating system installed, and here too would mean duplicating the information of device types.

@jeremystretch jeremystretch added needs milestone Awaiting prioritization for inclusion with a future NetBox release and removed status: under review Further discussion is needed to determine this issue's scope and/or implementation labels Nov 24, 2020
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed needs milestone Awaiting prioritization for inclusion with a future NetBox release labels Mar 29, 2021
@jeremystretch jeremystretch added this to the v2.11 milestone Mar 29, 2021
@jeremystretch jeremystretch self-assigned this Mar 29, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 28, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

3 participants