Greetings Everyone,
In an effort to divide the labor, openly plan, and move the elastic stack
charms forward post 5.0 release I've scheduled a meeting on *11/15/2016 at
10AM PST*. If you are a consumer of our charms in the following list, this
meeting is for you:
- Elasticsearch
- Kibana
- Beats
Oops, Missed the document attachment. The meeting agenda/notes will be
here:
https://docs.google.com/document/d/1Aq7JfAVZWoT2IAQGsR3UWGWO6wUka2ztvB0hLbwPy2Q
Charles Butler - Juju Charmer
Come see the future of modeling your datacenter: http://jujucharms.com
On Wed, Nov 9, 2016 at 10:04 AM, Ch
Hi members of the list ,
I'm playing/discovering JUJU I would like to know if anyone is using CONSUL as
a DNS server to resolve new running containers
I'm using LXD as a cloud provider
juju --version
2.0.1-xenial-amd64
consul --version
Consul v0.6.4
Consul Protocol: 3 (Understands bac
I do see this:
https://github.com/hashicorp/consul/issues/854
Which is that the output from consul is too large and doesn't conform to
the RFC which makes Go unable to read the DNS record.
It does feel like this is a stdlib issue. Are you able to do thinks like
python3 -c "import socket; print
