Hi Dave,
On Tue, May 1, 2018 at 4:30 AM, Dave Holland wrote:
> On Mon, Apr 30, 2018 at 12:41:21PM -0400, Mathieu Gagné wrote:
>> Weighers for baremetal cells:
>> * ReservedHostForTenantWeigher [7]
> ...
>> [7] Used to favor reserved host over non-reserved ones based on project.
>
> Hello Mathieu,
You may also need something like pre-emptible instances to arrange the clean up
of opportunistic VMs when the owner needs his resources back. Some details on
the early implementation at
http://openstack-in-production.blogspot.fr/2018/02/maximizing-resource-utilization-with.html.
If you're in Va
[Resending for a colleague who's not on openstack-dev-- SL.]
Yeap, because of the bug [#1677217] in the standard
AggregateImagePropertiesIsolation filter, we have written a custom
Nova scheduler filter.
The filter AggregateImageOsDistroIsolation is a simplified version the
AggregateImagePropertie
On 4/30/2018 11:41 AM, Mathieu Gagné wrote:
[6] Used to filter Ironic nodes based on the 'reserved_for_user_id'
Ironic node property.
This is mainly used when enrolling existing nodes already living
on a different system.
We reserve the node to a special internal user so the customer
ca
On Mon, Apr 30, 2018 at 1:06 PM, Jay Pipes wrote:
> Mathieu,
>
> How do you handle issues where compute nodes are associated with multiple
> aggregates and both aggregates have different values for a particular filter
> key?
>
> Is that a human-based validation process to ensure you don't have tha
Mathieu,
How do you handle issues where compute nodes are associated with
multiple aggregates and both aggregates have different values for a
particular filter key?
Is that a human-based validation process to ensure you don't have that
situation?
Best,
-jay
On 04/30/2018 12:41 PM, Mathieu
Hi,
On Sun, Apr 29, 2018 at 5:29 PM, Ed Leafe wrote:
> On Apr 29, 2018, at 1:34 PM, Artom Lifshitz wrote:
>>
>> Based on that, we can definitely say that SameHostFilter and
>> DifferentHostFilter do *not* belong in the defaults. In fact, we got
>> our defaults pretty spot on, based on this admit
On Mon, Apr 30, 2018 at 8:46 AM, Jay Pipes wrote:
> On 04/30/2018 09:18 AM, Mikhail Medvedev wrote:
>>
>> On Sun, Apr 29, 2018 at 4:29 PM, Ed Leafe wrote:
>>>
>>>
>>> Another data point that might be illuminating is: how many sites use a
>>> custom (i.e., not in-tree) filter or weigher? One of th
On 04/30/2018 09:18 AM, Mikhail Medvedev wrote:
On Sun, Apr 29, 2018 at 4:29 PM, Ed Leafe wrote:
Another data point that might be illuminating is: how many sites use a custom
(i.e., not in-tree) filter or weigher? One of the original design tenets of the
scheduler was that we did not want to
On Sun, Apr 29, 2018 at 4:29 PM, Ed Leafe wrote:
>
> Another data point that might be illuminating is: how many sites use a custom
> (i.e., not in-tree) filter or weigher? One of the original design tenets of
> the scheduler was that we did not want to artificially limit what people
> could use
On Apr 29, 2018, at 1:34 PM, Artom Lifshitz wrote:
>
> Based on that, we can definitely say that SameHostFilter and
> DifferentHostFilter do *not* belong in the defaults. In fact, we got
> our defaults pretty spot on, based on this admittedly very limited
> dataset. The only frequently occurring
On 4/27/2018 4:02 AM, Tomáš Vondra wrote:
Also, Windows host isolation is done using image metadata. I have filled
a bug somewhere that it does not work correctly with Boot from Volume.
Likely because for boot from volume the instance.image_id is ''. The
request spec, which the filter has acce
Hi!
What we‘ve got in our small public cloud:
scheduler_default_filters=AggregateInstanceExtraSpecsFilter,
AggregateImagePropertiesIsolation,
RetryFilter,
AvailabilityZoneFilter,
AggregateRamFilter,
AggregateDiskFilter,
AggregateCoreFilter,
ComputeFilter,
ImagePropertiesFilter,
Server
13 matches
Mail list logo
