Cloud requirements
Using Jamroom
For #2- You might want to update the cloud documentation. It does not indicate you need the audio and video modules on the conversion worker. I think this is where there is where I keep getting confused. You say you have to install jamroom core. But my main JR site has many modules besides the core. This includes audio and video. However I thought the core included ffmpeg and other tools so the audio and video modules weren't necessary.
Additionally, this means that each additional conversion server needs:
1 Core client ($$ unknown)
1 Queue client ($$ unknown)
1 worker client ($$ unknown)
1 Audio client ($29)
1 Vidio client ($29)
It seems this could get expensive. It would be great if you just charged for the masters and let the clients be unlimited. And if the core components needed from the audio and video modules were included in the core. The point is we are not really using the full audio/video modules on each worker; just the free conversion tools.
#4- Which modules are safe to disable on conversion workers? (sorry, still getting terminology right)
#6- For the conversion server, is it better to have more memory or more cores? How does each affect performance?
#7- Do you have any recommendations for disabling/securing the jamroom sites on the cloud servers (conversion, log, etc), so that they are only used by the main site? It seems silly to have a bunch of unconfigured jamroom sites just sitting there that people can try to log into.
updated by @dannya: 01/29/15 10:48:58PM