On 2017-12-09 15:57, Andreas Jaeger wrote:
> Anthony, Christophe, Gauvin,
>
> The last merge to one of the cerberus repositories was December 2015, I
> propose to retire the repositories to avoid people submitting changes to
> them.
>
> See
> https://docs.openstack.org/infra/manual/drivers.html#r
Hi,
Review https://review.openstack.org/#/c/535206/ was merged yesterday to
create some new releases for puppet modules in pike. I've observed that
releases were not created for following modules:
puppet-tacker
puppet-zaqar
puppet-tempest
puppet-vswitch
puppet-vitrage
puppet-trove
I couldn't fin
Here's resource provider and placement update 18-03. I'm travelling so
this version may be a bit abridged.
# Most Important
This remains mostly the same, getting alternate hosts all the way in
and finishing up nested resource provider support (as ProviderTree
on the nova side and support for ne
Hi!
This is the weekly summary of Technical Committee initiatives. You can
find the full list of all open topics (updated twice a week) at:
https://wiki.openstack.org/wiki/Technical_Committee_Tracker
If you are working on something (or plan to work on something)
governance-related that is not re
On Fri, Jan 19, 2018 at 1:52 AM, Ken'ichi Ohmichi wrote:
> 2018-01-18 12:36 GMT-08:00 Doug Hellmann :
>>
>> I feel pretty sure that was discussed in a TC meeting, but I can't
>> find that. I do find Matt and Ken'ichi voting +1 on the resolution
>> itself. https://review.openstack.org/#/c/312718/.
On 19/01/18 04:10, Ghanshyam Mann wrote:
> On Thu, Jan 18, 2018 at 11:22 PM, Graham Hayes wrote:
>> On 18/01/18 16:25, Doug Hellmann wrote:
>>> Excerpts from Graham Hayes's message of 2018-01-18 15:33:12 +:
>>
>>
>>
>>>
>>> In the past the QA team agreed to accept trademark-related tests from
On 19/01/18 03:28, Ghanshyam Mann wrote:
> On Thu, Jan 11, 2018 at 10:06 PM, Colleen Murphy wrote:
>> Hi everyone,
>>
>> We have governance review under debate[1] that we need the community's help
>> on.
>> The debate is over what recommendation the TC should make to the Interop team
>> on wher
Looking at
http://logs.openstack.org/0f/0f0c9871144bf3b658f73f60f35f3068612a6bb2/release-post/tag-releases/629d779/job-output.txt.gz
(thanks ykarel for pointing it out) it seems the "run releases script"
tasks timed out and some releases were not properly created. I'd say that
the script stuck doin
On 19/01/18 00:52, Ken'ichi Ohmichi wrote:
> 2018-01-18 12:36 GMT-08:00 Doug Hellmann :
>> Excerpts from Doug Hellmann's message of 2018-01-18 15:21:12 -0500:
>>> Excerpts from Graham Hayes's message of 2018-01-18 19:25:02 +:
On 18/01/18 18:52, Doug Hellmann wrote:
> Excerpts fr
Matthew Thode wrote:
> On 18-01-18 11:20:21, Thierry Carrez wrote:
>> [...]
>> You'll also notice that some teams (in orange below the table in above
>> link) do not have pre-allocated slots. One key difference this time
>> around is that we set aside a larger number of rooms and meeting spots
>> f
Colleen Murphy wrote:
> On Fri, Jan 19, 2018 at 1:52 AM, Ken'ichi Ohmichi
> wrote:
>> 2018-01-18 12:36 GMT-08:00 Doug Hellmann :
>>>
>>> I feel pretty sure that was discussed in a TC meeting, but I can't
>>> find that. I do find Matt and Ken'ichi voting +1 on the resolution
>>> itself. https://r
On Fri, Jan 19, 2018 at 11:54:09AM +0100, Alfredo Moralejo Alonso wrote:
> Looking at
> http://logs.openstack.org/0f/0f0c9871144bf3b658f73f60f35f3068612a6bb2/release-post/tag-releases/629d779/job-output.txt.gz
> (thanks ykarel for pointing it out) it seems the "run releases script"
> tasks timed ou
> Earlier in the week I did some exercising by humans and was confused
> by the state of traits handling on /allocation_candidates (it could be
> the current state is the expected state but the code didn't make that
> clear) so I made a bug on it make sure that confusion didn't get forgotten:
>
>
>
> There appears to have been a transient failure with a timeout on a git pull
> request in the job. I have asked in -infra if there is anyone that can just
> re-enque the job for us. It should pass this time. This one is for
> puppet-swift.
>
> There was another failure yesterday with puppet-ho
Thanks Marius for sending this out and kicking off a conversation.
On Tue, Jan 2, 2018 at 12:56 PM, Marius Cornea wrote:
> Hi everyone and Happy New Year!
>
> As the migration of tripleo-upgrade repo to the openstack namespace is
> now complete I think it's the time to create a Pike branch to ca
On 01/18/2018 02:54 PM, Mathieu Gagné wrote:
We use this feature to segregate capacity/hosts based on CPU
allocation ratio using aggregates.
This is because we have different offers/flavors based on those
allocation ratios. This is part of our business model.
A flavor extra_specs is use to sched
On Fri, Jan 12, 2018 at 9:50 AM Luigi Toscano wrote:
> On Thursday, 11 January 2018 23:52:00 CET Matt Riedemann wrote:
> > On 1/11/2018 10:36 AM, Colleen Murphy wrote:
> > > 1) All trademark-related tests should go in the tempest repo, in
> > > accordance
> > >
> > > with the original resolut
On Mon, Jan 15, 2018 at 12:59 PM Erno Kuvaja wrote:
> On Thu, Jan 11, 2018 at 4:36 PM, Colleen Murphy
> wrote:
> > Hi everyone,
> >
> > We have governance review under debate[1] that we need the community's
> help on.
> > The debate is over what recommendation the TC should make to the Interop
>
Hi Chris,
On Fri, Jan 19, 2018 at 10:21 AM, Chris Friesen
wrote:
>
> The existing mechanisms to control aggregate membership will still work, so
> the remaining issue is how to control the allocation ratios.
>
> What about implementing a new HTTP API call (as a local private patch) to
> set the a
On 01/19/2018 10:21 AM, Chris Friesen wrote:
On 01/18/2018 02:54 PM, Mathieu Gagné wrote:
We use this feature to segregate capacity/hosts based on CPU
allocation ratio using aggregates.
This is because we have different offers/flavors based on those
allocation ratios. This is part of our busine
On Fri, Jan 19, 2018 at 10:21 AM, Wesley Hayutin
wrote:
> Thanks Marius for sending this out and kicking off a conversation.
>
> On Tue, Jan 2, 2018 at 12:56 PM, Marius Cornea wrote:
>
>> Hi everyone and Happy New Year!
>>
>> As the migration of tripleo-upgrade repo to the openstack namespace is
On Thu, Jan 18, 2018 at 3:33 PM Graham Hayes wrote:
>
>
> On 11/01/18 16:36, Colleen Murphy wrote:
> > Hi everyone,
> >
> > We have governance review under debate[1] that we need the community's
> help on.
> > The debate is over what recommendation the TC should make to the Interop
> team
> > on
On Thu, Jan 11, 2018 at 4:36 PM Colleen Murphy wrote:
> Hi everyone,
>
> We have governance review under debate[1] that we need the community's
> help on.
> The debate is over what recommendation the TC should make to the Interop
> team
> on where the tests it uses for the OpenStack trademark pro
>
> Just an update - it does look like it was just the one job failure. There are
> multiple puppet-* releases done as part of the one job, and it appears they
> are
> processed in alphabetically order. So this last time it got as far as
> puppet-swift (at least further along than puppet-horizon)
On Wed, Jan 17, 2018 at 7:27 PM Ihar Hrachyshka wrote:
> Hi all,
>
Hi!
>
> tl;dr I propose to switch to lib/neutron devstack library in Queens. I
> ask for buy-in to the plan from release and QA teams, something that
> infra asked me to do.
>
> ===
>
> Last several cycles we were working on get
Hello everyone,
After a long holiday break I would like to resume work on bringing the QA
SIG to life.
I proposed a QA SIG session [0] for the next PTG, but I'm not sure the
right audience will be in Dublin.
Could you please reply if you are interested but won't be in Dublin or add
your name to t
On 01/18/2018 09:45 AM, Emilien Macchi wrote:
On Thu, Jan 18, 2018 at 6:34 AM, Or Idgar wrote:
Hi,
we're encountering many timeouts for zuul gates in TripleO.
For example, see
http://logs.openstack.org/95/508195/28/check-tripleo/tripleo-ci-centos-7-ovb-ha-oooq/c85fcb7/.
rechecks won't help a
On Fri, Jan 19, 2018 at 5:50 PM, Sean McGinnis
wrote:
> >
> > Just an update - it does look like it was just the one job failure.
> There are
> > multiple puppet-* releases done as part of the one job, and it appears
> they are
> > processed in alphabetically order. So this last time it got as fa
# Keystone Team Update - Week of 15 January 2018
## News
### Core team changes
We added a new core reviewer! Thanks Gage Hugo for all your hard work
and for stepping up to take on more responsibility!
We also lost some core members: Boris Bobrov, Steve Martinelli, Brant
Knudson and Brad Topol h
On 9 January 2018 at 15:28, Matthew Booth wrote:
> In summary, the patch series is here:
>
> https://review.openstack.org/#/q/status:open+project:opensta
> ck/nova+branch:master+topic:bp/local-disk-serial-numbers
>
> The bottom 3 patches, which add BDM.uuid have landed. The next 3 currently
> hav
Hi Thierry
On Thu, 18 Jan 2018 at 10:20 Thierry Carrez wrote:
> Hi everyone,
>
> Here is the proposed pre-allocated track schedule for the Dublin PTG:
>
>
> https://docs.google.com/spreadsheets/d/e/2PACX-1vRmqAAQZA1rIzlNJpVp-X60-z6jMn_95BKWtf0csGT9LkDharY-mppI25KjiuRasmK413MxXcoSU7ki/pubhtml?gid
We've recently discovered an issue with the way we handle dependencies for
tripleo-ui. This is an explanation of the problem, and a proposed solution.
I'm looking for feedback.
Before the upgrade to zuul v3 in TripleO CI, we had two types of jobs for
tripleo-ui:
* Native npm jobs
* Undercloud in
On 01/19/2018 11:43 AM, Honza Pokorny wrote:
> We've recently discovered an issue with the way we handle dependencies for
> tripleo-ui. This is an explanation of the problem, and a proposed solution.
> I'm looking for feedback.
>
> Before the upgrade to zuul v3 in TripleO CI, we had two types of j
I remembered there are several discussions about action APIs in the past. This
is one discussion I can find:
http://lists.openstack.org/pipermail/openstack-dev/2016-December/109136.html .
An obvious alternative is to expose each action with an independent API
endpoint. For example:
* POST /ser
Hi Kuryr team,
I think Kuryr-libnetwork is ready to move out of beta status. I propose to
make the first 1.x release of Kuryr-libnetwork for Queens and cut a stable
branch on it. What do you think about this proposal?
Best regards,
Hongbin
_
Hey there,
We have just recently integrated MAGNUM into our OpenStack Distribution.
QUESTION:
When MAGNUM is creating the ‘instances’ for the COE master and minion nodes,
WHY does it create the instances with ports using ‘fixed-ips’ ?
- instead of just letting the instance’s port
Hi Andrea,
thanks for taking time to reply. I left some answers inline.
On Fri, Jan 19, 2018 at 9:08 AM, Andrea Frittoli
wrote:
>
>
> On Wed, Jan 17, 2018 at 7:27 PM Ihar Hrachyshka wrote:
>>
>> Hi all,
>
>
> Hi!
>>
>>
>> tl;dr I propose to switch to lib/neutron devstack library in Queens. I
>>
Happy Friday all.
Now that we are past the non-client lib freeze, we will need to have
stable/queens branches for those libs. For all libraries that did not miss the
freeze, I will be proposing the patches to get those stable branches created.
This should have been enforced as part of the last de
On Fri, Jan 19, 2018 at 12:23 PM, Ben Nemec wrote:
>
>
> On 01/18/2018 09:45 AM, Emilien Macchi wrote:
>
>> On Thu, Jan 18, 2018 at 6:34 AM, Or Idgar wrote:
>>
>>> Hi,
>>> we're encountering many timeouts for zuul gates in TripleO.
>>> For example, see
>>> http://logs.openstack.org/95/508195/28/
On Fri, Jan 19, 2018 at 11:23:45AM -0600, Ben Nemec wrote:
>
>
> On 01/18/2018 09:45 AM, Emilien Macchi wrote:
> > On Thu, Jan 18, 2018 at 6:34 AM, Or Idgar wrote:
> > > Hi,
> > > we're encountering many timeouts for zuul gates in TripleO.
> > > For example, see
> > > http://logs.openstack.org/9
40 matches
Mail list logo
