sandkasten
/
planificador
6
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
A container orchestrator
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
38 Commits
2 Branches
0 Tags
836 KiB
 
 
 
 
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'master'
${ noResults }
Go to file
Bastien OLLIER 234bbb1be8
continuous-integration/drone/push Build is passing Details
Merge pull request 'Allow multiple backends' (#5) from feature/multiple-backends into master 		1 month ago
libzmq-pkg-config Allow fetching locally ZeroMQ if not already installed 9 months ago
src Support patterns in config 2 months ago
.clang-format use the good image 9 months ago
.dockerignore Add Dockerfile 7 months ago
.drone.yml Allow fetching locally ZeroMQ if not already installed 9 months ago
.gitignore Allow fetching locally ZeroMQ if not already installed 9 months ago
CMakeLists.txt Update to the new config format 7 months ago
Dockerfile Add Dockerfile 7 months ago
Makefile Run a container for each program 9 months ago
README.md Define the protocol 6 months ago
config.toml Support patterns in config 2 months ago

README.md

planificador

A sandbox execution environment for untrusted code. It acts as a front-end in front of Docker+Bubblewrap.

Tasks are submitted using a ZeroMQ message queue, allowing quick scaling of the system.

Protocol

planificador receives messages from a ZeroMQ queue in binary format in big-endian.

Executor bound

The first byte of the message is the message type. The following types are supported:

  • 0x00: SUBMIT - Submit a new task to the system.
  • 0x02: CANCEL - Cancel a task.

The following bytes are the payload of the message. The format of the payload depends on the message type.

SUBMIT

  • 32 bytes: Task ID
  • 4 bytes: Image field length
  • 4 bytes: Code length
  • Image field length bytes: Image field
  • Code length bytes: Code

CANCEL

  • 32 bytes: Task ID

Client bound

The first byte of the message is the message type. The following types are supported:

  • 0x01: APPEND_OUT - Append text to the task's stdout.
  • 0x02: APPEND_ERR - Append text to the task's stderr.
  • 0x03: EXITED - The task has exited.

APPEND_OUT / APPEND_ERR

  • 32 bytes: Task ID
  • 4 bytes: Text length
  • Text length bytes: Text

EXITED

  • 32 bytes: Task ID
  • 4 bytes: Exit code