Bug 748750

Summary:	Split out openstack-nova-compute
Product:	[Fedora] Fedora	Reporter:	Mark McLoughlin <markmc>
Component:	openstack-nova	Assignee:	Nobody's working on this, feel free to take it <nobody>
Status:	CLOSED NEXTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16	CC:	alexander.sakhnov, asalkeld, markmc, matt_domsch, mlvov, pbrady, p, rbryant, rkukura
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:	2012-09-06 13:16:25 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Mark McLoughlin 2011-10-25 09:28:43 UTC

A common deployment of OpenStack is to have a controller node with all the services running and a compute node with nova-compute running

Currently we just install the openstack-nova package on the compute nodes. That's fine, but since it's such a common deployment scenario it would be nice to be able to just install the nova-compute service. It doesn't save much in disk space, but it would help make things more clear.

We could potentially do the same for all services, probably starting with nova-network (since that can be installed on all compute nodes in HA mode) but I don't think there's any great need for it yet.

So, we should have:

  - the main body of python code in an openstack-nova-common package

  - the nova-compute service in openstack-nova-compute, which requires common

  - everything else in openstack-nova, which requires openstack-nova-compute

The common package isn't completely necessary to do this, but it would seem odd to have most of the code in openstack-nova-compute.

Comment 1 Pádraig Brady 2012-09-06 13:16:25 UTC

This split was done for the Essex packages in Fedora 17 and EPEL