W dniu 04.01.2018 o 01:02, Matt Riedemann pisze:
> I've started building a list of things that need to be done by the time
> we get to RC1:
>
> https://etherpad.openstack.org/p/nova-queens-release-candidate-todo
Can I add two small tweaks needed for AArch64 architecture to your list?
https://rev
Hi!
This is the weekly summary of Technical Committee initiatives. You can
find the full list of all open topics (updated twice a week) at:
https://wiki.openstack.org/wiki/Technical_Committee_Tracker
If you are working on something (or plan to work on something)
governance-related that is not re
From: CARVER, PAUL [mailto:pc2...@att.com]
Sent: Thursday, December 28, 2017 2:57 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron][neutron-lib]Service function defintion
files
It was a gating criteria for stadium status. The idea was t
čt 4. 1. 2018 v 10:00 odesílatel Dmitry Tantsur
napsal:
> On 01/03/2018 04:24 PM, milanisko k wrote:
> > Folks,
> >
> > as announced already on the Ironic upstream meeting, I'm hereby
> resigning my
> > core-reviewer duties. I've changed my downstream occupation recently and
> I won't
> > be able
Hi everyone,
During our last meeting we decided to get together at IRC for a work
session dedicated to get the "Missing features list" up to date, and
take the fist steps converting items into a more official list at
launchpad - where we have a project [1]. Would be awesome to see as many
of
Development Focus
-
Teams should be focused on implementing planned work for the cycle and bug
fixes.
General Information
---
The deadline for extra ATC's is coming up on January 12. If there is someone
that contributes to your project in a way that is not reflec
First resource provider and placement update for 2018. This year
I'll be labelling the report with %y-%W to distinguish from last
year, so this is 18-01.
The engine of activity is still warming up for the new year, so much
of this is pre-existing stuff.
# Most Important
Matt posted a message w
Hey all,
This note is a continuation of a thread we started last year on
analyzing other policy systems [0]. Now that we're back from the
holidays and having policy meetings on Wednesdays [1], it'd be good to
pick up the conversation again. We had a few good sessions a couple
months ago going thro
# Keystone Team Update - Weeks of 25 December 2017 and 1 January 2018
## News
Happy new year! Things have been slow during the holiday season so not
much to report.
The policy meeting was short but we talked about starting up our
investigations into other RBAC systems again. Lance kicked off a
t
On Thu, 4 Jan 2018 08:46:38 -0600, Matt Riedemann wrote:
The main issue is for newer jobs like tempest-full, the logs are under
controller/logs/ and we lose the log analyze formatting for color, being
able to filter on log level, and being able to link directly to a line
in the logs.
I also n
On Fri, 5 Jan 2018, 7:14 pm melanie witt, wrote:
> On Thu, 4 Jan 2018 08:46:38 -0600, Matt Riedemann wrote:
> > The main issue is for newer jobs like tempest-full, the logs are under
> > controller/logs/ and we lose the log analyze formatting for color, being
> > able to filter on log level, and
On Fri, Jan 5, 2018, at 10:26 AM, Andrea Frittoli wrote:
> On Fri, 5 Jan 2018, 7:14 pm melanie witt, wrote:
>
> > On Thu, 4 Jan 2018 08:46:38 -0600, Matt Riedemann wrote:
> > > The main issue is for newer jobs like tempest-full, the logs are under
> > > controller/logs/ and we lose the log analyz
I've noticed that our CI logs have API extension policy deprecation
warnings in them on startup, even though we don't use any non-default
policy rules in our CI runs, so everything is just loaded from policy in
code.
Jan 05 16:58:48.794318 ubuntu-xenial-rax-dfw-0001705089
nova-compute[11289]:
I thought we planned for that case, but it looks like we log a warning
regardless (obviously from your trace) so that operators don't miss
opportunities to clean up code. In addition to that, the removal of a
policy might make a role obsolete, which is harder to check for than
just seeing if they h
I recreated this locally. Turns out I missed an attribute that the
oslo_policy.policy:Enforcer class had called self.file_rules, which
appear to the be specific policies pulled from policy.json or
policy.yaml files. I modified the check to compare the deprecated policy
against that instead of self.
Excellent work on this, Kevin. I'll review the patch series on Monday.
Best,
-jay
On 01/04/2018 09:53 PM, Zhenyu Zheng wrote:
Hi All,
We are working on patches to improve the performance filtering instance
by IP address this cycle. As discussed in the previous ML[1], it
contains both patches
On 01/04/2018 09:50 PM, wenran xiao wrote:
hi all,
neutron metering can only count traffic that we send to
*remote_ip*(egress), and *remote_ip* send to us(ingress), I think we
should add method to count the traffic for floating ip or internal ip.
Any suggestions is welcome.
Neutron metering
Seems that sometime between 1/2 and 1/3 this year,
tempest.config.CONF.service_available.aodh_plugin as well as
..service_available.mistral became unavailable in congress dsvm check/gate
job. [1][2]
I've checked the changes that went in to congress, tempest, devstack,
devstack-gate, aodh, and mist
We've been discussing generic push drivers for Congress for quite a while.
Finally sketching out something concrete and looking for some preliminary
feedback. Below are sample interactions with a proposed generic push
driver. A generic push driver could be used to receive push updates from
vitrage,
19 matches
Mail list logo