| Anonymous | Login | Signup for a new account | 2013-05-18 02:28 PDT | ![]() |
| Main | My View | View Issues | Change Log | Roadmap |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
| 0001187 | LuxRender | Core | public | 2012-01-15 11:30 | 2012-08-21 10:16 | ||||||||
| Reporter | Omniflux | ||||||||||||
| Assigned To | |||||||||||||
| Priority | low | Severity | feature | Reproducibility | N/A | ||||||||
| Status | new | Resolution | open | ||||||||||
| Platform | OS | OS Version | |||||||||||
| Product Version | |||||||||||||
| Target Version | Fixed in Version | ||||||||||||
| Summary | 0001187: Multicast network support | ||||||||||||
| Description | It would be nice if luxrender supported multicast for its master/slave communication, especially the transfer of files at the beginning. | ||||||||||||
| Tags | No tags attached. | ||||||||||||
| Mercurial Changeset # | |||||||||||||
| Requires Documentation Update | No | ||||||||||||
| Requires Exporter Update | |||||||||||||
| Attached Files | |||||||||||||
Notes |
|
|
(0003309) Lord Crc (administrator) 2012-01-17 18:53 |
Do you know of an existing reliable multicast protocol we could use? Think it would be somewhat outside the scope of this project to reinvent the wheel here. |
|
(0003314) Omniflux (developer) 2012-01-18 17:01 |
Not off hand. This one will require some research. |
|
(0003341) Lord Crc (administrator) 2012-01-28 16:19 |
Found this, just dropping it here so I don't forget http://code.google.com/p/openpgm/ [^] |
|
(0003347) Omniflux (developer) 2012-02-04 17:40 edited on: 2012-02-04 17:41 |
I'm envisioning something like this: Master starts up and listens on multicast addresses X, Y Master announces on X: Scene ID, File list Amount of memory required to render the scene Maybe current number of slaves or kS/s Slave starts up and listens on multicast address X Slave announces that it is available Master responds with announcement again Slave chooses a master from all that respond by: Matching with the scene ID specified by the user Choosing master with the fewest slaves or kS/s Choosing master with a scene with the most files already cached on slave Choosing the only master that responded Slave joins multicast group Y Slave simultaneously: listens for server sending files it needs listens for other slaves requesting files it needs after random delay, requests files it needs that other slaves have not yet requested Master sends requested files on Y Slave leaves multicast group Y Slave begins rendering and notifies master via unicast Master periodically sends announcement on X Slave may change scenes based on announcements if multiple masters available Master can instruct slaves to stop or request samples on X Slaves should respond via unicast Thoughts? |
|
(0003377) FishB8 (reporter) 2012-04-17 18:27 |
Use DNS-SD (Zeroconfig) for slaves to advertise their location and status. tftp multicast can be used for multicast data transfer, although I think it's probably more headache than it's worth to implement it. |
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2012-01-15 11:30 | Omniflux | New Issue | |
| 2012-01-17 18:53 | Lord Crc | Note Added: 0003309 | |
| 2012-01-18 17:01 | Omniflux | Note Added: 0003314 | |
| 2012-01-28 16:19 | Lord Crc | Note Added: 0003341 | |
| 2012-02-04 17:40 | Omniflux | Note Added: 0003347 | |
| 2012-02-04 17:41 | Omniflux | Note Edited: 0003347 | View Revisions |
| 2012-04-17 18:27 | FishB8 | Note Added: 0003377 | |
| 2012-08-21 07:10 | jeanphi | Target Version | => 1.1 |
| 2012-08-21 10:16 | jeanphi | Target Version | 1.1 => |
| Copyright © 2000 - 2012 MantisBT Group |