oslo.config has the idea of remote backends the two examples of backend driver are the envionment backedn https://github.com/openstack/oslo.config/blob/68cefad313bd03522e99b3de95f178... which uses envionment variables and the remote uri backedn https://github.com/openstack/oslo.config/blob/68cefad313bd03522e99b3de95f178... the docs for both can be found here https://docs.openstack.org/oslo.config/latest/reference/drivers.html i you want to use dns for configuration i think the best approch woudl be to add a dns backend drvier to oslo and work with them to upstrema it. that woudl enabel the functionaltiy in almost all openstack services. im not really going to comment on the merrit of that approch but that is the simplest way to enable that that i can think of. It shoudl not require any code change to any service that uses oslo.config for its config managment. On 09/12/2024 14:59, Shi Wei wrote:
Hi, everyone, I have a suggestion. we can use LDAP service to mange all openstak components and nodes(including physical nodes and vm nodes). Because ldap is easy to read and ldap can support DNS and DHCP service. if a node get ip address by DHCP server with ldap. You and get the Mac address information from the LDAP server. and if all components are communicated by domain name. all records are on the LDAP server. if the one node will change IP address, you can just modify on the ldap server. The ldap server can easy to backup and extend. use ldap command to export as a ldf file. you can easy to backup before update configuration. if a new component will join, you can extend the schema by .sch file.