e has any details about this, please give me a heads up so
we can try to correct the situation.
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.open
ead rather than
improving Cinder's existing solution so that people who have been
using that can benefit directly?
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: ope
z
sha256sum:
a84fd2b18f922be4b2aca7c89baf2153f9656ebe6791a9de37f56283f866645c
/srv/static/tarballs/ceilometer/ceilometer-2015.1.3-py2-none-any.whl
465f8605639b36bbb86c3198a58ef3282e54546bc587c436db34cb613e1f2404
/srv/static/tarballs/ceilometer/ceilometer-2015.1.3.tar.gz
--
Jeremy Stanley
signature.asc
Descript
drawbacks mostly come down to needing to apply some
additional scrutiny to the generated tarball before pronouncing it
viable, and the need to place trust in a manual process slightly
inconsistent with our usual sdist generation mechanism
On 2016-01-29 18:27:18 + (+), Jeremy Stanley wrote:
[...]
> Due to unfortunate timing, the last commit on stable/liberty was
> tested with pip 7 and merged, but the 2015.1.2 tag for that commit
> was pushed after pip 8 was released and so tox was no longer able
> to work wit
o leadership from stable branch
management, Telemetry and the community at large. Our infrastructure
exists to make things more consistent and convenient, but it's there
to serve us and so we shouldn't be slaves to it.
--
Jeremy Stanley
he tox.ini is also configured to add
(--download-cache), making the sdist unbuildable via tox at that
tagged point in the ceilometer repository.
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage ques
il/openstack-dev/2015-December/082902.html
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi
bug upstream:
https://github.com/eventlet/eventlet/issues/290
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lis
t is:
https://git.openstack.org/cgit/openstack/fuel-library/plain/deployment/Puppetfile
The copy on GitHub is only a best-effort mirror and may not always
reflect upstream reality.
--
Jeremy Stanley
__
OpenStack Development
nes we already
added (while riding in on magic rainbow-vomiting unicorns, perhaps).
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.opensta
ooks like it's going to ship with QEMU 2.5.
Alternatively, look into getting a live migration job running on
CentOS 7 or Fedora 23 if it can't wait until after Mitaka.
[1] http://lists.openstack.org/pipermail/openstack-dev/2016-January/084148.html
--
Jerem
ht assignment model) would need input from their legal
counsel, and possibly even a majority vote of the foundation
membership to actually enact.
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
On 2016-01-16 12:12:00 +0800 (+0800), Thomas Goirand wrote:
> On 01/15/2016 11:26 PM, Jeremy Stanley wrote:
> > On 2016-01-15 23:09:34 +0800 (+0800), Thomas Goirand wrote:
> >> On 01/15/2016 09:57 PM, Jeremy Stanley wrote:
> > [...]
> >>> res
icient experience in copyright law to know whether it's possible
at all under the current foundation bylaws and I doubt you know
either.
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsub
ackage maintainer easier. If there was
ever a good reason for copyright assignment in free software, that's
not it.
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-de
On 2016-01-15 23:09:34 +0800 (+0800), Thomas Goirand wrote:
> On 01/15/2016 09:57 PM, Jeremy Stanley wrote:
[...]
> > resulting in the summary at
> > https://wiki.openstack.org/wiki/LegalIssuesFAQ#Copyright_Headers for
> > those who choose to learn from history rather than re
resulting in the summary at
https://wiki.openstack.org/wiki/LegalIssuesFAQ#Copyright_Headers for
those who choose to learn from history rather than repeating it.
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage
ported crippling bugs in newer versions of system
dependencies which have caused us to scurry to roll that back. While
it may be time to try our luck again and hope we fare better, we're
also only a few months from the next Ubuntu LTS (and as also
mentioned CentOS 7 is available for use right now).
--
ack.org/resolutions/20150615-stackforge-retirement.html
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists
TS distro releases to run production systems. We've also got a
modest sized OpenStack deployment on its way to production, again on
an LTS distro release. I agree that releasing server software which
is only well tested on "desktop" pace distro releases would be a
serious misstep for the
sid
nodepool image shows up we could certainly try running Py3K jobs on
that instead.
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.
ents repo (our generic unit
test job-templates very specifically assume the change proposed is
to the repo under which tox is invoked and what's needed is
something more like an integration test job).
--
Jeremy Stanley
__
OpenSta
robably
destroy any system on which it runs.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@list
by the TC, however don't confuse that with the "TC Approved
Release" which is something else:
https://governance.openstack.org/reference/tags/tc-approved-release.html
--
Jeremy Stanley
__
OpenStack Development Mailing
requirement of the Docs team, since
they were having trouble triaging auto-generated bugs they were
receiving and wanted to enforce the inclusion of some expository
metadata.
--
Jeremy Stanley
__
OpenStack Development
complaining about how nobody has time to build an ideal environment
for him before he can even get started.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage q
sis.
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
e systems we support are working as designed,
and you should still be able to use them for your existing project
without having to abandon it and create a new one under a different
name.
--
Jeremy Stanley
signature.asc
Description: Digit
rlier state), I'm even less thrilled with the idea that
people might just slash-and-burn repos, abandoning them and creating
new ones because they've put them in an unusable state.
--
Jeremy Stanley
__
OpenStack Development Mailing Li
blueprint/spec?).
I'm not a core reviewer for DIB, but for a small modification I
doubt they expect you to create a Launchpad blueprint or an
associated specification. I would just start by pushing the proposed
addition into Gerrit and see what else they reque
ling
lack a swap memory device. I have a feeling if you swapoff before
this point in the job you'll see it fail everywhere.
For consistency, we probably should make sure that our workers have
similarly sized swap devices (using a swapfile on the rootfs if
necessary).
--
Jerem
t/openstack-org/+filebug and someone should
get back to you after fixing the problem.
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?sub
st, but I observed the unwanted behavior using Iceweasel 38.1.0
(basically un/rebranded FF 38.0).
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.open
e it's own kill ring (copy/paste), but I can also
use tmux's copy and paste features as well. Less time touching the
mouse means more efficient reviewing for me!
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for
thinking it's sane to delete their latest releases of
some dependencies from PyPI) but it's a long road to full
implementation.
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
nstack-manuals
maintainers. Thanks for spotting this and brining it up!
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
The
constraints-based solution is certainly a cross-project priority
effort, but the developers who are in the process of implementing it
are wary of rushing it into place and causing new problems.
Sometimes the devil you know is easier to deal with than the one you
don'
all either have "constraints" or
"dsvm" in their job names).
I'll let Robert and Sachi, who have been spearheading this effort up
to this point, comment on whether additional assistance is needed
and where they see next steps lead
a
team know as soon as possible and we can roll back to pre-2.3.x
images again.
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsub
o accomplish it (as we discovered
back when we used to run DevStack smoke tests to validate our images
and frequently rejected perfectly good images due to
nondeterministic errors in the tests).
--
Jeremy Stanley
__
OpenStack
er-constraints is merely used to constrain
requirements lists.
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http:/
On 2015-12-12 16:51:09 + (+), Jeremy Stanley wrote:
[...]
> No, it won't, since upper-constraints is merely used to constrain
> requirements lists.
I take that back, the pip_install function in DevStack applies
upper-constraints.txt on anything it installs, but regardless it's
misl
nt should run on nodes with an earlier
(working) tox version.
If anyone sees any further use of tox 2.3.0 after the time of this
E-mail, please let us know.
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage
v, so if tox is not a
direct or transitive requirement then it will end up dropped from
upper-constraints.txt on the next automated proposal in review.
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
a/tree/doc/source/_exts/vmt.py
which does very similar things.
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
locally installed distro
packages of fonts and similar resources might get complicated, and
so may still be easier left as distro-specific patches in their
respective packaging).
--
Jeremy Stanley
__
OpenStack Develo
.2.0?) so that
other projects jobs will actually pick it up.
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.open
File "cinder/common/config.py", line 32, in
from oslo_utils import netutils
File
"/home/jenkins/workspace/gate-cinder-python27/.tox/py27/local/lib/python2.7/site-packages/oslo_utils/netutils.py",
line 25, in
i
On 2015-12-07 23:03:56 + (+), Jeremy Stanley wrote:
[...]
> from oslo_utils import netutils
[...]
FWIW, here's a query for repos following the above pattern:
http://codesearch.openstack.org/?q=import%20netutils
Any of those not carrying either netifaces or oslo.ut
And there's a bug open at https://launchpad.net/bugs/1523706 for
this issue as well.
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
OpenStack team instead (per
Emilien's original suggestion).
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.op
rathon?
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
try "just" installing
(and running) Juno DevStack. We have enough trouble doing that in
our CI system right now.
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
ng upgrade testing *to* every
supported stable branch, since there will always be a starting point
we test upgrading *from* without being able to continue supporting
the version which came before it.
--
Jeremy Stanley
__
OpenStack D
(that discussion
concluded more than a year ago), it's time for discussing what we
can implement in Mitaka so we have more reasonable options for
keeping the stable/mitaka branch healthy a year from now.
--
Jeremy Stanley
signature.asc
Description: Digital signature
___
important" security advisories, as it would be a waste of all our
time and we already have plenty of other things to do. ;)
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questio
me at
any time they see fit.
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/m
lly
identical contents, were not generated at the same time nor by the
same event so it's perfectly reasonable that the former would be
versioned as a dev commit working toward the release tag of the
latter.
--
Jeremy Stanley
___
ully our member companies are
figuring this dynamic out for themselves. ;)
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:u
for once... ;)
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/
I find it's preferable to review code without thinking about who
wrote it, though admittedly that's sometimes easier said than done.
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscr
to pick another :)
Thanks--I (perhaps incorrectly?) assumed that only those they
maintain in the chat.freenode.net DNS round-robin are considered
active.
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questio
f hour since. That's not to say I
have much faith at the moment it'll stick around, but it's at least
an improvement.
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-
s are not, so there is no way in the
reviewers box of the Web UI right now to distinguish someone who
commented without voting (a.k.a. a 0 vote) on the current patchset
from someone who only voted on previous patchsets.
--
Jeremy Stanley
__
roved instance turnaround for us.
There may also have been other reasons for recommending rebuild to
us, but if so I don't recall what they were.
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage question
ter the 2014.2.4 release on November 19. If projects want
to restore Python 2.6 testing, they'll need some custom job to
install the desired interpreter from somewhere unofficial (e.g. the
deadsnakes PPA for Ubuntu Trusty) at runtime.
--
Jeremy Stanley
_
ave configuration which enforces more than one +2, it's
just custom/convention between reviewers).
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.
already showed on
> https://review.openstack.org/#/settings/.
[...]
OpenStackId and Gerrit are unrelated systems. Have you tried
changing your primary E-mail address on your OpenStack Foundation
member profile at https://www.openstack.org/profile/
SSH banner starting
with a string like "SSH-2.0-GerritCodeReview_2.8.4-19-g4548330
(SSHD-CORE-0.9.0.201311081)" or something else?
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Devel
ime and starts a
list of jobs associated with that pipeline for any projects. This is
why the working periodic jobs have different names than their gerrit
triggered pipeline equivalents... they need to hard-code a branch
(usually as a JJB parameter).
--
Jeremy Stanley
signature.asc
Descripti
ity, we can
revisit the LTS discussion once you finish that).
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
h
in fact have some confirmation from their
developer community--at least in the form of code comments--of only
being reliable/supported in conjunction with a non-free JDK. Thanks
be to Joshua for setting me straight in #openstack-infra on that
matter! ;)
might be).
3. The core review team for this is the core review team for all our
infrastructure systems, and we're all unfortunately very behind in
handling the current review volume.
--
Jeremy Stanley
__
OpenStack
Also if change 237936 gets corrected in the next 18 hours or so, we
may rename:
openstack/networking-bagpipe-l2 -> openstack/networking-bagpipe
As always, feel free to follow up to this message or pop into
#openstack-infra on Freenode if you have any questions/concerns.
--
Jeremy Stanl
the individual projects/jobs to
define the packages they'll need to be able to run. I'll save the
lengthy list of whys, it's been in progress for a while and we're
finally close to making it a reality.
--
Jeremy Stanley
_
y do need to install the services from source
during the job, not in advance. Otherwise you would be unable to
have your project's change declare a cross-repository dependency
(depends-on) to a pending change in another one of those projects.
--
Jerem
here the requirements change and
the diskimages haven't been rebuilt or in jobs testing proposed
changes which explicitly alter these requirements, but could be
augmented by similar mechanisms in devstack itself to avoid building
them more than onc
rinted on
business cards and always carry plenty with me when I travel for
conferences.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
it.sched.org/event/c4170a605301dbf9bfa19b9e6a651a87
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.o
oject, my recommendation is:
neither. Link them to your published documentation (and make sure it
includes information on where to browse and clone your source
code!).
--
Jeremy Stanley
__
OpenStack Development Mailing List (not
elf-owned but is rather under the care of the stable-maint-core
group. https://review.openstack.org/#/admin/groups/1099,info
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ..
nted. Defining the option is easy,
> but that's a lot of project patches.
[...]
However, it does make it possible for projects to use this feature
in oslosphinx even if they're not using our hosting infrastructure.
Again, probably a corner case so not a necessary usage for us to
support I guess.
ject-config)
where we can set any new environment variable oslosphinx cares about
to that value quite trivially. The envvar name should ultimately
just be something which makes sense for oslosphinx outside of the CI
system as well.
a clone URL? If it's
supposed to be browseable, then querying git remote is a bad idea
regardless.
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstac
r than the present situation and will get these links
working correctly on docs.openstack.org for now.
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-de
On 2015-10-16 15:46:33 + (+), Jeremy Stanley wrote:
[...]
> a somewhat more thorough regex like '/([^/]+/[^/]$)(\.git|)$'
[...]
Heh, mailer regex obviously. ;)
I meant '/([^/]+/[^/]+)(\.git|)$' of course (and then take
search().group(1) if it succeeds).
--
Jeremy Stan
On 2015-10-16 15:46:33 + (+), Jeremy Stanley wrote:
[...]
> Depending on how the job is constructed in our CI, the origin may
> be reset to a proxied URL which isn't formed in the expected
> fashion. In this case you can see it happen in a recent job
> log[*], d
popular of
the three: Masterless Puppet. I have confidence you'll let me know
if this is insane, and in that case provide alternative suggestions!
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack
d be able make that possible?
[...]
The Infrastructure team is in the process of standing up a
community-managed deployment of OpenStack, but it's not even within
an order of magnitude of being 1k host scale (and at that, it's
still a multi-cycle plan just to reach viability).
--
Jerem
xtra hardware,
people and time to implement and manage.
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists
some
economy of scale (where the OpenStack Foundation does not).
> Anyway, perhaps this is for another conversation...
Indeed, and one better had with the OpenStack Foundation Board of
Directors rather than the developer community/Infra
un third party CI on a single node"
[...]
For those who haven't been following the puppet-openstackci effort,
note that https://review.openstack.org/200330 added turn-key support
for third-party CI on one machine with Zuul/Nodepool/JJB/Jenki
ry
version ever released for packages like python-requests and
python-urllib3, apt-get will begin to exhibit similar dependency
resolution challenges).
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for
ast supported them or perhaps fall back on the
versions provided by their distro's package manager.
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@l
gt; > Looks pretty complete to me.
>
> The official list is
> http://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml
They're both official. The former is automatically rendered and
published from the latter at
changes submitted (often
more), and for some of those I might miss failures or negative
review comments for a month or so at a time depending on what else I
have going on. It's very easy to lose track of a change if someone
abandons it for me.
y far.
We're committed to providing test results for all patchsets when
possible; that doesn't mean you are required to pay attention to the
results or even wait for them to be posted on your change while it's
still in a state of initial fl
is still under debate, feel free to simply ignore
test results until you get it to a point where you see them start to
become relevant.
--
Jeremy Stanley
__
OpenStack Development Mailing List (not for usage questions)
Un
e the
number of individual IRC bots we're managing. Ultimately I'm
interested in seeing us collapse our current family (gerritbot,
statusbot, meetbot) into one codebase/framework to further reduce
the maintenance burden, but haven't found interested parties yet to
contribute the coding effort.
--
Je
901 - 1000 of 1661 matches
Mail list logo
