openstack/kolla.git/ansible/roles/neutron/defaults, branch master

Remove Ansible from Kolla

2016-11-16T04:34:17+00:00

Change-Id: I5396e4b9927d3e65b6aa4185238a43a4765a996b

Integrate neutron-vpnaas-agent into the neutron Ansible role

2016-09-15T05:07:46+00:00

Implements: blueprint neutron-vpnaas-agent Co-Authored-By: zhubingbing Change-Id: I1fae21f48d5beef47934aef7c23910536955f2b8

Add Networking-SFC role

2016-09-14T07:41:03+00:00

Networking-SFC is a neutron big-tent project support Service Function Chaining in Neutron. * Rename the image from neutron-networking-sfc-agent to neutron-sfc-agent. * Add networking-sfc role in playbooks. Co-Authored-by: Jeffrey Zhang Change-Id: I1f99650eed85f59929d4ab6b2226603c54f29577 Implements: blueprint enable-networking-sfc-support

Add option to support dhcp/l3 agent ha

2016-08-31T08:31:07+00:00

New option enable_neutron_agent_ha added to enable/disable dhcp/l3 agent high availability, dhcp_agents_per_network is default to 2 and it's configurable. Implement blueprint: support-network-ha Change-Id: Id4742aa67c80584634b923195545bf2b654172f3

Adds Neutron LBaaS Support

2016-05-27T15:41:25+00:00

Previously, kolla did not support neutron lbaas functionality. Only Lbaasv2 is supported in Mitaka. Additional information can be found here: http://docs.openstack.org/mitaka/networking-guide/adv-config-lbaas.html Magnum uses Neutron Lbaas to provide high availability to COE API and Etcd endpoints within a bay. Therefore, Neutron Lbaas is required for Kolla to support Magnum. Co-Authored-By: Serguei Bezverkhi Partial-Bug: #1551992 Change-Id: I05360b7c447c601fcb3c2b6b2a913ef5cc0f3a1b

add support for non-default database_port in kolla/ansible

2016-05-13T12:12:25+00:00

This change makes each step of the kolla deployment aware of the port database was configured to listen on. It defaults mariadb_port to database_port. Change-Id: I8e85d5732015afc0a5481cb33e0b629fdfa84a1b Closes-Bug: #1576151 DocImpact

Fix Keystone v3 and Horizon

2016-03-03T15:44:53+00:00

After our switch to keystone-manage bootstrap Horizon is not happy due to v3 not being setup correctly. This patch fixes that This also includes removal of unused variables (transforms them into endpoint url variables) TrivialFix Change-Id: I1e04db8c24049f80e974c063f03068a2ab32a563

Move shared variables to group_vars/all.yml

2016-02-29T18:40:15+00:00

This follows the structure we have for Ironic and Nova Closes-Bug: #1551316 Change-Id: I609e3dda40c65b73bb5e1208f702740416a042ed

Change kolla_internal_address variable

2016-02-26T20:00:09+00:00

Due to poor planning on our variable names we have a situation where we have "internal_address" which must be a VIP, but "external_address" which should be a DNS name. Now with two vips "external_vip_address" is a new variable. This corrects that issue by deprecating kolla_internal_address and replacing it with 4 nicely named variables. kolla_internal_vip_address kolla_internal_fqdn kolla_external_vip_address kolla_external_fqdn The default behaviour will remain the same, and the way the variable inheritance is setup the kolla_internal_address variable can still be set in globals.yml and propogate out to these 4 new variables like it normally would, but all reference to kolla_internal_address has been completely removed. Change-Id: I4556dcdbf4d91a8d2751981ef9c64bad44a719e5 Partially-Implements: blueprint ssl-kolla

Merge "Use uppercase 'S' in word "OpenStack""

2016-02-15T16:23:37+00:00