network_1.yaml¶

Usage¶

1. Dump network information using the following Fuel command:

   fuel --env 1 network --download
   

   where --env 1 points to the specific environment (id=1 in this example).

2. Edit file and add information about the new Network Group(s).

3. Upload the modified file:

   fuel --env-1 network --upload
   

If you make a mistake when populating this file, it seems to upload normally but no network data changes are applied; if you then download the file again, the unmodified file may overwrite the modifications you made to the file. To protect yourself, we recommend the following process:

• After you edit the file but before you upload it, make a copy in another location.
• Upload the file.
• Download the file again.
• Compare the current file to the one you saved. If they match, you successfully configured your networks.

If you configure your networking by editing this file, you should create and configure the rest of your environment using the Fuel CLI rather than the Web UI. Especially do not attempt to configure your networking using the Web UI screens.

File Format¶

The network_1.yaml file contains global settings and the networks section.

Note that the network_1.yaml is dumped in dictionary order so the sections may appear in a different order than documented here.

Global settings¶

are mostly at the beginning of the file but one (public_vip) is at the end of the file, When configuring a new environment, you must set values for the management_vip, floating_ranges, and public_vip parameters.

management_vip: 10.108.37.2
networking_parameters:
  base_mac: fa:16:3e:00:00:00
  dns_nameservers:
  - 8.8.4.4
  - 8.8.8.8
  floating_ranges:
  - - 10.108.36.128
    - 10.108.36.254
  gre_id_range:
  - 2
  - 65535
  internal_cidr: 192.168.111.0/24
  internal_gateway: 192.168.111.1
  net_l23_provider: ovs
  segmentation_type: gre
  vlan_range:
  - 1000
  - 1030
. . .
public_vip: 10.108.36.2

Networks¶

The networks section contains the configurations of each Network Group that has been created.

You must set values for the cidr, gateway, and ip_ranges parameters for each logical network in the group. This is what the configuration of one logical network (public)looks like. A similar section is provided for each of the logical networks that belong to the Node Group.

networks:
- cidr: 10.108.36.0/24
  gateway: 10.108.36.1
  group_id: 1
  id: 1
  ip_ranges:
  - - 10.108.36.2
    - 10.108.36.127
  meta:
    assign_vip: true
    cidr: 172.16.0.0/24
    configurable: true
    floating_range_var: floating_ranges
    ip_range:
    - 172.16.0.2
    - 172.16.0.126
    map_priority: 1
    name: public
    notation: ip_ranges
    render_addr_mask: public
    render_type: null
    use_gateway: true
    vlan_start: null
  name: public
  vlan_start: pull
    - 10.108.35.254
  vlan_start: null

If you create additional Node Groups, the file contains segments for each Node Group, each identified by a unique group_id, with configuration blocks for each of the four logical networks associated with that Node Group.