perhaps you're suggesting that we should allow approved
changes to merge even with a workflow -2 from another reviewer
(keeping in mind that we don't currently allow changes with a
workflow -1 to merge).
--
Jeremy Stanley
___
OpenStack-dev mailing list
better than master from git.
[...]
Would getting it into EPEL for CentOS 7 or UCA for Ubuntu 14.04 LTS
hopefully be an option?
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman
is published.
Not sure that's supported in Gerrit though :)
As far as I know it's not... otherwise we'd have made WIP do the
same as you describe.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi
EPEL on the
other hand would be a much more viable long-term solution.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
mirroring solution is something new we have to monitor, maintain and
troubleshoot so we must ask ourselves whether the increased
management burden from that new complexity is balanced by potential
decreases in management burden found by improving stability in other
parts of the system.
--
Jeremy Stanley
for a handful of files. It's worth adding to
https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting
and discussing tomorrow, if you're around, so we can be sure to
get input from more of the Infra team.
--
Jeremy Stanley
___
OpenStack-dev
feature through deprecation or insist on continued
testing until its full removal can be realized.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
trying to trigger it by
leaving unnecessary review comments on lots of changes.
[1] https://launchpad.net/bug/1355480
[2] https://review.openstack.org/109565
[3] http://lists.openstack.org/pipermail/openstack-infra/2014-August/001681.html
--
Jeremy Stanley
when it was brought to your attention!
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
something similar when I need to get in touch with a project
about an infrastructure-related task instead would be equally
convenient.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman
supporting your drivers/features/whatever might.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
history) time we replaced the Gerrit SSH API RSA host key on
review.openstack.org was in April as a safety precaution in the wake
of the Heartbleed Bug announcement. We definitely haven't touched it
in the four months since then.
--
Jeremy Stanley
solutions to your
needs rather than embracing less convenient free and open options
which may still require improvement.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo
why we
have those additional pipelines and instead focus on resolving the
underlying issues which led to their use as a stop-gap.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin
to take their place once those are solved/worked around,
but at least the current state is not entirely due to the volume and
duration of jobs we run.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
into an official project. Pretty sure that
counts as one of the reasons we maintain that whole rig. ;)
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
will believe that there are unicorns!
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
to be using our mirror for YOUR systems. If you're not
running a PyPI mirror of your own, you should just use
pypi.python.org instead.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman
On 2014-08-17 23:53:12 -0700 (-0700), daya kamath wrote:
[...]
openstack-infra does not get updated as part of the gate jobs
[...]
Right, we use puppet to continuously apply that configuration to our
durable workers and nodepool templates.
--
Jeremy Stanley
name which is unique
per project).
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
powerful about the appointment.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
is encountering changes which really
can't be merged (rebased, cherry-picked, whatever) to the project
then they should refrain from commenting at all... at this point it
would be at best redundant, and at worst entirely incorrect.
--
Jeremy Stanley
___
OpenStack-dev
lucky).
That is gate debugging and, to support your point, is something
which can at best be only vaguely documented.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo
integration for Zuul... however it's also an
option not to be taken lightly and comes with its own set of unique
challenges.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo
On 2014-08-27 16:53:39 -0700 (-0700), Clark Boylan wrote:
[...]
I thought there was a wiki article on how they work but I can't
find it. Maybe someone else can link it here.
[...]
https://wiki.openstack.org/wiki/GerritJenkinsGit#Merge_Commits
--
Jeremy Stanley
to just keep those
pieces in their own separate Git repositories outside of the core
Neutron repository in perpetuity (even after they graduate from
incubation). One package per repository. That should be chiseled in
stone somewhere.
--
Jeremy Stanley
ideal world) it might
allow the reference L3 service plugin to be extracted from the main
tree and developed within a separate source code repository with its
own life cycle.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev
/GerritJenkinsGit#Merge_Commits if
you're interested in how it's implemented.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
for any existing pipelines).
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
,
ready to drop once the j-3 milestone has been tagged and is finally
behind us.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
about just automatically abandon any new change as soon
as it's published, and if the contributor really feels it's
important they'll unabandon it./snark
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
are a neat idea.
[...]
Well, you already had me with 80 columns, but I actually
[32;1mdo[0m think ANSI escape sequences are a neat idea.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin
it.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-raise this question on the
legal-disc...@lists.openstack.org mailing list as well.
[1] http://dev.hasenj.org/post/3272592502/ibm-and-its-minions
[2] https://github.com/jshint/jshint/issues/1234
[3] http://www.mail-archive.com/debian-legal%40lists.debian.org/msg40718.html
--
Jeremy Stanley
/jshint/jshint/blob/master/LICENSE
Ahem. https://github.com/jshint/jshint/blob/master/src/jshint.js#L19
You are thinking of JSLint, which is written by Douglas Crockford.
JSHint is a derivative project of JSLint. Sorry to burst your
bubble.
--
Jeremy Stanley
though.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
get all excited that 2.6 is going away entirely in a couple
months.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
before we noticed this unfortunate loss of date/time information.
This maintenance notification looks relevant...
http://lists.openstack.org/pipermail/openstack-dev/2012-December/003934.html
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev
',
[...]
Could not find any downloads that satisfy the requirement Paste
[...]
You have your environment misconfigured to use a mirror of PyPI
which is no longer maintained. Please use pypi.python.org or a
mirror you maintain for your own development work.
--
Jeremy Stanley
the first solution as it was
more directly under the control of the infrastructure and nova core
teams involved at that moment.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo
randomization in newer tox releases would seem to contradict your
assertion. Also documentation...
https://docs.python.org/2.7/using/cmdline.html#envvar-PYTHONHASHSEED
(New in version 2.6.8.)
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev
to pass -R to get that behavior) but you can
still totally override the hash seed from the environment in 2.x
(and more recent versions of tox happily do this for you and print
out the hash seed which was chosen for a given test run).
--
Jeremy Stanley
time to the next test run, but you can iterate fairly tightly after
that as long as you're not actively moving stuff around while you
troubleshoot (and coupled with a git hook like Doug described for
cleaning on topic branch changes would be a huge boon as well).
--
Jeremy Stanley
by a Git hook
which is installed in your local repository configuration the first
time you run 'git review' and then gets inserted into commit
messages for you on each subsequent commit message edit in that
repository). Please do not manually construct the Change-Id for a
commit.
--
Jeremy Stanley
of the OpenStack projects.
[...]
Sounds like an NP-complete problem, but if you manage to solve it
let me know and I'll turn it into the first line of triage for Infra
bugs. ;)
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
list of projects being moved is:
* stackforge/manila - openstack/manila
* stackforge/python-manilaclient - openstack/python-manilaclient
We'll follow up with a reply to this thread once the planned work is
complete.
--
Jeremy Stanley
signature.asc
Description: Digital signature
this, but alas, it is no more.
I think it was excellent at arbitrarily abandoning open changes
which happened to meet a poorly-thought-out set of criteria. I'm
personally quite glad it broke and we didn't waste time
reimplementing something similar for new Gerrit versions.
--
Jeremy Stanley
/37461 (so I don't think
it's entirely fair to assert that OpenStack doesn’t pin requests
because...extraordinarily stable).
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman
interested in maintaining that feature had explicitly removed it
instead... but then it sounds like you would assert that having the
machine abandon this feature for us was less likely to offend
anyone. ;)
--
Jeremy Stanley
___
OpenStack-dev mailing list
On 2014-09-16 21:42:49 + (+), Jeremy Stanley wrote:
The project infrastructure team will be taking the Gerrit service on
review.openstack.org offline briefly from 20:30 to 21:00 UTC this
Friday, September 19 in an effort to move the newly-approved Shared
File Systems program
, since the
stable server releases will continue needing to use them.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
).
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
contracts on facilities/hotels a year or more in advance.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
ways.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
to servers
which require unreleased client features.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
the
core group small (minimizing risk of premature disclosure). More
info at...
https://wiki.openstack.org/wiki/Vulnerability_Management
/end_public_service_announcement
--
Jeremy Stanley
signature.asc
Description: Digital signature
___
OpenStack-dev
-1point6 and
pitch in on reviews, patches or discussions related to this work if
it is important to you.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
to recheck against is 1263824.
Also, the fix is merged as of a few hours ago, so we shouldn't
expect any new recurrences.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman
if field you see on the Watched Projects setting
page.
https://review.openstack.org/#/settings/projects
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
into their
corporate security policies (so they'll need to be able to support
such schemes no matter how backward it might seem).
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman
in the search interface may
increase significantly (I've heard it gives you the ability to
bookmark various searches as custom dashboard views, but not sure
what other search improvements may be added there).
--
Jeremy Stanley
___
OpenStack-dev mailing list
or schedule for it at this point, but it is
definitely being worked on.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
autogenerated by PBR from the Git commit
log while others prefer to hand-curate their ChangeLog file instead.
The first project will want ChangeLog listed in .gitignore while the
second will want it to actually get checked into the repo.
--
Jeremy Stanley
this thread a little more visible to them.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-centric development culture with it. I can definitely see the
relationship though, and so concur it's a positive outcome (and not
merely a throwback to the beforetime).
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
is that anyone with earlier virtualenv installed will
need to upgrade to a version bundling pip 1.5 since pip before 1.5
the --allow-unverified option isn't recognized so pip exits nonzero
when tox tries to pass it in.
--
Jeremy Stanley
___
OpenStack-dev
been
invaluable.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
of the many ways a contributor avoids wasting reviewer
time by neither polluting their changes nor every project's
.gitignore with details potentially relevant only to their own
personal development system and nowhere else.
--
Jeremy Stanley
___
OpenStack-dev
changes for a library/client against
released versions of any other libraries or clients on which they
depend as well, for those same reasons.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org
).
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
(system-wide installs of old Jinja on CentOS 6 seems
like where nova ran into this).
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
what's wrong there soon so
we can actually start using UCA to get the bits we need for newer
PyPIfied MySQL-python to work for us).
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman
cetera)?
MD5 is still resistant to preimage and second preimage attacks as
far as I've seen, and SHA256 doesn't take too many orders of
magnitude more operations to calculate than MD5.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev
in any automated fashion but keep in mind that we've only
gotten the requirements update proposal job working reliably this
cycle, so it could still take some time for the various projects to
decide how to finish syncing up.
--
Jeremy Stanley
___
OpenStack
in reviewday and
elastic-recheck, et cetera), so we need to keep plugging the hole
with workarounds there in the meantime.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman
.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On 2014-01-09 14:16:09 +0400 (+0400), Sergey Lukjanov wrote:
we've finally updated our CI to use Zuul
[...]
Awesome! I can't wait to see your improvements.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
any policy which suggests a configuration that
alters the behavior of systems comment go unanswered.)
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
in the weekly meetings though, if anyone's seeking highlights).
Also, I know he and others have exciting plans/ideas for getting
things scaled to run even faster and more smoothly still.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev
not on pypi... also
it's largely abandoned).
This should (hopefully) now be solved as of my patch to pypi-mirror
yesterday. If it's not, please let me know.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
On 2014-01-16 14:20:15 +0100 (+0100), Thierry Carrez wrote:
#openstack-meeting-3 proposed at: https://review.openstack.org/67152
Will let you know if/when accepted and merged.
Accepted and merged... The bot has joined (and so have I).
--
Jeremy Stanley
else.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
that tarball at the same time
that it's being updated from a post-merge branch-tarball job, you
will end up with a truncated file and your job will fail. The larger
and more complex the tarball (for example nova's), the greater
chance you have to catch it at just the wrong moment.
--
Jeremy Stanley
changes in right away also helps you
pick up the workflow and toolset, but reviewing others changes is a
huge boon to both the project and the would-be contributors doing
the reviewing... much more so than correcting a handful of
typographical errors.
--
Jeremy Stanley
100% of the time, or...
...you get the idea.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
on just a handful of building nodes (I think that must have
been cleaned up since then), and nodepool couldn't ssh to the nodes
which did build (seems like Clint said the L3 agent wasn't running).
Anyway, seems running and mostly caught up now.
--
Jeremy Stanley
almost certainly be a low-hanging-fruit bug against
openstack-ci. The file in question is:
URL:
http://git.openstack.org/cgit/openstack-infra/jeepyb/tree/jeepyb/cmd/update_bug.py
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev
aren't yet packaged in mainstream Linux
distributions).
On the other hand, testing the latest of everything is what we do
now, mostly because that is pip's default (and at the end of the
day, its only reasonably reliable) behavior.
--
Jeremy Stanley
make sure we prioritize merging it ASAP to get client gating
unwedged and follow up to this thread with relevant updates.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo
On 2014-03-10 18:33:14 + (+), Jeremy Stanley wrote:
[...]
Monty originally proposed an improvement to the way we bootstrap
setuptools on our job workers which ought to help with this, so
I'll see whether it's in shape and still resolves the issue. If
so, I'll make sure we prioritize
some StackForge projects which have put
in requests for renames. Updates will be provided in the
#openstack-infra and #openstack-dev channels on the Freenode IRC
network. Once completed, I'll follow up to this mailing list thread
as well.
--
Jeremy Stanley
signature.asc
Description: Digital
On 2014-03-11 04:29:04 + (+), trinath.soman...@freescale.com wrote:
+1
Attending
Note that announcement was for yesterday. Nobody showed up with
questions so it ended very early.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack
will mention a failure to fetch the origin
remote for openstack/savanna if so).
A minor issue with some recent statusbot improvements left stale
topics in a lot of channels, but I have manually corrected them all
at this point and a fix is already in review for that.
--
Jeremy Stanley
On 2014-03-10 21:56:57 + (+), Jeremy Stanley wrote:
[...]
I've determined that (for reasons as of yet unknown) this is only
happening in one of our two providers, so I'm temporarily removing
the problem nodes while I continue to debug this. Hopefully that
un-breaks gating for clients
sprang up
shortly beforehand, I ended up making a course correction with
little time for proper planning. We can, and will, do better!
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin
fingerprints because they don't (yet) operate in circles where
keysigning is commonplace. There are much better methods for
high-volume KSPs (Clint links to my favorites in his message later
in the thread, so I won't) and we should use one of those this time.
--
Jeremy Stanley
who might be doing
those things instead...
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
for anyone who spends time mentoring new contributors, so that
we can be sure to keep it up to date and relevant.
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
a session for this purpose, but there's no expectation
it'll be approved (at which point we have even less time to consider
alternative solutions).
--
Jeremy Stanley
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi
1 - 100 of 1661 matches
Mail list logo
