-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[New] Manually Deploy a Jitsi Cluster on Akamai #7012
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[New] Manually Deploy a Jitsi Cluster on Akamai #7012
Conversation
✅ Deploy Preview for nostalgic-ptolemy-b01ab8 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
||
[Jitsi](https://jitsi.org/) is a free, open source video conferencing and communication platform that provides a secure, stable, and free alternative to other popular video conferencing services. With Jitsi, you can use built-in features to limit meeting access with passwords or stream on YouTube so anyone can attend. | ||
|
||
This guide walks you through how to create a scalable Jitsi Meet cluster using [Ansible](https://www.ansible.com/). The provided Ansible playbook creates an initial deployment that can then be scaled up or down as needed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe: "this guide walks through creating..."
|
||
1. Each JVB connects to the singular Jitsi meet instance running XMPP via Prosody on port 5222. | ||
|
||
1. Jicofo (Jitsi Conference Focus) runs on the Jitsi meet instance and is configured to split up load balanced traffic between each JVB instance. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Caps on meet?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't need "up" after split
|
||
1. Jicofo (Jitsi Conference Focus) runs on the Jitsi meet instance and is configured to split up load balanced traffic between each JVB instance. | ||
|
||
1. NGINX runs on the meet instance and functions to serve client requests and communicate with internal Jitsi components. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't need "functions to", add 's' to serve
|
||
The following software and components must be installed and configured on your local system in order for the playbooks in this guide to function: | ||
|
||
- An installed [Python](https://www.python.org/downloads/) version: > v3.8 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't need "an installed"
git clone https://github.com/linode/docs-cloud-projects.git | ||
``` | ||
|
||
1. Navigate to the manual-jitsi-cluster directory within your local cloned repository to begin installation steps: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't need "to begin installation steps"
``` | ||
|
||
{{< note title="Upgrading the ansible-core package" >}} | ||
Some ansible-core package versions may contain older parameters. Should you experience any errors related to out-of-date or deprecated parameters, the ansible-core version can be updated with the below command: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"you can update the ansible-core version with the below command"
|
||
## Provision Your Cluster | ||
|
||
1. Using the `ansible-playbook` utility, run the `provision.yml` playbook with verbose options to keep track of the deployment process. This stands up Linode instances and dynamically writes the Ansible inventory to the hosts file. The playbook is complete when ssh is available on all deployed instances. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Creates" rather than "stands up"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Caps on SSH
|
||
## Benchmarking Your Cluster With WebRTC Perf | ||
|
||
[webrtcperf](https://github.com/vpalmisano/webrtcperf) is an open source utility used to evaluate the performance and quality for WebRTC-based services. To benchmark your Jitsi cluster's performance, WebRTC Perf can be run from a Docker container. Note that Docker must be loaded and configured prior to running the below `docker run` command. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can run rather than "can be run"
New guide that walks through manually creating a Jitsi Cluster on Akamai using Ansible