steven
/
cyclescaler
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Why containers

This commit is contained in:
Steven Polley 2020-05-31 00:25:46 +00:00
parent a9d05eeef8
commit d76f1d7b32
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -23,6 +23,12 @@ The project is broken into two parts:
* Master - This can be thought of as the server, it's the portal that users interact with to upload .blend files and tweak render parameters.
* Slave - This can be thought of as a client, and it handles rendering the images which get stitched together to create an animation. There can be as many instances of the slave as you want, the more slaves, the more simultaneous frames can be rendered.
#### Why Containers?
That's the secret sauce of the whole operation. Containers provide a unit of deployment. What does that give you? It gives you an easy way to launch an application, anywhere, across as many machines as you need to. Sign up for a cloud provider, most support running containers natively. Many providers make it as easy as pasting in the URL to download your container from a registry, and putting a number for how many instances you want to run.
You can also run containers on your own equipment utilizing an orchestrator such as Kubernetes.
#### Web interface
When you run the master, it listens on port 8097. Here's a screenshot of the web interface on the status page for an ongoing render job: