Description of problem: When user configures its hosts to work with the neutron appliance, he has to follow the next steps: 1. Install host with the external provider (creates the br-neurton ovs bridge) 2. Add 'neutron' LB via setup networks 3. Manually connect 'neutron' to 'br-neutron' (via "ovs-vsctl add-port br-neutron neutron") The third step is tedious when required to be executed on all of the hosts which are installed with the external provider. There should be a method to mitigate the need for that manual step, i.e. by marking the 'neutron' network on setup-networks with a property/label that will instruct setup networks hook to execute that command manually. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
is step #3 really needed manyually? I thought that's the point of the additional host mapping properties for a re-deploy action.
(In reply to Itamar Heim from comment #1) > is step #3 really needed manyually? I thought that's the point of the > additional host mapping properties for a re-deploy action. Probably if this is the bug reproduction steps. Have not tried this myself.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
We do not plan to improve the automatic configuration of neutron host agent within RHEV installation. this should be the task of partner-specific install script or VIF driver.