ded up
readding around 15% (the ones which looked like they generated
errors according to the WebUI feedback). If you receive a second
ballot E-mail, you can discard it. They're just duplicates with the
same unique URL in them, so not good for a second vote. ;)
--
Jeremy Stanley
signature.asc
Descr
sion to help us move
> towards bringing that vision to reality.
So (straw man!) we can make Rocky "the constellations cycle"?
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing
in the
meantime and carefully manage the transition so that we increase
ease of contribution for them ahead of that curve rather than once
it's too late.
--
Jeremy Stanley
signature.asc
Description: PGP signature
ware,
is aggregate links to these somewhere and promote that in ways that
the intended audience will find them.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usag
ng a hollow sort
of "me too" reply. I have added this as one of my suggested bullet
points for proposed forum discussion
http://forumtopics.openstack.org/cfp/details/122 as well.
--
Jeremy Stanley
signature.asc
ung over the wall" to the community they tend to flounder in
their attempts to gain traction as properly open projects in their
own right. I don't think we do a good enough job at highlighting
this risk (yet), and will remember to point it out more often when I
spot it in the future. Than
put on some feature
they needed for their new product launch, that's rather self-serving
and doesn't really help us much.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (no
tox-py35 job (Ran: 176
tests in 8.8742 sec.) if you feel like approving.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-r
can be dropped from them entirely.
There is some discussion in https://review.openstack.org/561593 but
a centralized temporary workaround is somewhat risky since the
people in charge of reviewing any eventual revert will have a hard
time knowing when it's finally safe to do so.
--
Jeremy Stanley
sting Python 3 support for
their changes, not even in a non-voting capacity.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openst
rg/cgit/openstack/api-site/tree/www/index.html
Happy hacking!
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ..
to clean up this change and make it
> mergeable.
Ideally, someone convinces the libguestfs authors of the benefits of
putting sdist/wheel builds of their python module on PyPI like
(eventually) happened with libvirt.
--
Jeremy Stanley
signature.asc
Description
PI guarantee rather than treating the API as "whatever
kolla-ansible does" significantly increases the chances of other
projects being able to rely on kolla's images in the long term.
--
Jeremy Stanley
signature.asc
Description: PGP signature
_
er images
for use by arbitrary deployment solutions, along with an example
deployment solution for use with them" (kolla-ansible on equal
footing with competing systems that make use of the same images)?
--
Jeremy Stanley
signa
for addressing that, but we don't
know how much more widespread the problem might end up being so
encourage everyone to try it out now where they can.
[1] https://mail.python.org/pipermail/distutils-sig/2018-March/032104.html
[2] https://github.com/pypa/pip/issues/4805
--
Jeremy Stanley
signature.asc
ide production-ready containers and deployment tools for
operating OpenStack clouds" could use some adjustment to drop the
production-ready containers aspect for further clarity. Do you
agree?
--
Jeremy Stanley
signature.asc
D
ile and
then handle it browser-side, so I expect we'll be able to switch
back to collecting it for all job runs again fairly soon.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing L
lly clients/libraries/utilities--since a
lot of my (workstation and portable) systems are running it. If
someone is interested in and has time to work on this, I'm happy to
provide guidance and review their changes.
--
Jeremy Stanley
signature.asc
Description: PGP signat
milar
date-based versions we need to clean up and I'm happy to take care
of it.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstac
available from https://tarballs.openstack.org/ if
anyone _does_ need a copy.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack
to land a small patch to trigger a rebuild, but the patch
> switching them from oslosphinx to openstackdocstheme would serve
> for that and a small change to the readme or another file would do it
> for any that are already using the theme.
Seems like a reasonable incentive for some nee
s a possible alternative means of injection as well.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.o
in
Apache but that also seems like a bit of a kluge.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.open
ets if you don't want
listeners on the loopback interface).
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ..
se since the task did not
require any changes merged to your source code.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-re
org/pipermail/openstack-dev/2018-February/127103.html
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.
syncs or amend them to undo the lower-bounds
changes before merging). At any rate, I suppose that's a separate
conversation to be had, and as you say it's just a place to start
from but projects will be able to change it to wh
n-depth
description, but it's targeted at all who have a vested interest in
design and planning for the future of OpenStack
(devsopsusersadminseveryone).
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Devel
know that I will resign from
> the core reviewers group immediately if I feel that I cannot meet
> the obligations of the role.
[...]
Remember: it's only a non-OpenStack job until you can convince your
employer it should be OpenStack-related! ;)
--
Jeremy Stanley
signature.asc
Descript
facial expression. It's harder for someone on the other end
of a phone or computer to successfully interject during a heated
conversation, and also conversely harder for the in-person
participants to interject when a remote speaker is saying something.
--
Jeremy Stanley
signature.
n the past, but it's not so
simple as you would seem to imply no matter how good the technology.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage question
elease channel.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
-15T15:12:44
--
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
er get presented
with a captcha challenge when making page edits now that you're
verified.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
any of us can be found.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubsc
derway to switch that CI system to Zuul
v3 (perhaps after 3.0.0 officially releases soon).
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: ope
norance of our reasons for these choices.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:un
atives. The `source` command is not
implemented by a number of other popular shells however, which may
make it a poor interoperability choice (given csh is an arguably
less popular shell these days) unless we assume a specific shell
(e.g., bash).
--
Jeremy Stanley
signature.asc
Description: PGP sig
eas of the community I would otherwise
have missed. Please keep it up!
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-r
it's
not really the OpenStackID database, OpenStackID is just one
component there). A user can choose to enter any E-mail address they
like in Gerrit, and we can only advise them to configure their
foundation member profile so that it includes that address.
--
Jeremy Stanley
signature.asc
D
ldn't be any more of a problem than it is for code
contributors (where at least one of the addresses for their Gerrit
account needs to appear in at least one of the E-mail address fields
for their member profile).
--
Jeremy Stanley
signature.asc
Description: P
nitial member in both of them.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
at same boat
as far as I'm aware. In both cases the projects have basically been
dead for half a decade (and in the magnum case they never even seem
to have uploaded an initial package at all).
--
Jeremy Stanley
signature.asc
Description: P
ing his time on more
interesting endeavors instead. He will be missed.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openst
we should hopefully at least have
logs detailing the problem though if all goes well you'll have
properly updated documentation there instead.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Developmen
eading me to suspect
that either the GH repo is non-canonical or its Python packaging
files are maintained independent of revision control.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mai
ific versions of jobs for neutron and horizon plugins.
Nice! I somehow missed that merging a couple of weeks back. In that
case, I suppose we could in theory do one final transitional package
upload of DOA depending on the conflicting Horizon release if others
think that's a good idea.
--
Jeremy St
else different in the
new model.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:u
amenting that it's not something we can take advantage of for the
current DOA/Horizon transition.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
e in mistakes made by) already overburdened reviewers.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstac
to stop
providing any module itself and depend on the new version of Horizon
which provides that module instead. I suppose without Horizon on
PyPI, documentation of the issue is the most we can do for this
situation.
--
Jeremy Stanley
signature.as
ot
> logs).
Sounds fine to me, I didn't have anything new to bring up (also,
I'll be indisposed/travelling next week and unable to attend then as
well, just FYI, though other members of the VMT will likely be
around some if we need to be reached on an urgent matter).
--
Jeremy Stanley
signature.asc
On 2018-01-16 16:29:32 + (+), Jeremy Stanley wrote:
[...]
> Thankfully, SB was designed from the very beginning in an API-first
> manner with the WebUI merely one possible API client (there are also
> other clients like the boartty console client and a .
[...]
Oops, to complete m
d a . In theory
pretty much anything you can do through the WebUI can also be done
through the API, as opposed to LP where the API is sort of
bolted-on.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenSta
intenance so my ideas may be
terrible, but have you considered just making it possible to set a
version pattern option in setup.cfg so that this sort of filtering
is more easily generalized?
--
Jeremy Stanley
signature.asc
Descr
that logging in and going to
https://storyboard.openstack.org/#!/profile/tokens will allow you to
issue one (with up to a 10-year expiration based on my modest
experimentation). I believe this to be the same solution we're using
to grant teh storyboard-its Gerrit plugin to update tasks/stories
from review
re
missing pip. When that was caught they were rolled back to the
previous working images so this should now succeed if rerun. I'll
catch up with you in #openstack-release about reenqueuing the tag
for it.
--
Jeremy Stanley
sign
patch sets is that the old Jenkins -1 still
took precedence in the change list view even if there were more
recent +1 votes from Zuul v3. Now that these have been cleaned up,
that behavior should hopefully no longer be present.
--
Jeremy Stanley
signature.asc
Description: Digital
from Queens, Pike, or Ocata.
[...]
Sounds fairly similar to the conclusion the fast-forward upgrades
discussions arrived at. I don't think there are any major objections
to this plan, people just need to work on an implementation.
--
Jeremy Stanley
signature.asc
Description: Digit
velopment on a team.
I personally prefer the first definition. Operators are often also
developers and vice versa. It's not one side against the other, but
to me the PTG is mostly about doing software development so
attendees should come prepared to roll up their sleeves and do that.
--
Jeremy
o have a straw man release schedule for a
year-long Rocky so we can see what that might look like.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage que
k/gate pipelines at that point.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
rom others in the community on getting
solutions for these sorts of migration blockers implemented; so
please anyone interested in helping pop into #storyboard and there
are usually people around even if it seems relatively quiet. ;)
--
Jeremy Stanley
signature.asc
Description: Digital signat
solution would be support for
custom reporting URLs which can feed arbitrary values into the
creation form.
[*]
http://eavesdrop.openstack.org/meetings/storyboard/2017/storyboard.2017-12-06-19.05.log.html#l-36
--
Jeremy Stanley
signature.asc
Descr
ely just get refaced with some sort of neutral
branding in places where distinct brand identity is less important.
Preliminary plan for the "hard bits" is up for review at
https://review.openstack.org/524024 and likely to be approved next
week unless major objections are raised in the meanti
r own rather than being told what to do/use.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.o
haking a cane at the kids on his lawn
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
he reason apps.openstack.org and the
app-catalog project were discontinued was in an effort to avoid
confusion/competition with other more full-featured and established
application catalogs. Is there somewhere we (or someone) should
start publishing built images for Murano Agent?
--
Jeremy Stanley
sign
eges
(e.g., adjusting packet filtering) are really only a fix on the CI
side and won't be replicated for local runs by developers.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mai
nue allowing stateful ingress
from our control plane and whatever else gets access to the job
nodes now.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
ole which restricts
egress access to only allow reaching the mirror server for the
provider where that job is running, we could try adding it to some
copies of unit test jobs in a few projects to see what happens.
--
Jeremy Stanley
signature.asc
Description: Digital
nversation with
the community becomes a little easier.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.open
ne an issue is out of scope for an advisory, and I don't see
that process would need to change.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
velopment environments, I don't think we can completely get rid of
the associated pip wrapper scripts in those various projects (but we
can at least find a way to stop running them in the CI system in the
meantime).
--
Jeremy Stanley
signature.asc
Description: Digital
der those security hardening patches
and not vulnerability fixes. If Horizon or any other consuming
application fails to properly sanitize data before performing
potentially unsafe actions with it, that's a vulnerability and would
generally warrant an official security advisory.
--
Jeremy Stanl
asures in the software
which should actually be taking on that responsibility.
Of course, I'm just one voice. Others on the VMT certainly might
disagree with my opinion on this.
--
Jeremy Stanley
signature.asc
Description: Digital sig
ling the security of their Web
frontend to their APIs. OpenStack can't easily make the same sorts
of assumptions.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not fo
e sorts of docs linters other
projects rely on.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@list
a database validation tool now? If we do,
is it deficient in some way? If we don't, what specifically should
it be checking? Seems like something we would also want to run at
the end of all our upgrade tests too.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
o support different
versions of Puppet than the Puppet OpenStack deliverables last time
I checked.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Un
On 2017-11-05 16:18:23 +0800 (+0800), Margin Hu wrote:
[...]
> is storage.apps.openstack.org working now ?
Explained at
http://lists.openstack.org/pipermail/openstack-operators/2017-July/013965.html
but yes, it's been offline for months at this point.
--
Jeremy Stanley
signature.
g IP address.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsu
rely legitimate for these
discussions to continue into the voting week as some voters may wait
until toward the end of the period to make up their minds on how to
rank various candidates (I know I did, at least).
--
Jeremy Stanley
signature.asc
Description: Di
y
since the structured data output by the validation script includes
all contributors and merely flags the "member" contributors eligible
to vote by including their discovered OpenStack Foundation
Individual Member Id numbers.
--
Jeremy Stanley
signature.as
On 2017-10-24 16:24:39 -0700 (-0700), Armando M. wrote:
[...]
> I hope I represented the conversation correctly!
[...]
Totally accurate, thanks!
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenSt
unit testing still
continue to need neutron?
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.o
2678231
[2] http://git.openstack.org/cgit/openstack/governance/commit/?id=2c0cdd2
[3] http://git.openstack.org/cgit/openstack/governance/commit/?id=df438a7
[4]
http://git.openstack.org/cgit/openstack-infra/zuul-jobs/tree/roles/tox-siblings
--
Jeremy Sta
orthwhile
behavior change, since there may be good reasons it was designed to
work this way from the outset. I'll bring this thread to Jim's
attention once he's around today; he will doubtless have more
accurate details and concrete suggestions than I.
--
Jeremy Stanley
signature.asc
Description
e
about ways to improve similar cases in the future. However, I also
understand that no matter how widely and carefully changes are
communicated, there's only so much anyone can do to avoid surprising
the subset of users who simply don't pay attention.
--
Jeremy Stanley
signature.asc
Descript
no cloud-init), but on
Red Hat derivatives there are a lot of deep operating system
internals built on top of packaged Python libraries which simply
can't be uninstalled cleanly nor safely.
--
Jeremy Stanley
signature.asc
g else entirely?
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
ate
the existing deprecation tag (or come up with an additional one) to
covers this additional policy?
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questi
gesting
that policy was not followed, or that it's merely insufficient?
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@
https://etherpad.openstack.org/p/zuulv3-migration-faq
Thanks for your patience throughout this process, and hopefully
you'll agree the new features were worth the wait!
--
Jeremy Stanley
signature.asc
Description: Digital signature
.openstack.org/p/zuulv3-issues
We're assembling a sort of FAQ in the migration guide
here:
https://docs.openstack.org/infra/manual/zuulv3.html
...and we also have some more content in progress at:
https://etherpad.openstack.org/p/zuulv3-migration-faq
Here's to the week ahead!
--
...]
Yes, now that we have the situation with the logs site under
control, we're working on getting v3 running check jobs for all
projects again in an advisory fashion (hopefully within the next few
hours).
--
Jeremy Stanley
signature.asc
Des
happy to reenqueue the release pipeline refs for
the affected tags as long as someone has a list and I can knock them
out in a single batch.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Devel
d to know for
better pruning down the docs and mirroring volumes in AFS.
--
Jeremy Stanley
signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstac
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
Descripti
nly 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 life).
--
Je
201 - 300 of 1661 matches
Mail list logo
