Non-consistent public and floating networks parameters are reported via CLI

[Aleksey Kasatkin]

Nailgun. Nova-Network only.
Public and Floating networks parameters became non-consistent when public CIDR is changed via UI (affects v.4.0, 3.2.1 or earlier).

It doesn't affect functionality as parameters which were not updated are not utilized in Nailgun nor for deployment.

CLI output after change of public netmask to "255.255.0.0" and change of public and floatign IP ranges (v.3.2.1):

dns_nameservers:
  nameservers:
  - 8.8.8.8
  - 8.8.4.4
net_manager: FlatDHCPManager
networks:
- amount: 1
  cidr: 172.16.0.0/24
  cluster_id: 1
  gateway: 172.16.0.1
  id: 2
  ip_ranges:
  - - 172.16.1.128
    - 172.16.1.254
  name: floating
  netmask: 255.255.255.0
  network_size: 256
  vlan_start: null
- amount: 1
  cidr: 172.16.0.0/24
  cluster_id: 1
  gateway: 172.16.0.1
  id: 3
  ip_ranges:
  - - 172.16.0.2
    - 172.16.1.127
  name: public
  netmask: 255.255.0.0
  network_size: 256
  vlan_start: null

Public network 'cidr' and 'network_size' parameters must be updated using 'netmask' and 'gateway' parameters (it is done the same way in case of Neutron for both v.3.2.1 and v.4.0). Floating network parameters must be updated from public network parameters.

[Aleksey Kasatkin (alekseyk-ru)]

PR https://review.openstack.org/#/c/59420/ addresses the problem partially (Public network 'cidr' and 'network_size' parameters are updated).

[Alexandr Notchenko (anotchenko)]

Bug will be resolved as part of https://blueprints.launchpad.net/fuel/+spec/nailgun-refactor-nova-network-neutron