linux/meta-cloud-services.git/meta-openstack/recipes-devtools/python/python-nova-controller_2013.1.3.bb, branch styhead

python-nova: unify controller and compute recipes

2013-10-04T04:26:04+00:00

The split of compute and controller is no longer necesary, since configuration inheritance is done with overriding layers, not split recipes. This simplifies the build, and packaging of the recipe. Good riddance. Signed-off-by: Bruce Ashfield

nova: add novnc console proxy support

2013-10-03T05:16:44+00:00

With this commit the appropriate daemons are started on a control node boot to support horizon console access via the novnc proxy. Additionally, the proper nova configuration is set for boh the control and compute nodes for out of the box console connectivity between the compute, control and horizone interface. Signed-off-by: Bruce Ashfield

nova: use common 'hosts' configuration versus 'controller' and 'compute'

2013-10-03T05:16:44+00:00

Since external IPs can now be used, we can unify the IP configuration to the single global file. Signed-off-by: Bruce Ashfield

nova-controller: fix packaging error

2013-10-03T05:15:42+00:00

nova controller's configuration files in /etc were being improperly packaged in nova-controller-misc. Signed-off-by: Bruce Ashfield

python-nova*: FILES re-ordering and clarification

2013-09-16T01:59:45+00:00

To prevent build errors to the order of evaluation of FILES_* we re-order and clarify the contents of each package. Signed-off-by: Mark Hatle

python-nova: use explicit file lists, versus variables

2013-09-06T22:00:08+00:00

By setting the FILES_ packaging variables via .inc local vars, we can run into trouble with variable resolution timing and hence packaging fails. We temporarily switch back to explicit (and duplicated) file lists to fix packaging Signed-off-by: Bruce Ashfield

nova: split into explicit compute and controller recipes

2013-08-28T22:42:00+00:00

To allow unique configuration of nova for compute and controller nodes, the nova class is split into two, but packaged largely the same way. The compute and controller classes are introduced to hold configuration values and operations that are used by the common packaging routines to customize and deploy. Signed-off-by: Bruce Ashfield