8 Commits

Author SHA1 Message Date
Harald Jensås
91985cfbce L3 routed networks - data + env (1/3)
Render composable network L3 routed subnets in
network-environment yaml files.

Partial: blueprint tripleo-routed-networks-templates
Change-Id: I4ba234ede5b7f243ba41e8fec8f78e1f1cc261c8
2018-12-30 19:24:29 +01:00
Harald Jensås
e644e3dda9 Add MTU to neutron networks and nic-config templates
Neutron has support[1] to set the guaranteed MTU for
networks and network segments so that this is exposed
to plug-ins. In interest of supporting the use of
plug-ins to configure network devices in the future
this change adds MTU property on neutron networks.

The new (optional) property 'mtu' in the network
defenitions in 'network_data.yaml' is used to control
the MTU settings. By default the mtu is '1500'.

We already configure the MTU on the ctlplane neutron
networks, this adds the MTU to composable networks.

Also update the nic-config sample templates to include
mtu settings. A heat value resource is added to
nic-config templates to get the required minimum
viable MTU value for bridges, bonds and member
interfaces to ensure the MTU is large enough to allow
the largest configured MTU to traverse the path.

Closes-Bug: #1790537
Change-Id: I11e38f82eb9040f77412fe8ad200fcc48031e2f8
2018-12-22 17:03:09 +01:00
Sorin Sbarnea
446dcc179d Fix fs035 by defining a default gateway_ipv6
Change-Id: I95e2a659927f44e2941b10daa10c7fc9c605bbd8
Closes-Bug: 1806897
2018-12-05 14:23:51 +00:00
Zuul
aee048d3bb Merge "Add a gateway IP to the Management net in network_data.yaml" 2018-12-04 14:03:09 +00:00
Saravanan KR
00652b6596 Fix error in Tenant network routes definition
Deploying with network_data_routed.yaml is throwing
'Unknown Property ip_netmask' for the Tenant network routes.
Fix the network_data_routed.yaml definition to use the
right keys for the route definition.

Change-Id: Ied81ed342dbeb026225b01aeed66aca7411b3555
2018-09-24 19:33:00 +05:30
Dan Sneddon
2fb91cd5b0 Add a gateway IP to the Management net in network_data.yaml
In several places in our documentation, we discuss enabling
the Management network as a default route in some cases.
However, we don't set this value by default. Setting a
gateway IP in the example versions of network_data.yaml
would help to demonstrate this, and would create a good
default for testing.

Change-Id: Ibbb2a403f0733a016f1f49b4acdbdcfe7b9ab5a3
2018-09-04 18:33:36 -07:00
Harald Jensås
4e1d12b4c7 Fix typo in network_data files
The comments use ipv6_gateway, while the actual data
and code uses gateway_ipv6. This changes the comments
to use gateway_ipv6 as well.

Change-Id: I3b173fca479e778f75307b7bb47bd7954ea786f4
2018-08-20 08:25:15 +02:00
Harald Jensås
4e44547533 Add host routes to subnets
This change adds a new routes field to the network
definition in network_data.yaml. This field contains
a list of network routes in JSON, e.g.
  [{'destination':'10.0.0.0/16','nexthop':'10.0.0.1'}].

This list is used to set the ``host_routes`` property
of each networks subnet.

Co-Authored-By: Dan Sneddon <dsneddon@redhat.com>
Partial: blueprint tripleo-routed-networks-templates
Depends-On: Ifc5aad7a154c33488a7613c8ee038c92ee6cb1a7
Change-Id: I33b34f1445f4203fbf25edeb093b37c7494c664f
2018-07-30 09:42:19 +02:00