...
- Overview
- Interfaces
- Applications
- Input + Output Files
- Distributed Storage
- Networking
- Instance Types
- Support
...
Overview
Charity Engine provides a compute service running on volunteer devices. The system allows one to run compute jobs, executing standard Docker images from Docker Hub, custom docker containers or a set of proprietary applications for an additional fee.
...
You will need your docker image name/URL or a proprietary application name, your input files and the command line to execute within the executed environment. The command line can be as simple as executing an application with a docker image, a command to execute the first input file, or a more involved script that handles the logic of your job.
...
Interfaces
- Remote API
- This API is provided for integration of Charity Engine as a backend service, and summarizes functions for managing the entire lifecycle of jobs submitted to the network.
- Remote CLI
- The Remote CLI provides a means to run jobs on Charity Engine compute resources using simple command line tools. (e.g. custom scripts or tools such as GNU Parallel). This interface is geared toward running large batches of jobs, but can be used anytime a command line approach is more appropriate than a web API.
- Standalone command-line interface
- GNU Parallel (using Parallel allows you to manage batches of work using just a single command line tool)
- Ethereum
- Custom Arrangements
...
Applications
Charity Engine supports several types of applications:
- Docker images available on Docker Hub (e.g. docker:python:3.7)
- Custom Docker images available anywhere online (e.g. docker:image-name https://example.com/file for 64bit docker images, or docker-x86:image-name https://example.com/file for 32bit docker images)
- Proprietary applications deployed directly on the Charity Engine network (e.g. charityengine:wolframengine). The AppStore library can be viewed here.
...
Input + Output Files
Once the computation environment runs, the input files provided during job completion are downloaded from the internet and are made available for the applications on the compute nodes in the /local/input virtual disk location.
...
containerized_app --param example; cp output_file /local/output/output_file
...
Distributed Storage
Distributed Storage is a networked file storage system which can be used to host large quantities of data, with data persistently maintained and replicated across multiple devices distributed worldwide. Access to this network is possible using all of the Charity Engine interfaces such as the Remote API, Remote CLI, and Smart Contracts, as well as industry standard IPFS client applications.
...
Networking
Network access through HTTP and HTTPS protocols is allowed. The network speeds may vary based on the node location and the network/system load. Network latency is artificially throttled to several seconds per request, but multiple parallel requests are allowed and recommended.
...
Additionally, network requests can be routed through the Charity Engine Distributed Proxy Service which uses the power and unique, geographically-dispersed nature of our network to allow web requests to originate from locations around the world.
...
Instance Types
Initial service implementation defines three instance types: CE.2x2, CE.2x4, CE.4x4, where the first number denotes the number of available vCPUs and the second number denotes the amount of available RAM (in GiB).
Custom arrangements may be possible; contact us if currently available instances types are not suitable for your workloads.
...
Support
(*link to forums)