Emanuel Muckenhuber wrote:
Hmm some modifications i have in mind are: -) subsystem updates - since they are part of extensions
-) creating new subsystems - since they might require an <extension /> module
-) a domain deployment used by 2 server-groups... where you update only one group with a new deployment
-) changing the value of a socket binding / jvm and determining which server-groups / servers are affected
-) a deployment targeted to a single server - which would require to split the server-group? not sure if we want to allow that, but we had some discussions with the console team about that
That seems like a good list, except for the last one. That's OK, too, but I was just now thinking that kind of thing should be decomposed into 2 steps: forming a new server-group from a set of servers, and then applying any change to that new server group. So the deployment becomes one type of change. All the servers that form a new server group would need to be consistent. They wouldn't need to come from the same server-group (although we could require that to make life easier) but their configurations would need to be consistent.