Bug 748750 - Split out openstack-nova-compute
Summary: Split out openstack-nova-compute
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: openstack-nova
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nobody's working on this, feel free to take it
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-25 09:28 UTC by Mark McLoughlin
Modified: 2012-09-06 13:16 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-06 13:16:25 UTC
Type: ---


Attachments (Terms of Use)

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


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