[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
Graham Hayes writes:
> I would like to suggest we have an office hours style meeting, with
> one in the UTC evening and one in the UTC morning.
> If this seems reasonable - when and what frequency should we do
> them? What times suit the current set of contributors?
In general, I prefer
Artom Lifshitz writes:
> To that end, we'd like to know what filters operators are enabling in
> their deployment. If you can, please reply to this email with your
> [filter_scheduler]/enabled_filters (or
> [DEFAULT]/scheduler_default_filters if you're using an older version)
> option from
Joe Topjian writes:
> Terraform hat! I want to slightly nit-pick this one since the words
> "leak" and "admin-priv" can sound scary: Terraform technically wasn't
> doing anything wrong. The problem was that Octavia was creating
> resources but not setting ownership to the tenant. When it came time
Paul Bourke writes:
> So I think everyone is in agreement that it should be option 2. I'm
> leaning towards this also but I'm wondering how much of this makes
> things easier for us as developers rather than operators.
> How committed this are we in practice? For example, if we take
Ihar Hrachyshka writes:
> I just saw the plan merged in master:
> https://review.openstack.org/#/c/451492/ That's cool! Can we also
> backport the change to Ocata and maybe Newton so that we don't hit the
> same bug there? The backport is already up:
Clark Boylan writes:
> "id": "network1",
> "link": "tap14b906ba-8c",
> "network_id": "7ee08c00-7323-4f18-94bb-67e081520e70",
> "type": "ipv6_dhcp"
> "services": 
> You'll notice that the network1
Emilien Macchi writes:
> DIB folks: please confirm on this thread that you're ok to move out
> DIB from TripleO and be an independent project.
As a DIB user (and occasional contributor of patches in the past) and
TripleO non-user, I'm in favor of the separation.
> Also please decide if we want
Stephane Miller writes:
> I'm proposing that we have a regular, IRC-based meeting for the
> project. This could be done on its own, or as part of the TripleO
> meeting. I don't think we necessarily need to do this every week, but
> a fortnightly chance to get together to chat about big changes,
1- Create and maintain a Ubuntu PPA Archive to host Neutron with IPv6
patches (from Nephos6 / Shixiong?).
Let me know if there are interest on this...
Great initiative! We're building a new Icehouse cluster soon and are
very interested in trying these packages, because
Collins, Sean writes:
Looking at the calendar, our options for 1500 UTC require us to change
the day that we meet. The following days are available:
For what it's worth (I haven't been contributing so far but I'm very
interested in the topic and would
Mail list logo