2016-10-16 23:30:16 +00:00
|
|
|
# This file is part of BOINC.
|
|
|
|
# http://boinc.berkeley.edu
|
|
|
|
# Copyright (C) 2016 University of California
|
|
|
|
#
|
|
|
|
# BOINC is free software; you can redistribute it and/or modify it
|
|
|
|
# under the terms of the GNU Lesser General Public License
|
|
|
|
# as published by the Free Software Foundation,
|
|
|
|
# either version 3 of the License, or (at your option) any later version.
|
|
|
|
#
|
|
|
|
# BOINC is distributed in the hope that it will be useful,
|
|
|
|
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
|
|
|
# See the GNU Lesser General Public License for more details.
|
|
|
|
#
|
|
|
|
# You should have received a copy of the GNU Lesser General Public License
|
|
|
|
# along with BOINC. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
|
|
|
|
|
2016-10-18 07:38:02 +00:00
|
|
|
# Python bindings of the remote job submission and file management APIs
|
2016-10-16 23:28:55 +00:00
|
|
|
|
|
|
|
import urllib
|
|
|
|
import copy
|
|
|
|
import xml.etree.ElementTree as ET
|
2016-10-16 23:30:16 +00:00
|
|
|
import requests
|
|
|
|
# you'll need to "yip install requests"
|
2016-10-16 23:28:55 +00:00
|
|
|
|
Remote job submission: add support for per-job templates in submit requests
This supports the TACC use case,
in the jobs in a batch can use different Docker images
and different input and output file signatures,
none of which are known in advance.
Python API binding:
- A JOB_DESC object can optionally contain wu_template and result_template
elements, which are the templates (the actual XML) to use for that job.
Add these to the XML request message if present.
- Added the same capability to the PHP binding, but not C++.
- Added and debugged test cases for both languages.
Also, submit_batch() can take either a batch name (in which case
the batch is created) or a batch ID
(in which the batch was created prior to remotely staging files).
RPC handler:
- in submit_batch(), check for jobs with templates specified
and store them in files.
For input templates (which are deleted after creating jobs)
we put them in /tmp,
and use a map so that if two templates are the same we use 1 file.
For output templates (which have to last until all jobs are done)
we put them in templates/tmp, with content-based filenames
to economize.
- When creating jobs, or generating SQL strings for multiple jobs,
use these names as --wu_template_filename
and --result_template_filename args to create_work
(either cmdline args or stdin args)
- Delete WU templates when done
create_work.cpp:
handle per-job --wu_template and --result_template args in stdin job lines
(the names of per-job WU and result templates).
Maintain a map mapping WU template name to contents,
to avoid repeatedly reading them.
For jobs that don't specify templates, use the ones specified
at the batch level, or the defaults.
2017-01-21 08:24:11 +00:00
|
|
|
# describes an input file
|
2016-10-16 23:28:55 +00:00
|
|
|
#
|
|
|
|
class FILE_DESC:
|
|
|
|
def __init__(self):
|
|
|
|
return
|
|
|
|
def to_xml(self):
|
|
|
|
xml = ('<input_file>\n'
|
|
|
|
'<mode>%s</mode>\n'
|
|
|
|
) %(self.mode)
|
|
|
|
if self.mode == 'remote':
|
|
|
|
xml += ('<url>%s</url>\n'
|
|
|
|
'<nbytes>%f</nbytes>\n'
|
|
|
|
'<md5>%s</md5>\n'
|
|
|
|
) %(self.url, self.nbytes, self.md5)
|
|
|
|
else:
|
|
|
|
xml += '<source>%s</source>\n' %(self.source)
|
|
|
|
xml += '</input_file>\n'
|
|
|
|
return xml
|
|
|
|
|
Remote job submission: add support for per-job templates in submit requests
This supports the TACC use case,
in the jobs in a batch can use different Docker images
and different input and output file signatures,
none of which are known in advance.
Python API binding:
- A JOB_DESC object can optionally contain wu_template and result_template
elements, which are the templates (the actual XML) to use for that job.
Add these to the XML request message if present.
- Added the same capability to the PHP binding, but not C++.
- Added and debugged test cases for both languages.
Also, submit_batch() can take either a batch name (in which case
the batch is created) or a batch ID
(in which the batch was created prior to remotely staging files).
RPC handler:
- in submit_batch(), check for jobs with templates specified
and store them in files.
For input templates (which are deleted after creating jobs)
we put them in /tmp,
and use a map so that if two templates are the same we use 1 file.
For output templates (which have to last until all jobs are done)
we put them in templates/tmp, with content-based filenames
to economize.
- When creating jobs, or generating SQL strings for multiple jobs,
use these names as --wu_template_filename
and --result_template_filename args to create_work
(either cmdline args or stdin args)
- Delete WU templates when done
create_work.cpp:
handle per-job --wu_template and --result_template args in stdin job lines
(the names of per-job WU and result templates).
Maintain a map mapping WU template name to contents,
to avoid repeatedly reading them.
For jobs that don't specify templates, use the ones specified
at the batch level, or the defaults.
2017-01-21 08:24:11 +00:00
|
|
|
# describes a job
|
2016-10-16 23:28:55 +00:00
|
|
|
#
|
|
|
|
class JOB_DESC:
|
|
|
|
def __init__(self):
|
|
|
|
return
|
|
|
|
def to_xml(self):
|
Remote job submission: add support for per-job templates in submit requests
This supports the TACC use case,
in the jobs in a batch can use different Docker images
and different input and output file signatures,
none of which are known in advance.
Python API binding:
- A JOB_DESC object can optionally contain wu_template and result_template
elements, which are the templates (the actual XML) to use for that job.
Add these to the XML request message if present.
- Added the same capability to the PHP binding, but not C++.
- Added and debugged test cases for both languages.
Also, submit_batch() can take either a batch name (in which case
the batch is created) or a batch ID
(in which the batch was created prior to remotely staging files).
RPC handler:
- in submit_batch(), check for jobs with templates specified
and store them in files.
For input templates (which are deleted after creating jobs)
we put them in /tmp,
and use a map so that if two templates are the same we use 1 file.
For output templates (which have to last until all jobs are done)
we put them in templates/tmp, with content-based filenames
to economize.
- When creating jobs, or generating SQL strings for multiple jobs,
use these names as --wu_template_filename
and --result_template_filename args to create_work
(either cmdline args or stdin args)
- Delete WU templates when done
create_work.cpp:
handle per-job --wu_template and --result_template args in stdin job lines
(the names of per-job WU and result templates).
Maintain a map mapping WU template name to contents,
to avoid repeatedly reading them.
For jobs that don't specify templates, use the ones specified
at the batch level, or the defaults.
2017-01-21 08:24:11 +00:00
|
|
|
xml = '<job>\n'
|
|
|
|
if hasattr(self, 'rsc_fpops'):
|
|
|
|
xml += '<rsc_fpops_est>%f</rsc_fpops_est>\n'%self.rsc_fpops_est
|
|
|
|
if hasattr(self, 'command_line'):
|
|
|
|
xml += '<command_line>%s</command_line>\n'%self.command_line
|
|
|
|
if hasattr(self, 'wu_template'):
|
|
|
|
xml += '<wu_template>\n%s\n</wu_template>\n'%self.wu_template
|
|
|
|
if hasattr(self, 'result_template'):
|
|
|
|
xml += '<result_template>\n%s\n</result_template>\n'%self.result_template
|
2016-10-16 23:28:55 +00:00
|
|
|
for file in self.files:
|
|
|
|
xml += file.to_xml()
|
2016-10-16 23:30:16 +00:00
|
|
|
xml += '</job>\n'
|
2016-10-16 23:28:55 +00:00
|
|
|
return xml
|
|
|
|
|
Remote job submission: add support for per-job templates in submit requests
This supports the TACC use case,
in the jobs in a batch can use different Docker images
and different input and output file signatures,
none of which are known in advance.
Python API binding:
- A JOB_DESC object can optionally contain wu_template and result_template
elements, which are the templates (the actual XML) to use for that job.
Add these to the XML request message if present.
- Added the same capability to the PHP binding, but not C++.
- Added and debugged test cases for both languages.
Also, submit_batch() can take either a batch name (in which case
the batch is created) or a batch ID
(in which the batch was created prior to remotely staging files).
RPC handler:
- in submit_batch(), check for jobs with templates specified
and store them in files.
For input templates (which are deleted after creating jobs)
we put them in /tmp,
and use a map so that if two templates are the same we use 1 file.
For output templates (which have to last until all jobs are done)
we put them in templates/tmp, with content-based filenames
to economize.
- When creating jobs, or generating SQL strings for multiple jobs,
use these names as --wu_template_filename
and --result_template_filename args to create_work
(either cmdline args or stdin args)
- Delete WU templates when done
create_work.cpp:
handle per-job --wu_template and --result_template args in stdin job lines
(the names of per-job WU and result templates).
Maintain a map mapping WU template name to contents,
to avoid repeatedly reading them.
For jobs that don't specify templates, use the ones specified
at the batch level, or the defaults.
2017-01-21 08:24:11 +00:00
|
|
|
# describes a batch for submit() or estimate()
|
2016-10-16 23:28:55 +00:00
|
|
|
#
|
|
|
|
class BATCH_DESC:
|
|
|
|
def __init__(self):
|
|
|
|
return
|
|
|
|
|
|
|
|
def to_xml(self, op):
|
|
|
|
xml = ('<%s>\n'
|
Remote job submission: add support for per-job templates in submit requests
This supports the TACC use case,
in the jobs in a batch can use different Docker images
and different input and output file signatures,
none of which are known in advance.
Python API binding:
- A JOB_DESC object can optionally contain wu_template and result_template
elements, which are the templates (the actual XML) to use for that job.
Add these to the XML request message if present.
- Added the same capability to the PHP binding, but not C++.
- Added and debugged test cases for both languages.
Also, submit_batch() can take either a batch name (in which case
the batch is created) or a batch ID
(in which the batch was created prior to remotely staging files).
RPC handler:
- in submit_batch(), check for jobs with templates specified
and store them in files.
For input templates (which are deleted after creating jobs)
we put them in /tmp,
and use a map so that if two templates are the same we use 1 file.
For output templates (which have to last until all jobs are done)
we put them in templates/tmp, with content-based filenames
to economize.
- When creating jobs, or generating SQL strings for multiple jobs,
use these names as --wu_template_filename
and --result_template_filename args to create_work
(either cmdline args or stdin args)
- Delete WU templates when done
create_work.cpp:
handle per-job --wu_template and --result_template args in stdin job lines
(the names of per-job WU and result templates).
Maintain a map mapping WU template name to contents,
to avoid repeatedly reading them.
For jobs that don't specify templates, use the ones specified
at the batch level, or the defaults.
2017-01-21 08:24:11 +00:00
|
|
|
'<authenticator>%s</authenticator>\n'
|
|
|
|
'<batch>\n'
|
|
|
|
'<app_name>%s</app_name>\n'
|
|
|
|
) %(op, self.authenticator, self.app_name)
|
|
|
|
|
|
|
|
if hasattr(self, 'batch_id'):
|
|
|
|
xml += '<batch_id>%s</batch_id>\n'%(self.batch_id)
|
|
|
|
elif hasattr(self, 'batch_name'):
|
|
|
|
xml += '<batch_name>%s</batch_name>\n'%(self.batch_name)
|
2016-10-16 23:28:55 +00:00
|
|
|
for job in self.jobs:
|
|
|
|
xml += job.to_xml()
|
|
|
|
xml += '</batch>\n</%s>\n' %(op)
|
|
|
|
return xml
|
|
|
|
|
2016-10-18 07:38:02 +00:00
|
|
|
class CREATE_BATCH_REQ:
|
|
|
|
def __init__(self):
|
|
|
|
return
|
|
|
|
def to_xml(self):
|
Remote job submission: add support for per-job templates in submit requests
This supports the TACC use case,
in the jobs in a batch can use different Docker images
and different input and output file signatures,
none of which are known in advance.
Python API binding:
- A JOB_DESC object can optionally contain wu_template and result_template
elements, which are the templates (the actual XML) to use for that job.
Add these to the XML request message if present.
- Added the same capability to the PHP binding, but not C++.
- Added and debugged test cases for both languages.
Also, submit_batch() can take either a batch name (in which case
the batch is created) or a batch ID
(in which the batch was created prior to remotely staging files).
RPC handler:
- in submit_batch(), check for jobs with templates specified
and store them in files.
For input templates (which are deleted after creating jobs)
we put them in /tmp,
and use a map so that if two templates are the same we use 1 file.
For output templates (which have to last until all jobs are done)
we put them in templates/tmp, with content-based filenames
to economize.
- When creating jobs, or generating SQL strings for multiple jobs,
use these names as --wu_template_filename
and --result_template_filename args to create_work
(either cmdline args or stdin args)
- Delete WU templates when done
create_work.cpp:
handle per-job --wu_template and --result_template args in stdin job lines
(the names of per-job WU and result templates).
Maintain a map mapping WU template name to contents,
to avoid repeatedly reading them.
For jobs that don't specify templates, use the ones specified
at the batch level, or the defaults.
2017-01-21 08:24:11 +00:00
|
|
|
xml = ('<create_batch>\n'
|
2016-10-18 07:38:02 +00:00
|
|
|
'<authenticator>%s</authenticator>\n'
|
|
|
|
'<app_name>%s</app_name>\n'
|
|
|
|
'<batch_name>%s</batch_name>\n'
|
|
|
|
'<expire_time>%f</expire_time>\n'
|
|
|
|
'</create_batch>\n') %(self.authenticator, self.app_name, self.batch_name, self.expire_time)
|
|
|
|
return xml
|
|
|
|
|
2016-10-16 23:28:55 +00:00
|
|
|
# a generic request
|
|
|
|
#
|
|
|
|
class REQUEST:
|
|
|
|
def __init__(self):
|
|
|
|
return
|
|
|
|
|
2016-10-18 07:38:02 +00:00
|
|
|
def do_http_post(req, project_url, handler='submit_rpc_handler.php'):
|
Remote job submission: add support for per-job templates in submit requests
This supports the TACC use case,
in the jobs in a batch can use different Docker images
and different input and output file signatures,
none of which are known in advance.
Python API binding:
- A JOB_DESC object can optionally contain wu_template and result_template
elements, which are the templates (the actual XML) to use for that job.
Add these to the XML request message if present.
- Added the same capability to the PHP binding, but not C++.
- Added and debugged test cases for both languages.
Also, submit_batch() can take either a batch name (in which case
the batch is created) or a batch ID
(in which the batch was created prior to remotely staging files).
RPC handler:
- in submit_batch(), check for jobs with templates specified
and store them in files.
For input templates (which are deleted after creating jobs)
we put them in /tmp,
and use a map so that if two templates are the same we use 1 file.
For output templates (which have to last until all jobs are done)
we put them in templates/tmp, with content-based filenames
to economize.
- When creating jobs, or generating SQL strings for multiple jobs,
use these names as --wu_template_filename
and --result_template_filename args to create_work
(either cmdline args or stdin args)
- Delete WU templates when done
create_work.cpp:
handle per-job --wu_template and --result_template args in stdin job lines
(the names of per-job WU and result templates).
Maintain a map mapping WU template name to contents,
to avoid repeatedly reading them.
For jobs that don't specify templates, use the ones specified
at the batch level, or the defaults.
2017-01-21 08:24:11 +00:00
|
|
|
print req
|
2016-10-18 07:38:02 +00:00
|
|
|
url = project_url + handler
|
2016-10-16 23:28:55 +00:00
|
|
|
params = urllib.urlencode({'request': req})
|
|
|
|
f = urllib.urlopen(url, params)
|
|
|
|
reply = f.read()
|
|
|
|
print reply
|
2016-10-16 23:30:16 +00:00
|
|
|
return ET.fromstring(reply)
|
2016-10-16 23:28:55 +00:00
|
|
|
|
2016-10-18 07:38:02 +00:00
|
|
|
########### API FUNCTIONS START HERE ###############
|
|
|
|
|
|
|
|
def abort_batch(req):
|
|
|
|
req_xml = ('<abort_batch>\n'
|
|
|
|
'<authenticator>%s</authenticator>\n'
|
|
|
|
'<batch_id>%s</batch_id>\n'
|
|
|
|
'</abort_batch>\n'
|
|
|
|
) %(req.authenticator, req.batch_id)
|
|
|
|
return do_http_post(req_xml, req.project)
|
|
|
|
|
|
|
|
def abort_jobs(req):
|
|
|
|
req_xml = ('<abort_jobs>\n'
|
|
|
|
'<authenticator>%s</authenticator>\n'
|
|
|
|
) %(req.authenticator)
|
|
|
|
for job in req.jobs:
|
|
|
|
req_xml += '<job_name>%s</job_name>\n'%(job)
|
|
|
|
req_xml += '</abort_jobs>\n'
|
|
|
|
return do_http_post(req_xml, req.project)
|
Remote job submission: add support for per-job templates in submit requests
This supports the TACC use case,
in the jobs in a batch can use different Docker images
and different input and output file signatures,
none of which are known in advance.
Python API binding:
- A JOB_DESC object can optionally contain wu_template and result_template
elements, which are the templates (the actual XML) to use for that job.
Add these to the XML request message if present.
- Added the same capability to the PHP binding, but not C++.
- Added and debugged test cases for both languages.
Also, submit_batch() can take either a batch name (in which case
the batch is created) or a batch ID
(in which the batch was created prior to remotely staging files).
RPC handler:
- in submit_batch(), check for jobs with templates specified
and store them in files.
For input templates (which are deleted after creating jobs)
we put them in /tmp,
and use a map so that if two templates are the same we use 1 file.
For output templates (which have to last until all jobs are done)
we put them in templates/tmp, with content-based filenames
to economize.
- When creating jobs, or generating SQL strings for multiple jobs,
use these names as --wu_template_filename
and --result_template_filename args to create_work
(either cmdline args or stdin args)
- Delete WU templates when done
create_work.cpp:
handle per-job --wu_template and --result_template args in stdin job lines
(the names of per-job WU and result templates).
Maintain a map mapping WU template name to contents,
to avoid repeatedly reading them.
For jobs that don't specify templates, use the ones specified
at the batch level, or the defaults.
2017-01-21 08:24:11 +00:00
|
|
|
|
|
|
|
# req is a CREATE_BATCH_REQ
|
|
|
|
#
|
2016-10-18 07:38:02 +00:00
|
|
|
def create_batch(req):
|
|
|
|
return do_http_post(req.to_xml(), req.project)
|
|
|
|
|
2016-10-16 23:28:55 +00:00
|
|
|
def estimate_batch(req):
|
|
|
|
return do_http_post(req.to_xml('estimate_batch'), req.project)
|
|
|
|
|
2016-10-18 07:38:02 +00:00
|
|
|
def query_batch(req):
|
|
|
|
req_xml = ('<query_batch>\n'
|
|
|
|
'<authenticator>%s</authenticator>\n'
|
|
|
|
'<batch_id>%s</batch_id>\n'
|
|
|
|
'<get_cpu_time>%d</get_cpu_time>\n'
|
|
|
|
'</query_batch>\n'
|
|
|
|
) %(req.authenticator, req.batch_id, 1 if req.get_cpu_time else 0)
|
|
|
|
return do_http_post(req_xml, req.project)
|
2016-10-16 23:28:55 +00:00
|
|
|
|
|
|
|
def query_batches(req):
|
|
|
|
req_xml = ('<query_batches>\n'
|
|
|
|
'<authenticator>%s</authenticator>\n'
|
|
|
|
'<get_cpu_time>%d</get_cpu_time>\n'
|
|
|
|
'</query_batches>\n'
|
|
|
|
) %(req.authenticator, 1 if req.get_cpu_time else 0)
|
|
|
|
return do_http_post(req_xml, req.project)
|
|
|
|
|
2016-10-18 07:38:02 +00:00
|
|
|
def query_completed_job(req):
|
|
|
|
req_xml = ('<query_completed_job>\n'
|
2016-10-16 23:28:55 +00:00
|
|
|
'<authenticator>%s</authenticator>\n'
|
2016-10-18 07:38:02 +00:00
|
|
|
'<job_name>%s</job_name>\n'
|
|
|
|
'</query_completed_job>\n'
|
|
|
|
) %(req.authenticator, req.job_name)
|
2016-10-16 23:28:55 +00:00
|
|
|
return do_http_post(req_xml, req.project)
|
|
|
|
|
|
|
|
def query_job(req):
|
|
|
|
req_xml = ('<query_job>\n'
|
|
|
|
'<authenticator>%s</authenticator>\n'
|
|
|
|
'<job_id>%s</job_id>\n'
|
|
|
|
'</query_job>\n'
|
|
|
|
) %(req.authenticator, req.job_id)
|
|
|
|
return do_http_post(req_xml, req.project)
|
|
|
|
|
|
|
|
def get_output_file(req):
|
|
|
|
auth_str = md5.new(req.authenticator+req.instance_name).digest()
|
|
|
|
name = req.instance_name
|
|
|
|
file_num = req.file_num
|
2016-10-16 23:30:16 +00:00
|
|
|
return project_url+"/get_output.php?cmd=result_file&result_name=%s&file_num=%s&auth_str=%s"%(name, file_num, auth_str)
|
2016-10-16 23:28:55 +00:00
|
|
|
|
|
|
|
def get_output_files(req):
|
|
|
|
auth_str = md5.new(req.authenticator+req.batch_id).digest()
|
|
|
|
return project_url+"/get_output.php?cmd=batch_files&batch_id=%s&auth_str=%s"%(req.batch_id, auth_str)
|
|
|
|
|
|
|
|
def retire_batch(req):
|
|
|
|
req_xml = ('<retire_batch>\n'
|
|
|
|
'<authenticator>%s</authenticator>\n'
|
|
|
|
'<batch_id>%s</batch_id>\n'
|
|
|
|
'</retire_batch>\n'
|
|
|
|
) %(req.authenticator, req.batch_id)
|
2016-10-18 07:38:02 +00:00
|
|
|
return do_http_post(req_xml, req.project)
|
|
|
|
|
|
|
|
def submit_batch(req):
|
|
|
|
return do_http_post(req.to_xml('submit_batch'), req.project)
|
|
|
|
|
2016-10-16 23:28:55 +00:00
|
|
|
|
2016-10-16 23:30:16 +00:00
|
|
|
############ FILE MANAGEMENT API ##############
|
2016-10-16 23:28:55 +00:00
|
|
|
|
2016-10-16 23:30:16 +00:00
|
|
|
class QUERY_FILES_REQ:
|
|
|
|
def __init__(self):
|
|
|
|
return
|
|
|
|
|
|
|
|
def to_xml(self):
|
|
|
|
xml = ('<query_files>\n'
|
|
|
|
'<authenticator>%s</authenticator>\n'
|
2016-10-18 07:38:02 +00:00
|
|
|
'<batch_id>%d</batch_id>\n') %(self.authenticator, self.batch_id)
|
|
|
|
for name in self.boinc_names:
|
|
|
|
xml += '<md5>%s</md5>\n' %(name)
|
|
|
|
xml += '</query_files>\n'
|
|
|
|
return xml
|
2016-10-16 23:30:16 +00:00
|
|
|
|
|
|
|
class UPLOAD_FILES_REQ:
|
|
|
|
def __init__(self):
|
|
|
|
return
|
|
|
|
|
|
|
|
def to_xml(self):
|
|
|
|
xml = ('<upload_files>\n'
|
|
|
|
'<authenticator>%s</authenticator>\n'
|
2016-10-18 07:38:02 +00:00
|
|
|
'<batch_id>%d</batch_id>\n') %(self.authenticator, self.batch_id)
|
|
|
|
for name in self.boinc_names:
|
|
|
|
xml += '<md5>%s</md5>\n' %(name)
|
|
|
|
xml += '</upload_files>\n'
|
|
|
|
return xml
|
2016-10-16 23:30:16 +00:00
|
|
|
|
Remote job submission: add support for per-job templates in submit requests
This supports the TACC use case,
in the jobs in a batch can use different Docker images
and different input and output file signatures,
none of which are known in advance.
Python API binding:
- A JOB_DESC object can optionally contain wu_template and result_template
elements, which are the templates (the actual XML) to use for that job.
Add these to the XML request message if present.
- Added the same capability to the PHP binding, but not C++.
- Added and debugged test cases for both languages.
Also, submit_batch() can take either a batch name (in which case
the batch is created) or a batch ID
(in which the batch was created prior to remotely staging files).
RPC handler:
- in submit_batch(), check for jobs with templates specified
and store them in files.
For input templates (which are deleted after creating jobs)
we put them in /tmp,
and use a map so that if two templates are the same we use 1 file.
For output templates (which have to last until all jobs are done)
we put them in templates/tmp, with content-based filenames
to economize.
- When creating jobs, or generating SQL strings for multiple jobs,
use these names as --wu_template_filename
and --result_template_filename args to create_work
(either cmdline args or stdin args)
- Delete WU templates when done
create_work.cpp:
handle per-job --wu_template and --result_template args in stdin job lines
(the names of per-job WU and result templates).
Maintain a map mapping WU template name to contents,
to avoid repeatedly reading them.
For jobs that don't specify templates, use the ones specified
at the batch level, or the defaults.
2017-01-21 08:24:11 +00:00
|
|
|
# This actually does two RPCs:
|
2016-10-18 07:38:02 +00:00
|
|
|
# query_files() to find what files aren't already on server
|
|
|
|
# upload_files() to upload them
|
|
|
|
#
|
2016-10-16 23:30:16 +00:00
|
|
|
def upload_files(upload_files_req):
|
2016-10-18 07:38:02 +00:00
|
|
|
query_req = QUERY_FILES_REQ()
|
|
|
|
query_req.authenticator = upload_files_req.authenticator
|
|
|
|
query_req.batch_id = upload_files_req.batch_id
|
|
|
|
query_req.boinc_names = upload_files_req.boinc_names
|
|
|
|
query_req_xml = query_req.to_xml()
|
|
|
|
reply = do_http_post(query_req_xml, upload_files_req.project, 'job_file.php')
|
|
|
|
if reply[0].tag == 'error':
|
|
|
|
return reply
|
|
|
|
|
|
|
|
absent = reply.find('absent_files').findall('file')
|
|
|
|
#print 'query files succeeded; ',len(absent), ' files need upload'
|
|
|
|
boinc_names = []
|
|
|
|
local_names = []
|
|
|
|
for n in absent:
|
|
|
|
ind = int(n.text)
|
|
|
|
boinc_names.append(upload_files_req.boinc_names[ind])
|
|
|
|
local_names.append(upload_files_req.local_names[ind])
|
|
|
|
upload_files_req.boinc_names = boinc_names
|
|
|
|
upload_files_req.local_names = local_names
|
|
|
|
|
|
|
|
# make a description of upoad files for "requests"
|
|
|
|
#
|
|
|
|
files = []
|
|
|
|
for i in range(len(boinc_names)):
|
|
|
|
bn = boinc_names[i]
|
|
|
|
ln = local_names[i]
|
|
|
|
upload_name = 'file_%d'%(i)
|
|
|
|
files.append((upload_name, (bn, open(ln, 'rb'), 'application/octet-stream')))
|
|
|
|
|
|
|
|
url = upload_files_req.project + '/job_file.php'
|
|
|
|
req_xml = upload_files_req.to_xml()
|
|
|
|
#print req_xml
|
|
|
|
req = {'request': req_xml}
|
|
|
|
reply = requests.post(url, data=req, files=files)
|
|
|
|
#print "reply text: ", reply.text
|
|
|
|
return ET.fromstring(reply.text)
|