Bug 1194297 - [RFE] Allow to synchronize only out-of-sync networks on an host
Summary: [RFE] Allow to synchronize only out-of-sync networks on an host
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RFEs
Version: ---
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ovirt-3.6.0-rc
: 3.6.0
Assignee: Eliraz Levi
QA Contact: Meni Yakove
URL:
Whiteboard: network
Depends On: 1136329
Blocks: 1044485
TreeView+ depends on / blocked
 
Reported: 2015-02-19 13:52 UTC by Lior Vernia
Modified: 2023-09-14 02:55 UTC (History)
15 users (show)

Fixed In Version: 3.6.0-12
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-04 11:40:32 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-3.6.0+
ylavi: planning_ack+
rule-engine: devel_ack+
rule-engine: testing_ack+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 41526 0 master MERGED engine: Introduce syncAllHostNetwork command Never
oVirt gerrit 42024 0 master MERGED webadmin: adding sync all networks button Never
oVirt gerrit 44017 0 master MERGED engine: adding CTOR for GetNetworkAttachmentsByHostIdQuery Never
oVirt gerrit 45641 0 ovirt-engine-3.6 MERGED engine: adding CTOR for GetNetworkAttachmentsByHostIdQuery Never
oVirt gerrit 45642 0 ovirt-engine-3.6 MERGED engine: Introduce PersistentHostSetupNetworks command Never
oVirt gerrit 45704 0 ovirt-engine-3.6 MERGED engine: Introduce syncAllHostNetwork command Never
oVirt gerrit 45705 0 ovirt-engine-3.6 MERGED webadmin: adding sync all networks button Never
oVirt gerrit 45707 0 ovirt-engine-3.6 MERGED engine: Introduce PersistentHostSetupNetworksParameters Never

Description Lior Vernia 2015-02-19 13:52:56 UTC
Description of problem:

A host might have several out-of-sync networks, a user has to currently go network-by-network and mark them to be synchronized as part of a Setup Networks command. This is tedious, especially when numerous hosts have numerous out-of-sync networks, especially via the GUI.

Moreover, the "barrier" to start using the 3.6 Host Network QoS feature is quite high at the moment. Say a user has an existing setup, where several networks exist on each host interface, and they want to apply QoS on all their networks

Due to the engine validation that either none or all of the networks on a specific NIC has QoS configured, adding QoS to each network separately (via the edit network dialog) will never succeed to propagate to the hosts using it. The end-state will be that all these networks will remain out-of-sync on all the hosts, their QoS configuration not applied - and to apply them, a user would have to go host-by-host, and mark each network to be synchronized.


Version-Release number of selected component (if applicable):

3.6.


How reproducible:

Always.


Steps to Reproduce:
1. Have one or more hosts with several networks on one interface.
2. Edit all these logical network entities, and attach QoS to each of them.

Actual results:

The logical network entities are up-to-date, but these networks will remain out-of-sync (and with no QoS applied) on the hosts using them (as long as no network was the only network on the same interface).


Expected results:

When editing each logical network entity separately, I don't see how the out-of-sync situation could be avoided. However, it should be easier for users to get out of this state - at least via the GUI, I'd expect users to be able to select all out-of-sync hosts and just press a button to synchronize all networks that are out-of-sync on them.

Comment 1 Lior Vernia 2015-02-24 15:21:42 UTC
Could be implemented by properly crafting a Setup Networks command to the host, based on its current configuration and only marking all out-of-sync networks to be synchronized.

Would be nice to also expose a special action via REST (on /api/hosts/{host:id}), not sure if necessary.

Comment 2 Sven Kieske 2015-03-11 17:17:50 UTC
(In reply to Lior Vernia from comment #1)
> Could be implemented by properly crafting a Setup Networks command to the
> host, based on its current configuration and only marking all out-of-sync
> networks to be synchronized.
> 
> Would be nice to also expose a special action via REST (on
> /api/hosts/{host:id}), not sure if necessary.

From a customer perspective I think this would be a very cool feature!

Comment 3 Lior Vernia 2015-03-16 10:13:18 UTC
Also, an "out-of-sync" column should be added to the hosts main tab - currently it would be marked as such if at least one of its networks is out-of-sync, but eventually this display might be affected by other notions of "out-of-sync-ness" if they exist (similarly the button would not only synchronize networks, rather anything that is out-of-sync).

Comment 4 Yaniv Lavi 2015-04-05 15:41:53 UTC
Is this similar to BZ #1037612?

Comment 5 Lior Vernia 2015-04-06 07:33:38 UTC
Could be considered related, but there's no overlap in actual functionality/implementation.

Comment 7 Barak 2015-07-13 11:43:08 UTC
What about rest api ?

Comment 8 Michael Burman 2015-11-03 10:13:16 UTC
Verified on - 3.6.0.2-0.1.el6

Comment 9 Sandro Bonazzola 2015-11-04 11:40:32 UTC
oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue.
If problems still persist, please open a new BZ and reference this one.

Comment 10 Red Hat Bugzilla 2023-09-14 02:55:04 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.