Cloud requirements
Using Jamroom
DannyA:I want to clarify some requirements around the cloud components.
1. I understand you need to configure a mysql server for each of the additional cloud servers
1a. Is it safe to assume that it is not used for anything? e.g. the conversion client does not use the mysql server at all. its just there for installing the core files
1b. would it be possible to just connect them all to the same db and further reduce the footprint of the install?
It would be a mistake to assume MySQL is not used for anything - every single server will use MySQL since the core requires it, and all JR config is stored in it, etc. You need to have MySQL on EACH server - you cannot hook them all up to one server.
Quote:2. I understand we need the core and cloud files. But want to confirm we don't need the audio or video modules.
On the Conversion Worker you need the Audio and Video modules.
Quote:3. Does the hardware configuration have to match? I was thinking my master server has more memory than you conversion server (at the moment). This means that my maximum file size is larger on my main server. What happens if the conversion server tries to pick up a file that is too big for its current hardware?
You mean more disk space than you have? That would fail. If the RAM size on the worker server is smaller than the file the it will likely just be really slow and "swap". I'd recommend fairly beefy servers for your Conversion
worker servers, and make sure you are running the same PHP upload limits on EVERY server in your cluster.
Quote:4. Which modules is it safe to disable from the core install of the client servers?
Which client servers?
Quote:5. Which modules in the core must be configured for quotas, etc? I am assuming nothing except the cloud modules, but I wanted to make sure.
Well it depends on what server you are talking about... On your main JR site you will want to configure quotas - on backend Cloud servers you don't need to worry about it.
Hope this helps!