|Anonymous | Login | Signup for a new account||02-28-2020 10:26 PST|
|Main | My View | View Issues | Change Log | Docs|
|Viewing Issue Simple Details [ Jump to Notes ]||[ View Advanced ] [ Issue History ] [ Print ]|
|ID||Category||Severity||Reproducibility||Date Submitted||Last Update|
|0002867||[Resin]||minor||always||08-25-08 14:16||03-25-09 09:20|
|Summary||0002867: dynamic server with load balancing|
(rep by Dana P'Simer)
We are looking for a way to achieve a requirement that will help us
stand up new versions of our application in production. What we want to
be able to do is bring down a server and install new software on it.
For a short time we would like that server with the new software to only
be available to certain clients. These clients can either set a cookie
or add a parameter to the URL. Then when we have tested the build on
that one node, we would then push it into the production pool for new
traffic to hit and do the same to another node untill all the nodes have
I am looking at Resin's load balancer to see if it can fill this need.
I do not, however, see any way to change the members of a cluster at
runtime. Is there are feature that I am missing or can you suggest
another route to achive the same result?
|08-25-08 14:16||ferg||New Issue|
|03-25-09 09:20||ferg||Note Added: 0003924|
|03-25-09 09:20||ferg||Assigned To||=> ferg|
|03-25-09 09:20||ferg||Status||new => closed|
|03-25-09 09:20||ferg||Resolution||open => fixed|
|03-25-09 09:20||ferg||Fixed in Version||=> 4.0.0|
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
28 total queries executed.|
25 unique queries executed.