On 2018-08-01 12:48:39 -0400 (-0400), Doug Hellmann wrote:
> Excerpts from Monty Taylor's message of 2018-08-01 09:58:03 -0500:
> > On 08/01/2018 08:38 AM, Jeremy Stanley wrote:
> > > On 2018-08-01 09:58:48 -0300 (-0300), Rafael Weingärtner wrote:
> > >> What abou
losely reflect those of our
community), but even with that our biggest fear was disruption and
fracturing with some people holding conversations in one network and
some in the other.
--
Jeremy Stanley
signature.asc
Description: PGP sig
use it to hide their origins from the IRC server
operators and put us in the middle of the problem.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
ell). A +1 from the current PTL of
record on that change would probably be a good idea.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscr
an" entry (similar to the "Keystone" entry). The
only thing previously standing in the way was a use case for a
fundamental feature from the trademark programs' interoperability
set.
--
Jeremy Stanley
signature.asc
Description: PGP signature
___
ame should be an E-mail address
you use both with your Gerrit account and your OpenStack Foundation
Individual Member profile since we'll use it both to confirm you
have a qualifying change merged to a relevant deliverable repository
and that you have an active foundation membership.
--
Jeremy Stanl
the support lifetime of the distro release is
shorter than the maintenance lifetime of our stable branches. Would
probably be fine for master branch jobs but not beyond, right?
--
Jeremy Stanley
signature.asc
Description: PGP signature
___
thread or the review
linked from it:
http://lists.openstack.org/pipermail/openstack-sigs/2018-July/000429.html
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage
won't be an issue, but we have
to go in assuming that it still might.
> Should I propose a patch to include it in review.o.o ?
I recommend trying out the one we have already, fixing it if needed,
and then coordinating a time to merge a change switching that
zuul_inline toggle to true.
--
Jerem
release anything at the moment, so I
> can't prove anything right now. So, take my advice with a grain of
> salt. :)
[...]
Anything like http://www.airshipit.org/ ?
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
hours can go to the the point in the IRC logs that
> they are interested in.
[...]
Heartily seconded.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubsc
nstack.org/wiki/PyMySQL_evaluation
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:u
questions, feel free to follow
up to this notification or pop into the #openstack-release channel
on the Freenode IRC network. Thanks!
[*] https://review.openstack.org/579188
--
Jeremy Stanley
signature.asc
Description: PGP signature
reason, be it affinity, anti-affinity, et cetera).
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.opensta
access. It may be a pain to
collect up instance UUIDs and them pass those along to the provider
so they can correlate to compute nodes in their service logs, but
that's ultimately the right way to go about it so that separation of
concerns is preserved.
--
Jeremy Stanley
signature.asc
D
hasn't migrated because
> other projects haven't migrated (we really need to be on both systems
> unfortunately). Is it possible to half migrate?
The SB migration script is set up to handle incremental importing,
so this could be an option in theory. In practice, we've not really
used it t
ipated some questions. I will be prepared to
> talk to people about it regardless, and maybe we won't need a
> separate room.
I think the up side to the current plan is that there are likely to
also be Zuulies in that same room answering Zuulish sorts of
questi
g support in the future).
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubsc
want to take advantage
of any features of other services which require user interaction
with the key store.
Making a user-facing API service a "required project" from that
perspective is a bigger discussion, in my opinion. I'm in favor of
trying, but to me this piece is the first step
On 2018-06-06 01:29:49 + (+), Jeremy Stanley wrote:
[...]
> Seeing no further objections, I give you
> https://review.openstack.org/572656 for the next step.
That change merged just a few minutes ago, and
https://governance.openstack.org/tc/reference/base-services.html#curren
tion data so is
really no increased burden in that regard.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.o
> it clearly helped to stabilize our container jobs, I actually haven't seen
> timeouts since we merged your patch. Thanks a ton!
[...]
As best we can tell from logs, the way Dockerhub served these images
changed a few weeks ago (at the end of May) leading to this problem.
--
Jeremy Stanl
ount forward. It's useful for centralized spam
> filtering.
I'm not personally comfortable having someone else decide for me
what is or isn't spam, and I doubt I'm alone in that.
--
Jeremy Stanley
signature.asc
Description
.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi
On 2018-06-13 14:11:22 -0500 (-0500), Matthew Thode wrote:
[...]
> What if we want that train experience. I feel like there will be
> something missing without it.
Sounds like it may require us to bring our own train whistles.
--
Jeremy S
t's at least one way to keep a user from accidentally booting an
untrusted/unsigned image, assuming that's a goal for this feature.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development
On 2018-06-11 17:55:24 -0500 (-0500), Matt Riedemann wrote:
> On 6/11/2018 3:23 PM, Jeremy Stanley wrote:
> > If you recall the "specs" experiment years
> > ago, a few teams tried mildly different solutions for moving from LP
> > blueprints with random wiki page l
s relying on different tools,
realizing that no progress would ever be made if we required
everyone to agree to use it first.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not
wn out. I personally don't
even feel that teams should be forced to use StoryBoard (or any
particular tool for that matter), but just want to focus on making
sure we provide useful, free and open tools through which and on
which we can colle
e benefit of search engines should likely come with or
shortly after that.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: opensta
presumably "important" sample) who are actually using that
feature, how many of them are simply doing it because they thought
the release team was still making use of that information? (Hint:
they stopped as of mitaka
ent the minimal install
image build isn't likely to actually break with any significant
frequency once we get it working.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for
.]
The Kata community (currently) hosts all their work in GitHub rather
than our infrastructure, so I'm not sure that's an altogether useful
distinction.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack
On 2018-06-06 14:52:04 -0400 (-0400), Zane Bitter wrote:
> On 29/05/18 13:37, Jeremy Stanley wrote:
> > On 2018-05-29 10:53:03 -0400 (-0400), Zane Bitter wrote:
[...]
> > > * If the repo is a fork of another project, there must be (public)
> > > evidence o
t also might not!) for your Python package is
suitable for rendering on PyPI.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: opensta
bs, so maybe that would be a
lower-overhead place to introduce the setup rst check?
Brainstorming.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
On 2018-05-31 13:00:47 + (+), Jeremy Stanley wrote:
> On 2018-05-31 10:33:51 +0200 (+0200), Thierry Carrez wrote:
> > Ade Lee wrote:
> > > [...]
> > > So it seems that the two blockers above have been resolved. So is it
> > > time to ad a castellan
ython 3.6 it provides) before we force the PTI jobs
over to it at the start of the Stein cycle.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscrib
's not so
much a matter of a lack of trust on anyone's part, as a desire for
me to keep and further improve on that trust I've already built.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Developmen
o
use it for similar reasons to the governance repo. But no, it's not
common enough I'd bother to mention it in any sort of documentation
aimed at the general reviewer base.
--
Jeremy Stanley
signature.asc
Description: PGP signature
_
is to
the base services list in the next day or so as the mailing list
discussion didn't highlight any new concerns and indicated that the
previous blockers we identified have been resolved in the
intervening year.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
push back on
those sorts of adverse influences directly, I have a feeling not
everyone can comfortably do so. On the other hand, it might also
just be easy enough to give one of your fellow reviewers in another
org a heads up that maybe they should take a look at that patch over
there and provid
ist of it is that we wanted to switch to
a workflow which 1. didn't assume you were a Python-oriented
project, and 2. was more in line with how most projects outside
OpenStack make use of Sphinx.
[*] https://review.openstack.org/508694
--
Jeremy Stanley
sig
On 2018-05-31 16:49:13 -0400 (-0400), John Dennis wrote:
> On 05/30/2018 08:23 PM, Jeremy Stanley wrote:
> > I think this is orthogonal to the thread. The idea is that we should
> > avoid nettling contributors over minor imperfections in their
> > submissions (
l/openstack-dev/2018-May/130567.html
I figured I'd let it run through the summit to garner feedback
before proposing the corresponding Gerrit change.
--
Jeremy Stanley
signature.asc
Description: PGP signature
_
then rebase onto all the broken and cross your
fingers that you're not making the job of whoever has to untangle
trunk before release that much harder.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack
ction, it's about incremental
improvement. If a proposed change is an improvement, that's enough.
If it's not perfect... well, that's just opportunity for more
improvement later.
--
Jeremy Stanley
signature.asc
Description: PGP signature
___
that team will likely get scaled back to just the
remaining interested maintainers and its continued governance
situation can be revisited at that future date.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
Open
On 2018-05-30 16:59:10 +0200 (+0200), Julien Danjou wrote:
[...]
> I see cliff has already set that requirements in its master branch, but
> no new version has been released. Releasing a new cliff version should
> fix that issue.
Yes, that's in progress today.
--
Jeremy Stanley
sign
3.4 and later:
https://github.com/python-cmd2/cmd2/issues/421
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-r
hlight whatever we discussed in the
resulting meeting minutes. I'm planning to do that at our 01:00z
office hour (a couple hours from now) and see how it goes, though
that timeslot in particular tends to have little or no discussion.
--
Jeremy Stanley
signature.asc
Descript
g Author requires creating a new commit from scratch or
passing extra options to git to reset it, while changing the Owner
needs a completely new Change-Id footer).
--
Jeremy Stanley
signature.asc
Description: PGP signature
e could consider
overloading status:maintenance-mode for this purpose, but some teams
perhaps simply don't have large amounts of code change ever and
that's just a normal effect of how they operate.
--
Jeremy Stanley
signature.asc
Descriptio
rs have also said, this seems like a potentially useful
metric on its own anyway. We could simply avoid including
low-activity tagged teams in diversity reporting and not associate
any diversity tags with them.
--
Jeremy Stanley
signature.asc
Description: P
On 2018-05-29 15:51:31 -0400 (-0400), Doug Hellmann wrote:
[...]
> Could we, for example, look at the set of packages installed under
> python2 and report errors if any OpenStack packages end up there?
[...]
This sounds like a marvellous solution.
--
Jeremy Stanley
signature.asc
Descr
g the DCO in commit messages, so I'm not a fan of
adding some new agreement people have to directly acknowledge along
with associated automation and policing.
--
Jeremy Stanley
signature.asc
Description: PGP signature
_
e
free tools at every opportunity, I sure wish we had in this case.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ..
On 2018-05-23 15:20:28 -0400 (-0400), Brian Haley wrote:
> On 05/23/2018 02:00 PM, Jeremy Stanley wrote:
> > On 2018-05-22 17:41:18 -0400 (-0400), Brian Haley wrote:
> > [...]
> > > I read this the other way - the goal is to get all the forked code from
> > &
ost to developer efficiency, but ultimately are an
implementation detail.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-
d, et
cetera as appropriate.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsu
a good name. ;)
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.opens
mbers of the TC (in #openstack-tc[*]) before it
was agreed there was room to squeeze this particular latecomer into
the lineup.
[*]
http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-05-14.log.html#t2018-05-14T17:27:05
--
Jeremy Stanley
signatu
On 2018-05-17 16:35:36 +0200 (+0200), Petr Kovar wrote:
> On Wed, 16 May 2018 17:05:15 +
> Jeremy Stanley <fu...@yuggoth.org> wrote:
>
> > On 2018-05-16 18:24:45 +0200 (+0200), Petr Kovar wrote:
> > [...]
> > > I'd like to propose replacing
s up to the Nova team to
decide when to move their master branch testing to new versions of
these. Per the example above if they upped their hacking cap to <1.2
they would get hacking==1.1.0 (the latest release) which would
install flake8==2.6.2 and so pycodestyle==2.0.0.
--
Jeremy Stanle
On 2018-05-16 17:42:09 + (+), Jeremy Stanley wrote:
[...]
> Unfortunately, I'm unable to find any follow-up summary on the
> mailing list from the aforementioned session, but recollection from
> those who were present (I had a schedule conflict at that time) was
> that
services.html
So a year has passed... where are we with this? Is it still
something we want to do (I think so, do others)? What are the next
steps so this doesn't come up again and again?
--
Jeremy Stanley
signature.asc
Description: PGP signature
_
a need to
overhaul some aspects of style in existing documents, so I can
understand it's not a choice to be made lightly. Still, we should
always consider embracing open process, and that includes using
guidelines which we can freely derive and republish as needed.
--
Jeremy Stanley
signature.as
e up from proposed source in one
job and then fire several other jobs which used that proposed image
well-predates similar requests from container-oriented projects.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
equent build steps.
I still don't see what it has to do with containers. We've known
these were potentially useful features long before
container-oriented projects came into the picture. We simply focused
on implementing other, even more generally-applicable features
first.
--
Jeremy Stanley
s
uot; artifact sizes.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://
n the
> change. We don't have that feature yet, but if we did, would you prefer
> to use that instead of the intermediate swift storage?
If the subsequent jobs depending on that one get nodes allocated
from the same provider, that could solve a lot of the potential
network performance risks as
may
introduce more issues than it solves.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstac
ul refers to that relationship as a job dependency:
https://zuul-ci.org/docs/zuul/user/config.html#attr-job.dependencies
To be clearer, you might refer to this as dependent job ordering or
a job dependency graph.
--
Jeremy Stanley
signature.asc
Description: PGP
d from execution.
[...]
Your choice of terminology is making it hard to follow this
proposal. You seem to mean something other than
https://zuul-ci.org/docs/zuul/user/config.html#pipeline when you use
the term "pipeline" (which gets confusing very quickly for anyone
familiar with Zu
On 2018-05-14 18:56:51 + (+), Jeremy Stanley wrote:
[...]
> Gödel's completeness theorem at work
[...]
More accurately, Gödel's first incompleteness theorem, I suppose. ;)
--
Jeremy Stanley
signature.asc
Description: PGP signat
testing complex enough to be a significant regression
magnet itself (Gödel's completeness theorem at work, I expect?).
That said, the idea of turning more of Nodepool's tasks into Zuul
jobs is an interesting one worthy of lengthy discussion sometime.
--
Jeremy Stanley
signature.asc
Desc
On 2018-05-14 09:57:17 -0600 (-0600), Wesley Hayutin wrote:
> On Mon, May 14, 2018 at 10:36 AM Jeremy Stanley <fu...@yuggoth.org> wrote:
[...]
> > Couldn't a significant burst of new packages cause the same
> > symptoms even without it being tied to a minor version increase
and 16.04.3.
Even if we somehow managed to pause our CentOS image updates
immediately prior to 7.5, jobs would still try to upgrade those
7.4-based images to the 7.5 packages in our mirror, right?
--
Jeremy Stanley
signature.asc
Description: PGP signature
___
ackages available for a given major
release series) then we should perhaps take a step back and
reevaluate this model. For now we have some fairly deep-driven
assumptions in that regard which are reflected in the Linux
distributions support policy of our project testing interface as
documented
xtra time to build and upload to
all our providers, as well as that much more storage on our builders
and in our Glance quotas.)
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mai
uld likely
reevaluate our support claims.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:un
with you all in another part of the world :)
> (who knows, maybe I’ll just tag along to PTG’s as a social outing…
> how cool am I?!)
[...]
Your sheer awesomeness has touched our community in countless ways;
I really hope you do continue to hang out with the rest of us at
every opportunity!
red a source of long-term support
documentation.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.
rganizations who employ them)
who have their own goals and set their own priorities.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: op
d tearing down the old infrastructure for it.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.open
ore about the
prior state of it than I though.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
tack_project/manifests/static.pp
as DNS appears to no longer be pointed there.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openst
ething along the lines of a README.rst
with a sentence or two about what happened, and removing the other
content from the repository. Basically it can just follow our
https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project
directions.
--
Jeremy Stanley
signature.asc
Description: P
ere the ballot has been sent.
[1]
https://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml?id=apr-2018-elections
[2] http://governance.openstack.org/election/#election-officials
--
Jeremy Stanley, Election Official
signature.asc
Description: PGP signat
ion we've struggled with for years: are we
testing against "Python X.Y" or are we testing against "Python as
provided by distro Z"? Depending on how you think about that, one
solution or the other is technically a more accurate reflection of
our choice here.
--
Jeremy Stanley
s
t release until tomorrow), and some teams have
started to use them for experimental or non-voting jobs:
http://codesearch.openstack.org/?q=ubuntu-bionic
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack
o 3.6 as the job default? I can see some value in each option.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@list
g for a seat on the TC in the future if you can
swing it.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.o
st expedient thing is to go ahead and make this part
> of the python 3 job transition.
We could provide an experimental job or some basic instructions in
an announcement and just schedule a flag day to start enforcing
everywhere.
--
Jeremy Stanley
signature.asc
Description
gather
neutron-lib is getting there, but I haven't heard about any work
toward that end in Horizon yet).
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage ques
ort of transition around release stable
branching to indicate what URLs should be used to correspond to
those branches. We've been doing basically that with release-time
edits to per-repo tox-install.sh scripts already, so maybe the same
workflow can be reused on test-requirements.txt a w
e requirements) and even
> possible to accelerate APIs.
[...]
How do you see this as being either similar to or different from the
https://git.openstack.org/cgit/openstack/oaktree/tree/README.rst
effort which is currently underway?
--
Jeremy Stanley
signature.asc
to noticing this
mistake (sorry!), and determined that restarting the poll and
issuing new ballots to everyone would be more disruptive for a
mostly aesthetic benefit.
--
Jeremy Stanley
signature.asc
Description: PGP signature
___
On 2018-04-24 09:59:57 -0400 (-0400), Zane Bitter wrote:
[...]
> the PTG has limited attendance from operators
[...]
I have high hopes that will not be the case for the next PTG.
--
Jeremy Stanley
signature.asc
Description: PGP signat
ir attention.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.o
101 - 200 of 1661 matches
Mail list logo
