Add IP and Resource Sync proposal document#2153
Conversation
This document outlines the proposal for IP and Resource Sync (ipsync) between Nautobot and Undercloud sites, detailing the motivation, goals, requirements, and implementation plans for achieving two-way synchronization of IPs and VLANs.
Removed an alternative consideration regarding full two-way sync due to potential sync loops.
cardoe
left a comment
cardoe
left a comment
There was a problem hiding this comment.
Overall I agree here. This is written up like a ADR (which is great). We should have a section for these in the docs so that it'll pass.
|
|
||
| This isn't settled yet, and it decides how the site talks to the operator: | ||
|
|
||
| - **If sites can reach the management cluster's API directly:** no new plumbing needed. The site just runs a scoped Kubernetes client (limited to its own site's CRs) reading `spec` and writing `status`. |
There was a problem hiding this comment.
Well the management cluster is the ArgoCD / logging environment. Not where Nautobot is running. The sites can reach the global cluster where Nautobot and Nautobot operator are running.
|
|
||
| #### Subtasks | ||
|
|
||
| - Confirm with Abhimanyu/Haseeb whether sites can reach the management cluster directly (blocks the interface design). |
There was a problem hiding this comment.
Just want to check which cluster you mean
|
We have to be very careful here. First we need to understand the difference between static and dynamic data. Nautobot is not the source of truth for many things. i.e for dynamic data:
As for IPs, this is more complicated. For OOB IP ranges, we'll use static generator which @stevekeay is working on as well as for other static data such as:
I think what we need to decide right now is what data needs to be in Nautobot and make a clear separation on static vs dynamic data and what mechanisms we'll be in charge of syncing that. Nautobotop was meant to deal with static data only, which would use the data from the file generated by static generator. The architecture of this is captured in https://docs.undercloud.rackspace.net/architecture-decisions/adr027-automated-cab-addition/ |
3 participants
This document outlines the proposal for IP and Resource Sync (ipsync) between Nautobot and Undercloud sites, detailing the motivation, goals, requirements, and implementation plans for achieving two-way synchronization of IPs and VLANs.