qat.qlmaas

• qat.qlmaas.upload

Submitting a job to a Qaptiva Access server

QLMaaS provides classes to connect to a Qaptiva Access server and defining a remote stack:

• The QLMaaSConnection class is used to connect to a Qaptiva Access server

• The remote QLMaaSGenerator, remote QLMaaSPlugin and remote QLMaaSQPU classes are used to define, using myQLM, a stack that will be built on the remote Qaptiva Access server

• AsyncResult is a class used to get information on a job that have already been submitted

• The UploadedQPU, UploadedPlugin and UploadedGenerator classes are used to define objects locally before uploading them on the server side

qat.qlmaas.QLMaaSConnection	Foremost interface for communicating with the QLMaaS server
qat.qlmaas.generators.QLMaaSGenerator	Interface for management of a remote Generator
qat.qlmaas.plugins.QLMaaSPlugin	Interface for management of a remote Plugin
qat.qlmaas.qpus.QLMaaSQPU	Interface for management of a remote QPU
qat.qlmaas.result.AsyncResult	High level class to manage a pending result

Classes QLMaaSQPU and QLMaaSPlugin are used to manage QPUs and Plugins defined on the server side. The object could be piped using the syntax PLUGIN | ... | PLUGIN | QPU to build a computation stack defined on the server side

Warning

Please note that a stack can’t be composed of both remote and local plugins / qpus

Getting information from the server

Classes QLMaaSConnection (using the method get_jobs_info()) and AsyncResult (using the method get_info()) can be used to get information on a list of jobs or a specific job.

All these meta data are wrapped in a data structure called JobInfo. A standard use of QLMaaS doesn’t require to instanciate these objects manually.