With Mitaka, Neutron has learned to set proper MTU values for the DHCP
agent depending on the encapsulation type being used. So do not override
them any more from our side.
Change-Id: Ib3c14a828374d607c49257682d552159c72a13f9
Closes-Bug: 1567923
* added new logic to render plugin templates
* refactored recipe names to be more consistence
* moved version up to 13.0.0 for mitaka release
* removed suse as supported platform
* added verisionbumb for refactored os-identity and common
* adapted optimized endpoint logic
* added endpoint attributes to fit new endpoint logic
* adapted the specs (unit tests) to work again
* refactored attributes throughout all recipes that were connected to the
attributes used for the neutron.conf.erb template to adapt the new template
attribute syntax
* removed some attributes that were set to non default values, since the
defaults from neutron cloud and should be used instead
* moved all attributes form attributes/default.rb that were used in
neutron.conf.erb to attributes/neutron_conf.rb
* refactored attributes to fit new template logic
* refactored recipes/default.rb to fit new template logic
* removed all attributes set to default values in attribtues/default and
template
* replaced static plugin logic and templates with new config logic, following
the same principles as for neutron.conf
* renamed recipes to fit attributes and actual service names
* added recipes for ml2_core_plugin, ml2_openvswitch and ml2_linuxbridge as well
as a recipe for the creation of all plugin configs (plugin_conf) like plugin.ini
Change-Id: I9cc1b5cc069987ac83e064322c2291772505ff5f
Implements: blueprint cookbook-refactoring
Depends-On: I0547182085eed91d05384fdd7734408a839a9a2c
Depends-On: I3262b2e6f792f37c32a446e6567790b82bdd4613
This will allow tenants who do not specify a
DNS server in their subnet creation to add
servers for the default dnsmasq process to use
to resolve upstream
Change-Id: I99f54667b758f83d8821b97957de92b97687740c
Most standard networks will have a 1500 MTU sized
provider network. Because there is a 24 byte overhead
with using any kind of encapsulation, most users will
want to downgrade the MTU set within their guests or
raise their internal network MTU above 1500. The former
is much easier to do and has been added as an option to
dnsmasq that is passed to the client.
Change-Id: I199ec6e46c114d0277230eded002ad99786c061c
Ghanshyam Mann