://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss
[1]
http://lists.openstack.org/pipermail/openstack-dev/2018-September/134911.html
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development
o them
over the next week.
[0] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss
[1]
http://lists.openstack.org/pipermail/openstack-dev/2018-September/134911.html
--
Jeremy Stanley
signature.asc
Description
case either might be resulting in
subscribers missing it.
[0] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss
[1]
http://lists.openstack.org/pipermail/openstack-dev/2018-September/134911.html
--
Jeremy Stanley
signature.asc
Description: PGP sign
opics
Which is its initial location for crowd-sourcing/brainstorming, but
will get published to a more durable location like on
lists.openstack.org itself or perhaps the Project-Team Guide once
the list is in use.
--
Jeremy Stan
are closed
down for good).
[0] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss
[1]
http://lists.openstack.org/pipermail/openstack-dev/2018-September/134911.html
--
Jeremy Stanley
signature.asc
Description: PGP
f you're not careful to keep your branches clean.)
[*]
https://git.openstack.org/cgit/openstack-infra/project-config/tree/gerrit/acls/openstack/neutron.config
[**] https://review.openstack.org/#/admin/groups/neutron-release
--
Jeremy Stanley
signature.asc
Description: PGP signature
_
hour has elapsed from the #startmeeting. After an hour, anyone can
so I did an #endmeeting in your channel and it wrapped up and wrote
the minutes and logs as usual:
http://eavesdrop.openstack.org/meetings/openstack_cyborg/2018/openstack_cyborg.2018-11-07-14.16.html
--
Jeremy Stanley
signature.asc
aving to manage a test platform transition on a
stable branch.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-de
lability of venues and other logistics.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsub
On 2018-11-01 09:27:03 -0400 (-0400), Doug Hellmann wrote:
> Jeremy Stanley writes:
>
> > On 2018-11-01 08:52:05 -0400 (-0400), Doug Hellmann wrote:
> > [...]
> >> Did I miss any options or issues with this approach?
> >
> > https://review.openstack.or
On 2018-11-01 08:52:05 -0400 (-0400), Doug Hellmann wrote:
[...]
> Did I miss any options or issues with this approach?
https://review.openstack.org/578557
--
Jeremy Stanley
signature.asc
Description: PGP signat
e referring. Sorry for the confusion!
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?su
o indicate). You can alternatively subscribe by sending E-mail
to openstack-discuss-requ...@lists.openstack.org with a subject line
of "subscribe" if you prefer.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
good).
[0] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss
[1]
http://lists.openstack.org/pipermail/openstack-dev/2018-September/134911.html
--
Jeremy Stanley
signature.asc
Description: PGP
://pypi.org/project/python-apmecclient/
then I'm happy to reenqueue that tag into Zuul.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
7d7bb347e1caba4d74c81712de86790316b/release/release-openstack-python/f38f2b9/job-output.txt.gz#_2018-10-24_03_20_02_134223
I suppose we don't expect a project to run both the
release-openstack-python and release-openstack-python3
On 2018-10-18 08:35:21 -0500 (-0500), Jay S Bryant wrote:
[...]
> When OpenStack developers think Denver, we think Trains. :-)
[...]
As, presumably, do many OpenStack operators now since the Ops
Mid-Cycle event was co-located with the most recent PTG.
--
Jeremy Stanley
signature.
ues comes from the fact that we build wheels if there are none available
> and had a race in it.
>
> I hope an admin can delete the broken file again and it works again tomorrow
> - if not, best to speak up quickly on #openstack-infra,
It's been deleted (again) and the suspected
stream past
September 2020.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?sub
#x27;re
dropping Python 3.5 testing in Stein, and more a question of whether
we're going to continue requiring OpenStack to also be able to run
on Ubuntu 16.04 LTS (which wasn't the latest LTS even at the start
of the cycle).
--
Jeremy Stanley
signature.asc
Description: PGP signature
r Java which needs a
server built from a newer distro version, which is all we've gotten
through on the upgrade plan so far).
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing Li
ng (if the team regularly holds one)
we've stuck to the quoted expectation as a requirement as far as I'm
aware.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Maili
o do by
default. If the job says it's going to run unit tests under Python
3.7 then the job should make sure a suitable interpreter is
installed to do so.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
Op
ficial OpenStack projects should be moving
their testing from Ubuntu Xenial (which provides 3.5) to Ubuntu
Bionic (which provides 3.6 and, now, 3.7 as well) during the Stein
cycle and so will drop 3.5 testing on master in the process.
--
Jeremy Stanley
signature.asc
Description: PGP sig
erested in handling
that with their own unique organizations in those platforms, and so
on. It's progressing, though perhaps too slowly to solve your
immediate concerns.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
tack projects are hopefully switching to testing on Bionic
instead of Xenial during the Stein cycle, so will stop testing with
Python 3.5 on master when that happens (since Bionic provides
3.6/3.7 and no 3.5).
--
Jeremy Stanley
signature.asc
Descripti
ce consumed in our providers, et cetera). Bionic
seems like it will serve fine for this purpose now that it's got
more than a pre-release of 3.7.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Dev
for Bionic in the last few weeks?
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscr
On 2018-10-10 13:24:28 +1100 (+1100), Gilles Dubreuil wrote:
> On 09/10/18 23:58, Jeremy Stanley wrote:
> > On 2018-10-09 08:52:52 -0400 (-0400), Jim Rollenhagen wrote:
> > [...]
> > > It seems to me that a major goal of openstacksdk is to hide
> > > differences
hemselves.
> Did I understand that correctly?
This is especially useful where the SDK implements business logic
for common operations like "if the user requested A and the cloud
supports features B+C+D then use those to fulfil the request,
otherwise fall back to using features E+F&quo
s from
also updating the setup.cfg files in their repositories should they
choose to do so. That's all I've been trying to say.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailin
ng topics, like
> updates for ongoing projects.
>
> Does that work for everyone?
[...]
Seems fine to me.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage
On 2018-10-04 18:21:50 -0400 (-0400), Doug Hellmann wrote:
> Jeremy Stanley writes:
>
> > On 2018-10-04 17:57:06 -0400 (-0400), Doug Hellmann wrote:
> > [...]
> >> HTTPError: 400 Client Error: Invalid value for classifiers. Error:
> >> 'Topic:: Utilit
ttps://github.com/pypa/twine/pull/395 for details) which seems like
a more natural solution anyway.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions
ernate times).
This time is acceptable to me. As long as we ensure that community
feedback continues more frequently in IRC and on the ML (for example
by making it clear that this meeting is expressly *not* for that)
then I'm fine with resuming formal meetings.
--
Jeremy Stanley
signature.asc
the setup.cfg files are corrected over time, to
reduce the urgency of doing so. Wheel building happens in more
places than just our CI system, so only fixing it in CI is not a
good long-term strategy.
--
Jeremy Stanley
signature.asc
Description: PGP signat
; Agreed?
I believe the confusion is that ignore_basepython_conflict didn't
appear in a release of tox until after we started patching projects
for this effort (in fact it was added to tox in part because we
discovered the issue in originally attempting to use basepython
globally).
--
Jeremy Sta
has recently worked on a feature which required
coordination between several teams (but not a majority of teams like
our cycle goals process addresses) can comment on what worked for
them and what improvements they would make on the process they
followed.
--
Jeremy Stanley
signature.asc
Descri
ion if you're
able, I think every one of you would have made a great choice for a
seat on the OpenStack TC. Our community is really lucky to have so
many qualified people eager to take on governance tasks.
--
Jeremy Stanley
signature.asc
Description: PG
their release artifacts. Coverage
has improved for finding these issues before merging now, as well as
in flight tests on proposed releases, making the risk lower than it
used to be.
--
Jeremy Stanley
signature.asc
Description: PGP sig
uld allow them to match the queries those
teams have defined for their worklists, boards, et cetera. It's of
course possible to just hand-wave that these intersections are rare
enough to ignore and go ahead and use generic story tags, but the
recommendation is there to allow teams to
ty. Maybe there's a solution to that?
A board with automatic lanes for each priority tag? That way you can
also have a lane for "stories with incomplete tasks for projects in
my project-group but which haven't been prioritized yet" and be able
to act on/triage them accordingl
rt bugs for
Oslo their oslo-critical tag is applied to any with a critical
bugtask, oslo-medium to any with medium priority tasks, and so on.
Not all teams using StoryBoard will want to have a bucketed priority
scheme, and those who do won't necessarily want to use the same
number or kinds o
t; Local meetups/events, we discussed putting that here as well.
It seems a fine plan, just keep in mind that documenting and
publishing feedback doesn't magically translate into developers
acting on any of it (and this is far from the first time it's been
tml#prepare-an-initial-release
Perhaps slightly more aligned with the context of the question is
this document:
https://docs.openstack.org/infra/manual/drivers.html#tagging-a-release
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
any special
handling is needed. Basically any time after November 19 just send a
post to the old list saying that subsequent messages need to
go to openstack-discuss instead, and then immediately set it to no
longer accept new messages.
--
Jeremy Stanley
signature.
nfra-ptg-denver-2018
[4] https://www.ietf.org/rfc/rfc2369.txt
[5] https://etherpad.openstack.org/p/common-openstack-ml-topics
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List
hing new, since we already declare how and where
official discussion takes place and the measure doesn't make any
attempt to change that. We also don't regulate where unofficial
discussions are allowed to take place, and so it doesn't open up any
ne
he concrete reasons why continue to be missing from these
discussions.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ..
hat interactions as mere
"personal preference," and the idea that those who hold this
"preference" are somehow weak or afraid of the people they'll
encounter there.
For me, it borders on insulting. I (and I believe many others) have
strong ideological opposition to partic
xamples of social media. I'm
really not even opposed to using other forms as long as they rely on
open protocols and both the client _and_ server software are
available under a free/libre open source license.
--
Jeremy Stanley
signature.asc
Description: PGP signature
nications and content for which you use that
mobile device to wechat developers/service operators and, by proxy,
the Chinese government.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Ma
an engaged and effective contributor to our
community without compromising those ideals.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage quest
On 2018-09-11 16:53:05 + (+), Jeremy Stanley wrote:
> On 2018-08-01 08:40:51 -0700 (-0700), James E. Blair wrote:
> > Monty Taylor writes:
> > > On 08/01/2018 12:45 AM, Ian Wienand wrote:
> > > > I'd suggest to start, people with an interest in a channel
r willingness to do
> that within their project, they shouldn't be the PTL. The same
> goes for TC members IMO.
Completely agree, I think we might just disagree on where to strike
the balance of purely technical priorities for the TC (as I
personally think the TC is somewhat incorrectly
st about the limited number of available hours in the day
for one person versus many. The successes goal champions experience,
the connections they make and the elevated reputation they gain
throughout the community during the process of these efforts builds
new leaders for us all.
--
Jeremy Stanley
On 2018-09-12 17:03:10 -0600 (-0600), Matt Riedemann wrote:
> On 9/12/2018 4:14 PM, Jeremy Stanley wrote:
> > I think Doug's work leading the Python 3 First effort is a great
> > example. He has helped find and enable several other goal champions
> > to collaborate
On 2018-09-12 16:03:12 -0600 (-0600), Zhipeng Huang wrote:
> On Wed, Sep 12, 2018 at 3:55 PM Jeremy Stanley wrote:
> > On 2018-09-12 09:47:27 -0600 (-0600), Matt Riedemann wrote:
> > [...]
> > > So I encourage all elected TC members to work directly with the
> > >
hate to give the impression
that you must be on the TC to have such an impact.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: o
his thread or in #openstack-infra on Freenode) if you see any
signs of resurgence.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions
us to start
hyperlinking Task footers in commit messages within the Gerrit
change view. I'll try and figure out what we need to adjust in our
Gerrit commentlink and its-storyboard plugin configs to make that
happen.
--
Jeremy Stanley
signature.asc
Description: PGP signature
cessible so I don't see why it needs to be members of the
technical committee who write the software to collect that.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing
ort optionally using the project name now that SB
supports querying with it and uses it by default in webclient URLs.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usag
On 2018-09-06 15:03:52 -0500 (-0500), Matt Riedemann wrote:
> On 9/6/2018 2:56 PM, Jeremy Stanley wrote:
> > On 2018-09-06 14:31:01 -0500 (-0500), Matt Riedemann wrote:
> > > On 8/29/2018 1:08 PM, Jim Rollenhagen wrote:
> > > > On Wed, Aug 29, 2018 at 12:51 PM, Ji
> > // jim
>
> FYI for those that didn't see this on the other ML:
>
> http://lists.openstack.org/pipermail/foundation/2018-August/002617.html
[...]
While I agree that's a great post to point out to all corners of the
community, I don't see what it has to do wit
b-stein-ptg-planning and am
looking forward to seeing you in Denver!
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-req
gt; Is there anything that I need to do to link those 2 together?
In change 600316 you included a "Task: #2619" footer, when the
actual task you seem to have wanted to reference was 26199 (task
2619 is associated with unrelated story 2000403).
--
Jeremy Stanley
signature
aking Python API contracts for it to be usable
as an importable library, there's probably no need to install its
modules into the global Python search path anyway. They could just
go into a private module path on the filesystem instead as long as
the placement service/entrypoint wrapper knows wher
, and hope you
continue providing it whether or not you're serving on the TC.
Thanks, really!
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubsc
On 2018-09-04 19:46:30 -0400 (-0400), Paul Belanger wrote:
> After a year on the TC, I've decided not to run for another term.
[...]
Thank you for your service (past and future)!
--
Jeremy Stanley
signature.asc
Description: PGP s
o best represent you, your beliefs, your ideals. Vote for those
who share your vision for who, how and what OpenStack should be. If
you've been paying attention these past years, you already know my
opinions. I'd rather hear some new opinions from you.
--
Jeremy
acement" in the default import path, then Debian
wouldn't be able to carry packages for both projects without
modifying. At least one would need the module renamed or would need
to put it in a private path and then any cons
de the limited scope of the OpenStack community. Is the
expectation that the project when packaged (on PyPI, in Linux
distributions and so on) will just be referred to as "placement"
with no further context?
--
Jeremy Stanley
signature.asc
De
pointed out we
don't usually tell them to take their questions elsewhere any more).
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage question
tough, but luckily MIT's
listadmins have posted some so we don't need to:
http://web.mit.edu/lists/mailman/topics.html
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing
welcome
message, or merely linked to a published document (and whether
that's best suited for the Infra Manual or New Contributor Guide or
somewhere else entirely is certainly up for debate), or even
potentially both.
--
Jeremy Stanley
signature
way, come to understand it, and
become part of that process. Requiring them to have their
conversations elsewhere sends the opposite message.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Dev
ve a *lot*
of "black hole" subscribers who aren't actually following that list
but whose addresses aren't bouncing new posts we send them for any
of a number of possible reasons.
--
Jeremy Stanley
signature.asc
Description: PGP signature
support in
Mailman unless we can somehow work with them to help in
reimplementing it.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: opensta
he irony of cross-posting this
message to four mailing lists is not lost on me. ;)
[1] https://etherpad.openstack.org/p/YVR-ops-devs-one-community
[2] https://etherpad.openstack.org/p/common-openstack-ml-topics
--
Jeremy Stanley
signature.asc
Description: PGP signature
please don't assign copyright of your works to
the OSF).
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.opens
to the legal-discuss ML
so as to make the subscribers there aware of this thread.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openst
of this idea. I can see the Intel money rolling in now...
Seems like a sound idea. Can we call it "Nostalgia" for no
particular reason? Though maybe "Recurring Nightmare" would be a
more accurate choice.
--
Jeremy Stanley
cular_ situation, what action are you asking the
TC or other community leaders to take to resolve the problem (and
what do you see as "the problem" in this case, for that matter)?
--
Jeremy Stanley
signature.asc
Description: PGP signature
the Placement-only contributors what to prioritize working
on? Or are you saying that if they disagree that's fine because the
Nova+Placement contributors will get along just fine without the
Placement-only contributors helping them get it d
familiar with specific kernel subsystems and vanishingly few who can
efficiently (that is to say without investing lots of time to come
up to speed) implement novel features in multiple unrelated
subsystems.
We'll all continue to work on get better at this, but hard things
are... well... ha
y currently rely. For that, there needs to be a
positive working relationship, one we can't simply demand into
being, so it's in their best interests to work things out amicably
and directly instead of asking someone else (the TC) to decide this
for t
clear, it's not that TC members are unwilling to step into
these discussions. Rather, it's that most times when a governing
body has to tell volunteers to do something they don't want to do,
it tends to not be particularly helpful in solving the underlying
disagreement.
--
Jer
ou take
in to consideration the knock-on effects of duplicating things like
review dashboards for the various prolog rules defined for those
different subsets of the repository). If you're going to attempt to
delegate review on portions of a Git repository, in most cases you
may as well go ahead and ma
e keeping those older branches updatable does in fact
require quite a bit of effort. When we agreed to the suggestion of
not closing branches, it was with the understanding that they won't
just suddenly get taken care of by the same people who were already
not doing that because they considered
for consistency.
[*] https://review.openstack.org/592520
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@list
We might want to consider kicking it from
channels while they have nick registration enforced.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubs
sion on what it is or isn't using at this point.
If someone wants to resurrect it, updating things like the use of
the Nova notification interface seem like the bare minimum amount of
work they should commit to doing anyway.
--
Jeremy Stanley
signature.asc
eeting to the IRC meetings schedule at
http://eavesdrop.openstack.org/ (the first sentence in the section
contains instructions for doing so), that way people in the
community can find out when it is held without having to rely solely
on announcements. Thanks!
--
Jeremy Stanley
signature.asc
Descripti
that; thanks for all you've done and all
you have yet to do, it's important!
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
tover.)
>
> Now I can base it on PTG design work in a backronym fashion.
[...]
Speaking of which, is it too soon to put in bids to name the Denver
summit and associated release in 2019 "OpenStack Train"? I feel like
we're all honorary railroad engine
> create an its-launchpad plugin.
[...]
Careful; if you let anyone know you've touched a Gerrit plug-in the
requests for more help will never end.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStac
ot-useful
> ones.
[...]
Also, the OpenStack VMT doesn't prioritize information leaks which
are limited to debug-level logging[*], so leaving debug logging
enabled is perhaps more risky if you don't safeguard those logs.
[*] https://security.openstack.org/vmt-process.html#incident-repo
most of us care to experience.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subje
at nowish and not appoint a Stein
cycle PTL.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.opens
1 - 100 of 1706 matches
Mail list logo
