Difference between revisions of "Talk:Educaship Jitsi"
(→Communicating with contractors before hiring) |
(→Load balancing) |
||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | == | + | [[TAJ-1]] |
| + | |||
| + | == Load balancing == | ||
Questions: | Questions: | ||
| − | + | Could you describe in more detail how you can solve our challenges? For example: | |
| − | # | + | # what exactly is the best solution to implement a load balancer, what can you suggest? |
| − | # | + | # where is the best place to host our Jitsi instances? On ProxmoxVE or separately on a virtual private server? |
| − | + | ===AS=== | |
| − | |||
| − | |||
| − | |||
| − | |||
:1) Need to make sure of the following to ensure best practices to implement a load balancer: | :1) Need to make sure of the following to ensure best practices to implement a load balancer: | ||
:- performance to handle the traffic | :- performance to handle the traffic | ||
| Line 18: | Line 16: | ||
:I think 2 of the challenges can be covered in an estimated timeline of 2 working days. | :I think 2 of the challenges can be covered in an estimated timeline of 2 working days. | ||
| − | + | ===RN=== | |
[[File:Sample_Jitsi_setup.png|right|500px]] | [[File:Sample_Jitsi_setup.png|right|500px]] | ||
| − | :I've attached a sample setup for my previous clients. You may ignore the DB and the admin as it's my | + | :I've attached a sample setup for my previous clients. You may ignore the DB and the admin as it's my customization. |
:We can have multiple JVB installed which is hiding behind a firewall. OCTO bridging and JVB load balancing will be setup as well to provide better call quality for all users. JVB by the way, is where all conferences take place. So the more JVB you have, the more conferences your JITSI instance can handle simultaneously. The OCTO protocol will help in distributing the users to the nearest JVB instance to provide better experience. For OCTO protocol, you can read more info here (https://webrtchacks.com/sfu-cascading/). | :We can have multiple JVB installed which is hiding behind a firewall. OCTO bridging and JVB load balancing will be setup as well to provide better call quality for all users. JVB by the way, is where all conferences take place. So the more JVB you have, the more conferences your JITSI instance can handle simultaneously. The OCTO protocol will help in distributing the users to the nearest JVB instance to provide better experience. For OCTO protocol, you can read more info here (https://webrtchacks.com/sfu-cascading/). | ||
:the front end which is jitsi-meet will be installed separately as well(blue box in the diagram above). | :the front end which is jitsi-meet will be installed separately as well(blue box in the diagram above). | ||
| Line 29: | Line 27: | ||
:Before I answer your last question, Do you have already an existing jitsi meet running in production? I want to know what jitsi meet version are you currently using. I might have a problem with non fresh jitsi meet installation as there will be some configuration for JVB during the initial installation of jitsi meet. Also, what linux distro are you using and what version? | :Before I answer your last question, Do you have already an existing jitsi meet running in production? I want to know what jitsi meet version are you currently using. I might have a problem with non fresh jitsi meet installation as there will be some configuration for JVB during the initial installation of jitsi meet. Also, what linux distro are you using and what version? | ||
:from my experience, ubuntu 18 + has been smooth sailing for me. | :from my experience, ubuntu 18 + has been smooth sailing for me. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
*'''NN:''' | *'''NN:''' | ||
:Currently, I think you use only one server for all jitsi service? -> I need to know how many conferences (participants) do you want support. | :Currently, I think you use only one server for all jitsi service? -> I need to know how many conferences (participants) do you want support. | ||
| − | |||
:'''We plan to have no more than 1-2 conferences at a time and about 10-15 participants.''' | :'''We plan to have no more than 1-2 conferences at a time and about 10-15 participants.''' | ||
:I think 1 server can handle this load. So you don't need any balancer. | :I think 1 server can handle this load. So you don't need any balancer. | ||
| − | + | ===KN=== | |
:I need to see your current infra first like server configuration etc, then can suggest the best plan to balance the jitsi. | :I need to see your current infra first like server configuration etc, then can suggest the best plan to balance the jitsi. | ||
[[File:Type_of_Jitsi_configuration.png|right|500px]] | [[File:Type_of_Jitsi_configuration.png|right|500px]] | ||
| − | + | ===BP=== | |
:1) Please find the attached image - that type of configuration can be used depending upon the requirement for load balancing the jitsi configuration. | :1) Please find the attached image - that type of configuration can be used depending upon the requirement for load balancing the jitsi configuration. | ||
:2) Jitsi can be deployed on ProxmoxVE or VPS or even on the cloud providers like (AWS, GCP or Azure) depending upon the connectivity and usability of the application which can be disccussed. | :2) Jitsi can be deployed on ProxmoxVE or VPS or even on the cloud providers like (AWS, GCP or Azure) depending upon the connectivity and usability of the application which can be disccussed. | ||
:We can deploy it using docker on any server which you would perfer may be (VPS / Contabo / AWS EC2 or any other provider) whichever is comfortable from your side. Also, we have deployed many jitsi setups in AWS EC2 server and they seemed to work perfectly good and fine with good connectivity. | :We can deploy it using docker on any server which you would perfer may be (VPS / Contabo / AWS EC2 or any other provider) whichever is comfortable from your side. Also, we have deployed many jitsi setups in AWS EC2 server and they seemed to work perfectly good and fine with good connectivity. | ||
Latest revision as of 15:41, 20 April 2024
Contents
Load balancing
Questions: Could you describe in more detail how you can solve our challenges? For example:
- what exactly is the best solution to implement a load balancer, what can you suggest?
- where is the best place to host our Jitsi instances? On ProxmoxVE or separately on a virtual private server?
AS
- 1) Need to make sure of the following to ensure best practices to implement a load balancer:
- - performance to handle the traffic
- - scalability of the solution to withstand hardware and software choke failures
- - security features to prevent intrusion and DDoS attacks, as well as SSL offloading
- - the solution needs to be reliable to withstand hardware or software choke failures
- 2) I prefer a virtual private server, and for that, I have used AWS services and Digital Ocean cloud services.
- I think 2 of the challenges can be covered in an estimated timeline of 2 working days.
RN
- I've attached a sample setup for my previous clients. You may ignore the DB and the admin as it's my customization.
- We can have multiple JVB installed which is hiding behind a firewall. OCTO bridging and JVB load balancing will be setup as well to provide better call quality for all users. JVB by the way, is where all conferences take place. So the more JVB you have, the more conferences your JITSI instance can handle simultaneously. The OCTO protocol will help in distributing the users to the nearest JVB instance to provide better experience. For OCTO protocol, you can read more info here (https://webrtchacks.com/sfu-cascading/).
- the front end which is jitsi-meet will be installed separately as well(blue box in the diagram above).
- default webserver running in jitsi is nginx. it's sufficient enough as long as you have jvb loadbalanced.
- So far, I haven't installed jitsi in ProxmoxVE, technically it can just work but OCTO protocol might be useless in this setup. I'm assuming your ProxmoxVE is installed in your our Data center?
- If I were to suggest, based on experience, I would suggest install it in Private Cloud like those from GCP or Digital Ocean. We can install our JVB instances in different VPS situated in different locations.
- So far, GCP and DO have served me well. Haven't tried installing it in AWS but pretty much should be the same.
- Before I answer your last question, Do you have already an existing jitsi meet running in production? I want to know what jitsi meet version are you currently using. I might have a problem with non fresh jitsi meet installation as there will be some configuration for JVB during the initial installation of jitsi meet. Also, what linux distro are you using and what version?
- from my experience, ubuntu 18 + has been smooth sailing for me.
- NN:
- Currently, I think you use only one server for all jitsi service? -> I need to know how many conferences (participants) do you want support.
- We plan to have no more than 1-2 conferences at a time and about 10-15 participants.
- I think 1 server can handle this load. So you don't need any balancer.
KN
- I need to see your current infra first like server configuration etc, then can suggest the best plan to balance the jitsi.
BP
- 1) Please find the attached image - that type of configuration can be used depending upon the requirement for load balancing the jitsi configuration.
- 2) Jitsi can be deployed on ProxmoxVE or VPS or even on the cloud providers like (AWS, GCP or Azure) depending upon the connectivity and usability of the application which can be disccussed.
- We can deploy it using docker on any server which you would perfer may be (VPS / Contabo / AWS EC2 or any other provider) whichever is comfortable from your side. Also, we have deployed many jitsi setups in AWS EC2 server and they seemed to work perfectly good and fine with good connectivity.
