-
Notifications
You must be signed in to change notification settings - Fork 264
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 abstract location model #774
Comments
I loveeeeee this idea. Imagine having This could open the door for a myriad of custom locations like:
etc... Questions/concerns:
|
We should probably have a flag or mechanism on a |
Yes.
I would think both for now.
I'm not following this. As this is proposed now, this would just be wherever there is region/site today, there would now be location. Wouldn't add more to it than that for now.
Don't know. But automatically would be the intention. I think it's too early to define that because we don't know what the end-state would be.
This makes sense. |
Any thought about rebranding 'Rack Groups' for this purpose? Many users will be using rack groups in this way currently and seems to achieve the goal with out adding additional models :) |
Rebranding brings in other changes that need to happen then, such as updates to Ansible modules. Instead of a rebranding, a new model with a method to migrate may make sense. |
I think For our use case we need to know location of But |
@jedelman8 - is this moving along? We have some pretty serious need for a more flexible model. Eg we want to be able to create locations like 'vpc' and 'room,' and we wan tto be able to assign prefixes to any location object. I think we've discussed this before. Is there a target version? |
This structure follows our requirement - the model would allow to represent physical location of the device/unit. |
@lampwins can you provide an update on thought process and timing based on @cmacnevin question above? |
@itdependsnetworks @jdrew82 |
Initial Locations implementation was done by #1891. Known remaining action items:
Longer-term action items:
|
All remaining actions have now been resolved. #2516 will come in as a UX improvement for the UI overhaul. |
User Stories
As Nelly the Network Engineer,
I want...
So that...
I know this is done when...
Austin the Network Automation Engineer
I want…
So that…
MVP
Future
I know this is done when...
Questions
Additional Context
For more context, please see #613 and #230
This issue will supersede #613 and #230 (eventually replace) and provide a foundation for a new abstract organizational model. In the short-term, a new location model (that includes location type) is proposed that links to all objects that already link to region and site. Similar to region, this will be an optional attribute users can take advantage to further define the location relationship to other objects.
The text was updated successfully, but these errors were encountered: