Bug 1054360 - RFE: let users run an AS7/EAP6 CLI script with an operation on Standalone or Host Controller resources
Libor Zoubek
lzoubek at redhat.com
Wed Feb 19 09:53:07 UTC 2014
Thanks Jay.
Dne Mon, 17 Feb 2014 22:38:10 +0100 Jay Shaughnessy <jshaughn at redhat.com>
napsal(a):
>
> On 2/17/2014 10:48 AM, Libor Zoubek wrote:
>> Hello,
>>
>> I started to work on
>> https://bugzilla.redhat.com/show_bug.cgi?id=1054360 I have several more
>> or less cosmetic questions:
>>
>> 1. In order to run jboss-cli plugin needs to know AS7 native management
>> port and interface. I've introduced 1 pluginConfig property
>> <host>:<port> and added it into "operations" group. Could it be
>> considered as correct? I mean I could create 2 properties (similar to
>> what we have for http management interface host and port).
>
> In general we use separate properties, I think, one text and one
> integer. This is easier to validate. Actually, I thought the
> management host and port were already connection properties? No? If not,
> and if not discoverable, then perhaps the missing information should be
> operation properties as opposed to connection properties (plugin config).
Management host and port in connection properties regard to EAP's
http-interface, CLI tool talks to native (DMR). I could reuse host - that
would work for 99% of cases, but once user would configured his EAP and
set different interface (IP address) to http and native management, we'd
fail.
Thanks, I'll split.
>>
>> 2. Plugin in the end runs jboss-cli process with several parameters. I
>> am setting ProcessExecution.setWaitForCompletion some hardcoded value
>> to wait for process to finish. Is it possible/recommended to fill the
>> value with timeout for operation defined in plugin descriptor? When
>> timeout ProcessExecution.setWaitForCompletion is reached, child process
>> is killed, I tend to set such timeout to very big number, since I don't
>> want child script to get interrupted in case user did not correctly set
>> operation timeout (he did not expect his script to run too long).
>
> I would suggest the timeout probably be an operation config property.
But there already is timeout for operations. Is there a way to get to this
value at runtime on agent side within operation code? I am only able to
get to default value using ResourceType.
>>
>> 4. What would you suggest as default timeout for "executeCommands" and
>> "executeScript" operations? (Iam now on 60s)
>>
>> 5. As scripts are expected to do AS configuration changes, would you
>> recommend to requestAvailabilityCheck() and
>> requestDeferredChildResourcesDiscovery() after successfull script
>> execution?
>
> I don't know but these could, I guess also be operation config
> properties.
>>
>> Thank you
>>
>
> _______________________________________________
> rhq-devel mailing list
> rhq-devel at lists.fedorahosted.org
> https://lists.fedorahosted.org/mailman/listinfo/rhq-devel
--
Libor Zoubek
More information about the rhq-devel
mailing list