You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Limit Guest Network per project/account, etc. #10940
As an Admin/Operator I would like to limit the number of Guest Networks a user can have.
In our multi-tenant environment, each Guest Network of type Shared gives the user VMs a public IP. And the option that already exists for limiting public IPs does not work for our use case because of our architecture.
I have implemented most of the code in a private branch and it is currently going through some internal testing. I would like to know if this is something you want implemented in the upstream branch so I can go ahead and create a PR for it.
@hosmir, on accounts you can set a limit to the number of networks they can create. If this is not the functionality you mean, then we are certainly interested in your proposal/code.
In our multi-tenant environment, each Guest Network of type Shared gives the user VMs a public IP. And the option that already exists for limiting public IPs does not work for our use case because of our architecture.
@hosmir
Is it a typo, did you mean Isolated network (not Shared) ?
@hosmir, on accounts you can set a limit to the number of networks they can create. If this is not the functionality you mean, then we are certainly interested in your proposal/code.
Tenants are free to create and use many networks if they wish, only the public IPs (that they attain via assigning a shared guest network to their VMs) should be limited.
I will tidy up the code in the coming days and since I implemented the code for v4.17.2, I will need to adapt it to the main branch from upstream. Will open a PR the soonest I can.
Thanks
In our multi-tenant environment, each Guest Network of type Shared gives the user VMs a public IP. And the option that already exists for limiting public IPs does not work for our use case because of our architecture.
@hosmir Is it a typo, did you mean Isolated network (not Shared) ?
No, I actually meant shared networks, since they are how tenants can assign a public IP to their VMs from pools of predefined shared networks.
Activity
DaanHoogland commentedon Jun 2, 2025
@hosmir, on accounts you can set a limit to the number of networks they can create. If this is not the functionality you mean, then we are certainly interested in your proposal/code.
weizhouapache commentedon Jun 2, 2025
@hosmir
Is it a typo, did you mean Isolated network (not Shared) ?
hosmir commentedon Jun 3, 2025
Tenants are free to create and use many networks if they wish, only the public IPs (that they attain via assigning a shared guest network to their VMs) should be limited.
I will tidy up the code in the coming days and since I implemented the code for v4.17.2, I will need to adapt it to the main branch from upstream. Will open a PR the soonest I can.
Thanks
hosmir commentedon Jun 3, 2025
No, I actually meant shared networks, since they are how tenants can assign a public IP to their VMs from pools of predefined shared networks.