Commit 05242aa2 authored by Carlos Torres's avatar Carlos Torres

Adding config guide for sc_pack v2.

parent 992aec2a
Pipeline #9484 passed with stage
in 1 minute and 4 seconds
......@@ -29,7 +29,7 @@ Have on hand the information that is needed about the application to continue, f
**Details of step 2-4:**
The simplest, and recommended, way to complete steps 2 through 4 is to use [our Ansible recipe](/tutorials/setup_with_ansible/) created for that purpose.
The simplest, and recommended, way to complete steps 2 through 4 is to use [our Ansible recipe](/tutorials/setup_with_ansible/) created for that purpose.
This recipe will create and place in its respective locations the necessary configuration files (sc_pack.conf.yaml, devlove.yaml) and install the sc_pack. It will be responsible for installing and configuring the haproxy load balancer. Finally ShimmerCat and haproxy will be demonized.
......@@ -191,25 +191,25 @@ If you want to know more about the rules and views we wrote above, please read:
- If the website does not appear in your browser, please login to your remote server and check-restart the services.
Normally, the sc_pack service will be called with the one in the folder where it was installed (variable install_dir),
replacing '.' with "\_" followed by ".service".
For example: if install_dir is `/srv/deployment_A`, the service will be called `deployment_A.service`
replacing '.' with "\_" followed by ".service", with the prefix `sc-`.
For example: if install_dir is `/srv/deployment_A`, the service will be called `sc-deployment_A.service`
You can check the status of services:
```
$ systemctl status deployment_A.service
$ systemctl status sc-deployment_A.service
```
To restart it, run in the terminal:
```
$ systemctl restart deployment_A.service
$ systemctl restart sc-deployment_A.service
```
And, for the haproxy
```
$ systemctl status deployment_A.service
$ systemctl status sc-deployment_A.service
```
```
$ systemctl restart haproxy.service
```
You can also check the logs files, located in the folders of the display. For example, the shimmercat logs are located in `/srv/deployment_A/shimmercat/data/shimmercat.log`
You can also check the logs files, located in the folders of the deploy. For example, the shimmercat logs are located in `/srv/deployment_A/shimmercat/data/logs/current`
<br>
<br>
\ No newline at end of file
<br>
......@@ -102,6 +102,8 @@ Below are descriptions of the variables that can be configured in the file `grou
| `run_install_haproxy` | Task that installs and configures the <a href="http://www.haproxy.org" target="_blank">haproxy load balancer</a>. This is demonized. |
| `run_install_prometheus_node_exporter` | Task that installs the <a href="prometheus.io/docs/guides/node-exporter" target="_blank">prometheus node exporter</a>. Only necessary if you want to create alerts or view and visualize your metrics. |
| `run_install_haproxy_exporter` | Task that installs the <a href="https://github.com/prometheus/haproxy_exporter" target="_blank">haproxy exporter</a>. Only necessary if you want to create alerts or view and visualize your metrics.|
| `run_install_grok_exporter` | Task that installs the <a href="https://github.com/fstab/grok_exporter" target="_blank">grok exporter</a>. Only necessary if you want to create alerts or view and visualize your metrics.|
| `run_update_grok_exporter_config` | You can indicate whether or not you want to update grox exporter config. |
| `run_install_accelerator_client` | Task that installs the [accelerator client](../../accelerator/accelerator_intro/), responsible for registering the domain and the deployment in the Accelerator Platform database, as well as updating the sc_pack configuration, i.e. the sc_pack.conf.yaml file. |
| `run_create_deploys` | Task that creates the new [Deployment Sites](../../accelerator/deployment_sites_and_domains/) instances on the Accelerator Platform database in the cloud (calling the accelerator_client). The task installs and configures sc_pack and updates devlove.yml, sc_pack.conf.yaml, haproxy.cfg, and the views-dir. This is demonized. |
| `create_deployment` | You can indicate whether or not you want to create a new deploy and link it to the existing domain. |
......@@ -199,12 +201,12 @@ Now open your browser and check `https://<your_domain>/index.html`.
We suggest the `/index.html` because by by default, for `haproxyconfig_option` as `option-1` or `option-3`, we configure an [example static website](https://gitlab.zunzun.se/public-items/sampleshop/raw/master/tutorials/tutorial-2.zip) when the Ansible recipes run, which has `index.html`, `index-2.html`, `index-3.html`, and several more pages. You should be able to access all of them. If you use `haproxyconfig_option = option-2`, then check `https://<your_domain>`.
If the website does not appear in your browser, login to your remote server and restart the services. Normally, the `sc_pack` service will be called using the variable `deployment_name` value followed by `.service`. For example: if deployment_name is `deployment_A`, the service will be called `deployment_A.service`.
If the website does not appear in your browser, login to your remote server and restart the services. Normally, the `sc_pack` service will be called using the variable `deployment_name` value with the prefix `sc-` followed by `.service`. For example: if deployment_name is `deployment_A`, the service will be called `sc-deployment_A.service`.
To restart it, run in the terminal:
```
$ systemctl restart deployment_A.service
$ systemctl restart sc-deployment_A.service
```
<br>
......
......@@ -101,6 +101,8 @@ Below are descriptions of the variables that can be configured in the file `grou
| `run_install_haproxy` | Task that installs and configures the <a href="http://www.haproxy.org" target="_blank">haproxy load balancer</a>. This is demonized. |
| `run_install_prometheus_node_exporter` | Task that installs the <a href="prometheus.io/docs/guides/node-exporter" target="_blank">prometheus node exporter</a>. Only necessary if you want to create alerts or view and visualize your metrics. |
| `run_install_haproxy_exporter` | Task that installs the <a href="https://github.com/prometheus/haproxy_exporter" target="_blank">haproxy exporter</a>. Only necessary if you want to create alerts or view and visualize your metrics.|
| `run_install_grok_exporter` | Task that installs the <a href="https://github.com/fstab/grok_exporter" target="_blank">grok exporter</a>. Only necessary if you want to create alerts or view and visualize your metrics.|
| `run_update_grok_exporter_config` | You can indicate whether or not you want to update grox exporter config. |
| `run_install_accelerator_client` | Task that installs the [accelerator client](../../accelerator/accelerator_intro/), responsible for registering the domain and the deployment in the Accelerator Platform database, as well as updating the sc_pack configuration, i.e. the sc_pack.conf.yaml file. |
| `run_create_deploys` | Task that creates the new [Deployment Sites](../../accelerator/deployment_sites_and_domains/) instances on the Accelerator Platform database in the cloud (calling the accelerator_client). The task installs and configures sc_pack and updates devlove.yml, sc_pack.conf.yaml, haproxy.cfg, and the views-dir. This is demonized. |
| `create_deployment` | You can indicate whether or not you want to create a new deploy and link it to the existing domain. |
......@@ -220,12 +222,12 @@ Now open your browser and check `https://<your_domain>/index.html`.
We suggest the `/index.html` because by by default, for `haproxyconfig_option` as `option-1` or `option-3`, we configure an [example static website](https://gitlab.zunzun.se/public-items/sampleshop/raw/master/tutorials/tutorial-2.zip) when the Ansible recipes run, which has `index.html`, `index-2.html`, `index-3.html`, and several more pages. You should be able to access all of them. If you use `haproxyconfig_option = option-2`, then check `https://<your_domain>`.
If the website does not appear in your browser, login to your remote server and restart the services. Normally, the `sc_pack` service will be called using the variable `deployment_name` value followed by `.service`. For example: if deployment_name is `deployment_A`, the service will be called `deployment_A.service`.
If the website does not appear in your browser, login to your remote server and restart the services. Normally, the `sc_pack` service will be called using the variable `deployment_name` value with the prefix `sc-` followed by `.service`. For example: if deployment_name is `deployment_A`, the service will be called `sc-deployment_A.service`.
To restart it, run in the terminal:
```
$ systemctl restart deployment_A.service
$ systemctl restart sc-deployment_A.service
```
<br>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment