Rochelle Grober wrote:
> Thierry Carrez wrote:
>> One question I have is whether we'd need to keep the "QA" project team at
>> all. Personally I think it would create confusion to keep it around, for no
>> gain.
>> SIGs code contributors get voting rights
der turning other non-purely-upstream teams
(like I18n) in the future.
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscri
free to add to it !
== Recently-approved changes ==
* Add the supports-rolling-upgrade tag to Ironic [1]
* Select Thierry Carrez as TC chair [2]
* Update house rules to reflect absence of meetings [3]
* Split up sahara deliverables [4] [5]
* Goal updates: sahara, glance, senlin, designate, zun
vember/000149.html
Please continue the discussion there, to avoid the cross-posting.
If you haven't already, please subscribe at:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs
--
Thierry Carrez (ttx)
signature.asc
Description: OpenPGP
subscribe at:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
istinfo/openstack-sigs
While I'm not sure that's the best name for it, as suggested by Rocky
let's use [lts] as a prefix there.
I'll start a couple of threads.
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not
ng OS/PyPI substrate) and enable whoever steps
up to maintain longer-lived branches to come up with a set of tests that
actually match their needs (tests that would be less likely to bitrot
due to changing OS/PyPI substrate).
A number of people from all backgrounds volunteered to flesh out a more
detaile
f TC-owned working group dedicated to the production of OpenStack
software.
With security having so much operational ties, it feels like a SIG would
be the best match as it prevents artificial governance boundaries from
getting in the way of getting people more directly involved.
--
T
Michael Still wrote:
> The privsep session doesn't appear to be in that list. Did it get
> dropped or something?
It's definitely on the schedule. You have to create and link to the
etherpad yourself, though...
--
Thierry Carre
Hi everyone,
Etherpads for the Forum sessions in Sydney can be found here:
https://wiki.openstack.org/wiki/Forum/Sydney2017
If you are moderating such a session and the etherpad is missing, please
add it !
--
Thierry Carrez (ttx
t up a specific, technically-focused personal blog aggregator.
But I feel like we could also reuse the SuperUser publication and the
existing Planet. The main issue seems to be the lack of produced
content, rather than lack of discoverability of the existing outlets...
--
Thierry Carrez (ttx)
signatu
Luke Hinds wrote:
> On Fri, Oct 27, 2017 at 6:08 PM, Jeremy Stanley <fu...@yuggoth.org
> <mailto:fu...@yuggoth.org>> wrote:
>
>> On 2017-10-27 15:30:34 +0200 (+0200), Thierry Carrez wrote:
>>> [...]
>>> I think the Security project team would benefit f
concerned.
What do you think ?
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-b
g next two status updates ==
Due to travel and low expected activity on the governance repository
front during summit, I'll be skipping the next two reports. The next one
shall be published on Friday, November 17.
Cheers,
--
Thierry Carrez (ttx)
_
in your calendars.
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman
e/ campaigning
time but not too much :)
Ideally discussions would start once people self-nominate, and we could
keep the period between nomination close and election start relatively
short (3/4 business days max).
--
Thierry Carrez (ttx)
signature.asc
Description: OpenPGP digital signatur
gt; (b) Do we want to have multiple release job templates due to custom
> dependencies (or any other reason)?
Leaning towards no if we can avoid it, again to simplify operations.
That said, it will be difficult to enforce...
--
d to be in the past) then I think people would care
more about representation of their interests and who exactly ends up
being elected.
--
Thierry Carrez (ttx)
signature.asc
Description: OpenPGP digital signature
__
OpenStac
contributing, it won't be as effective as if the Tacker PTL did the
outreach). One thing we could do would be to productize those tools and
make them available to a wider number of people.
--
Thierry Carrez (ttx)
__
09:00 UTC on Tuesdays
* 01:00 UTC on Wednesdays
* 15:00 UTC on Thursdays
For the coming week, I expect the main topic of discussion to be the
onboarding of the newly-elected membership, as well as Summit preparations.
Ch
benefiting the users interested in
stability (i.e. a good trade-off between getting desirable fixes and
being exposed to unnecessary risk).
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage q
Thierry Carrez wrote:
> == Final call on votes ==
>
> We need to make a final call on the Glare project team application for
> the Queens cycle. If by the end of day (AOE) on Monday there is no
> majority support for it, the application will be denied. So please jump
> on
owever rather than call it "relaxed"
I would make it specific to deployment/lifecycle or cycle-trailing
projects.
Ideally this policy could get adopted by any such project. The
discussion started on the review and it's going well, so let's see where
it goes :)
--
Thierry Carrez (ttx)
_
ctions, as well as iterations on the exact wording for the
"champions and stewards" top-5 item.
Cheers,
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openst
on the same day (bonus point for
eliminating the QA/Zuul session conflict there).
Cheers,
--
Thierry Carrez (ttx)
signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage q
Monty Taylor wrote:
> I have decided not to seek reelection for the TC.
Thanks for all your insights and guidance during all those years. Please
continue to scream and let us know whenever we are doing anything crazy!
--
Thierry Carrez (
requiring a specific meeting. Expect
the election season and the last project team applications to be the
main topics discussed during TC office hours next week. You can find TC
office hours at:
https://governance.openstack.org/tc/#office-hours
Cheers,
--
Thierry C
arrant its own data set, and using a set of binary tags is not the best
way to capture it.
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack
Graham Hayes wrote:
> On Thu, 5 Oct 2017, at 09:50, Thierry Carrez wrote:
>> [...]
>> In particular, we created two paths in the graph:
>> * upgrade < accessible-upgrade
>> * upgrade < rolling-upgrade < zero-downtime < zero-impact
>>
>>
ent rolling-upgrade things (cinder,
neutron, nova, swift) that would not qualify for accessible-upgrade as
well ?
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
e development dynamics will
be missed ! I really appreciated your insights and grounded perspective
in difficult governance discussions that we had to navigate together. I
hope you'll still be able to weigh in on some of those, e
. Join us on #openstack-tc !
[1]
http://lists.openstack.org/pipermail/openstack-dev/2017-October/122942.html
[2] https://governance.openstack.org/tc/
--
Thierry Carrez (ttx)
Chair, OpenStack Technical Committee
__
OpenStack Dev
)
sahara-image-elements 2014.*.*
sahara-dashboard 2014.*.*
Cheers,
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
iew and during office hours. I propose we give it another week before
calling a more formal meeting to discuss this. You can find TC office
hours at:
https://governance.openstack.org/tc/#office-hours
Cheers,
--
Thierry Carrez (ttx)
__
us on penstack-swg if
interested !
Regards,
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
ht foot.
Zhenguo: if you plan to be present, could you suggest this topic for
discussion at: http://forumtopics.openstack.org/
Deadline is tomorrow :)
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usa
Miguel Lavalle wrote:
> Is this the link we are supposed to use:
> http://forumtopics.openstack.org/cfp/create
Yes.
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsub
proposals during the TC office hours next week. You can join us at:
https://governance.openstack.org/tc/#office-hours
Cheers,
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions
pgrade,
supports-zero-downtime-upgrade, and supports-zero-impact-upgrade (+
supports-api-interoperability which has had little support so far).
They can always be resurrected when a project reaches new heights?
--
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-congressclient 2015.1.0
>> python-congressclient 2015.1.0rc1
>> python-designateclient 201
the PostgreSQL one. So,
> making Keystone working with CockroachDB should be easy peasy right?
> Almost! The rest of this email describes what we have done, to make it
> works.
> [...]
Thanks Ronan-Alexandre for the update! Great to see some progress in the
ex
to
avoid the stragglers tax !
Cheers,
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org
next week.
We should definitely take advantage of the Office Hours[7] for
preparatory discussions as we prep for the Board+TC+UC+Staff meeting on
Sunday and the PTG week after, though.
[7] https://governance.openstack.org/tc/#office-hours
Cheers,
--
Thierry Carrez (ttx
ment cycle and a smooth release. Take a step back, look at what
you achieved, and be proud.
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-
ait until we can get PTL signoff.
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.or
at's alright).
--
Thierry Carrez (ttx)
signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsu
Gathering to kickstart the work for the coming 6 months. I hope to
see you there!
Thanks,
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
lunch on Thursday
Let us know if you have any question, on the #openstack-ptg event
channel on IRC or by email at p...@openstack.org.
Hoping to see you there!
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List
Chen Ying wrote:
> hi Thierry Carrez,
> Could you help me to delete this wiki page[1]? This page about
> Smaug is not used any longer. Thanks.
>
> [1] https://wiki.openstack.org/wiki/File:Smaug-available-protectables.svg
Done!
--
Thie
ute. It's not
really destroying it, it just prevents PyPI from erroneously
distributing it, without having to add a PEP440-Epoch to an OpenStack
deliverable and discovering all the bugs that it would trigger.
--
Thierry Ca
in the
"Pike release" tomorrow.
Cheers!
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.ope
ould be deleted
> by anyone who has the
> administrator permissions to the wiki. Thanks.
Done!
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ..
Flavio Percoco wrote:
> On 18/08/17 11:17 +0200, Thierry Carrez wrote:
>> == Need for a TC meeting next Tuesday ==
>>
>> I'll be off next week (therefore skipping this update next Friday). I
>> don't think we have anything thoroughly blocked at this point requ
sold out, but Erin outlined options in hotels close to the
event venue that you can consider:
http://lists.openstack.org/pipermail/openstack-dev/2017-August/121192.html
I hope to see you there !
--
Thierry Carrez (ttx
s update next Friday). I
don't think we have anything thoroughly blocked at this point requiring
a meeting. However if something comes up and requires a meeting next
week while I'm off, please feel free to self-organize :)
Cheers,
--
you have any
questions or concerns.
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org
lc.openstack.org/Queens-PTG-Discussion-Rooms
It feels like this discussion could be scheduled in the Oslo room as
well. I guess it depends whether you need extra room :)
--
Thierry Carrez (ttx)
__
OpenStack Development
to a static,
mobile-friendly page that exposes the topics being currently discussed
at the PTG (driven by the ptgbot[1]).
[1] http://lists.openstack.org/pipermail/openstack-dev/2017-May/116974.html
See you there !
--
Thierry Carrez (ttx
h of those tasks as you can!
Thank you again for your help. Let's make Queens a great cycle!
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-
elease branch next week. That means potentially
> making a last Pike release, and in all cases posting the stable/pike
> branch creation request:
>
> ...
> branches:
> - location: YOUR.PIKE.VERSION
> name: stable/p
week), so if it's just
doc/releasenotes updates, I'd advise you to wait a bit before cutting RC2.
Regards,
--
Thierry Carrez (ttx)
signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mai
ce hours and
general #openstack-tc discussions to nudge them forward. Therefore I
don't think we need a synchronous TC meeting next week. Let me know if
you'd still like to have one and the topic you would like to see discussed.
Cheers!
--
ates / intermediary releases: August 24
Final Pike release: August 30
Queens PTG in Denver: Sept 11-15
As usual come find us on #openstack-release IRC channel if you have any
questions or concerns.
--
Thierry Carrez (ttx)
__
OpenS
issues in
testing.
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/li
> Neutron doesn't create conntrack entries in production code - only in
> testing. That said, agents should work just fine even with the
> kernel bug.
--
Thierry Carrez (ttx)
__
OpenStack Development Mail
ailing List (not for usage questions)
> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> <http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> <http://lists.openstack
c/457491/
> [2] https://review.openstack.org/#/c/491692/
It feels like this could wait until we create a stable/pike branch for
the requirements (which will happen as soon as we have RC1 for all
cycle-with-milestones projects, in theory at the end of this week, in
practice probably early next wee
- this topic is also
> critical to us and I think we can make our schedule to have one free
> room during the 2 and a half days that we have.
> Just let me know.
It could also be scheduled in one of the extra reservable rooms we have
on Thursday/Friday. The ethercalc for that should b
kages used in our system.
Since this change affects behavior, it's better to do it before Pike
release than after Pike release as a stable point update. So if my hunch
on CLI usage above is right, then I would rather grant the library
release freeze exception now.
guidance, assistance, tooling, and style guides
enabling OpenStack project teams to produce consistent, accurate, and
high-quality documentation.
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for
.
Cheers!
--
Thierry Carrez (ttx)
__
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
ut I digress). So I agree that the
situation should be clarified.
I know that Monty has pretty strong feelings about this too, so I'll
wait for him to comment.
--
Thierry Carrez (ttx)
__
OpenStack Developme
/pike
Upcoming Deadlines & Dates
--
RC1 target deadline (and HardStringFreeze): August 10
Final Pike release: August 30
Queens PTG in Denver: Sept 11-15
As usual come find us on #openstack-release IRC channel if you have any
questions or concerns.
--
Thierry Carrez
://docs.google.com/spreadsheets/u/1/d/1xmOdT6uZ5XqViActr5sBOaz_mEgjKSCY7NEWcAEcT-A/pubhtml?gid=397241312=true
Let me know if you have any question. You can also ask questions on
#openstack-ptg, or contact the events team at p...@openstack.org.
--
Thierry Carrez (ttx
s list and constraints list. I think the
> risk is minimal.
>
> https://review.openstack.org/489998
Sounds like something we should fix before release rather than after, so
+2 from me.
--
Thierry Carrez (ttx)
__
need so that it's clearer that
help with maintaining the doc toolchain is also a top wanted thing ?
[1]
https://governance.openstack.org/tc/reference/top-5-help-wanted.html#documentation-owners
--
Thierry Carrez (ttx)
__
OpenStack Dev
a
security focus.
--
Thierry Carrez (ttx)
__
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
yield results, you might try the legal list.
>
> The dev mailer is no place for this discussion.
Although I'm not a lawyer, I replied on the legal-discuss thread asking
for more information, and pointing to:
https://governance.openstack.org/tc/reference/licensing.html
Let's follow-up there.
that no other project depends
on python-tricircleclient, damage would be limited in cutting 0.2.0 now
and recreating stable/pike from it. We'll coordinate with infra to make
it happen.
Next time, please don't miss the deadline and create additional work for
the release team !
-
el if you have any
questions or concerns.
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.ope
e to
newer / better-supported versions.
> 2) The openstackdocstheme has the report a bug link feature. We can
> disable this. If we EOL docs (so, push a change before we eol them), we
> could remove the setting so that "report a bug" does not work.
Cheers,
--
Thierry Carrez (
mplemented the described change.
Thierry needs to reach out to existing WG to propose them to migrate to
the new SIG format.
== Need for a TC meeting next Tuesday ==
No initiative is currently stuck, so there is no need for a TC meeting
next week.
Cheers!
--
Thierry C
Doug Hellmann wrote:
> Sean has been increasingly active with the release team this cycle, and
> wants to contribute. I think we should go ahead and add him to the
> releases-core group.
>
> Please respond +1/-1.
+1!
--
Thie
my fair share of the release management
duties ! Whoever steps up and gets elected will be able to count on a
solid team of seasoned release managers and mentors :)
Regards,
--
Thierry Carrez (ttx)
__
OpenStack Development
that I can think of.
== Need for a TC meeting next Tuesday ==
No initiative is currently stuck, so there is no need for a TC meeting
next week.
Cheers!
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not
gust 30
Queens PTG in Denver: Sept 11-15
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
have to reject it.
Mike's answers are reassuring, so I'm looking forward to continuing this
discussion on this list and at the Denver PTG, and finally make the call
at the start of the Queens cycle.
--
Thierry Carrez (ttx)
_
ay ==
No initiative is currently stuck, so there is no need for a TC meeting
next week.
Cheers!
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...
/os-manuals-migration.html
Upcoming Deadlines & Dates
--
Non-client libraries final releases: July 20
Client libraries final releases: July 27
Pike-3 milestone (and Feature freeze): July 27
Final Pike release: August 30
Queens PTG in Denver: Sept 11-15
--
Thierry Ca
n't exist or not a regular file
The issue is that etc/monasca/log-api.conf is still in the data_files in
setup.cfg, but it's been removed by commit d243ed35.
https://review.openstack.org/481539 should fix it.
--
Thierry Ca
l meeting slot
time on Tuesday ?
Cheers!
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstac
Flavio Percoco wrote:
> On 03/07/17 13:58 +0200, Thierry Carrez wrote:
>> Flavio Percoco wrote:
>>> Sometimes I wonder if we still need to maintain a Wiki. I guess some
>>> projects still use it but I wonder if the use they make of the Wiki
>>&g
git repository
with a docs job and an etherpad.
FWIW the job of migrating authoritative things off the wiki is still
on-going. As an example, Thingee is spearheading the effort to move the
"How to Contribute" page and other first pointers to a reference website
(see recent thre
* Split Tempest plugins into separate repos/projects [1]
* Move policy and policy docs into code [2]
[1]
https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html
[2] https://review.openstack.org/#/c/469954/
--
Thierry Ca
sly
on the #openstack-tc channel instead.
Cheers!
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://list
or projects outside of openstack governance. This clarifies things a
lot, but presents challenges of its own, as that space was pretty
convenient to bootstrap projects or host companion projects, as well as
build a community.
--
Thierry Carrez (ttx)
___
TG in Denver: Sept 11-15
--
Thierry Carrez (ttx)
__
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
my analysis says otherwise... Although it's far from
complete I would say about half of them haven't been touched over the
past year. Feel free to help classifying them at:
https://etherpad.openstack.org/p/negative-space-analysis
--
Thierry
Jimmy McArthur wrote:
> Thierry Carrez wrote:
>> The confusion I'm talking about is not the passive-aggressive from
>> people involved in openstack. It's from our prospective new users, who
>> have no idea about our governance, making random searches on Google.
>> I
James E. Blair wrote:
> Thierry Carrez <thie...@openstack.org> writes:
>
>> Removing the root cause would be a more radical move: stop offering
>> hosting to non-OpenStack projects on OpenStack infrastructure
>> altogether. We originally did that for a reason, thoug
201 - 300 of 1930 matches
Mail list logo
