Hey!
I'm probably missing something obvious, but there is something I do not understand about our hiera hierarchy as part of change 274711 [1].
What I am trying to achieve:
1) activate HTTPS for elastic search in both eqiad and codfw 2) not activate it for logstash (it would not hurt, but it does not seem like we need it at the moment) 3) define base::puppet::dns_alt_names for elasticsearch servers to 'search.svc.eqiad.wmnet' and 'search.svc.codfw.wmnet' respectively
How I'm trying to achieve this:
1) Adding the property elasticsearch::https::ensure: 'present' in hieradata/role/common/elasticsearch/server.yaml
2) Adding the property elasticsearch::https::ensure: 'present' in hieradata/role/common/logstash/server.yaml
3) Adding the property base::puppet::dns_alt_names: 'search.svc.[codfw|eqiad].wmnet' in hieradata/role/[codfw|eqiad]/elasticsearch/server.yaml respectively.
What makes me think it is not working:
The excellent puppet-compiler gives me a view on the change catalog [6], [7] that tells me that
* elasticsearch::https is ensured 'present' for both elasticsearch and logstash nodes * dns_alt_names is not defined for any node
Anyone has a pointer on what I'm missing?
Thanks!
MrG
[1] https://gerrit.wikimedia.org/r/#/c/274711/ [2] https://gerrit.wikimedia.org/r/#/c/274711/10/hieradata/role/common/elasticse... [3] https://gerrit.wikimedia.org/r/#/c/274711/10/hieradata/role/common/logstash/... [4] https://gerrit.wikimedia.org/r/#/c/274711/10/hieradata/role/codfw/elasticsea... [5] https://gerrit.wikimedia.org/r/#/c/274711/10/hieradata/role/eqiad/elasticsea... [6] http://puppet-compiler.wmflabs.org/2048/elastic1001.eqiad.wmnet/change.elast... [7] http://puppet-compiler.wmflabs.org/2048/logstash1001.eqiad.wmnet/change.logs...
--- Guillaume Lederrey Operations Engineer, Discovery Wikimedia Foundation
You can forget about this request, it seems that it is now working. No idea why. Either I was just blind and not reading the output correctly, or I forgot to push my code before running puppet-compiler...
Sorry for wasting your time...
On Mon, Mar 14, 2016 at 4:14 PM, Guillaume Lederrey glederrey@wikimedia.org wrote:
Hey!
I'm probably missing something obvious, but there is something I do not understand about our hiera hierarchy as part of change 274711 [1].
What I am trying to achieve:
- activate HTTPS for elastic search in both eqiad and codfw
- not activate it for logstash (it would not hurt, but it does not
seem like we need it at the moment) 3) define base::puppet::dns_alt_names for elasticsearch servers to 'search.svc.eqiad.wmnet' and 'search.svc.codfw.wmnet' respectively
How I'm trying to achieve this:
- Adding the property elasticsearch::https::ensure: 'present' in
hieradata/role/common/elasticsearch/server.yaml
- Adding the property elasticsearch::https::ensure: 'present' in
hieradata/role/common/logstash/server.yaml
- Adding the property base::puppet::dns_alt_names:
'search.svc.[codfw|eqiad].wmnet' in hieradata/role/[codfw|eqiad]/elasticsearch/server.yaml respectively.
What makes me think it is not working:
The excellent puppet-compiler gives me a view on the change catalog [6], [7] that tells me that
- elasticsearch::https is ensured 'present' for both elasticsearch and
logstash nodes
- dns_alt_names is not defined for any node
Anyone has a pointer on what I'm missing?
Thanks!
MrG[1] https://gerrit.wikimedia.org/r/#/c/274711/ [2] https://gerrit.wikimedia.org/r/#/c/274711/10/hieradata/role/common/elasticse... [3] https://gerrit.wikimedia.org/r/#/c/274711/10/hieradata/role/common/logstash/... [4] https://gerrit.wikimedia.org/r/#/c/274711/10/hieradata/role/codfw/elasticsea... [5] https://gerrit.wikimedia.org/r/#/c/274711/10/hieradata/role/eqiad/elasticsea... [6] http://puppet-compiler.wmflabs.org/2048/elastic1001.eqiad.wmnet/change.elast... [7] http://puppet-compiler.wmflabs.org/2048/logstash1001.eqiad.wmnet/change.logs...
Guillaume Lederrey Operations Engineer, Discovery Wikimedia Foundation