Version: openstack-packstack-2013.1.1-0.23.dev642.el6ost Description: I've installed Grizzly on RHEL6.4 with Neutron + OVS on 4 machines: 1. Machine with all services including neutron server (no compute, no l3, no dhcp) 2. L3-only machine 3. DHCP-only machine 4. Compute-only machine After installation quantum-openvswitch-agent and openvswitch services are active on machines 2,3,4 (as expected), however, quantum-openvswitch-agent is inactive and openvswitch is active on machine 1, where both services are not in use. Packstack's puppet modules which disable quantum-openvswitch-agent service should also disable openvswitch, or to not install both packages where they're not needed. Note that openvswitch package/service was installation by packstack.
Hi Rami I was able to accomplish both tasks with the difference that I achieved the second by installing openvswitch manually. Did you perform all this on a single VM or on multiple VMs? Thanks Rushil (In reply to Rami Vaknin from comment #0) > Version: > openstack-packstack-2013.1.1-0.23.dev642.el6ost > > Description: > I've installed Grizzly on RHEL6.4 with Neutron + OVS on 4 machines: > 1. Machine with all services including neutron server (no compute, no l3, no > dhcp) > 2. L3-only machine > 3. DHCP-only machine > 4. Compute-only machine > > After installation quantum-openvswitch-agent and openvswitch services are > active on machines 2,3,4 (as expected), however, quantum-openvswitch-agent > is inactive and openvswitch is active on machine 1, where both services are > not in use. > > Packstack's puppet modules which disable quantum-openvswitch-agent service > should also disable openvswitch, or to not install both packages where > they're not needed. > > Note that openvswitch package/service was installation by packstack.
(In reply to Rushil Chugh from comment #2) > Hi Rami > I was able to accomplish both tasks with the difference that I achieved the > second by installing openvswitch manually. Did you perform all this on a > single VM or on multiple VMs? I'm not sure I understand which tasks do you refer to? The numbers 1 to 4 represent 4 different bare-metal machines which all are in a same single installataion, so I'm acctually using 4 bare-metals as one openstack environment, no additional vms. > Thanks > Rushil > (In reply to Rami Vaknin from comment #0) > > Version: > > openstack-packstack-2013.1.1-0.23.dev642.el6ost > > > > Description: > > I've installed Grizzly on RHEL6.4 with Neutron + OVS on 4 machines: > > 1. Machine with all services including neutron server (no compute, no l3, no > > dhcp) > > 2. L3-only machine > > 3. DHCP-only machine > > 4. Compute-only machine > > > > After installation quantum-openvswitch-agent and openvswitch services are > > active on machines 2,3,4 (as expected), however, quantum-openvswitch-agent > > is inactive and openvswitch is active on machine 1, where both services are > > not in use. > > > > Packstack's puppet modules which disable quantum-openvswitch-agent service > > should also disable openvswitch, or to not install both packages where > > they're not needed. > > > > Note that openvswitch package/service was installation by packstack.
Is it necessary to use bare metal machines? I am running the 4 machines on top of Fedora 19. (In reply to Rami Vaknin from comment #3) > (In reply to Rushil Chugh from comment #2) > > Hi Rami > > I was able to accomplish both tasks with the difference that I achieved the > > second by installing openvswitch manually. Did you perform all this on a > > single VM or on multiple VMs? > > I'm not sure I understand which tasks do you refer to? > The numbers 1 to 4 represent 4 different bare-metal machines which all are > in a same single installataion, so I'm acctually using 4 bare-metals as one > openstack environment, no additional vms. > > > Thanks > > Rushil > > (In reply to Rami Vaknin from comment #0) > > > Version: > > > openstack-packstack-2013.1.1-0.23.dev642.el6ost > > > > > > Description: > > > I've installed Grizzly on RHEL6.4 with Neutron + OVS on 4 machines: > > > 1. Machine with all services including neutron server (no compute, no l3, no > > > dhcp) > > > 2. L3-only machine > > > 3. DHCP-only machine > > > 4. Compute-only machine > > > > > > After installation quantum-openvswitch-agent and openvswitch services are > > > active on machines 2,3,4 (as expected), however, quantum-openvswitch-agent > > > is inactive and openvswitch is active on machine 1, where both services are > > > not in use. > > > > > > Packstack's puppet modules which disable quantum-openvswitch-agent service > > > should also disable openvswitch, or to not install both packages where > > > they're not needed. > > > > > > Note that openvswitch package/service was installation by packstack.
(In reply to Rushil Chugh from comment #4) > Is it necessary to use bare metal machines? I am running the 4 machines on > top of Fedora 19. VMs are ok, no need for bare-metals here. > (In reply to Rami Vaknin from comment #3) > > (In reply to Rushil Chugh from comment #2) > > > Hi Rami > > > I was able to accomplish both tasks with the difference that I achieved the > > > second by installing openvswitch manually. Did you perform all this on a > > > single VM or on multiple VMs? > > > > I'm not sure I understand which tasks do you refer to? > > The numbers 1 to 4 represent 4 different bare-metal machines which all are > > in a same single installataion, so I'm acctually using 4 bare-metals as one > > openstack environment, no additional vms. > > > > > Thanks > > > Rushil > > > (In reply to Rami Vaknin from comment #0) > > > > Version: > > > > openstack-packstack-2013.1.1-0.23.dev642.el6ost > > > > > > > > Description: > > > > I've installed Grizzly on RHEL6.4 with Neutron + OVS on 4 machines: > > > > 1. Machine with all services including neutron server (no compute, no l3, no > > > > dhcp) > > > > 2. L3-only machine > > > > 3. DHCP-only machine > > > > 4. Compute-only machine > > > > > > > > After installation quantum-openvswitch-agent and openvswitch services are > > > > active on machines 2,3,4 (as expected), however, quantum-openvswitch-agent > > > > is inactive and openvswitch is active on machine 1, where both services are > > > > not in use. > > > > > > > > Packstack's puppet modules which disable quantum-openvswitch-agent service > > > > should also disable openvswitch, or to not install both packages where > > > > they're not needed. > > > > > > > > Note that openvswitch package/service was installation by packstack.
This was fixed together with simplification patch.