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.

Sign up for GitHub

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

Jump to bottom

Include number of subnets in vlan table #334

Open
lukasjuhrich opened this issue Sep 21, 2019 · 0 comments
Open

Include number of subnets in vlan table #334

lukasjuhrich opened this issue Sep 21, 2019 · 0 comments
Labels
enhancement 🔨 web/ui Things relating to Flask routes and Jinja templates

Comments

@lukasjuhrich
Copy link
Collaborator

The vlan table (infrastructure/vlans) should provide information about how many subnets reference this vlan. In the future, this information may be contrasted with the number of isid-mappings.

Since every vlan should correspond to ≥1 subnets, this would not really provide new information – however, it might be a good sanity check of the vlan pool.

For instance:

# Name VID Ref by
1 Wu1 11 1 Subnet(s)
2 Wu5 15 1 Subnet(s)
3 Vlan3 11001 1 Isid(s)
4 Vlan4 11002 Nothing!
@lukasjuhrich lukasjuhrich added enhancement 🔨 web/ui Things relating to Flask routes and Jinja templates labels Sep 21, 2019
@lukasjuhrich lukasjuhrich mentioned this issue Sep 21, 2019
Open
5 tasks
lukasjuhrich added a commit that referenced this issue Feb 10, 2021
@lukasjuhrich
Implement room address suggestion
3c914d4 
Rooms of the same building, especially one that'? about to be created,
usually have the same address data (except for `addition`).

Not providing the user this preexisting data would be inefficient.

Refs #334
lukasjuhrich added a commit that referenced this issue Feb 10, 2021
@lukasjuhrich
Implement room address suggestion
41fcd44 
Rooms of the same building, especially one that'? about to be created,
usually have the same address data (except for `addition`).

Not providing the user this preexisting data would be inefficient.

Refs #334
lukasjuhrich added a commit that referenced this issue Feb 10, 2021
@lukasjuhrich
Implement room address suggestion
383e81a 
Rooms of the same building, especially one that'? about to be created,
usually have the same address data (except for `addition`).

Not providing the user this preexisting data would be inefficient.

Refs #334
lukasjuhrich added a commit that referenced this issue Feb 10, 2021
@lukasjuhrich
Implement room address suggestion
4767a4f 
Rooms of the same building, especially one that'? about to be created,
usually have the same address data (except for `addition`).

Not providing the user this preexisting data would be inefficient.

Refs #334
lukasjuhrich added a commit that referenced this issue Feb 10, 2021
@lukasjuhrich
Implement room address suggestion
cc6f68f 
Rooms of the same building, especially one that'? about to be created,
usually have the same address data (except for `addition`).

Not providing the user this preexisting data would be inefficient.

Refs #334
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement 🔨 web/ui Things relating to Flask routes and Jinja templates
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lukasjuhrich