linux/meta-cloud-services.git/meta-openstack/recipes-devtools/python/python-nova/nova.conf, branch wrynose

python-nova: uprev to latest openstack sable/pike release

2018-04-09T14:48:37+00:00

This requires several new recipes and package uprevs (python-tooz, python-os-brick, python-pypowervm, python-networkx, python-microversion-parse, python-os-win, python-os-vif, and python-os-traits). Along with updates to make things work with systemd. We also take steps to make setup/init use the directions from https://docs.openstack.org/nova/pike/install/controller-install-ubuntu.html After these changes we can validate that nova is operating nominally using the command: +-------+--------------------------------------+ | Name | UUID | +-------+--------------------------------------+ | cell0 | 00000000-0000-0000-0000-000000000000 | | cell1 | f547fa04-7c82-4498-95ee-210fc40abdb6 | +-------+--------------------------------------+ Signed-off-by: Mark Asselstine Signed-off-by: Bruce Ashfield

nova: uprev to Liberty

2016-02-05T19:42:18+00:00

Signed-off-by: Mark Asselstine Signed-off-by: Bruce Ashfield

nova: update configuration settings

2014-11-17T22:50:23+00:00

The following nova commit: commit 5cacad3508570ce70b1f9ef620e0508169687fda Author: Gary Kotton Date: Tue Jun 3 03:44:40 2014 -0700 Deprecate neutron_* configuration settings Create a new section in the configuration file called 'neutron'. Move all of the neutron_* configuration settings to this section. DocImpact The table below has the changes: +---------------------------------+-------------------------+ | 'DEFAULT' Section | 'neutron' Section | |---------------------------------|-------------------------| | neutron_url | url | | neutron_url_timeout | url_timeout | | neutron_admin_username | admin_username | | neutron_admin_password | admin_password | | neutron_admin_tenant_id | admin_tenant_id | | neutron_admin_tenant_name | admin_tenant_name | | neutron_region_name | region_name | | neutron_admin_auth_url | admin_auth_url | | neutron_api_insecure | api_insecure | | neutron_auth_strategy | auth_strategy | | neutron_region_name | region_name | | neutron_ovs_bridge | ovs_bridge | | neutron_extension_sync_interval | extension_sync_interval | | neutron_ca_certificates_file | ca_certificates_file | +---------------------------------+-----------------------=-+ Means that we need to create a [neturon] section, move and rename our configs appropriately. Signed-off-by: Bruce Ashfield

neutron: move from OVS unified to OVS ml2 plugin

2014-10-27T13:30:52+00:00

Juno removes support for the unified OVS and linuxbridge plugins. So we switch to the ml2 OVS plugin. This involves configuration and packaging changes. Signed-off-by: Bruce Ashfield

keystone: Change packages configuration to use apache keystone.

2014-09-22T15:46:43+00:00

This commit changes all required configurations to use keystone running on apache. The following packages configurations were modified for keystone running on apache: python-neutron, python-nova, tempest, python-swift, python-rally, python-heat, python-glance, python-cinder, python-ceilmoeter, python-horizon. Signed-off-by: Liam R. Howlett

python-nova: Remove duplicate line from conf file.

2014-09-04T19:06:44+00:00

Removed duplicate dhcpbridge_flagfile from the nova.conf file. Signed-off-by: Liam R. Howlett Signed-off-by: Bruce Ashfield

nova: update to juno configuration requirements

2014-09-03T05:08:14+00:00

To boot a nested guest in juno, we need to relocate the virtualization type config setting into the [libvirt] section. With this, we can sucessfully launch a guest. Signed-off-by: Bruce Ashfield

Add metadata service support to controller node

2014-06-18T19:08:11+00:00

The metadata service is working as the following: - metadata is being served by nova-api on controller at port 8775. - VM instance requests metadata by 169.254.169.254 (eg, curl http://169.254.169.254/latest/meta-data) - metadata request comes to neutron-ns-metadata-proxy on controller in dhcp network name space. - neutron-ns-metadata-proxy forwards the request to neutron-metadata-agent through a unix domain socket (/var/lib/neutron/metadata_proxy). - neutron-metadata-agent sends the request to nova-api on port 8775 to be serviced. To support metadata service, neutron-ns-metadata-proxy is baked into the controller image. Also neutron-metadata-agent startup script (/etc/init.d/neutron-metadata-agent) and config file (/etc/neutron/metadata_agent.ini) are added to start up metadata agent at system initialization. dhcp_agent.ini and nova.conf are updated as well. A README.metadata is added in the Documentation/ directory. Signed-off-by: Andy Ning Signed-off-by: Bruce Ashfield

nova: uprev to icehouse/stable support

2014-04-30T04:07:28+00:00

Updating the recipe's branch and SRCREV to the icehouse/stable release branch. The configuration changes required for basic operation are limited, so we keep nearly everything the same, and will update the config in subsequent commits. Signed-off-by: Bruce Ashfield

OpenStack: modify controller to be able to talk to both console

2014-03-25T13:56:15+00:00

We modify the controller so that both vnc and spice html5 proxies are running. Since in the current recipe, both controller and compute share the same nova.conf file, in the compute, both vnc and spice html5 are set to enabled and in this configuration, vnc is chosen (in source: vnc is chosen because it's better tested). To change to spice, only change required is on the compute side. The controller (since the default console_type is auto) will try to talk to both and run whichever is available. Signed-off-by: Amy Fong