Hi Sergii, As for me, if someone creates a plugin for infiniband - he may store it's mac address at any place, not strictly in our Nailgun model. Also, I created the request changing field length in Nailgun, but there are still possible places in Fuel library or even some other related projects
Hi, Sylwester, Fuel-plugin-mellanox is in development stage now, so no one can use it. I think, a longer MAC field may be helpful for other plugin developers in future. On Tue, Apr 28, 2015 at 12:50 AM, Sylwester Brzeczkowski sbrzeczkow...@mirantis.com wrote: We have a bug in fuel  which
Hi everybody, does anybody besides Mellanox need this? If not and while it's already solved issue for Mellanox itself - let's just close the bug as won't fix for now. On Wed, Apr 29, 2015 at 11:16 AM, Andrey Danin ada...@mirantis.com wrote: Hi, Sylwester, Fuel-plugin-mellanox is in
Hello, If all is ok, let's move bug to 7.0 and fix it with netaddr as it was proposed in comments to the ticket. - Igor On Wed, Apr 29, 2015 at 6:29 PM, Nikolay Markov nmar...@mirantis.com wrote: Hi everybody, does anybody besides Mellanox need this? If not and while it's already solved
Hi, At my point we need to fix it 6.1. As during whole lifecycle of 6.1 someone may create own plugin for infiniband. If it's not required now, it may be required later. Extending column in table should not be a big problem. If we drop the feature, the documentation should be updated accordingly.
We have a bug in fuel  which concerns infiniband support. It's mostly about expanding the size of mac field in db from 17 to 59. But I've email Aviram Bar-Haim who was working on for infiniband support  for fuel-plugin-mellanox  and he said that they use eIPoIB mac (mapping between ETH