Only the controller (running neutron-server) contains the ML2 plug-in ([ml2*] options in ml2_conf.ini) and schedules routers (L3 options neutron.conf). Use of ml2_conf.ini on other nodes is a bit misleading. However, prior to Liberty, configuration for L2 agents that reside on network/compute nodes commonly went into ml2_conf.ini for convenience. Liberty uses openvswitch_agent.ini or linuxbridge_agent.ini for L2 agent configuration, therefore eliminating the ml2_conf.ini file from network/compute nodes. Updates to the networking guide for Liberty will reflect this change.
On Sun, Jan 10, 2016 at 6:12 AM, Akshay Kumar Sanghai < akshaykumarsang...@gmail.com> wrote: > Hi, > I was following this link > http://docs.openstack.org/liberty/networking-guide/scenario_l3ha_ovs.html > for the setup of l3 ha using vrrp. > > I followed the kilo ubuntu installtion guide for multi node setup of > openstack. > > In the configuration for controller node, in neutron.conf file , there are > some changes for l3 ha, > like l3_ha, max_l3_agents_per_router. > But in the configuration for network node and controller node, in > neutron.conf file, there is no change introduced. Same for the ml2_conf.ini > file > > Why is this so? Does it because we have already done the configuration for > neutron.conf in controller node ? > > Thanks, > Akshay > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > >
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
