Shared application network variables

These variables are for access to the applications housed on the Cloud Pak for Data System Cluster.

Variables

Note: If the template you are editing is from a release older than 1.0.5.1, then it does not include the application_network_enabled line. When starting with an existing System_Name.yml file, this line must be added manually before the application_network line:

application_network_enabled: True/False
    application_network:

If you are only using Management connection (1G), the setting must be: application_network_enabled: False, and the application_network section must be blank.

If you have a standard network layout (Management plus Application), you should set application_network_enabled to True.

In the vars section, update the following:

VLAN
If you use VLAN tags on your side of the house connection to Cloud Pak for Data System, use those values. If you do NOT use a VLAN tag on your network connection, use 4080.
Example:
```
vars:
    [...]
    application_network:
      network1:
        [...]
        vlan: 4080
```

Application prefix

This is the netmask, converted into the bitmask integer.

Example:

 vars:
    [...]
    application_network:
      network1:
        [...]
        prefix: 24

Application gateway

This is the gateway on the application network.

Example:

vars:
    [...]
    application_network:
      network1:
        [...]
        gateway: 192.168.1.1

Application floating address

This is the Floating Address on the Application Network.

Example:

 vars:
    [...]
    application_network:
      network1:
        [...]
        floating_ip: 192.168.1.204

Application network MTU
If you require a special MTU, override the default here. Otherwise, leave the <OPTIONAL> tag from the template as is. The default value is 9000.
```
vars:
    [...]
    application_network:
      network1:
        [...]
        mtu: <OPTIONAL>
```

Application network custom routes


  vars:
    [...]
    application_network:
      network1:
        [...]
        custom_routes: <OPTIONAL>

Note: The route format must be provided in the following format:

["ip/prefixlen via gateway dev interface"]

Example:

custom_routes: ["192.128.0.0/24 via 10.123.10.2 dev mgt1"]

Additional application address
In cases you wish to use a second network interface for your application connections, copy the network1 section under application_network, rename it as network2, and reset the default_gateway to false. This will give a file which looks like this:
```
vars:
    [...]
    application_network:
      network1:
        default_gateway: true
        vlan: 
        # just number, no slash 
        prefix: 
        gateway: 
        floating_ip: 
        mtu: 
        custom_routes: 
      network2:
        default_gateway: false
        vlan: 
        # just number, no slash 
        prefix: 
        gateway: 
        floating_ip: 
        mtu: 
        custom_routes: 
```
Note: In the network2 section, the default_gateway must be reset to false. Otherwise the parameters have the same meaning but with different values as their counterparts in network1.