Monitoring multiple targets

[fcohen]

Here is my proposed solution to ticket 240:

<monitoring enablednodes="true" enabledtarget="true" targethost="http://localhost">
    <targethost name="host1" location="http://192.168.1.102:8011/targethost1" enabled="true"/>
    <targethost name="host2" location="http://192.168.1.102/targethost1" enabled="true"/>
    <targethost name="host3" location="http://192.168.1.102/targethost1" enabled="false"/>
    <testnode name="node1" location="http://localhost:51111"/>
</monitoring>

The <targehost> entries use 51111 by default. This is overridden in the location attributed.

TestMaker ignores entries with the enabled attribute set to false.

-Frank

[jack]

I've tested this ticket and it worked according to Max's directions.

[mvillalobos]

Replying to fcohen:

[mvillalobos]

<monitoring enablednodes="true" enabledtarget="true" targethost="http://localhost">

<targethost name="host1" location="http://192.168.1.102:8011/targethost1" enabled="true"/> <targethost name="host2" location="http://192.168.1.102/targethost1" enabled="true"/> <targethost name="host3" location="http://192.168.1.102/targethost1" enabled="false"/>

</monitoring>

In the previous XML, there's a conflict between the targethost attribute in the <monitoring> tag and the list of targethost elements that go inside the <monitoring> tag.

When parsing the XML, you wrote reader.getMonitoring().getTargethost() and the compiler had a conflict because it didn't know if it was searching the targethost in the <monitoring> tag or the list of targethosts inside it.

To solve that, we used the tag <host> for the list of multiple hosts and left targethost for the one that is an attribute of the tag <monitoring>, so the XML will be like this:

<monitoring enablednodes="true" enabledtarget="true" targethost="http://localhost">

<host name="host1" location="http://192.168.1.102:8011/targethost1" enabled="true"/> <host name="host2" location="http://192.168.1.102/targethost1" enabled="true"/> <host name="host3" location="http://192.168.1.102/targethost1" enabled="false"/>

</monitoring>

[fcohen]

Max wrote:

For ticket, 240, which Jack needs to check, there was a little thing to fix. ControlRunner? was throwing the information of all hosts together in a file named AppHost?, but now it throws the information of the multiple targets in separate files. It was a big mistake from my part not explaining this commit. It tends to happen when the commit is just a small change.

[fcohen]

Confirmed working. Closing this ticket. -Frank