On 10/30/2017 11:28 PM, Matthew Thode wrote:
On 17-10-30 20:48:37, [email protected] wrote:
The second seem to be better suited for per driver requirement handling and per
HW type per function.
Which option is easier to handle for container per dependency for the future?
Thanks,
Arkady
I don't think it affects containers directly. Depending on how you build
containers you may have to do nothing (if you use package, for example) or
update your pip install to do a different thing (or things).
On 10/30/2017 09:48 PM, [email protected] wrote:
The second seem to be better
On 10/31/2017 12:11 AM, [email protected] wrote:
From: Dmitry Tantsur [mailto:[email protected]]
Cons:
1. more work for both the requirements team and the vendor teams
Please elaborate on the additional work you envision for the vendor teams.
Any requirements updates with have to be
Hi all,
Due to a technical issue we had to have our weekly meeting in our main channel
this time. And we liked it :) I wonder if we should switch to it.
Pros:
* easier to find
* no channel switching
Cons:
* potential conflicts with other meetings (already a problem, given how many
rooms we h
Thank you. I too vote for 'Option 1'.
Thanks and Regards
Shiv
On Wed, Nov 15, 2017 at 1:03 AM, Villalovos, John L <
[email protected]> wrote:
> Thanks for sending this out.
>
>
>
> I would vote for Option 1.
>
>
>
> Thanks,
>
> John
>
>
>
> *From:* Pavlo Shchelokovskyy [mailto:pshche
Thank you Mathieu for the insights!
To add details to what happened:
* Upgrade was never made a #1 priority. It was a one man show for far
too long. (myself)
I suppose that confirms that upgrades is very nice to have in production
deployments, eventually, maybe... (please read below to contin
On 13/11/17 22:51, Nikhil Komawar wrote:
I think it will a rather hard problem to solve. As swift store can be
configured to store objects in different configurations. I guess the
next question would be, what is your underlying problem -- multiple
build requests or is this for retry for a singl
On 15 November 2017 at 11:15, Matt Keenan wrote:
> On 13/11/17 22:51, Nikhil Komawar wrote:
>
> I think it will a rather hard problem to solve. As swift store can be
> configured to store objects in different configurations. I guess the next
> question would be, what is your underlying problem --
Hi Team,
As agreed last week we will begin our weekly video conference to speed up
the development, ZOOM meeting link could be found at
https://wiki.openstack.org/wiki/Meetings/CyborgTeamMeeting#Next_meeting_:_Nov_8th.2C_2017
.
The meeting will start as usual from UTC1500, and we will log necessa
On Tue, Nov 14, 2017 at 11:44 PM, Andreas Jaeger wrote:
> On 2017-11-15 01:18, Emilien Macchi wrote:
>> Hi,
>>
>> I'm working on migrating all TripleO CI jobs to be in-tree, I'm also
>> refactoring the layout and do some cleanup.
>
> Please don't move *all* in tree - only the legacy ones. There's
Rochelle Grober wrote:
> Folks,
>
> This discussion and the people interested in it seem like a perfect
> application of the SIG process. By turning LTS into a SIG, everyone can
> discuss the issues on the SIG mailing list and the discussion shouldn't end
> up split. If it turns into a projec
> -Original Message-
> From: Ihar Hrachyshka [mailto:[email protected]]
> Sent: Tuesday, November 14, 2017 4:19 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [neutron] multiple agents with segment access
>
> In general, you should be
I suggested by Rocky, I moved the discussion to the -sigs list by
posting my promised summary of the session at:
http://lists.openstack.org/pipermail/openstack-sigs/2017-November/000148.html
Please continue the discussion there, to avoid the cross-posting.
If you haven't already, please subscrib
Hello,
On November 13 we came the end of sprint using our new team structure [1],
and here’s the highlights:
Sprint Review:
The sprint epic was Reproduce of upstream CI jobs against RDO cloud
personal tenant [2] in order to help our Ruck and Rover to reproduce CI
issues.
It was we set several c
John Dickinson wrote:
> What I heard from ops in the room is that they want (to start) one
> release a year who's branch isn't deleted after a year. What if that's
> exactly what we did? I propose that OpenStack only do one release a year
> instead of two. We still keep N-2 stable releases around.
On 2017-11-15 00:37:26 + (+), Fox, Kevin M wrote:
[...]
> One idea is that at the root of chaos monkey. If something is
> hard, do it frequently. If upgrading is hard, we need to be doing
> it constantly so the pain gets largely eliminated. One idea would
> be to discourage the use of stand
Excerpts from Fox, Kevin M's message of 2017-11-15 00:37:26 +:
> I can think of a few ideas, though some sound painful on paper Not really
> recommending anything, just thinking out loud...
>
> One idea is that at the root of chaos monkey. If something is hard, do it
> frequently. If upg
On 11/15/2017 06:28 AM, Duncan Thomas wrote:
On 15 November 2017 at 11:15, Matt Keenan wrote:
On 13/11/17 22:51, Nikhil Komawar wrote:
I think it will a rather hard problem to solve. As swift store can be
configured to store objects in different configurations. I guess the next
question would
On 14/11/17 15:10 -0500, Doug Hellmann wrote:
Excerpts from Chris Friesen's message of 2017-11-14 14:01:58 -0600:
On 11/14/2017 01:28 PM, Dmitry Tantsur wrote:
>> The quality of backported fixes is expected to be a direct (and only?)
>> interest of those new teams of new cores, coming from user
On 17-11-15 09:32:33, Dmitry Tantsur wrote:
> On 10/31/2017 12:11 AM, [email protected] wrote:
> > > From: Dmitry Tantsur [mailto:[email protected]]
> >
> > > Cons:
> > > 1. more work for both the requirements team and the vendor teams
> >
> > Please elaborate on the additional work you en
Hello everyone,
We would like to choose the optimal time for our Team Meeting. I have created a
doodle [1] for that. Please put your preferences until Monday 1200 UTC if you
want to attend the meeting.
Cheers
Witek
[1] https://doodle.com/poll/s5fwqtu7ik898p57
_
On 15 Nov 2017, at 7:40, Jay Pipes wrote:
> On 11/15/2017 06:28 AM, Duncan Thomas wrote:
>> On 15 November 2017 at 11:15, Matt Keenan wrote:
>>> On 13/11/17 22:51, Nikhil Komawar wrote:
>>>
>>> I think it will a rather hard problem to solve. As swift store can be
>>> configured to store objects
2017-11-15 1:06 GMT+09:00 Andreas Jaeger :
> On 2017-11-14 17:03, Doug Hellmann wrote:
>> Excerpts from Andreas Jaeger's message of 2017-11-14 09:31:48 +0100:
>>> On 2017-11-13 22:09, Doug Hellmann wrote:
Excerpts from zuul's message of 2017-11-13 20:37:18 +:
> Unable to freeze job gra
Hey all,
I wanted to let everyone know that we just merged a patch [0] that
allows developers to deprecate policies (just like deprecating
configuration options). The functionality is implemented using the
DeprecatedRule object [1] and emits a warning to operators when
deprecated policies are used
I messed up the links in the previous note.
Merged implementation: https://review.openstack.org/#/c/509909/
Documentation:
https://docs.openstack.org/oslo.policy/latest/reference/api/oslo_policy.policy.html#oslo_policy.policy.DeprecatedRule
On 11/15/2017 11:34 AM, Lance Bragstad wrote:
> Hey all
Some clarifications below.
On Wed, Nov 15, 2017 at 4:52 AM, Bogdan Dobrelya wrote:
> Thank you Mathieu for the insights!
>
>> To add details to what happened:
>> * Upgrade was never made a #1 priority. It was a one man show for far
>> too long. (myself)
>
>
> I suppose that confirms that upgrades
Team,
Wanted to just send out a note for those of you who were not able to
attend today's weekly meeting.
There is a bugsmash coming up next week in China [1] . If you have bugs
that are appropriate to be addressed during the bugsmash please update
them in Launchpad with the 'bugsmash' tag.
Excerpts from Akihiro Motoki's message of 2017-11-16 01:32:00 +0900:
> 2017-11-15 1:06 GMT+09:00 Andreas Jaeger :
> > On 2017-11-14 17:03, Doug Hellmann wrote:
> >> Excerpts from Andreas Jaeger's message of 2017-11-14 09:31:48 +0100:
> >>> On 2017-11-13 22:09, Doug Hellmann wrote:
> Excerpts f
Ok so here's the latest. We've switched scenario001 to non-voting[0]
for now until Bug 1731063[1] can be resolved. We should be OK to start
merging thing in master as the other current issues don't appear to be
affecting the gate significantly as it stands. We still need to
understand why we're hi
Hello Frank,
I have just answered the survey - hopefully the survey end time is based
on UTC
and my survey answer will be also considered well.
If you (developers, translators) are interested in seeing the translated
version of
project repository documentation, please fill out the survey, whi
Just a thought, cause I have known/do know what Mathieu is talking about
and find the disconnect still oddly weird. Why aren't developer people
from other companies coming into to where Mathieu works (or where I
work) and seeing how it really works down on the ground here.
I mean if we still h
Some progress today:
https://review.openstack.org/#/q/topic:tripleo/migrate-to-zuulv3+(status:open+OR+status:merged)
- TripleO UI switched to new jobs
- tripleo-ci has playbooks, jobs and templates ready for review
- THT and puppet-tripleo has project layout ready for review
Next by order: tripl
This keynote talk about the evolution of governance in the kubernetes community
and the CNCF more broadly discusses some interesting parallels with our own
history.
https://m.youtube.com/watch?feature=youtu.be&v=Apw_fuTEhyA
_
On 15/11/17 03:07, Doug Hellmann wrote:
Excerpts from Gilles Dubreuil's message of 2017-11-14 10:15:02 +1100:
Hi,
Follow-up conversation from our last "API SIG feedback and discussion
session" at Sydney Summit [1], about APIs schema consumption.
Let's summarize the current situation.
Each Op
Hello everyone,
Please reminder that the weekly OpenStack QA team IRC meeting will be
Thursday, Nov 16th at 8:00 UTC in the #openstack-meeting channel.
The agenda for the meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_Nov_16th_2017_.280800_UTC.29
A
Doug Hellmann wrote:
This keynote talk about the evolution of governance in the kubernetes community
and the CNCF more broadly discusses some interesting parallels with our own
history.
https://m.youtube.com/watch?feature=youtu.be&v=Apw_fuTEhyA
___
Hello,
Some time ago we started the process of moving towards projects being
more explicit about thier binary dependencies using bindep [1]
To facilitate the transition, we created a "fallback" set of
dependencies [2] which are installed when a project does not specifiy
it's own bindep dependenci
Hi, Nova developers.
In nova-specs project, there is an 'openstack-tox-py27' job (in Zuul
check or Zuul gate).
The job checks whether spec files comply with the template or not, line
length, etc.
But there are cases that the job is not executed even if a spec file is
added or modified.
For e
Hello folks!
A few months ago Dan Sneddon and me worked in an ansible role that would
enable IPSEC for the overcloud [1]. Currently, one would run it as an extra
step after the overcloud deployment. But, I would like to start integrating
it to TripleO itself, making it another option, probably as
39 matches
Mail list logo
