Cloud requirements

alt=
DannyA
@dannya
9 years ago
584 posts
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?

2. I understand we need the core and cloud files. But want to confirm we don't need the audio or video modules.

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?

4. Which modules is it safe to disable from the core install of the client servers?

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.


updated by @dannya: 03/07/15 06:03:41AM
brian
@brian
9 years ago
10,148 posts
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!


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
alt=
DannyA
@dannya
9 years ago
584 posts
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
michael
@michael
9 years ago
7,717 posts
DannyA:....It seems this could get expensive. It would be great if you just charged for the masters and let the clients be unlimited...

There is an unlimited plan in the subscriptions area that allows for use of unlimited modules on unlimited domains. "VIP Unlimited"

http://www.jamroom.net/subscribe
brian
@brian
9 years ago
10,148 posts
DannyA:
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.

When I say "Jamroom Core" I just mean the free Jamroom Core - NOT all the modules that are on your site. And although the core provides ffmpeg, the Audio and Video modules are what provide all the logic and functions to do the actual WORK. The only functionality the core provides is media meta data reading using FFMpeg.

Quote:
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)

That's for each Conversion Worker. You only need Audio and Video on the Conversion Workers.

Quote:
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.

I'm not sure I understand what you mean here - the Conversion Workers use the functions from the Audio and Video support modules to do conversions.

Quote:
#4- Which modules are safe to disable on conversion workers? (sorry, still getting terminology right)

If you go here:

https://www.jamroom.net/jamroom-cloud/documentation/installation/2219/setting-up-a-dedicated-conversion-service

You only need to install the FREE Jamroom Core + the modules outlined for each of the server types.

I know the docs are limited right now but I'm slowly getting them done. Any questions I can help.

Quote:
#6- For the conversion server, is it better to have more memory or more cores? How does each affect performance?

It depends a little:

- more cores = more simultaneous conversions going on
- more memory - LARGER files will convert faster

1 GIG RAM per Core should be fine.

Quote:
#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.

- All communication between servers is encrypted (SHA256)
- disable signups on any server that users are not logging in to
- run the Cloud Skin on the servers - it's a minimal skin that disables profiles (skin setting)

Like Michael pointed out too - if you plan on running A LOT of servers, the VIP Unlimited subscription was designed for that - all modules and skins are free on as many servers as you would like.

Hope this helps!


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
alt=
DannyA
@dannya
9 years ago
584 posts
Thanks. That helps

Tags