Nailgun API should validate Neutron segmentation type

[Oleg Bondarev]

Valid segmentation types prior to 7.0 are: 'gre', 'vlan'.
Since 7.0 valid types are: 'tun', 'vlan'.

To make transition smoother we want to allow 'gre' for 7.0 with a deprecation warning.

[Sergey Vasilenko (xenolog)]

> and comment that vxlan will be used unstead.

Do you mean "comment that TUN will be used unstead."

Also this request should be processed as 'tun'. Just warning should be given, not an error.

[Sergey Vasilenko (xenolog)]

strict checking should be implemented not earlier 8.0

[Oleg Bondarev (obondarev)]

'tun' is still unclear. I agree it should not be an error, but in warning message we can clarify that default for 'tun' is vxlan.

[Oleg Bondarev (obondarev)]

Marking as incomplete for now as correct behavior is to be agreed yet

[Vladimir Sharshov (vsharshov)]

Still discussion. Does not affect deployment. Moving to 8.0

[Artem Roma (aroma-x)]

Are the final agreement on how deprecation should be done in general regarding Nailgun API is met. Can someone possessing such knowledge please share the details in the comments or update the description. It is not completely clear what must be done on Nailgun side. Also, FYI, I've started thread in openstack-dev [1], feel free to post your comments there too. Move to incomplete until further update.

[1] http://lists.openstack.org/pipermail/openstack-dev/2015-November/079556.html

[Alexey Shtokolov (ashtokolov)]

@xenolog could you please provide the final decision about valid Neutron segmentation types for 7.0 and 8.0?

[Sergey Vasilenko (xenolog)]

7.0 and above has two segmentation types: 'vlan' and 'tun'
'tun' means a 'vxlan'. Also has workaround 'gre' for use deprecated, unrecommended to use 'gre' segmentation.

I propose leave it as is, because we going to deploy both segmentation (tun and vlan) cases simultaneously. VXLAN will be used for this case as tun.