Skip to content

Beta Version 1.0

Past due by almost 9 years 21% complete

This is the first introduction to the public. This version of the interface contains the following pages and forms.

Settings

The user should be able to add some basic settings that correspond to AWS properties. To start, these would include:

  • Project bucket URL: AWS S3 bucket that contains zip versions of the project.
  • Frame bucket URL: AWS S3 bucket whe…

This is the first introduction to the public. This version of the interface contains the following pages and forms.

Settings

The user should be able to add some basic settings that correspond to AWS properties. To start, these would include:

  • Project bucket URL: AWS S3 bucket that contains zip versions of the project.
  • Frame bucket URL: AWS S3 bucket where frames are rendered.
  • Naming convention: This section of the settings page allows you to tweak the naming convention of the frames that are rendered.
  • Information pertinent to building ~./brenda.conf files for each job. See below for a standard brenda.conf
INSTANCE_TYPE=c3.2xlarge
BLENDER_PROJECT=s3://NAMEOF.blender.project.bucket/PROJECT_NAME.tar.gz
WORK_QUEUE=sqs://NAMEOF-queue
RENDER_OUTPUT=s3://NAMEOF.blender.frame.bucket
DONE=shutdown
EC2_REGION=us-west-2
SQS_REGION=us-west-2
AMI_ID=ami-####AA##

Jobs Overview Status

This page is an overview of all of the jobs currently running. It should show how many instances are running for each job along with some basic project properties.

Job Detail

Contains the details about a job. This page will also allow you to download your project. Could contain features that use ImageMagick to automatically build subframe renders and also convert frames to a video format for frames. It should calculate the total cost of the job along with a high level overview of the EC2 instances running the job with some detail.

Submit Job

Form that allows you to quickly create a job. As of the beta, we can focus on allowing the user to upload a raw .blend file. It'd be nice if the backend handled:

  • Converting file to zip
  • Uploading to S3 project bucket
  • Build SQS queue based on the form input data
  • Allow user to run the job or just save the job in the queue (Process vs. Just fill SQS queue)
Loading