+1 from Searchlight since we have only a small number of changes.
Thanks,
On Fri, Oct 12, 2018 at 5:07 AM Sean McGinnis wrote:
> Libraries should be released early and often so their consumers can pick up
> merged changes, and issues with those changes can be identified close to
> when
> the
Thank Doug for coordinating this,
Is there any way for us to update the health of the Searchlight project to
reflect the current state? Right now the status is not good to attract new
contributors.
Bests,
On Fri, Oct 12, 2018 at 6:50 AM Doug Hellmann wrote:
> Doug Hellmann writes:
>
> > TC
Doug Hellmann writes:
> TC members,
>
> Since we are starting a new term, and have several new members, we need
> to decide how we want to rotate the liaisons attached to each our
> project teams, SIGs, and working groups [1].
>
> Last term we went through a period of volunteer sign-up and then
Libraries should be released early and often so their consumers can pick up
merged changes, and issues with those changes can be identified close to when
the change is made. To help with this, we are considering forcing at least one
library release per milestone (if there are unreleased merged
Hi,
We recently merged a new feature to oslo.config and it was suggested
that I publicize it since it addresses a longstanding pain point. It's a
validator tool[1] that will warn or error on any entries in a config
file that aren't defined in the service or are deprecated.
Previously this
My understanding is it is still safeish to use when you deal with it right. it
causes a transaction abort if the race condition ever hits, and you can keep
retrying until your commit makes it. So, there are two issues here:
1. its a more rare kind of abort, so unless you are testing and
On Thu, Oct 11, 2018, at 7:17 AM, Ben Nemec wrote:
>
>
> On 10/11/18 8:53 AM, Felix Enrique Llorente Pastora wrote:
> > So for example, I don't see why changes at tripleo-quickstart can be
> > reset if tripleo-ui fails, this is the kind of thing that maybe can be
> > optimize.
>
> Because if
On 10/10/18 1:35 PM, Jay Pipes wrote:
+tc topic
On 10/10/2018 11:49 AM, Fox, Kevin M wrote:
Sorry. Couldn't quite think of the name. I was meaning, openstack
project tags.
I think having a tag that indicates the project is no longer using
SELECT FOR UPDATE (and thus is safe to use
Doug Hellmann writes:
> We have about 17 remaining patches to import zuul job settings into a
> few repositories. Those are mostly in stable branches and the jobs are
> failing in ways that may take us a long time to fix.
>
> Rather than waiting for those, Andreas and I are proposing that we
Hi all!
I'll be out starting from Oct 15th, coming back on Oct 19th.]
The upstream meeting will be led by Alex Schultz (mwhahaha).
Best Regards
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
Hi Kuryrs!
As I promised in my earlier email, I'd like to organize a virtual team
gathering to gather around and sync for the upcoming and next release.
I've put up an etherpad [1] for gathering topics for the sessions, which
will be open until October 22nd, where I'll put up a tentative
Hi all!
I'll be out for two weeks, coming back on Oct 30th. I won't cancel the
upstream meeting, which will be led by apuimedo in the meanwhile.
I also do plan to organize a vPTG, around my return date, so stay tuned
for an email with a document for topics.
See you in some days!
Best!
Daniel
On 10/10/2018 23.10, Jeremy Stanley wrote:
> I might have only pointed this out on IRC so far, but the
> expectation is that testing 3.5 and 3.6 at the same time was merely
> transitional since official OpenStack projects should be moving
> their testing from Ubuntu Xenial (which provides 3.5) to
Adding the mailing lists back to your reply, thank you :)
I guess that +melvin.hills...@huawei.com can
help us a little bit organizing the SIG,
but I guess the first thing would be collecting a list of tools which could
be published
under the umbrella of the SIG, starting by the ones already in
On 10/11/18 8:53 AM, Felix Enrique Llorente Pastora wrote:
So for example, I don't see why changes at tripleo-quickstart can be
reset if tripleo-ui fails, this is the kind of thing that maybe can be
optimize.
Because if two incompatible changes are proposed to tripleo-quickstart
and
So for example, I don't see why changes at tripleo-quickstart can be reset
if tripleo-ui fails, this is the kind of thing that maybe can be optimize.
On Thu, Oct 11, 2018 at 1:17 PM Emilien Macchi wrote:
>
>
> On Thu, Oct 11, 2018 at 10:01 AM Felix Enrique Llorente Pastora <
>
Am 08.10.2018 um 17:16 schrieb Markus Hentsch:
> Dear OpenStack developers,
>
> as you suggested, we have written individual specs for Nova [1] and
> Cinder [2] so far and will write another spec for Glance soon. We'd
> appreciate any feedback and reviews on the specs :)
>
> Thank you in advance,
On Wed, Oct 10, 2018 at 7:36 PM Goutham Pacha Ravi
wrote:
> On Wed, Oct 10, 2018 at 2:10 PM Jeremy Stanley wrote:
> >
> > On 2018-10-10 16:00:40 -0500 (-0500), Sean McGinnis wrote:
> > [...]
> > > I would rather see us testing 3.5 and 3.7 versus 3.5, 3.6, and
> > > 3.7.
> > [...]
> >
> > I
Hi everyone:
We've discussed bringing back meetings back to the TC and there's
different opinions on having biweekly vs monthly meetings. Therefore,
I have added a patch similar to Doug's that instead lists biweekly
meetings instead of monthly meetings.
I would really appreciate if other
Hi All,
Please find the Nova API highlights of this week.
Weekly Office Hour:
===
What we discussed this week:
- Discussed on api cleanup spec.
- Discussed api extensions work and pending things on this work. Proposed all
the pending item for this BP.
- Discussed on 2 new
On 11/10/18 00:18, Jeremy Stanley wrote:
On 2018-10-10 13:24:28 +1100 (+1100), Gilles Dubreuil wrote:
On 09/10/18 23:58, Jeremy Stanley wrote:
On 2018-10-09 08:52:52 -0400 (-0400), Jim Rollenhagen wrote:
[...]
It seems to me that a major goal of openstacksdk is to hide
differences between
As many of you will have seen on IRC, I've mostly been appearing AFK for the
last couple of development cycles. Due to other tasks downstream most of my
attention has been drawn away from upstream Ironic development. Going forward
I'm unlikely to be as heavily involved with the Ironic project
On Wednesday, 10 October 2018 22:42:03 CEST Telles Nobrega wrote:
> Hi all,
>
> I'm taking PTO from tomorrow until Monday Oct 22nd. I won't cancel the
> meeting yet but let me know if you want me to.
No strong opinions about it.
I will be around; if there are people asking for it, I can start
On Thu, Oct 11, 2018 at 10:01 AM Felix Enrique Llorente Pastora <
ellor...@redhat.com> wrote:
> Hello there,
>
>After suffering a lot from zuul's tripleo gate piepeline queue reseting
> after failures on patches I have ask myself what would happend if we have
> more than one queue for gating
Thanks Jeremy.
On Thu, 11 Oct 2018 at 02:09 Jeremy Freudberg
wrote:
> Enjoy the PTO, Telles!
>
> I don't really have much to share at a meeting. My vote is for no meeting.
> Our other active core and other active community members can agree to
> cancel or not, and I'll heed that decision.
>
> On
Hi folks,
Unfortunate we need to cancel todays meeting! Talk to you next Wednesday
at 0700 UTC.
Cheers,
Tobias
--
Tobias Rydberg
Senior Developer
Twitter & IRC: tobberydberg
www.citynetwork.eu | www.citycloud.com
INNOVATION THROUGH OPEN IT INFRASTRUCTURE
ISO 9001, 14001, 27001, 27015 &
Hello there,
After suffering a lot from zuul's tripleo gate piepeline queue reseting
after failures on patches I have ask myself what would happend if we have
more than one queue for gating tripleo.
After a quick read here https://zuul-ci.org/docs/zuul/user/gating.html,
I have found the
27 matches
Mail list logo
