-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Limit the number of app instances on the same node #6955
Labels
verified
All test cases were verified successfully
Milestone
Comments
23 tasks
DavidePrincipi
added a commit
to NethServer/ns8-core
that referenced
this issue
Jul 9, 2024
Add attribute install_destinations to list-modules Refs NethServer/dev#6955
Test case This feature can be tested once an application with label At that time, the Software Center prevents the installation of a second Mail instance into the same node. |
In testing:
|
This was referenced Oct 11, 2024
DavidePrincipi
added a commit
to NethServer/ns8-netdata
that referenced
this issue
Oct 14, 2024
DavidePrincipi
added a commit
to NethServer/ns8-crowdsec
that referenced
this issue
Oct 14, 2024
DavidePrincipi
added a commit
to nethesis/ns8-nethvoice-proxy
that referenced
this issue
Oct 14, 2024
DavidePrincipi
added a commit
to NethServer/ns8-mail
that referenced
this issue
Oct 15, 2024
Fix reference to NethServer/dev#6955 in Git history. See commit 501a6fb
stephdl
added a commit
to NethServer/ns8-ejabberd
that referenced
this issue
Oct 15, 2024
Limit ejabberd to one module per node NethServer/dev#6955
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Applications with fixed port numbers like Mail and Ejabberd are limited to one instance per node, otherwise a port conflict arises at run time. The Software Center should limit the number of instances in the same node for such applications.
The limit may be observed also by the Clone/Move action, available from Software Center. However these advanced cases may prefer to allow a temporary conflict: it is a scenario that needs further evaluation.
Proposed solution
In the Install action, the Software Center prevents the selection of cluster nodes that already have an instance of the conflicting application.
Alternative solutions
The Software Center warns if a node is selected that already has a conflicting app instance.
Additional context
See also
The text was updated successfully, but these errors were encountered: