d which drives the wedge between us and the greater Python
ecosystem ever deeper. They already get the impression we make up
our own self-serving solutions instead of helping out, so let's try
not to make that situation even worse if we can help it.
--
Jeremy Stanley
signature.asc
Description: Di
our only recourse for now is to further reduce log
retention to something like 2 weeks instead of 4 until we can get
this under control (if we were already on Zuul v3 we could fold in
draft documentation publishing and combine those volumes to buy us
some breathing room, but such is lif
t;midonet" account on PyPI
already took care of the networking-midonet cleanup, but I've
handled the others now.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (no
ou
know, dealing with API timeouts for LP is sort of un-fun so this
may be a foolish idea.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubs
ry time I needed someone to chair a meeting in my
absence. This doesn't seem like a common enough issue to warrant the
added complexity and red tape of access controls on our meeting
automation.
--
Jeremy Stanley
signature.asc
Descripti
x27;s not. Can we think about having one such
> restriction?
We don't implement technical solutions to social problems of this
nature. If you have an issue with the person who started the kolla
meeting in your absence, please take it up with them.
--
Jeremy Stanley
signature.asc
Descr
v3 has not officially reached
release yet, and the plan is to work on documentation for CI
operators upgrading from v2 to v3 after we've been able to
successfully use v3 ourselves upstream. The unfortunate lack of
documentation around migration is still expected at this stage.
--
Jeremy S
anywhere.
[...]
Good, you're still on the hook for anything you've broken that you
can't convince any of the rest of us to fix. ;)
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Devel
nyone (publicly or in private) at any time; I love
hearing from members of our community and attempting to find answers
for you.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Maili
e hope you'll
be as pleased with it as we are!
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@list
;re not relying on.
See https://launchpad.net/bugs/1563954 for the gory details.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: op
a https://review.openstack.org/510158 which has now
applied in Gerrit so please do try again and I'll try to be more
responsive in assisting with any further errors (but hopefully it'll
"just work" now).
--
Jeremy Stan
Google before it will (presumably) give me any
more detail, so that was the point where I stopped.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage
n changes and leaving
authoritative control over testing/merging to the "Jenkins" account.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not f
to reach out if you ever need anything whatsoever. See you
in Sydney to collect on those Australian beers! ;)
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for us
ything!
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
hat the Infra team
will not want to support integration with two task/defect trackers
indefinitely, and so at some point LP tie-ins to things like code
review and stats tracking are increasingly likely to simply be
removed rather than fixed if^H^Hwhen they break.
--
Jeremy Stanley
signatu
piece.
[...]
It should just be a matter of one of the 5 nova-release group
members (re?)adding your CI system's account at
https://review.openstack.org/#/admin/groups/nova-ci when they're
ready to do so.
--
Jeremy Stanley
signature.
come pretty close to the need Sean mentions for "solid network
security on the path between your guests and your nova-API."
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Ma
sults most of
the time but you can consider the v3 results merely an advisory
indicator of whether your v3 jobs are working correctly.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack
ghts. Thanks so much for everything! It was a pleasure to serve
alongside you.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubsc
nities.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
he pain of replacing unpopular cryptographic
primitives so you can avoid having this same discussion over and
over with people whose eyes glaze over as soon as you start to try
and tell them anything which disagrees with their paranoid
sensationalist media experts.
Oh, also, SHA-1 isn't much better i
/setuptools/issues/130
https://github.com/pypa/setuptools/issues/460
https://github.com/pypa/setuptools/issues/807
Also there's the problem that it's just a single bucket which could
be used to house example configuration files, shared datasets,
manpages or similar documen
lans, if they changed then we'd need to match them.
[...]
And to be clear, the main reason to only allow very minimal changes
in the last phase is because at that point you no longer have
working CI for the previous release and so cannot test that your
patches don't break the upgrade path
temporary." The ACL
only needs to allow merge commits to be pushed long enough for that
merge commit to get pushed for review, and then the ACL can be
reverted to its earlier state.
--
Jeremy Stanley
signature.asc
D
ser
frontends and also frees the Ironic team up from having to take on
yet more work directly.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Uns
eah, while it'll do in the short term it strikes me as more of a
workaround than a proper solution.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (
items may confuse the audience folks are trying to
> redirect here.
The original intent was not to publicize it until we had approved
three more items, but five seems like a somewhat arbitrary number to
me and baking it into the idea has resulted in us postponing
advertisement of good existing co
still trying to nail down the root cause.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?sub
ways to save what probably accounts for <1% of our overall
utilization. That's classic premature optimization. What's important
in this situation is the time wasted by reviewers having to respond
to or find ways to ignore these patches, so let's focus on that
rather than getting bogg
roperly declare their system-level dependencies any
longer. I don't know if anyone's concerned about that currently, but
it used to be the case that we'd regularly add/break the package
dependency declarations in DevStack because of running on images
where the things it expected
ould demographic profiling help us figure out the primary
motivation (whether it's testing the waters, stats padding or
employers pushing their staff to contribute patches before they've
had time to actually assimilate our community norms and
expectations)?
--
Jeremy Stanley
signatur
please double-check to make sure things are working the way
you expect once more.
> Sorry for this inconvenient.
My apologies for bounding forth and assuming I could tell which
account you were actually using!
--
Jeremy Stanley
signature.asc
Descrip
ovide useful information.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
ht
xperiences any complications
from this adjustment, have them E-mail the
openstack-in...@lists.openstack.org mailing list or find us in the
#openstack-infra channel on the Freenode IRC network. Thanks!
--
Jeremy Stanley
signature.a
e TC vision statement, though the earliest mention I
can locate is in John's post to this ML thread:
http://lists.openstack.org/pipermail/openstack-dev/2017-April/115319.html
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
On 2017-09-20 15:19:47 -0400 (-0400), Tony Breeds wrote:
> On Wed, Sep 20, 2017 at 06:59:50PM +0000, Jeremy Stanley wrote:
> > On 2017-09-20 14:46:32 -0400 (-0400), Tony Breeds wrote:
> > [...]
> > > I'd like to find a solution that doesn't need a tox_install.sh
straints file option agreeable to its maintainer so
that we don't have to override install-command to add it in all our
configs.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mai
adds an implicit dependency on git-review for every project doing
that, at least for developers who want to be able to make use of the
constraints URL fallback.
--
Jeremy Stanley
signature.asc
Description: Digital signature
___
plementation detail
could come back to bite us down the road.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-re
ances out the costs (not just in
resource consumption but also administrative overhead and community
impact... if DevStack gets custom images prepped to make its jobs
run faster, won't Triple-O, Kolla, et cetera want the same and where
do we draw that line?).
--
Jeremy Stanley
signature.
thod for when the constraints file is not already
provided locally. In the CI system, we directly provide constraints
files so that we can respect depends-on to requirements repo changes
and the like, so in practice this fallback is primarily for the
convenience of developers running to
during
the RC period for upcoming releases): specifically, publishing
branch series constraints files to the releases site. EOL'd projects
can refer to those at a static URL indefinitely rather than being at
the mercy of branch/tag changes in the Git repository.
--
Jeremy Stanley
signat
of the original as your seed
project (perhaps with history pruned to just the files you're
reusing via git filter-branch or similar). This way the complete
change history of the files in question is preserved for future
inspection.
--
Jeremy Stanley
signature.asc
Description: Digita
aching package mirrors we maintain nearby.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lis
On 2017-09-14 18:16:03 + (+), Jeremy Stanley wrote:
> On 2017-09-14 12:01:54 -0600 (-0600), Matt Riedemann wrote:
> [...]
> > I figured out the pattern when this happens to change the author.
> >
> > 1. git review -d
> > 2. git rebase -i master
> > 3.
gt;
> It's the merge conflict + git commit during the rebase that changes the
> author for me.
You ought to be able to completely skip #6 above. Continuing the
rebase (at least in the releases of Git I use) will amend the commit
correctly and give you the ability to adjust the commit me
On 2017-09-07 08:59:15 +0200 (+0200), Thierry Carrez wrote:
> Jeremy Stanley wrote:
> > On 2017-09-01 09:51:36 +0200 (+0200), Thierry Carrez wrote:
> > [...]
> >> Yes, for a first batch I propose we clean up the following:
> >>
> >> python-congress
Are we waiting for any confirmation on this, or does a week of
silence constitute tacit approval? Should I go ahead and delete
these from PyPI now?
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack D
a periodic pipeline job to find links as they become stale
might be a viable option though, as long as someone is going to pay
attention to failures for that.
--
Jeremy Stanley
__
OpenStack Development Mailing List
gine anyone wanting nova to
support it today over the far more flexible alternative hypervisors
available. This may also be worth mentioning on the operators ML,
but I would be surprised if anyone is still running it anywhere at
all.
--
Jeremy Stanley
signature.asc
Description: Digita
ecify the domain is more of a nuisance to be worked around than
anything.
You may also want to consider asking a similar question on the
operators ML, or perhaps sending them a pointer to this discussion
so you can get more real-world feedback.
--
Jeremy Stanley
signature.asc
Descri
e should
be added as an alias for the "shared-file-system" service (giving us
a redirect as I understand it) and then cleanup of various uses for
the old URL can happen at everyone's convenience?
--
Jeremy Stanle
rence URL in
openstack/service-types-authority needs adjusting to agree with the
service_type there. I'm guessing we'd prefer the latter for
consistency, but in that case we probably also need to add a
redirect and clean up as many of the references to the old URL as
possible.
--
to do the same (it just tends to vary by team
and origination timeframe). So, yes, probably easiest to give the
Infra team a list once it's been confirmed.
--
Jeremy Stanley
signature.asc
Description: Digital signature
_
t broke, it's increasingly likely
you'll break things for everyone else too and turn a few moments of
inconvenience for yourself into a week or more of pain for many
others.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
k
> deliverable and discovering all the bugs that it would trigger.
Agreed, we even still make it available from tarballs.openstack.org
in case someone doesn't want to have to try and rebuild it from the
tag.
--
Jeremy Stanley
signature.asc
Des
ing it up as a
silver bullet solution otherwise.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.or
atched into xenial-proposed for a
couple weeks already, awaiting confirmation from someone with the
ability to reproduce the issue. Please see
https://launchpad.net/bugs/1709032 if you can help close it out.
--
Jeremy Stanley
signature.asc
Description: Digital sig
o in a sense that is a form of servitude.
Basically, you're both correct depending on how you look at it. ;)
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usa
ough and as far as I'm aware reviewers
haven't previously rejected unofficial projects who want to receive
requirements updates. There are definitely projects who don't want
to (or for license reasons perhaps even can't) be official teams but
would still like their de
fixed version and you can try reenabling that test
again.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...
OpenStack's "Rocky" release cycle).
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openst
enial is not a good
platform to be running OpenStack on until they get the kernel
regression addressed.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for u
may also wish to consider removing Anne Gentle and Brant Knudson
> who are less available these days.
This makes sense, and I expect they're welcome back any time if they
wish to resume their involvement on it in the future.
--
Jeremy
infra/manual/developers.html#eligibility-to-vote-in-elections
[3] https://www.openstack.org/legal/technical-committee-member-policy/
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing
--pretty-print-code \
examples/slides.rst > reveal.html
.. _rst2html5: https://pypi.org/project/rst2html5-tools/
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (n
creased scrutiny at least in the form of
trying the jobs again in the check pipeline before going back to the
gate once more.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Maili
ntinue to rely on
zuul-cloner to place the constraints file where tox is expecting it
and so Depends-On would remain working the same way it does
presently.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
Open
On 2017-07-17 16:17:00 + (+), Jeremy Stanley wrote:
> If you want to run or vote in upcoming elections for PTL and TC,
> make sure your Foundation Individual Membership is active and has at
> least one Email address which matches an Email address in your
> Gerrit account: log
s / repos that don't use the release
> infrastructure.
[...]
Seems like a fine enough plan, but maybe the releases site is a
better place to publish these in that case?
--
Jeremy Stanley
signature.asc
Description: Digital signature
which can
> then correctly unpack the content for view.
>
> Lots of ways to shave down the capacity of the data-at-rest on the server.
Agreed, but realistically we're one or two orders of magnitude away
from needing to worry about that at the moment so should focus on
more pressing iss
ading the latest version is an issue.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubs
e base assumptions
about the test environment.
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/c
emove
> the installation guide anyway then maybe we can disable the bug link at
> the same time.
Could you have the buglink in the docs go to a centrally-managed,
pattern-based redirect per series and then change that redirect to
point them all to a page describing the EOL process later?
--
he current solution of
not publishing installation guides for EOL releases seems like a
good enough compromise there to me.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Developm
dards, but compared to the ~11TiB we host for
just two months of CI job logs it's a 1ml drop in a liter bucket.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not fo
are fixable by the teams that now own the
> documentation (the project teams).
We can look at including .htaccess files in the tree I guess? Or
some metadata the publish job uses to build them maybe?
--
Jeremy Stanley
signature.asc
Description: Digital signature
n release management, but for what it's
worth I'm eager to see him be able to take on more responsibility
there if he's willing. Seems like a great fit!
--
Jeremy Stanley
signature.asc
Description: Digital signature
_
aving any luck after double-checking the above
settings, please follow up and I'm happy to help you further.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not f
writer):
When you do things right, people won't be sure you've done
anything at all.
[Futurama season 3 episode 20, "Godfellas"]
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for
rmail/legal-discuss/2017-July/000477.html
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.
system for free
backends/drivers? Maintaining a third-party CI system for that seems
like overkill, but I'm unfamiliar with Cinder's particular driver
testing policies.
--
Jeremy Stanley
signature.asc
Desc
On 2017-07-25 22:13:59 + (+), Jeremy Stanley wrote:
[...]
> the reason why it's so hard to explain how to find your specific
> talk to be able to vote on it is because we (the community at
> large) wanted to stop people from doing that. Having "vote for my
> talk&quo
away
from the nomination period so start polishing your platforms; I
eagerly await the opportunity to read through them all as a regular
voter rather than a candidate for the first time in years!
--
Jeremy Stanley
signature
ternet gives others a very negative impression of our community.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-r
neral network
connectivity issues for that particular provider/region so we've
taken it out of service to avoid further impact:
https://review.openstack.org/485603
--
Jeremy Stanley
__
OpenStack Development Mai
ed
over the next few days.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
he real one is #puppet-openstack.
Yeah, and that one's reasonably active and being logged, so you/they
should be all set already?
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Ma
p logging it for now. Alternatively, even if we stop
logging it today, you can always submit a change to add logging back
later if people decide to start using that channel for discussions
again.
--
Jeremy Stanley
signature.asc
Description: Digital
tiple bots, but that will take some time
to implement and needs volunteers willing to work on it. In the
meantime we're running with the meetbot present in 120 channels and
have at least one new channel that desires logging and can't get it
until we whittle that number down.
--
Jeremy Stanl
k/gate-congress-dsvm-py35-api-mysql-ubuntu-xenial-nv/7ae2814/logs/reproduce.sh
Further, https://review.openstack.org/484158 seems to have changed
the behavior of the job since the log you posted from the 14th. Is
the result still the same in this case?
--
Jeremy Stanley
signature.asc
Description: Di
ntly stable for all projects involved. For pressure on our
quota, I don't think there's a good way to know what the impact will
be without going ahead and trying.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
helps, we believe the last patches needed to purge mysql.qcow2
assumptions from stable devstack branches merged yesterday and I
finally took the file back offline again roughly 16 hours ago. No
new complaints so far, at least!
--
Jerem
wizardry you haven't tried, they haven't chimed in to suggest
it either.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: opens
On 2017-07-17 18:24:39 -0500 (-0500), Matt Riedemann wrote:
> I don't have a strict recreate on this right now, but wanted to bring it up
> in case others have seen it.
[...]
Any chance you can find the author change in your git reflog?
--
Jer
.openstack.org/Documentation/config-contact.html
[6] https://gerrit-review.googlesource.com/c/70458
[7]
https://git.openstack.org/cgit/openstack-infra/openstackid-resources/tree/app/Models/Foundation/Main/Member.php?id=5b6011d
[8] https://review.openstack.org/483974
--
Jeremy Stanley
signature.asc
Descr
nging that in.
http://git.openstack.org/cgit/openstack/diskimage-builder/tree/diskimage_builder/elements/pip-and-virtualenv/
>
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mail
as a (very early) builder macro. Using constraints to
control these during image generation doesn't make a whole lot of
sense though as images are only rebuilt once a day and so tracking
these in the constraints list won't be self-testing in
301 - 400 of 1706 matches
Mail list logo
