Hello,
It looks like the new docker module is not installed.
The docker client moved from docker 1.x to 2.x and
unfortunately they changed the name.
Magnum Pike depends on python-docker 2.x.
http://git.openstack.org/cgit/openstack/magnum/tree/requirements.txt?h=stable%2Fpike#n16
Module named doc
cc Andy Wojnarek and Erik McCormick
On 3 October 2017 at 10:32, Spyros Trigazis wrote:
> Hello,
>
> It looks like the new docker module is not installed.
> The docker client moved from docker 1.x to 2.x and
> unfortunately they changed the name.
>
> Magnum Pike depends
Hello list,
I'm hitting quite easily this [1] exception with heat. The db server is
configured to have 1000
max_connnections and 1000 max_user_connections and in the database section
of heat
conf I have these values set:
max_pool_size = 22
max_overflow = 0
Full config attached.
I ended up with
ers = 2
Cheers,
Spyros
ps We will update the magnum docs as well
[1]
http://git.openstack.org/cgit/openstack/heat/tree/heat/engine/service.py#n375
On Mon, 18 Jun 2018 at 19:39, Jay Pipes wrote:
> +openstack-dev since I believe this is an issue with the Heat source code.
>
> On 06/
Hello all,
Following the vulnerability [0], with magnum rocky and the kubernetes driver
on fedora atomic you can use this tag "v1.11.5-1" [1] for new clusters. To
upgrade
the apiserver in existing clusters, on the master node(s) you can run:
sudo atomic pull --storage ostree
docker.io/openstackmag
Magnum queens, uses kubernetes 1.9.3 by default.
You can upgrade to v1.10.11-1. From a quick test
v1.11.5-1 is also compatible with 1.9.x.
We are working to make this painless, sorry you
have to ssh to the nodes for now.
Cheers,
Spyros
On Mon, 3 Dec 2018 at 23:24, Spyros Trigazis wrote