updated HP CDDLM server
Hi, I've rolled out an updated HP server recently,at the usual address ,http://deployapi.iseran.com:8080/alpine/portal/ now versioned according to <api:build/> field of the static system status property as as $Date: 2006/05/15 15:18:56 $ This release -correctly implements the WSDM management capabilities attribute -handles empty starttime terminatedtime responses. that is <getResourceProperty /> is a valid response for a query of anything with a minOccurs=0 value. -has updated hp tests to match these changes. William Vambenepe clarified what the spec really meant and showed that I'd misinterpreted a bit of it. What is also interesting about this deployment is that we are using the integrated smartfrog/commons-logging/log4j logging components, so that commons-logging stuff goes to smartfrog logs, which then relays to log4j. Which is set up to generate rolling html log files: http://deployapi.iseran.com:8080/logs/ Callers are now free to debug their own operations, as the logger logs received messages and responses. No more need to set up tcpmonitors to this endpoint. Everyone else is free to see what messages get sent around too, which may be informative. -steve
Hi Steve, we have performed our deployment API tests again and updated the test results available at: http://www.lsd.ufcg.edu.br/~ayla/cddlm/test_results_hp/ Regards, Ayla Steve Loughran wrote:
Hi,
I've rolled out an updated HP server recently,at the usual address ,http://deployapi.iseran.com:8080/alpine/portal/
now versioned according to <api:build/> field of the static system status property as as $Date: 2006/05/15 15:18:56 $
This release
-correctly implements the WSDM management capabilities attribute -handles empty starttime terminatedtime responses. that is <getResourceProperty /> is a valid response for a query of anything with a minOccurs=0 value. -has updated hp tests to match these changes.
William Vambenepe clarified what the spec really meant and showed that I'd misinterpreted a bit of it.
What is also interesting about this deployment is that we are using the integrated smartfrog/commons-logging/log4j logging components, so that commons-logging stuff goes to smartfrog logs, which then relays to log4j. Which is set up to generate rolling html log files:
http://deployapi.iseran.com:8080/logs/
Callers are now free to debug their own operations, as the logger logs received messages and responses. No more need to set up tcpmonitors to this endpoint. Everyone else is free to see what messages get sent around too, which may be informative.
-steve
Ayla Debora Dantas de Souza - Projeto Ourgrid wrote:
Hi Steve,
we have performed our deployment API tests again and updated the test results available at: http://www.lsd.ufcg.edu.br/~ayla/cddlm/test_results_hp/
Regards, Ayla
excellent, thank you! Ignoring WS-RF problems (which are strongly in the not-impemented category), the main stopping point is that my current implementation only supports addFile to file: urls , not http: ones. I can add the new feature fairly quickly I suspect, with a new filestore that serves stuff up to being locally visible over HTTP, and maybe externally retrievable too. In production, I'd be biased towards file: URLs for two reasons -you can trivially restrict access by userid -a good network filesystem is available to everything in the cluster, with redundancy. To give http urls redundancy you need multiple hosts responding to the same hostname, which either needs a fancy router (=failure point), dynamic DNS configuration or rendezvous-style mDNS hosts, and JVMs that have their IP caching parameters tuned to give hostname->IPaddr mapping lifetimes down to minutes. -steve
I cant run tests against either the NEC or Ourgrid endpoints -neither server appears to be there
telnet cddlm.lsd.ufcg.edu.br 8080 Trying 150.165.15.37... telnet: connect to address 150.165.15.37: Connection refused telnet: Unable to connect to remote host
telnet cddlm.nec-labs.com 8080 Trying 138.15.110.100...
...hangs until timeout
It is now online! Sorry for the inconvenience... Flávio Steve Loughran wrote:
I cant run tests against either the NEC or Ourgrid endpoints -neither server appears to be there
telnet cddlm.lsd.ufcg.edu.br 8080 Trying 150.165.15.37... telnet: connect to address 150.165.15.37: Connection refused telnet: Unable to connect to remote host
telnet cddlm.nec-labs.com 8080 Trying 138.15.110.100...
...hangs until timeout
-- Flavio Roberto Santos Undergraduate student at Universidade Federal de Campina Grande OurGrid Team Member - www.ourgrid.org My webpage - http://www.ourgrid.org/~flavio -- "As far as the laws of mathematics refer to reality, they are not certain, and as far as they are certain, they do not refer to reality." -- Albert Einstein
It's up now! Sorry for that. On Fri, 2006-06-16 at 12:57 -0300, Flávio Roberto Santos / OurGrid Project wrote:
It is now online! Sorry for the inconvenience...
Flávio
Steve Loughran wrote:
I cant run tests against either the NEC or Ourgrid endpoints -neither server appears to be there
telnet cddlm.lsd.ufcg.edu.br 8080 Trying 150.165.15.37... telnet: connect to address 150.165.15.37: Connection refused telnet: Unable to connect to remote host
telnet cddlm.nec-labs.com 8080 Trying 138.15.110.100...
...hangs until timeout
participants (4)
-
Ayla Debora Dantas de Souza - Projeto Ourgrid -
Flávio Roberto Santos / OurGrid Project -
Satish Bhat -
Steve Loughran