I deployed a new cluster with above variables and l3 agent and dhcp agent exists on expected nodes. But ovs agent is running on each node. So the CONFIG_NEUTRON_OVS_HOST doesn't work. On Tue, Jun 17, 2014 at 2:40 PM, Kun Huang <gareth(a)openstacker.org&gt; wrote: > hi all > > I have some questions about using RDO deploy neutron (based on > ovs). I need: > > node1: - neutron server > > node2 (all others): - dhcp agent - ovs agent - l3 agent > > Now in my understanding, CONFIG_NEUTRON_SERVER_HOST manages > neutron server, CONFIG_NEUTRON_DHCP_HOSTS manages dhcp agent, > CONFIG_NEUTRON_L3_HOSTS manages l3 agent, and > CONFIG_NEUTRON_OVS_HOST l2/ovs agent. Are those correct? > > Another question is after reading codes in neutron_350.py, I > found CONFIG_NEUTRON_L3_HOSTS may not work, because of [0]. It is > same about CONFIG_NEUTRON_OVS_HOST [1]. > > So are there some principles like "l2 agent must be installed on > same host with neutron server" > > [0] > https://github.com/stackforge/packstack/blob/master/packstack/plugins/neu... > >

_______________________________________________ Rdo-list mailing list Rdo-list(a)redhat.com https://www.redhat.com/mailman/listinfo/rdo-list -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCgAGBQJToBRMAAoJEC5aWaUY1u573KQH/3K6Rhu6PbzWfqWvxYje+7O6 FzVeY7AvJDx41ddm6p2WaG1L49EPGBb9y450A4lgMNR8WIR57WD1x9aCJutMgOIm fv0o4S5mxvcPG3MJ0ahcUNbdrmr5oQY3dnYJB/36uh4JXczE7utpDO5W6yxk1pnT ywHXgr7Yy6jeYWj2JIkK6O8zTKNhs6brwQYSD+tatVMzLsI4yH3TbIBpVE6FAVsH jH/988S42W8VKycE4CeoGGKeTXKY2xHphnnsLiL/ptGvQcP8rcOF4oNRZknql2Xf zD0vEN48nqfji6bsTbQE480HtwziDFUcq1IDHnxuC87D1oTei/i9TudKQzhjCOg= =l70v -----END PGP SIGNATURE-----

Thanks Ihar It is understandable to split neutron (API) server and L2 agent. But is it necessary to deploy nova-compute and L2 agent on same node? That reference doesn't explain the reason. On Tue, Jun 17, 2014 at 6:11 PM, Ihar Hrachyshka <ihrachys(a)redhat.com&gt; wrote: Quoting [1], "L2 agent should run on all machines except for the Neutron service machine (unless Neutron service resides with other component in the same machine)." That's what you observe. [1]: http://openstack.redhat.com/Neutron_with_OVS_and_VLANs On 17/06/14 10:23, Kun Huang wrote: >>> I deployed a new cluster with above variables and l3 agent >>> and dhcp agent exists on expected nodes. But ovs agent is >>> running on each node. So the CONFIG_NEUTRON_OVS_HOST doesn't >>> work. >>> >>> On Tue, Jun 17, 2014 at 2:40 PM, Kun Huang >>> <gareth(a)openstacker.org&gt; wrote: >>>> hi all >>>> >>>> I have some questions about using RDO deploy neutron (based >>>> on ovs). I need: >>>> >>>> node1: - neutron server >>>> >>>> node2 (all others): - dhcp agent - ovs agent - l3 agent >>>> >>>> Now in my understanding, CONFIG_NEUTRON_SERVER_HOST >>>> manages neutron server, CONFIG_NEUTRON_DHCP_HOSTS manages >>>> dhcp agent, CONFIG_NEUTRON_L3_HOSTS manages l3 agent, and >>>> CONFIG_NEUTRON_OVS_HOST l2/ovs agent. Are those correct? >>>> >>>> Another question is after reading codes in neutron_350.py, >>>> I found CONFIG_NEUTRON_L3_HOSTS may not work, because of >>>> [0]. It is same about CONFIG_NEUTRON_OVS_HOST [1]. >>>> >>>> So are there some principles like "l2 agent must be >>>> installed on same host with neutron server" >>>> >>>> [0] >>>> https://github.com/stackforge/packstack/blob/master/packstack/plugins/neu... >>>> >>>> >>>>

https://github.com/stackforge/packstack/blob/master/packstack/plugins/neu... >>> >>>

>>> list Rdo-list(a)redhat.com >>> https://www.redhat.com/mailman/listinfo/rdo-list >>> > > _______________________________________________ Rdo-list mailing > list Rdo-list(a)redhat.com -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCgAGBQJToqegAAoJEC5aWaUY1u571rMIANZtl09voEZ0zhgIQlkagOUo Bcsb2/czHuvHzySEAdE01TOqQl2rdLjv6R56uZO9FvQBTmwx+Hvp3RQa77H1i6NP l9meR2vhfDZwLDKUkM9AcUbKEjEX8h9Jlt3wswIrg5lIjjO8m03HlOwkgTY89kFE ktsg/5zUQ1df5rL8q+4rcz01EyOWvmTu31HbYoUIHiNLLhHVD3JGFjAyXqhFwFuK E2I/7Uqjxi32lUBOFKBAQ+eMDQruiGUKe19tehLveplsBw6f03JEIsK1MDXHTcCP TpnTfx82SXmsZnmMpUkBZXs2T2Zd3Auiu2otLV28KfiSESng8CP0TfniFJkfuwA= =J/sK -----END PGP SIGNATURE-----