Skip to content

Commit

Permalink
added all the photos and finished doc for azure for now (stable version)
Browse files Browse the repository at this point in the history
  • Loading branch information
Piwccle committed Feb 19, 2025
1 parent e404a71 commit 02b6839
Show file tree
Hide file tree
Showing 18 changed files with 28 additions and 33 deletions.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
12 changes: 6 additions & 6 deletions docs/docs/self-hosting/elastic/azure/admin.md
Original file line number Diff line number Diff line change
Expand Up @@ -176,20 +176,20 @@ In addition to these, an Azure deployment provides the capability to manage glob
=== "Changing Configuration through Key Vault secrets"

1. Navigate to the [Azure Portal Dashboard](https://portal.azure.com/#home){:target=_blank} on Azure.
2. Select the Resource Group where you deployed your OpenVidu Single Node Stack.
3. In the _"stackname-keyvault"_ resource, click at _"Objects -> Secrets"_ on the left panel. This will show you all the secrets that are stored in the Key Vault of the OpenVidu Single Node deployment.
2. Select the Resource Group where you deployed your OpenVidu Elastic Stack.
3. In the _"stackname-keyvault"_ resource, click at _"Objects -> Secrets"_ on the left panel. This will show you all the secrets that are stored in the Key Vault of the OpenVidu Elastic deployment.
<figure markdown>
![Azure Key Vault secrets location](../../../../assets/images/self-hosting/elastic/azure/azure-keyvault-secrets-location.png){ .svg-img .dark-img }
![Azure Key Vault secrets location](../../../../assets/images/self-hosting/shared/azure-keyvault-secrets-location.png){ .svg-img .dark-img }
</figure>
4. Click on the desired secret you want to change and click on _"New Version"_.
<figure markdown>
![Azure Key Vault New Version Secret](../../../../assets/images/self-hosting/elastic/azure/azure-keyvault-new-version-secret.png){ .svg-img .dark-img }
![Azure Key Vault New Version Secret](../../../../assets/images/self-hosting/shared/azure-keyvault-new-version-secret.png){ .svg-img .dark-img }
</figure>
5. Enter the new secret value on _"Secret Value"_ filed and click on _"Create"_.
<figure markdown>
![Azure Key Vault New Version Secret Create](../../../../assets/images/self-hosting/elastic/azure/azure-keyvault-secrets-create.png){ .svg-img .dark-img }
![Azure Key Vault New Version Secret Create](../../../../assets/images/self-hosting/shared/azure-keyvault-secrets-create.png){ .svg-img .dark-img }
</figure>
6. Go to the Instance resource of OpenVidu and click on _"Restart"_ to apply the changes to the OpenVidu Single Node deployment.
6. Go to the Master Node resource and click on _"Restart"_ to apply the changes to the OpenVidu Elastic deployment.
<figure markdown>
![Reboot Instance](../../../../assets/images/self-hosting/elastic/azure/reboot-instance.png){ .svg-img .dark-img }
</figure>
Expand Down
8 changes: 4 additions & 4 deletions docs/docs/self-hosting/elastic/azure/install.md
Original file line number Diff line number Diff line change
Expand Up @@ -101,7 +101,7 @@ The number of Media Nodes can scale up based on the system load. You can configu

Don't forget about changing the resource group where all the previous resources may be created (in case you use an existing public IP) and don't forget to fill the parameter **Stack Name** with the name you want for the stack (it will be used to create the names of the resources).

When you are ready with your Template parameters, just click on _"Next"_, then it will go through some validations, and if everything is correct, click on _"Create"_, then it will start deploying and you will have to wait the time that takes to install Openvidu, it takes about 5 to 10 minutes.
When you are ready with your Template parameters, just click on _"Next"_, then it will go through some validations, and if everything is correct, click on _"Create"_, then it will start deploying and you will have to wait the time that takes to install Openvidu, it takes about 7 to 12 minutes.

When everything is ready, you will see the following links in the Key Vault resource:

Expand All @@ -113,19 +113,19 @@ When everything is ready, you will see the following links in the Key Vault reso
2. Once you are in the Key Vault on the left panel click on _"Objects"_ and then into _"Secrets"_.

<figure markdown>
![Azure Key Vault secrets location](../../../../assets/images/self-hosting/elastic/azure/azure-keyvault-secrets-location.png){ .svg-img .dark-img }
![Azure Key Vault secrets location](../../../../assets/images/self-hosting/shared/azure-keyvault-secrets-location.png){ .svg-img .dark-img }
</figure>

3. Here click on the secret of your choice or whatever you need to check and click again in the current version of that secret

<figure markdown>
![Azure Key Vault Outputs](../../../../assets/images/self-hosting/elastic/azure/azure-keyvault-secret-value.png){ .svg-img .dark-img }
![Azure Key Vault Secret Version](../../../../assets/images/self-hosting/shared/azure-keyvault-secret-version.png){ .svg-img .dark-img }
</figure>

4. Now you will see a lot of properties but the one you are searching for is located at the bottom and it will be revealed by clicking in _"Show Secret Value"_.

<figure markdown>
![Azure Key Vault Outputs](../../../../assets/images/self-hosting/elastic/azure/azure-keyvault-output.png){ .svg-img .dark-img }
![Azure Key Vault Outputs](../../../../assets/images/self-hosting/shared/azure-keyvault-output.png){ .svg-img .dark-img }
</figure>
=== "Check outputs in the instance"

Expand Down
12 changes: 6 additions & 6 deletions docs/docs/self-hosting/ha/azure/admin.md
Original file line number Diff line number Diff line change
Expand Up @@ -174,20 +174,20 @@ In addition to these, an Azure deployment provides the capability to manage glob
=== "Changing Configuration through Key Vault secrets"

1. Navigate to the [Azure Portal Dashboard](https://portal.azure.com/#home){:target=_blank} on Azure.
2. Select the Resource Group where you deployed your OpenVidu Single Node Stack.
3. In the _"stackname-keyvault"_ resource, click at _"Objects -> Secrets"_ on the left panel. This will show you all the secrets that are stored in the Key Vault of the OpenVidu Single Node deployment.
2. Select the Resource Group where you deployed your OpenVidu HA Stack.
3. In the _"stackname-keyvault"_ resource, click at _"Objects -> Secrets"_ on the left panel. This will show you all the secrets that are stored in the Key Vault of the OpenVidu HA deployment.
<figure markdown>
![Azure Key Vault secrets location](../../../../assets/images/self-hosting/ha/azure/azure-keyvault-secrets-location.png){ .svg-img .dark-img }
![Azure Key Vault secrets location](../../../../assets/images/self-hosting/shared/azure-keyvault-secrets-location.png){ .svg-img .dark-img }
</figure>
4. Click on the desired secret you want to change and click on _"New Version"_.
<figure markdown>
![Azure Key Vault New Version Secret](../../../../assets/images/self-hosting/ha/azure/azure-keyvault-new-version-secret.png){ .svg-img .dark-img }
![Azure Key Vault New Version Secret](../../../../assets/images/self-hosting/shared/azure-keyvault-new-version-secret.png){ .svg-img .dark-img }
</figure>
5. Enter the new secret value on _"Secret Value"_ filed and click on _"Create"_.
<figure markdown>
![Azure Key Vault New Version Secret Create](../../../../assets/images/self-hosting/ha/azure/azure-keyvault-secrets-create.png){ .svg-img .dark-img }
![Azure Key Vault New Version Secret Create](../../../../assets/images/self-hosting/shared/azure-keyvault-secrets-create.png){ .svg-img .dark-img }
</figure>
6. Go to the Instance resource of OpenVidu and click on _"Restart"_ to apply the changes to the OpenVidu Single Node deployment.
6. Go to the Master Node resource you've want to change the secrets on and click on _"Restart"_ to apply the changes to the OpenVidu HA deployment.
<figure markdown>
![Reboot Instance](../../../../assets/images/self-hosting/ha/azure/reboot-instance.png){ .svg-img .dark-img }
</figure>
Expand Down
17 changes: 6 additions & 11 deletions docs/docs/self-hosting/ha/azure/install.md
Original file line number Diff line number Diff line change
Expand Up @@ -128,7 +128,7 @@ This section is optional. It is useful when your users are behind a restrictive

Don't forget about changing the resource group where all the previous resources may be created (in case you use an existing public IP) and don't forget to fill the parameter **Stack Name** with the name you want for the stack (it will be used to create the names of the resources).

When you are ready with your Template parameters, just click on _"Next"_, then it will go through some validations, and if everything is correct, click on _"Create"_, then it will start deploying and you will have to wait the time that takes to install Openvidu, it takes about 5 to 10 minutes.
When you are ready with your Template parameters, just click on _"Next"_, then it will go through some validations, and if everything is correct, click on _"Create"_, then it will start deploying and you will have to wait the time that takes to install Openvidu, it takes about 10 to 15 minutes.

When everything is ready, you will see the following links in the Key Vault resource:

Expand All @@ -140,19 +140,19 @@ When everything is ready, you will see the following links in the Key Vault reso
2. Once you are in the Key Vault on the left panel click on _"Objects"_ and then into _"Secrets"_.

<figure markdown>
![Azure Key Vault secrets location](../../../../assets/images/self-hosting/ha/azure/azure-keyvault-secrets-location.png){ .svg-img .dark-img }
![Azure Key Vault secrets location](../../../../assets/images/self-hosting/shared/azure-keyvault-secrets-location.png){ .svg-img .dark-img }
</figure>

3. Here click on the secret of your choice or whatever you need to check and click again in the current version of that secret

<figure markdown>
![Azure Key Vault Outputs](../../../../assets/images/self-hosting/ha/azure/azure-keyvault-secret-value.png){ .svg-img .dark-img }
![Azure Key Vault Secret Version](../../../../assets/images/self-hosting/shared/azure-keyvault-secret-version.png){ .svg-img .dark-img }
</figure>

4. Now you will see a lot of properties but the one you are searching for is located at the bottom and it will be revealed by clicking in _"Show Secret Value"_.

<figure markdown>
![Azure Key Vault Outputs](../../../../assets/images/self-hosting/ha/azure/azure-keyvault-output.png){ .svg-img .dark-img }
![Azure Key Vault Outputs](../../../../assets/images/self-hosting/shared/azure-keyvault-output.png){ .svg-img .dark-img }
</figure>

=== "Check outputs in the instance"
Expand All @@ -165,17 +165,12 @@ When everything is ready, you will see the following links in the Key Vault reso
![Connect via bastion](../../../../assets/images/self-hosting/ha/azure/azure-connect-bastion.png){ .svg-img .dark-img }
</figure>

3. Then click on _"Deploy Bastion"_.
<figure markdown>
![Deploy Bastion](../../../../assets/images/self-hosting/ha/azure/azure-bastion-deploy.png){ .svg-img .dark-img }
</figure>

4. Now, change **Authentication Type** to _"SSH Private Key from Local File"_, fill the username with the username you've used when filling the parameters and select the local file corresponding to the SSH Private Key of the SSH Public Key yo've used when deploying.
3. Now, change **Authentication Type** to _"SSH Private Key from Local File"_, fill the username with the username you've used when filling the parameters and select the local file corresponding to the SSH Private Key of the SSH Public Key yo've used when deploying.
<figure markdown>
![Bastion parameters](../../../../assets/images/self-hosting/ha/azure/azure-bastion-parameters.png){ .svg-img .dark-img }
</figure>

5. Click oon connect and you will be inside the Virtual Machine of the Master Node you've selected. You can do this for every Master Node the same way.
4. Click oon connect and you will be inside the Virtual Machine of the Master Node you've selected. You can do this for every Master Node the same way.

When you are inside of one Master Node go to the config folder using the following command: ```cd /opt/openvidu/config/cluster```. There you will see two folders and one **.env** file. To retrieve all access credentials check the following files:

Expand Down
6 changes: 3 additions & 3 deletions docs/docs/self-hosting/single-node/azure/admin.md
Original file line number Diff line number Diff line change
Expand Up @@ -63,15 +63,15 @@ In addition to these, an Azure deployment provides the capability to manage glob
2. Select the Resource Group where you deployed your OpenVidu Single Node Stack.
3. In the _"stackname-keyvault"_ resource, click at _"Objects -> Secrets"_ on the left panel. This will show you all the secrets that are stored in the Key Vault of the OpenVidu Single Node deployment.
<figure markdown>
![Azure Key Vault secrets location](../../../../assets/images/self-hosting/single-node/azure/azure-keyvault-secrets-location.png){ .svg-img .dark-img }
![Azure Key Vault secrets location](../../../../assets/images/self-hosting/shared/azure-keyvault-secrets-location.png){ .svg-img .dark-img }
</figure>
4. Click on the desired secret you want to change and click on _"New Version"_.
<figure markdown>
![Azure Key Vault New Version Secret](../../../../assets/images/self-hosting/single-node/azure/azure-keyvault-new-version-secret.png){ .svg-img .dark-img }
![Azure Key Vault New Version Secret](../../../../assets/images/self-hosting/shared/azure-keyvault-new-version-secret.png){ .svg-img .dark-img }
</figure>
5. Enter the new secret value on _"Secret Value"_ filed and click on _"Create"_.
<figure markdown>
![Azure Key Vault New Version Secret Create](../../../../assets/images/self-hosting/single-node/azure/azure-keyvault-secrets-create.png){ .svg-img .dark-img }
![Azure Key Vault New Version Secret Create](../../../../assets/images/self-hosting/shared/azure-keyvault-secrets-create.png){ .svg-img .dark-img }
</figure>
6. Go to the Instance resource of OpenVidu and click on _"Restart"_ to apply the changes to the OpenVidu Single Node deployment.
<figure markdown>
Expand Down
6 changes: 3 additions & 3 deletions docs/docs/self-hosting/single-node/azure/install.md
Original file line number Diff line number Diff line change
Expand Up @@ -67,19 +67,19 @@ When everything is ready, you will see the following links in the Key Vault reso
2. Once you are in the Key Vault on the left panel click on _"Objects"_ and then into _"Secrets"_.

<figure markdown>
![Azure Key Vault secrets location](../../../../assets/images/self-hosting/single-node/azure/azure-keyvault-secrets-location.png){ .svg-img .dark-img }
![Azure Key Vault secrets location](../../../../assets/images/self-hosting/shared/azure-keyvault-secrets-location.png){ .svg-img .dark-img }
</figure>

3. Here click on the secret of your choice or whatever you need to check and click again in the current version of that secret

<figure markdown>
![Azure Key Vault Outputs](../../../../assets/images/self-hosting/single-node/azure/azure-keyvault-secret-value.png){ .svg-img .dark-img }
![Azure Key Vault Secret Version](../../../../assets/images/self-hosting/shared/azure-keyvault-secret-version.png){ .svg-img .dark-img }
</figure>

4. Now you will see a lot of properties but the one you are searching for is located at the bottom and it will be revealed by clicking in _"Show Secret Value"_.

<figure markdown>
![Azure Key Vault Outputs](../../../../assets/images/self-hosting/single-node/azure/azure-keyvault-output.png){ .svg-img .dark-img }
![Azure Key Vault Outputs](../../../../assets/images/self-hosting/shared/azure-keyvault-output.png){ .svg-img .dark-img }
</figure>

=== "Check outputs in the instance"
Expand Down

0 comments on commit 02b6839

Please sign in to comment.