IP DOSSEE 2010, Team 3

738 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
738
On SlideShare
0
From Embeds
0
Number of Embeds
188
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
















































































  • IP DOSSEE 2010, Team 3

    1. 1. NEVERENDINGRENDERING also known as “team three”
    2. 2. Computing Resources
    3. 3. What We Have • Working system • RESTful API for developers • Sample desktop client built on the API
    4. 4. Switching to Production • More thorough security check • Better test coverage • Implementation of failsafe execution • Bigger cluster
    5. 5. Network and Servers
    6. 6. Operating Systems Desktop and Server
    7. 7. Servers • Control Panel - Web service • Data Store - Uploaded 3D model definitions - File sharing with Control Panel • Firewall - Routing, port forwarding, NAT
    8. 8. Servers • Render Master - Render control - File sharing with Data Store • Render Slaves - Shared computing resources - Scalability is unlimited
    9. 9. Software • Firewall - Port forwarding - Static routes • Control Panel
    10. 10. Web Service • Client registration and authentification • Render task creation and upload • Client task management
    11. 11. Client authentification
    12. 12. Task upload
    13. 13. Dynamic Classy Simple RESTful Productive DSL’d Ruby + Sinatra =
    14. 14. Revisioned with Mercurial
    15. 15. States • One state per task • States are changed manually or automatically through the web service • Change is restricted to the state graph
    16. 16. Task List Blender Queue Script Web Service :uploaded un zi p reject via API :unpacked open via control p anel :examined ll y manua reject validate :rejected :completed re :accepted ue tu que rn re su lt :sent :rendered ren der Slave Node start luxrender w ith slaves :deployed LuxRender Master Node Deploy Script LuxRender
    17. 17. Two crontab’d scripts
    18. 18. Written in a Java IDE
    19. 19. + LuxRender Blender with Python Graphics software
    20. 20. ...modeling, texturing, using materials, animating, rendering, particle simulation, fluid simulation, physics simulation, wind simulation, video editing, compositing, creating interactive 3D applications including games…
    21. 21. HDR / Tonemapping
    22. 22. Network Rendering • LuxConsole • Powerful cluster • Performance++
    23. 23. FREE BEER
    24. 24. RENDER QUIZ Real or fake?
    25. 25. How many CPUs were used to render “Avatar”? A. 20 000 B. 40 000
    26. 26. When was the first 3D model created and “rendered”? A. 1960 B. 1972
    27. 27. DEMO TIME!
    28. 28. The Showcase
    29. 29. 2 minutes
    30. 30. 5 minutes
    31. 31. 20 minutes
    32. 32. 2 hours
    33. 33. 5 hours
    34. 34. Materials
    35. 35. Materials
    36. 36. Materials
    37. 37. Materials
    38. 38. Teamwork • Cooperation • Journals
    39. 39. Cooperation • Analysts know every detail about the behaviour of the system • Administrator team controls the network, software and services • Graphics guys can tell you all about rendering and modelling software
    40. 40. Cooperation
    41. 41. Challenges • Port forwarding • NFS
    42. 42. Challenges • Understanding script logic • Working with E-mail in Java • JSON • Testing directly on our servers
    43. 43. Lessons Learned
    44. 44. Lessons Learned • Web services (SOAP vs. REST) • JSON and data structures in dynamic programming languages • Working with standard streams, RESTful APIs and E-mail in Java • Distributed version control systems; introduction to Mercurial • Document-oriented databases
    45. 45. The team
    46. 46. Dedicated grouping • Analysts • “Graphics guys” • Programmers • System administrators
    47. 47. Daily team meetings • “What have I accomplished?” • “What have I learned?” • “What’s next?”
    48. 48. Cooperation with other teams • Carrier Pidgeon aka “Team 6” - Domain services - Network monitoring
    49. 49. Kiitos huomiota! Thank you for your attention! Vielen Dank für eure Aufmerksamkeit! Grazie per la vostra attenzione! ¡Gracias por vuestra atención! Ďakujeme za pozornosť! Спасибо за внимание! Paldies par uzmanību!

    ×