A Cloud-based Architecture for Visual Effect Rendering System

Transcription

1 A Cloud-based Architecture for Visual Effect System Teng-Kai Fan Researcher Chunghwa Telecom Labs 20 August 2015 Outline Preliminary Motivation & Objective Cloud-based Visual Effect System 2/24 Copyright 2015 IEICE 61 APNOMS 2015

2 Outline Preliminary Motivation & Objective Cloud-based Visual Effect System 3/24 4/24 62

3 5/24 6/24 63

4 Production Pipeline of Animation Check to see more video clips of animation films 7/24 What is? The process of generating an image from a 2D or 3D model by means of computer programs. model It took a decent amount of time to render. On average it was about 30 hours for the tiger Ref:. 8/24 64

5 Outline Preliminary Motivation & Objective Cloud-based Visual Effect System 9/24 Why Using Cloud to Render? The need of computing resource for rendering increases tremendously. 5X 400 computational years (2010) 2,000 computational years (2011) 10/24 65

6 Studio s Challenges Challenges: Small studio (2~5 people, without render farm) Lack of budget for purchasing hardware. Background knowledge of building render farm. Medium studio (more than 20 people, with small render farm) Unable to undertake the sudden big case. Extending current render farm for next big case? Studio A Studio B Studio C 11/24 Objective Provide a cloud-based rendering system. Dynamic rendering resources. Pay as you go. Easy to share. Studio A Studio B Studio C 12/24 66

7 Outline Preliminary Motivation & Objective Cloud-based Visual Effect System 13/24 Cloud-based System Monitor infra. status/ Handle trouble ticket System Administrator Operation Create project/ Get project bill Film Producer User Animation Artist Submit render task /Get rendering progress API License Project Billing Account Allocation Workflow File Monitoring Render Virtual Machine Render Node FTP Server 14/24 DB Server 67

8 Film Producer can do Film Producer Operation User Create project/ Assign artists to the project License Project Allocation Workflow API Get usage statistics & project bill Billing Account Monitor rendering process File Monitoring Render FTP Server DB Server 15/24 Animation Artist can do Animation Artist Operation License User Schedule render task Project API Upload/download file Billing Account Allocation Workflow File Monitoring Render FTP Server DB Server 16/24 68

9 System Administrator can do System Administrator Operation User Manage/Configure Add new render render node License engine Project API Monitor infra. status/ Handle trouble ticket Billing Account Allocation Workflow File Monitoring Render FTP Server DB Server 17/24 Demo Submit a Render Task Create Account Create Project Upload File Submit Render Task Get Progress Download Result Get Usage Statistics Cloud Service User (Web) Cloud Service Plugin for Maya (i.e. 3D animation software) 18/24 69

10 Demo Get Progress Create Account Create Project Upload File Submit Render Task Get Progress Download Result Get Usage Statistics Easy to monitor rendering progress Time taken to render each image frame Thumbnails for preview 19/24 Demo Get Usage Statistics Create Account Create Project Upload File Submit Render Task Get Progress Download Result Get Usage Statistics Flexible charging policy: Pay as you go Lease on dedicated resource pool (rental fee by contract) 20/24 70

11 Exclusive Features (Distributed ) Distributed Render Task Render Task region rendering Render Task Splitter (region scripts) networking rendering Distributed rendering Render node 1 Render node 2 Render node n region 1 region 2 region n Assembler singe frame 21/24 Exclusive Features ( Time Prediction) Via machine learning to predict rendering time. unknown waiting time a specific rendering time 22/24 71

12 Open Source for System Architecture Web Layer * User Operation AP Layer Session Render setting memcached * Message Exchange Monitoring Auto Deploy Render Manager ** Render FTP Load Balancer (Director Server) ** Storage Layer Master-Master Database * FTP *** * Active-Active (keepalived) Storage ** Active-Standby (keepalived) *** Active-Active (IPVS) 23/24 Thank You Q&A Copyright 2015, Telecommunication Laboratories, Chunghwa Telecom All rights reserved. This work contains confidential, proprietary information and trade secrets of Telecommunication Laboratories, Chunghwa Telecom. No part of this document may be used, reproduced, displayed, recited, presented, adapted, distributed, compiled, or transmitted in any form or by any means without the prior written permission of Telecommunication Laboratories, Chunghwa Telecom. 24/24 72