everal projects
that follow standard deprecation and support rolling upgrade that
haven't asserted the corresponding tags yet.
For the time being we are looking at applying such tags only to
"type:service" deliverables (main user-facing services).
Thanks i
meeting if there is an agenda posted.
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.
?
Once we have a list of key members we should set up a meeting to discuss
the details.
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstac
eduction effort that typically falls
short of resources in a tragedy of the commons, I prefer to see it as a
great achievement for us as a community.
Thanks to all the people that drove Oslo from where it was to where it
is today, including (but not limited to) Mark McLoughlin, Doug Hellmann
and D
it uses (date_fix_committed or date_fix_released) instead.
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
htt
openstack/project-team-guide/tree/doc/source/stable-branches.rst
:)
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject
nvalidates the compromise
(using tooz) we came up during the session. ZooKeeper can totally be the
tooz default in devstack (something has to be). If other tooz drivers
reach the same level of maturity one day, they could run in specific
tests and/or become the new default ?
--
Thierry Carrez
ry.
I'm arguing that one of the reasons "nobody cares" is because it's
always been the 5th wheel of release management, and making it a
first-class citizen could unlock the situation. I don't see harm in
trying. Do you ?
--
Thierry Carrez (ttx)
signature.asc
Descriptio
category/Lwood/feed/
You should federate that one to Planet OpenStack!
See instructions at:
https://wiki.openstack.org/wiki/AddingYourBlog
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
U
that work
So.. good idea ? bad idea ? What do current stable-maint-core[2] members
think of that ? Who thinks they could step up to lead that team ?
[1] http://docs.openstack.org/project-team-guide/stable-branches.html
[2] https://review.openstack.org/#/admin/groups/530,members
--
Thierry C
of
that "same upstream". Ubuntu for example currently carries 69 patches on
top of OpenJDK 7 source.
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-req
en the midcycle sprints and the summit planning ?
--
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
e OpenJDK is always bad.
My main objection about picking a Java solution was that we'd in effect
force our users into a non-free solution so that they eliminate that
unknown themselves. I guess as long as we are reasonably confident that
ZooK
and fix the mess in the end.
PS: stable gates are currently broken for horizon/juno, trove/kilo, and
neutron-lbaas/liberty.
--
Thierry Carrez (ttx)
signature.asc
Description: OpenPGP digital signature
__
ected across a wide range of project-specific maintenance
teams. So that new team could definitely change the common rules there
:) More on that soon.
Cheers,
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (n
signed up to
build and maintain a Consul and/or etcd driver :)
NB: I wouldn't mind helping on an etcd driver, that sounds like a fun
side project. I'm just totally unsure I'll have time to do it.
--
Thierry Carrez (ttx)
__
d channel
(by virtue of being the old default dev channel).
So officially repurposing it for cross-project discussions /
announcements sounds like a good idea. Think of it as a permanent
cross-project meeting / announcement sp
Joe Cropper wrote:
>
>> On Nov 2, 2015, at 4:50 AM, Thierry Carrez wrote:
>>
>> Antoine CABOT wrote:
>>> We are pleased to introduce Watcher, a new project in the OpenStack
>>> ecosystem. We believe that a "resource optimization" service in an
dea, we could deprecate the meeting
starting next week.
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
/reference/new-projects-requirements.html
In the mean time, please refrain from calling your project "OpenStack
Watcher". Thanks in advance!
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing Lis
here we point people to the
policy and ask them to agree to follow it...
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subj
r-constraints expresses
clearly the combination that works and was tested. Combined with the
uncapped requirements (which express what *should* be working, to the
best of our knowledge), they make a more accurate, albeit admittedly
more complex, set of information for downstream packagers.
--
Thier
preparation ahead of the event.
Thanks!
--
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
Adrien Cunin wrote:
> Le 09/10/2015 11:42, Thierry Carrez a écrit :
> Nice! I've got a question though: is there another way than the wiki
> page to consume those successes?
>
> I was thinking of an RSS/Atom feed, which would make it possible to
> easily publish them els
https://launchpad.net/neutron/liberty/liberty-rc3
Unless hell freezes in the next four hours, these tarballs be formally
released as final "Liberty" versions tomorrow.
Cheers!
--
Thierry Carrez (ttx)
__
OpenStack D
Ihar Hrachyshka wrote:
> Chuck, have you forgotten about three more repositories for neutron-*aas?
Yeah, if those have fixes they should have been tagged as well.
Also we'll want a change to openstack/releases to include 2015.1.2 in
release history.
--
Thierry Carrez (ttx)
signa
p and cut the tag
from the commit just before that. That is how it's done on the main
release when we start cutting the release branch at RC1.
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for u
the CS2 vote results area a lot less clear than the table we
had in CS, but that may be because I'm used to it now.
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
berty/liberty-rc3
https://launchpad.net/manila/liberty/liberty-rc3
You'll have to walk over my dead body to get a release candidate respin
for those at this stage, so these tarballs will likely be formally
released as final "Liberty" versions Thursday.
Cheers!
--
py.
Based on currently-expressed constraints, we could swap sessions 3 and
26 so that mtreinish can attend 26 (and dhellmann can attend both 3 and 11).
--
Thierry Carrez (ttx)
signature.asc
Description: OpenPGP digital signature
only solution for a problem space that
might still be a good trade-off (compared to reinventing the wheel for
example), but to share state or distribute locks, there are some pretty
good other options out there that don't suffer from the same fundamental
problem...
--
Thierry Carrez (ttx)
e explore the options we have in that space, I'd like to
consider options that still enable us to plug such a no-scheduler
solution without too much trouble. Just for those of us who are ready to
make that trade-of
e latter at every update by a CI job.
Also worth noting that the Foundation is working on a new version of the
"software" section of the website for the Liberty release, which should
make it more convenient to discover all the projects under the OpenStack
umbrella.
Regards,
--
Thie
uide, the wiki page itself). I'll take care of it.
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:un
Ihar Hrachyshka wrote:
> Welcome Doug!
Please (re)read and apply the policy at:
https://wiki.openstack.org/wiki/StableBranch#Stable_branch_policy
--
Thierry Carrez (ttx)
signature.asc
Description: OpenPGP digital signat
ccess liberally and record lttle everyday OpenStack
successes. Share the joy and make the OpenStack community a happy place.
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
ould be easy to review.
>
> With a working (and voting?) python34 check job and these 6 changes, it
> will be (much) easier to work on porting Swift to Python 3. Following
> patches will be validated by the python34 check job, shorter and
> restricted to a few files.
>
> Vict
a/+filebug
or
https://bugs.launchpad.net/glance/+filebug
and tag it *liberty-rc-potential* to bring it to the release crew's
attention.
Thanks!
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for
der election / syncing status around.
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack
k.org/cgit/openstack/horizon/log/?h=stable/liberty
If you find an issue that could be considered release-critical, please
file it at:
https://bugs.launchpad.net/horizon/+filebug
and tag it *liberty-rc-potential* to bring it to the release crew's
attention.
Thanks!
--
Thie
al, please
file it at:
https://bugs.launchpad.net/neutron/+filebug
or
https://bugs.launchpad.net/heat/+filebug
and tag it *liberty-rc-potential* to bring it to the release crew's
attention.
Thanks!
--
Thie
ick N now, but not O. We
might want to change that (again) first.
[1] http://governance.openstack.org/reference/release-naming.html
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsub
al, please
file it at:
https://bugs.launchpad.net/cinder/+filebug
or
https://bugs.launchpad.net/keystone/+filebug
and tag it *liberty-rc-potential* to bring it to the release crew's
attention.
Thanks!
--
Thie
ed release-critical, please
file it at:
https://bugs.launchpad.net/designate/+filebug
or
https://bugs.launchpad.net/ceilometer/+filebug
and tag it *liberty-rc-potential* to bring it to the release crew's
attention.
Thanks!
--
Thie
t your deliverables.
This is why we recommend the "intermediary" model to mature projects and
project teams -- that model requires excellent test coverage and
discipline inside the team to slow down development as you get closer to
a release tag and spend time on testing.
--
Thierry Carre
.net/trove/+filebug
or
https://bugs.launchpad.net/barbican/+filebug
and tag it *liberty-rc-potential* to bring it to the release crew's
attention.
Thanks!
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List
that won't hurt.
--
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
/?h=stable/liberty
If you find an issue that could be considered release-critical, please
file it at:
https://bugs.launchpad.net/zaqar/+filebug
and tag it *liberty-rc-potential* to bring it to the release crew's
attention.
Thanks!
--
Thie
Thierry Carrez wrote:
> [...] Here is the resulting proposed room/time layout result:
>
> http://tinyurl.com/mitaka-design-summit
OK, I just pushed this track layout to the official Design Summit
schedule at:
https://mitakadesignsummit.sched.org/
> [...]
> I'll push thi
h at:
http://git.openstack.org/cgit/openstack/manila/log/?h=stable/liberty
If you find an issue that could be considered release-critical, please
file it at:
https://bugs.launchpad.net/manila/+filebug
and tag it *liberty-rc-potential* to bring it to the release crew's
attention.
Thanks!
--
Thie
ome
space as a result:
https://openstacksummitoctober2015tokyo.sched.org/overview/type/collaboration+day
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.open
lable if any project team decides they
don't need that much space after all). If there are a lot of requests
for those, I plan to give priority to the late-comers in the tent which
don't have any space yet.
See you all in 3.5 weeks in T
ron?
because they are not released for liberty yet. This site only contains
formal releases (for now). You can find Nova / Neutron alright for past
releases.
--
Thierry Carrez (ttx)
signature.asc
Description: OpenPGP digital signature
_
eries / versions map at:
http://docs.openstack.org/releases/
Hope this helps,
--
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
y question.
--
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
in advance!
--
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
cially open for Mitaka development, so feature freeze
restrictions no longer apply there.
Regards,
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@list
e branch was cut at:
http://git.openstack.org/cgit/openstack/ironic/log/?h=stable/liberty
> This means Ironic is now open for Mitaka development; commit away!
> [...]
Yay!
--
Thierry Carrez (ttx)
__
OpenStack Developm
ger apply there.
Regards,
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/
://bugs.launchpad.net/trove/+filebug
and tag it *liberty-rc-potential* to bring it to the release crew's
attention.
Note that the "master" branches of Nova and Trove are now officially
open for Mitaka development, so feature freeze restrictions no longer
apply there.
Regards,
--
Thie
it.
There isn't one yet (that I know of). In Paris (and Hong-Kong) it was
created by the local OpenStack user group, so hopefully the Japanese
user group will set up something :)
--
Thierry Carrez (ttx)
__
OpenStack Deve
there.
Regards,
--
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/m
Robert Collins wrote:
> On 23 September 2015 at 02:03, Thierry Carrez wrote:
>> Robert Collins wrote:
>>> [...]
>>> So, one answer we can use is "The version impact of a requirements
>>> change is never less than the largest version change in the change.&q
://bugs.launchpad.net/zaqar/+filebug
and tag it *liberty-rc-potential* to bring it to the release crew's
attention.
Note that the "master" branches of Heat and Zaqar are now officially
open for Mitaka development, so feature freeze restrictions no longer
apply there.
Regards,
--
Thie
projects.
[1]
http://governance.openstack.org/resolutions/20141128-elections-process-for-leaderless-programs.html
[2] http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-09-22-20.01.html
[3] https://review.openstack.org/#/c/224743/
Regards,
--
Thierry Carrez (ttx)
signature.asc
Description: OpenP
opened an etherpad for session
suggestion yet).
Otherwise we could also discuss it as part of the Infra/QA/RelMgt
contributors meetup on Friday.
--
Thierry Carrez (ttx)
signature.asc
Description: OpenPGP digital signature
here !
Regards,
--
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
t; major version change
> 1.2.y -> 1.3.0 -> minor version change
> 1.2.3. -> 1.2.4 -> patch version change
The last two sound like good rules of thumb.
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List
as good a time as any.
--
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
e experimental branch (master) and port pieces
of it in the release branch (latest). In our case only the
backward-incompatible work lands in the experimental branch (feature/*),
and the release branch (master) contains everything else.
I am just not sure it's different enough to justify
uch submission lives at:
https://review.openstack.org/#/c/207467/
The 'certified-by-rally' tag is a bit farther away I think (less
objective and needs your certification program to be set up first). You
should start with the other two.
--
Thierry Carrez (ttx)
_
d old "odsreg" system
for everyone to propose suggestions at:
http://odsreg.openstack.org/
If you have an idea of a topic that we should cover on that track,
please push it there. Please indicate if you're available to moderate
the session in case it's accepted.
Regards,
actually a candidate, they just missed the deadline. So that should be
an easy discussion at the next TC meeting.
For the last one, it is not an accident. I think it is indeed the final
nail on the coffin.
--
Thierry Carrez (ttx)
__
leverage when they have a cross-project idea, a team
that could define a few cycle goals and actively push them during the cycle.
Maybe cross-project initiatives are too important to be left to the
energy of an individual and rel
ment for Mitaka, or
that I won't ever be Release Management PTL again -- it's just that
someone else will take the PTL hat for the next cycle, drive the effort
and be the most visible ambassador of the team.
Cheers,
e stable release? For
>> projects doing intermediary releases, there may be several releases
>> within a 3 month period.
>
> Yes. 1 stable release branch AND 3 months linear time is what I'd
> consider reasonable.
OK, so it seems we have convergence around:
"config o
he community" expects the Glance leadership to focus
on in the very short term.
Cheers,
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.o
others. The tag doesn't prevent the project to exist
in OpenStack, it just informs our users that there is a level of risk
associated with it.
Or are you suggesting it is preferable to hide that risk from our
operators/users, to prote
is
now actually an acronym for "Project Team Leads".
Cheers,
--
Thierry Carrez (ttx)
signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: op
> * Exceptions need discussion
>
> Then at least 10 working days after RC1:
> * we need a new RC candidate to include any updated strings
>
> Is everyone happy with these changes?
That sounds pretty good.
--
Thierry Carrez (ttx)
___
to ship the filters, not the library itself (so rootwrap
would have to look into nova resources, not rootwrap resources). Another
trick is that it should require root rights (not nova rights) to change
those resources, otherwise the security model is
Sean Dague wrote:
> On 09/10/2015 08:23 AM, Thierry Carrez wrote:
>> Now another problem you're describing is that there is no single place
>> where those filters end up, depending on the way the projects (or libs)
>> are packaged and installed. And it's
using multiple concurrent packaging systems), but it's
not exactly new -- it's just that libraries shipping fliters file are
even more likely to ship their filters somewhere weird. So maybe we can
continue to live with that problem we always had, until the privsep
system co
ged clients starting next cycle, and release when there are changes
> that warrant (probably not just for requirements changes, unless
> it's necessary). I haven't worked out the details of how to do the
> review without me contacting release liaisons directly, so suggestions
> on that
imited (more like Paris than like Vancouver), but we have
a lunch room with roundtables which can be abused (outside lunch) for
ad-hoc discussions.
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usa
Nikhil Komawar wrote:
> No dedicated time slot for cross-project sessions this time around?
That's on the Tuesday. 3 parallel sessions all day.
In addition, the Ops track runs on Tuesday and Wednesday.
--
Thierry Car
lots. If you have constraints (I already know
searchlight wants to avoid conflicts with Horizon, Kolla with Magnum,
Manila with Cinder, Solum with Magnum...) please let me know, we'll do
our best to limit them.
--
Thierry Carrez (ttx)
__
s (or extra docs for that matter) don't count as a
"feature" for the freeze. In particular it doesn't change the behavior
of the software or invalidate testing that may have been conducted.
--
Thierry Carrez (ttx)
ilities, n+1 for config options
3. n+1 overall
Thanks in advance for your input.
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?s
a
project goes through a static code checker. So it is also about
proactively clearing the obvious stuff before it generates a spike in
VMT work.
--
Thierry Carrez (ttx)
__
OpenStack Development Mailing List (not fo
Lowery, Mathew wrote:
> Just curious if anyone is using containers in their deployments. If so,
> in what capacity? What are the advantages, gotchas, and pain points?
This might trigger more responses on the openstack-operators mailing-list.
--
Thierry Carre
y feel confident they can tackle the
additional workload.
You can find their contact details at:
https://security.openstack.org/
--
Thierry Carrez (ttx)
signature.asc
Description: OpenPGP digital signature
__
OpenStack Developm
w requirements (or requirements bumps)
should ideally be filed before end of next week if you want those part
of 4.1.0 (or stable/liberty).
Ift's a soft freeze so we'll still consider exceptions of course, but
that's the general rule.
--
Thierry Carrez (ttx)
>
> 5. add section describing 501 common mistake
> https://review.openstack.org/#/c/183456/
Added to cross-project meeting agenda at:
https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting
In the future, feel free to edit that directly :)
--
Thierry Carrez (ttx)
__
ludes (there should be only one at most, but lets not
>> error if there are multiple)
>
> Rather than sorting, which would change the order of notes as new items
> are added, what about listing them in an order based on when they were
> added in the histor
es.
The Death of the Incubator. Sounds like a great thing to discuss at the
Design Summit. I don't think we would kill it before start of Mitaka
anyway ?
--
Thierry Carrez (ttx)
signature.asc
Description: OpenPGP digital signature
?
Any benefit, difference ? Anything you could contribute back there ? Any
value in merging the two efforts ?
[1] http://governance.openstack.org/reference/projects/openstackansible.html
--
Thierry Carrez (ttx)
__
OpenSta
at least
one release candidate before the end of the cycle).
It's a balance between the pain of backporting fixes and the pain of
freezing master. At one point the flow of fixes slows down enough and/or
the pressure to unfreeze master becomes too strong: that's when you
should
Clark Boylan wrote:
> On Tue, Aug 25, 2015, at 05:32 AM, Thierry Carrez wrote:
>>> * what did we exactly mean by "master->stable cross-check" ?
>>
>> For completeness, during the transition period (when we use master
>> requirements for both master and s
Thierry Carrez wrote:
> [...]
> 1. Enable master->stable cross-check
> 2. Release Oslo, make stable branches for Oslo
> 2.1 Converge constraints
> 3. liberty-3 / FF / soft requirements freeze
> 4. hard requirements freeze
> 5. RC1 / make stable branches for services
901 - 1000 of 2055 matches
Mail list logo
