Hi Victoria,
Thank you so much for all your wonderful work especially around Outreachy! :)
Sincerely,
Mohammed
On Tue, Aug 7, 2018 at 7:47 PM, Victoria MartÃnez de la Cruz
wrote:
> Hi all,
>
> I'm reaching you out to let you know that I'll be stepping down as
> coordinator for OpenStack next ro
Hi all,
I'm reaching you out to let you know that I'll be stepping down as
coordinator for OpenStack next round. I had been contributing to this
effort for several rounds now and I believe is a good moment for somebody
else to take the lead. You all know how important is Outreachy to me and
I'm gr
Hi Jay,
Thank you for getting back to my question.
I agree that it is not an error; only a preset limit is reached. I
just wonder why this incident only got recorded in the
nova-conductor.log, but not in other files such as nova-scheduler.log,
which would make more sense to me. :-)
By the way, I
On 08/07/2018 10:57 AM, Cody wrote:
Hi everyone,
I intentionally triggered an error by launching more instances than it
is allowed by the 'cpu_allocation_ratio' set on a compute node. When it
comes to logs, the only place contained a clue to explain the launch
failure was in the nova-conducto
Hello
I'm trying to build a simple all-in-one system using DevStack with OVS+DPDK
with 4 public interfaces.
I'm using the local.conf here -
https://github.com/openstack/networking-ovs-dpdk/blob/master/doc/source/_downloads/local.conf.single_node
I have four physical networks defined here:
"ML
Hi everyone,
I intentionally triggered an error by launching more instances than it is
allowed by the 'cpu_allocation_ratio' set on a compute node. When it comes
to logs, the only place contained a clue to explain the launch failure was
in the nova-conductor.log on a controller node. Why there is
