Open Stack

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 am using the Queens release.

Regards,
Cody
On Tue, Aug 7, 2018 at 11:38 AM Jay Pipes <jaypipes at gmail.com> wrote:
>
> 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-conductor.log on a controller node. Why there is
> > no trace in the nova-scheduler.log (or any other logs) for this type or
> > errors?
>
> Because it's not an error.
>
> You exceeded the capacity of your resources, that's all.
>
> Are you asking why there isn't a way to *check* to see whether a
> particular request to launch a VM (or multiple VMs) will exceed the
> capacity of your deployment?
>
> Best,
> -jay
>
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack