All-
Based on a (long) discussion yesterday [1] I have put up a patch [2]
whereby you can set [compute]resource_provider_association_refresh to
zero and the resource tracker will never* refresh the report client's
provider cache. Philosophically, we're removing the "healing" aspect of
the resource
Forwarding to openstack-operators per Jay.
On 10/24/18 10:10, Jay Pipes wrote:
> Nova's API has the ability to create "quota classes", which are
> basically limits for a set of resource types. There is something called
> the "default quota class" which corresponds to the limits in the
> CONF.quota
Sorry, I'm opposed to this idea.
I admit I don't understand the political framework, nor have I read the
governing documents beyond [1], but that document makes it clear that
this is supposed to be a community-wide vote. Is it really legal for
the TC (or whoever has merge rights on [2]) to merge
How long are you willing to wait?
The work we're doing to use Placement from Nova ought to allow us to
model both of these things nicely from the virt driver, and request them
nicely from the flavor.
By the end of Rocky we will have laid a large percentage of the
groundwork to enable this. This i
There's [1], but I would have expected you to see error logs like [2] if
that's what you're hitting.
[1]
https://github.com/openstack/nova/blob/master/nova/conf/compute.py#L627-L645
[2]
https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L1714-L1716
efried
On 01/31/2018 03:16 P
Dan, et al-
> Well, (a) today you can't really externally retry a single instance
> build without just creating a new one. The new one could suffer the same
> fate, but that's why we just did the auto-disable feature for nova-compute.
Whoah, but that's after 10 tries (by default). And if e.g. it
Hey folks, sorry if this is a jejune question, but:
In a no-reschedules-by-nova world, if a deploy fails on host 1, how does
the orchestrator (whatever that may be) ask nova to deploy in such a way
that it'll still try to find a good host, but *avoid* host 1? If host 1
was an attractive candidate
Folks-
As of [1], devstack will include color escapes in the default log
formats under systemd. Production deployments can emulate as they see fit.
Note that journalctl will strip those color escapes by default, which
is why we thought we lost log coloring with systemd. Turns ou
Sam-
Under the current design, you can provide a specific endpoint
(singular) via the `endpoint_override` conf option. Based on feedback
on this thread, we will also be keeping support for
`[glance]api_servers` for consumers who actually need to be able to
specify multiple endpoints. See
ethod could be
moved to a more common lib (ksaor os-client-config perhaps) in the
future to facilitate this.
Eric (efried)
On 05/01/2017 09:17 AM, Matthew Treinish wrote:
> On Mon, May 01, 2017 at 05:00:17AM -0700, Flavio Percoco wrote:
>> On 28/04/17 11:19 -0500, Eric Fried wrot
se one of the
> Glance servers in the list is down, without putting them behind a load
> balancer. We also don’t run https for these “internal” Glance calls, to save
> the overhead when transferring images.
> >>
> >> End-user calls to Glance DO go through a real
ose the redundancy we get now by providing a list.
>> Or we would have to shunt all the calls through the user-facing endpoint,
>> which would generate a lot of extra traffic (in places where we don’t want
>> it) for image transfers.
>>
>> Thanks,
>> Mike
>>
12 matches
Mail list logo
