Description of problem: - Document the feature introduced by BZ #1200963 - The feature is currently being targeted for RHV 4.2 These are the steps: 1. In the Manager, open a console and add the custom property. # engine-config -s CustomDeviceProperties='{type=interface;prop={default_route=^(true|false)$}}' 2. On each host: 2.1 Set the property to False on the management (ovirtmgmt|rhevm) network 2.2 Set the property to True on the desired new default route network 2.3 Set a next-hop IP address (Gateway) in the new default route network 3. Apply configurations Two important notes that must be added to the docs: * This configuration is PER HOST, and needs to be done on each host. * If the gataway for the new default route network is not set, it will be IGNORED. Leaving the gateway blank will NOT set device based route (such as for proxy-arp scenarios).
Adding to the second note above, to make it clearer: * Leaving the gateway blank for the new default route network will result in no default route set in the host main routing table.
Which versions contain this feature?
https://gerrit.ovirt.org/#/q/Iaf392ea05e1e39acbf1b74a7a31acda9e750b36e Currently, only in 4.1
Assigning to Byron for review.
Marina, https://access.redhat.com/solutions/1407933 should not be proposed to customers once 4.1 is released. Instead, the method described in comment 0 should be used. What should I do to modify this KB item?
(In reply to Dan Kenigsberg from comment #5) > Marina, https://access.redhat.com/solutions/1407933 should not be proposed > to customers once 4.1 is released. Instead, the method described in comment > 0 should be used. > > What should I do to modify this KB item? This is done. Please refresh the solution. If you really want to modify kcs solution - reach out to me separately and we can work it out.
Dan, probably I misunderstand something here in the instructions. If I add this property under CustomDeviceProperty, I can see it only under general Networks tab, when editing vNic profile. And I see nowhere under hosts' networking setup where I can set it up, except the actual IP and Gateway setup. Maybe the instructions meant to say: 1. Add default route as customer device property. 2. Modify ALL the logical networks in the Data Center to specify which will be the default route and which won't. (only 1 network can have default_route=true) 3. Modify EACH host and make sure the interface that is on the logical network to be served as default route, has the GATEWAY value specified.
OMG, seems like a severe case of dyslexia. Thank you, Marina, for calling me out on it. engine-config -g UserDefinedNetworkCustomProperties engine-config -s UserDefinedNetworkCustomProperties='default_route=^(true|false)$' should be used in order to expose the 'default_route' property on each network attachment. Other than that, comment 0 is correct.
I documented the suggested solution in this kcs: https://access.redhat.com/solutions/2956471
Hi Michael, Can you please review my kcs for this feature to see if anything is missing there? And if all good, docs team can push it directly to the guides. https://access.redhat.com/solutions/2956471
(In reply to Marina from comment #11) > Hi Michael, > > Can you please review my kcs for this feature to see if anything is missing > there? And if all good, docs team can push it directly to the guides. > > https://access.redhat.com/solutions/2956471 Hello Marina, I reviewed your kcs for this feature and it's good, nothing missing)
Marina, to confirm, it sounds like the next step is to move this bug back to the Documentation component, and set it back to NEW so we can triage it and find an available writer. Is that correct?
Lucy, this bug introduces a (minor) functionality change; Maybe you can handle it as a new feature request that requires its own documentation, based on the doctext I've provided?
Thanks, Dan. I'll leave this one on ovirt-engine then, and have raised bug 1432730 to track the documentation updates.
Yep, no idea why Errata did not do so.