Out of band signaling from agent/plugin to server / user
Ian Springer
ian.springer at redhat.com
Fri May 11 14:43:13 UTC 2012
I also think the activation policy enum needs to be redesigned.
public enum ActivationPolicy {
IMMEDIATE, RESTART, SHUTDOWN
}
Does RESTART refer to the managed resource or to the server process?
What is SHUTDOWN supposed to mean? Here's what I would change it to:
public enum ActivationPolicy {
/** this managed resource needs to be restarted in order for the
change to take effect */
MANAGED_RESOURCE_RESTART_REQUIRED,
/** the server process needs to be restarted in order for the change
to take effect */
PROCESS_RESTART_REQUIRED
}
I would get rid of IMMEDIATE, and just interpret a null value for
PropertyDefinition.activationPolicy as "the change will go into effect
immediately".
On 05/11/2012 10:11 AM, Heiko W.Rupp wrote:
> Am 11.05.2012 um 15:33 schrieb John Mazzitelli:
>
>> <property name="foo" attribute="restart" ... />
>>
>> and that means if that property is changed, it requires a restart for the change to take effect.
> First this would be a tremendous effort to add this to every property or resource in the already
> huge plugin descriptor and then (could be partially automated) and then we may miss some
> in the future.
>
> And then, the idea is that a user can change several properties etc. and they come active
> as a whole after a restart/reload (slightly different semantics), so we would not want to automatically
> do that for the user.
> The user may in fact even plan a config change for midnight. She enters all the new values and
> then plans a reload operation for midnight to be executed.
>
> Heiko
>
> _______________________________________________
> rhq-devel mailing list
> rhq-devel at lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/rhq-devel
--
Ian Springer
Principal Software Developer
JBoss Operations Network
Red Hat
ian.springer at redhat.com
More information about the rhq-devel
mailing list