out changing any kolla container or
kolla-ansible code.
Am 10/10/18 um 9:18 AM schrieb Florian Engelmann:
by "another storage system" you mean the KV store of consul? That's
just someting consul brings with it...
consul is very strong in doing health checks
Am 10/9/18 u
On 17.10.2018 15:45, Florian Engelmann wrote:
On 10.10.2018 09:06, Florian Engelmann wrote:
Now I get you. I would say all configuration templates need to be
changed to allow, eg.
$ grep http /etc/kolla/cinder-volume/cinder.conf
glance_api_servers = http://10.10.10.5:9292
auth_url = http
Thanks,
Kevin
____
From: Florian Engelmann [florian.engelm...@everyware.ch]
Sent: Wednesday, October 10, 2018 12:18 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [kolla] add service discovery, proxysql, vault,
fabio and FQDN endpoints
by &
/tcp --expose 35357/tcp --name=keystone ...
Am 10/10/18 um 9:18 AM schrieb Florian Engelmann:
by "another storage system" you mean the KV store of consul? That's just
someting consul brings with it...
consul is very strong in doing health checks
Am 10/9/18 um 6:09 PM schrieb Fox, K
On 10.10.2018 09:06, Florian Engelmann wrote:
Now I get you. I would say all configuration templates need to be
changed to allow, eg.
$ grep http /etc/kolla/cinder-volume/cinder.conf
glance_api_servers = http://10.10.10.5:9292
auth_url = http://internal.somedomain.tld:35357
.conf (e.g. detailed mode,
disable-by-file, etc).
Cheers,
--Morgan
On Fri, Oct 12, 2018 at 3:07 AM Florian Engelmann
mailto:florian.engelm...@everyware.ch>>
wrote:
Hi,
I tried to configure the healthcheck framework (/healthcheck) for nova,
cinder, glance and keystone but it lo
Hi,
I tried to configure the healthcheck framework (/healthcheck) for nova,
cinder, glance and keystone but it looks like paste is not used with
keystone anymore?
https://github.com/openstack/keystone/commit/8bf335bb015447448097a5c08b870da8e537a858
In our rocky deployment the healthcheck is
consul so as to not add yet another storage system? coredns with the
https://coredns.io/plugins/etcd/ plugin would maybe do what you need?
Thanks,
Kevin
____
From: Florian Engelmann [florian.engelm...@everyware.ch]
Sent: Monday, October 08, 2018 3:14 AM
To
Am 10/9/18 um 1:47 PM schrieb Mark Goddard:
On Tue, 9 Oct 2018 at 12:03, Florian Engelmann
mailto:florian.engelm...@everyware.ch>>
wrote:
Am 10/9/18 um 11:04 AM schrieb Mark Goddard:
> Thanks for these suggestions Florian, there are some interesting
ideas
> in
Am 10/9/18 um 1:23 PM schrieb Jay Pipes:
On 10/09/2018 06:34 AM, Florian Engelmann wrote:
Am 10/9/18 um 11:41 AM schrieb Jay Pipes:
On 10/09/2018 04:34 AM, Christian Berendt wrote:
On 8. Oct 2018, at 19:48, Jay Pipes wrote:
Why not send all read and all write traffic to a single haproxy
anges/additions I agree. But adding those components without
kolla/kolla-ansible integration feels not right.
On Mon, 8 Oct 2018 at 11:15, Florian Engelmann
mailto:florian.engelm...@everyware.ch>>
wrote:
Hi,
I would like to start a discussion about some changes and additions I
Am 10/9/18 um 11:41 AM schrieb Jay Pipes:
On 10/09/2018 04:34 AM, Christian Berendt wrote:
On 8. Oct 2018, at 19:48, Jay Pipes wrote:
Why not send all read and all write traffic to a single haproxy
endpoint and just have haproxy spread all traffic across each Galera
node?
Galera, after
Hi,
I would like to start a discussion about some changes and additions I
would like to see in in kolla and kolla-ansible.
1. Keepalived is a problem in layer3 spine leaf networks as any floating
IP can only exist in one leaf (and VRRP is a problem in layer3). I would
like to use consul and
D portion of my name
--name/-n TYPE.ID set name
--cluster NAME set cluster name (default: ceph)
--setuser USERset uid to user or uid (and gid to user's gid)
--setgroup GROUP set gid to group or gid
--version show version and quit
-drun in foregr
14 matches
Mail list logo