Bug 905305

Summary:	Quantum service using OpenvSwicth has openvswitch as a dependency
Product:	[Fedora] Fedora	Reporter:	Gary Kotton <gkotton>
Component:	openstack-quantum	Assignee:	Ihar Hrachyshka <ihrachys>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	19	CC:	apevec, breu, chrisw, ihrachys, Jan.van.Eldik, jose.castro.leon, lpeer, markmc
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-10-06 10:31:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Gary Kotton 2013-01-29 06:10:41 UTC

Description of problem:
When installing Quantum service and using OVS as a plugin the openvswitch module is a dependency. This is not required as this is not a compute node


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


How reproducible:


Steps to Reproduce:
1. Install Quantum service
2. Install OpenvSwicth plugin
3.
  
Actual results:
Openvswicth is a dependency

Expected results:
That is should not be


Additional info:

Comment 2 Bob Kukura 2013-01-29 14:44:01 UTC

The openvswitch package is a dependency of the openstack-quantum-openvswitch package, which contains the openvswitch plugin and agent. Unless we split the plugin and agent into separate packages, then openvswitch should remain a dependency of openstack-quantum-openvswitch. I suggest we close this as not a bug, and if we really think its the right thing to do, file a different bug to split out each agent into a separate sub-package so that server-only installations have no unnecessary dependencies.

Comment 3 Bob Kukura 2013-01-29 14:54:06 UTC

Just a note, splitting out the agents is a bit complicated. Either the agent packages depend on the server packages, or both the server and agent packages need to depend on a 3rd common package. 

To avoid all unnecessary dependencies on both server and compute nodes, we'd need something like the following for openvswitch:

openstack-quantum-openvswitch-common (requires openstack-quantum-common)

openstack-quantum-openvswitch-server (requires openstack-quantum-server, openstack-quantum-openvswitch-common)

openstack-quantum-openvswitch-agent (requires openstack-agent, openstack-quantum-openvswitch-common, openvswitch)

Following the same pattern for all the plugins plus the l2-agent, dhcp-agent, metadata-proxy-agent, ... would result in an explosion in the total number of packages. Teasing apart the source tree to put python modules in the most optimal sub-packages would also be significant work, possibly needing updates with each rebase.

Comment 4 amazonsx 2013-03-13 05:09:47 UTC

How to solve this problem?

Comment 5 Fedora End Of Life 2013-04-03 17:23:39 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 8 Ihar Hrachyshka 2014-10-06 10:31:06 UTC

Introducing those -common packages is an overkill. There is nothing particularly bad in having openvswitch installed on controller, right? So let's not waste time on implementing the scheme proposed above.