Description of problem: NeutronL3AgentAvailabilityZone and NeutronDhcpAgentAvailabilityZone should be role specific. Those parameters assign the availability zone to l3 agents or dhcp agents. However, it is not role specific. That means all l3 agents and dhcp agens have the same configuration even though the user would like to configure different values to each l3/dhcp agent. Version-Release number of selected component (if applicable): OSP17.0.1 How reproducible: Always Steps to Reproduce: 1. Deploy overcloud with those parameters. 2. 3. Actual results: All l3-agent and dhcp agents have the same values. Expected results: Those parameters should work as role specific parameters. Additional info: The parameters will be used with ML2/OVS which will be removed from OSP18. However, this should be fixed.
Hello Keigo: The Neurton configuration provides only one single configuration option per agent type (translated from THT "neutron::agents::l3::availability_zone" or "neutron::agents::dhcp::availability_zone"). It is not possible to configure a different value per resource because the configuration file cannot consider any resource during the initialization. You can define the "availability-zone-hint" value per router (L3) and per network (DHCP) [1][2]. But this is a resource creational parameter and not a configuration parameter. Is this what you are looking for? Regards. [1]https://docs.openstack.org/neutron/queens/admin/config-az.html [2]https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.2/html/networking_guide/use-azs-make-network-nodes-ha_rhosp-network#assign-azs-network-resources_config_azs