I have not been able to do so, sadly.

> On Aug 15, 2017, at 2:31 PM, Howard Pritchard <hpprit...@gmail.com> wrote:
> 
> HI Folks,
> 
> Thanks Josh.  That doesn't seem to help much though.  Exactly which URL 
> should we be submitting a POST request to get a serial
> number, and what should the data payload format be?  Should it be SERIAL,1 or 
> serial,serial?  The perl code seems to imply
> the former.
> 
> I've tried using a totally generic setup, outside of any LANL firewalls, and 
> am pretty sure now that whatever we have coded up in
> IUDatabase.py doesn't work.
> 
> Has anyone actually gotten the python client to submit results to the IU 
> database?  If so, could someone post their ini
> file to this list?
> 
> Thanks,
> 
> Howard
> 
> 
> 
> 
> 2017-08-14 16:17 GMT-06:00 Howard Pritchard <hpprit...@gmail.com 
> <mailto:hpprit...@gmail.com>>:
> Hi Josh,
> 
> Okay, I changed the URL to submit and now get an interesting error back in 
> the raw output:
> 
> Absolute URI not allowed if server is not a proxy.
> Also, what should be the format of the POST request to get a serial #?  I'm 
> suspicious that
> 
> this area of the pyclient is buggy.
> 
> Howard
> 
> 
> 
> 
> 2017-08-14 15:50 GMT-06:00 Josh Hursey <jjhur...@open-mpi.org 
> <mailto:jjhur...@open-mpi.org>>:
> The CherryPy server was not running... It looks like it died on 6/9 (probably 
> when we upgraded the server since I had to rebuild it's virtualenv). It's 
> running now, and I have setup a monitor to let me know if it goes down again.
> 
> The URL that you need to use for the CherryPy API is:
>   https://mtt.open-mpi.org/submit/cpy/api 
> <https://mtt.open-mpi.org/submit/cpy/api>
> 
> I would give that one a try. If that doesn't work then try the PHP one here:
>   https://mtt.open-mpi.org/submit/ <https://mtt.open-mpi.org/submit/>
> 
> 
> On Mon, Aug 14, 2017 at 3:39 PM, Howard Pritchard <hpprit...@gmail.com 
> <mailto:hpprit...@gmail.com>> wrote:
> HI Folks,
> 
> Well actually I dug into this some more. 
> 
> The problem happens when the pyclient tries to get a serial number from the 
> "IUdatabase" via a post to
> 
> https://mtt.open-mpi.org/serial <https://mtt.open-mpi.org/serial>
> 
> This doesn't work.  mtt-open-mpi.org <http://mtt-open-mpi.org/> comes back 
> with an 404 error.
> 
> Any ideas which URL I should be using to get a serial number back from the 
> database server?
> 
> Howard
> 
> 
> 2017-08-09 12:44 GMT-06:00 Van Dresser, Daniel N 
> <daniel.n.van.dres...@intel.com <mailto:daniel.n.van.dres...@intel.com>>:
> Hi Howard,
> 
>  
> 
> Ricky might be able to answer this when he returns from holiday next week.  
> If not, Josh might know.
> 
>  
> 
> If you end up debugging this further on your own, I would recommend using the 
> docker images for postgres and cherrypy.
> 
>  
> 
> Instructions for building and testing those images: 
> https://github.com/open-mpi/mtt/blob/master/server/docker/README.docker.txt 
> <https://github.com/open-mpi/mtt/blob/master/server/docker/README.docker.txt>
> Note the instructions in that readme need to be run from the mtt/server 
> directory.
> 
>  
> 
> Thanks,
> 
>  
> 
>   -- Noah
> 
>  
> 
>   <>
>  <>From: mtt-devel [mailto:mtt-devel-boun...@lists.open-mpi.org 
> <mailto:mtt-devel-boun...@lists.open-mpi.org>] On Behalf Of Howard Pritchard
> Sent: Wednesday, August 09, 2017 3:06 AM
> To: Development list for the MPI Testing Tool <mtt-devel@lists.open-mpi.org 
> <mailto:mtt-devel@lists.open-mpi.org>>
> Subject: [MTT devel] trying again to ppost results to "IU" using pyclient
> 
>  
> 
> Hi Folks,
> 
>  
> 
> Finally I got a chance to return to using the pyclient (with python3 - which 
> is another story and subject of an upcoming PR).
> 
>  
> 
> Things seem to work till I try to post to "IU" database, in which case with 
> --verbose I get
> 
> this request/response output:
> 
>  
> 
> <<<<<<<---------------- Payload (End  ) -------------------------->>>>>>
> 
> /opt/hi-master/Python-3.6.2/lib/python3.6/site-packages/urllib3/connectionpool.py:858:
>  InsecureRequestWarning: Unverified HTTPS request is being made. Adding 
> certificate verification is strongly advised. See: 
> https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings 
> <https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings>
>   InsecureRequestWarning)
> 
> /opt/hi-master/Python-3.6.2/lib/python3.6/site-packages/urllib3/connectionpool.py:858:
>  InsecureRequestWarning: Unverified HTTPS request is being made. Adding 
> certificate verification is strongly advised. See: 
> https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings 
> <https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings>
>   InsecureRequestWarning)
> 
> <<<<<<<---------------- Response -------------------------->>>>>>
> 
> Result: 400: text/html; charset=UTF-8
> 
> {'Date': 'Wed, 09 Aug 2017 09:57:16 GMT', 'Server': 'Apache/2.4.18 (Ubuntu)', 
> 'Content-Length': '54', 'Connection': 'close', 'Content-Typ ----- Message 
> truncated -----
> 
> <<<<<<<---------------- Raw Output (Start) ---------------->>>>>>
> 
> MTTDatabase abort: 
> 
> MTT client version not specified.
> 
>  
> 
> <<<<<<<---------------- Raw Output (End  ) ---------------->>>>>>
> 
>  
> 
> Any ideas what I need to add to get the pyclient to submit results to "IU" 
> with client version
> 
> included in the HTTP request?
> 
>  
> 
> Thanks,
> 
> Howard
> 
>  
> 
> 
> _______________________________________________
> mtt-devel mailing list
> mtt-devel@lists.open-mpi.org <mailto:mtt-devel@lists.open-mpi.org>
> https://lists.open-mpi.org/mailman/listinfo/mtt-devel 
> <https://lists.open-mpi.org/mailman/listinfo/mtt-devel>
> 
> 
> _______________________________________________
> mtt-devel mailing list
> mtt-devel@lists.open-mpi.org <mailto:mtt-devel@lists.open-mpi.org>
> https://lists.open-mpi.org/mailman/listinfo/mtt-devel 
> <https://lists.open-mpi.org/mailman/listinfo/mtt-devel>
> 
> 
> 
> -- 
> Josh Hursey
> IBM Spectrum MPI Developer
> 
> _______________________________________________
> mtt-devel mailing list
> mtt-devel@lists.open-mpi.org <mailto:mtt-devel@lists.open-mpi.org>
> https://lists.open-mpi.org/mailman/listinfo/mtt-devel 
> <https://lists.open-mpi.org/mailman/listinfo/mtt-devel>
> 
> 
> _______________________________________________
> mtt-devel mailing list
> mtt-devel@lists.open-mpi.org
> https://lists.open-mpi.org/mailman/listinfo/mtt-devel

_______________________________________________
mtt-devel mailing list
mtt-devel@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/mtt-devel

Reply via email to