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,
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.
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 wrote:
> Hi everybody, does anybody besides Mellanox need this? If not and while
> it's already solved issue for Mellanox itse
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 wrote:
> Hi, Sylwester,
>
> Fuel-plugin-mellanox is in development stage now, so
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 [1] which
We have a bug in fuel [1] 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
[2] for fuel-plugin-mellanox [3] and he said that they use eIPoIB mac
(mapping between ETH
