Feature/registry drone roles #42
Conversation
| @@ -0,0 +1,7 @@ | |||
| - hosts: registry | |||
| roles: | |||
| - common-no-vlan | |||
There was a problem hiding this comment.
This role is useless at the moment, only needed for ssh keys, maybe in the future it will be of more use.
hosts.template
Outdated
| @@ -4,12 +4,14 @@ caliopen | |||
| gateway | |||
| storage | |||
| smtp | |||
| citools | |||
|
|
|||
| [services:vars] | |||
| dist_directory=./dist | |||
| object_store_access_key=SZ1BBGKTD2N13E0W5L8N | |||
| object_store_secret_key=qTsjiThBQA2NH6ZO32tCwCC6wcC8ValVLR16XUsB | |||
| caliopen_domain_name=alpha.caliopen.org | |||
There was a problem hiding this comment.
Can't we use variables caliopen_domain_name=alpha.{{caliopen_domain_base}}
And for consistency naming, use caliopen_domain_base instead of caliopen_base_domain
| @@ -107,3 +126,6 @@ mail1 ansible_host=ip_mail1 ansible_user=root backend_ip=backend_mail1 | |||
|
|
|||
| [logstash] | |||
| logstash1 ansible_host=ip_logstash1 ansible_user=root backend_ip=backend_logstash1 | |||
|
|
|||
| [registry] | |||
| registry1 ansible_host=ip_registry1 ansible_user=root backend_ip=backend_registry1 | |||
| get_url: | ||
| url: https://github.com/docker/compose/releases/download/1.22.0/docker-compose-Linux-x86_64 | ||
| dest: /usr/local/bin/docker-compose | ||
| mode: 0550 |
hosts.template
Outdated
| DRONE_SECRET=this_should_be_a_secret | ||
| # List of admins, Github usernames | ||
| DRONE_ADMIN= | ||
| DRONE_HOST=drone.caliopen.org |
There was a problem hiding this comment.
use of {{ caliopen_domain_base }} possible ?
| server { | ||
| listen 443 ssl; | ||
| listen [::]:443 ssl; | ||
| server_name registry.{{ caliopen_base_domain }}; |
There was a problem hiding this comment.
need to update all caliopen_base_domain variable to new naming
roles/nginx/tasks/main.yml
Outdated
| @@ -22,10 +22,12 @@ | |||
| git: | |||
| repo: "https://github.com/knyar/nginx-lua-prometheus.git" | |||
| dest: /srv/nginx-lua-prometheus | |||
| tags: monitoring | |||
There was a problem hiding this comment.
registry is deployed with extra parameter --skip-tags monitoring
There was a problem hiding this comment.
I'm not fan of tags for that purpose, as we will forget to give --skip-tags flag.
May include the nginx part directly in registry task ?
There was a problem hiding this comment.
we can just install it even if it isn't monitored atm
Has been dry runned;)