Out of band signaling from agent/plugin to server / user

John Mazzitelli mazz at redhat.com
Fri May 11 13:33:02 UTC 2012


can the "activation" attribute that all configuration simple properties support be used here?

That was the purpose of that - today, we can say something like:

<property name="foo" attribute="restart" ... />

and that means if that property is changed, it requires a restart for the change to take effect.

Today we actually don't do anything with that attribute, but its there and can be used for something.

----- Original Message -----
> Hi,
> 
> so in AS7 we have a situation, that a configuration change can be
> applied to a (as7)resource, but this
> change is not active until the target server is rebooted or reloaded.
> 
> [standalone at localhost:9999 subsystem=datasources] :read-resource
> {
>     "outcome" => "success",
>     "result" => {
> [...]    },
>     "response-headers" => {"process-state" => "reload-required"}
> 
> Now this only applies to some changes, so blindly just rebooting the
> server is not what the user wants.
> 
> One way to accomplish this is to signal this to the user -- e.g. via
> the Configuration object that is returned.
> One way could be by passing it via the notes field, which is unused
> (except for some tests). Another
> via additional "hidden" properties (that do not show up in the plugin
> descriptor).
> Both work and can trigger the display of a yellow bar in the UI (what
> about the CLI?), but they also trigger
> the recording of a new configuration version.
> 
> Of course the configuration change signaling is only one piece of the
> game. We also need that for operations or create
> child.
> 
> Ian has proposed to use the ResourceError object, which could work.
> It has from my POV the disadvantage that
> its notes are sticky. Either this RE only gets triggered on the
> resource itself, which means the user may not see it
> or it is triggered on other resources as well, which means after the
> "problem" goes away, the user must visit
> multiple places to click the yellow-triangle away. One can get this
> to work, but I think it is not user friendly at
> all.
> 
> Not giving the "reload needed" feedback to the user is IMO no option.
> 
> We could change the logic a bit that the storage of new versions is
> not taking the note field into
> account, but always deliver the latest version (comparing with the
> notes field ). Again this is only a tiny piece,
> but would at least give the user some feedback.
> 
> See also https://bugzilla.redhat.com/show_bug.cgi?id=802810
> 
> --
> Reg. Adresse: Red Hat GmbH, Technopark II, Haus C,
> Werner-von-Siemens-Ring 14, D-85630 Grasbrunn
> Handelsregister: Amtsgericht München HRB 153243
> Geschaeftsführer:  Mark Hegarty, Charlie Peters, Michael Cunningham,
> Charles Cachera
> 
> _______________________________________________
> rhq-devel mailing list
> rhq-devel at lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/rhq-devel
> 


More information about the rhq-devel mailing list