reserved VIP is placed in a wrong namespace

[Piotr Misiak]

reserved VIP should be placed in the main namespace regarding to configuration but it is placed in the haproxy namespace

network_roles.yaml:

- id: "zabbix"
default_mapping: "management"
properties:
  subnet: true
  gateway: false
  vip:
    - name: "zabbix_vip_management"

after deployment:

from astute.yaml:

vips:
   zabbix_vip_management:
     network_role: zabbix
     node_roles:
     - controller
     - primary-controller
     namespace:
     ipaddr: 10.109.2.3

crm configure show:

primitive vip__zabbix_vip_management ocf:fuel:ns_IPaddr2 \
  op monitor interval=3 timeout=30 \
  op start interval=0 timeout=30 \
  op stop interval=0 timeout=30 \
  params nic=br-mgmt base_veth=zabbix_vip-base ns_veth=zabbix_vip-ns ip=10.109.2.3 iflabel=ka cidr_netmask=24 ns=haproxy gateway=none gateway_metric=0 other_networks=false bridge=br-mgmt iptables_start_rules=false iptables_stop_rules=false iptables_comment=false ns_iptables_start_rules=false ns_iptables_stop_rules=false \
  meta migration-threshold=3 failure-timeout=60 resource-stickiness=1

plugin code:
https://github.com/stackforge/fuel-plugin-external-zabbix

[Alexander Saprykin (cutwater)]

Please provide contents of the astute.yaml file.

[Alexander Saprykin (cutwater)]

Sorry, found astute yaml example in the description of the bug. Namespace field is empty, since it wasn't set in the network_roles.yaml. This is as designed behaviour.

Data is serialized to the astute.yaml in the correct way. The problem should be in the fuel-library.

[Ihor Kalnytskyi (ikalnytskyi)]

Move it to Fuel Library then.

[Piotr Misiak (piotr-misiak)]

Guys, it's a blocker for us. Please fix this ASAP.

[Sergey Vasilenko (xenolog)]

Piotr, please provide debug snapshot from this env

[Sergey Vasilenko (xenolog)]

This bug looks like feature "VIP without network namespace".
In the Fuel, earlier 7.0, there are no VIPs, processed without network namespaces.

I can propose 3 ways to solve this issue:
* re-design plugin for using standart way for FUEL -- VIP inside network namespace.
* re-design ns_Ipaddr2 OCF script for provide additional functionality -- "VIPs without network namespaces"
* use Ipaddr2 OCF script from pacemaker toolset for handle VIP if no network namespace given in the incoming parameters.

IMHO first way is most correct for Fuel. Bacause linux kernel has some unpleasant features while local traffic processing.

But, take into account existing time limit, I start work on the 3d way.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/214514

[Sergii Golovatiuk (sgolovatiuk)]

During 5.0 cycle VIP was moved to namespaces to resolve issue when IP is moved without closing connections for processes on the same node. It's very dangerous to implement this feature.

[Sergey Vasilenko (xenolog)]

This story was implemented by:

Change-Id: I0d545567de84e13bf88fd95e2fc13a03378693b0
Change-Id: I3df45259b9f74e114eaaeaa28c47c5461a87f4a9

[OpenStack Infra (hudson-openstack)]

Change abandoned by Sergey Vasilenko (<email address hidden>) on branch: master
Review: https://review.openstack.org/214514
Reason: This story was implemented by:

Change-Id: I0d545567de84e13bf88fd95e2fc13a03378693b0
Change-Id: I3df45259b9f74e114eaaeaa28c47c5461a87f4a9