hanks. In one node installation no error happened but in two node
installation, I got the error. So I guess the answer of Laszlo is reasonable.
On Wed, Nov 7, 2018 at 10:23 AM Budai Laszlo mailto:laszlo.bu...@gmail.com>> wrote:
Hi
we had a similar situation when the ``host`` e
Hi
we had a similar situation when the ``host`` entry in the neutron.conf was
different than the host entry in the nova.conf on the compute nodes.
So if you're setting a ``host`` entry in one of these files, then make sure the
other file contains the same ``host`` setting.
see
https://docs.op
Hi,
run dmesg on your deployment host. It should print which process has been
evicted by the OOM killer.
We had similar issues with our deployment host. We had to increase its memory
to 9G to have openstack-ansiblle working properly.
You should also monitor the memory usage of your processes on
Dear all,
Openstack-ansible (OSA) allows us to override parameters in the configuration
files as described here:
https://docs.openstack.org/project-deploy-guide/openstack-ansible/draft/app-advanced-config-override.html
there is the following statement:
"You can also apply overrides on a per-h
Dear all,
is it possible to define exceptions in the group_binds definition for a network?
for instance we have something like this:
- network:
container_bridge: "vlan4"
container_type: "veth"
container_interface: "eth1"
ip_from_q: "container"
type: "r
