Hawkbit multitenancy implementation

[michalsroka]

Hi, My team would like to use hawkBit in our project. However, it requires multitenancy thus we are interested in implementing it.

Are You interested in such feature in the project? Maybe You already have it in your roadmap?

Do You believe that it would be possible to merge our solution to the master branch? Do You have any technical or maintenance concerns or suggestions?

[schabdo]

First of all sorry for the late reply. This issue got somehow off my grid. Nevertheless glad to hear that you're interested in using hawkBit and even consider a major contribution!

Are You interested in such feature in the project? Maybe You already have it in your roadmap?

It's currently not on the project's roadmap since demand is not high enough to justify the required implementation effort. Basic tenant support is already in place so extending it to multi-tenant should be feasible.

Do You believe that it would be possible to merge our solution to the master branch?

Do you have an implementation already?

Do You have any technical or maintenance concerns or suggestions?

If you seriously want to implement this feature I'm happy to support you in more detail. Generally speaking multitenancy should be an optional feature and we should aim for a generic plug-in point so the community is able to use change source of their tenants easily.

What exactly do you have in mind? A statically configured (e.g. file-based) list of tenants or even a 3rd-party system for management of tenants?

[rmrxOSB]

We would also be very interested in this feature.

We currently use one instance for every client.

But there could also be customers with very small numbers of devices. Were one server could easily handle 10 or more Clients/Tennants.

[harshadesai]

We would also be very interested in this feature. We don't want to use different instance for every client. Can you please guide me to some links or any pointers where I need to start looking into it.

Thanks.