Re: [openstack-dev] [tripleo] Blocking gate - do not recheck / rebase / approve any patch now (please)

On Wed, Oct 25, 2017 at 1:59 PM, Emilien Macchi wrote: > Quick update before being afk for some hours: > > - Still trying to land https://review.openstack.org/#/c/513701 (thanks > Paul for promoting it in gate). Landed. > - Disabling voting on scenario001 and scenario004

Re: [openstack-dev] [all] [elections] Technical Committee Election Results

On Wed, Oct 25, 2017 at 10:06:46PM -0400, David Moreau Simard wrote: > Was it just me or did the "official" period for campaigning/questions was > awfully short ? > > The schedule [1] went: > ​TC Campaigning: (Start) Oct 11, 2017 23:59 UTC (End) Oct 14, 2017 23:45 > UTC​ The original was: -

Re: [openstack-dev] [all] [elections] Technical Committee Election Results

Was it just me or did the "official" period for campaigning/questions was awfully short ? The schedule [1] went: ​TC Campaigning: (Start) Oct 11, 2017 23:59 UTC (End) Oct 14, 2017 23:45 UTC​ ​That's three days, one of which was a saturday. Was it always this short ? It seems to me that this is

Re: [openstack-dev] [all] [elections] Technical Committee Election Results

On Wed, Oct 25, 2017 at 09:48:06PM +, Jeremy Stanley wrote: > On 2017-10-25 12:18:59 -0400 (-0400), Zane Bitter wrote: > [...] > > Can we maybe calculate the electorate size using the old method as well so > > that we can quantify how much of the dropoff (in theory it could be more > > than

Re: [openstack-dev] [all] [elections] Technical Committee Election Results

On Wed, Oct 25, 2017 at 12:18:59PM -0400, Zane Bitter wrote: > On 20/10/17 20:20, Tony Breeds wrote: > > > > Hi All, > > With the election behind us it's somewhat traditional to look at > > some simple stats from the elections: > > > >

Re: [openstack-dev] [all] [elections] Technical Committee Election Results

On Wed, Oct 25, 2017 at 11:05:44AM +0100, Chris Dent wrote: > On Tue, 24 Oct 2017, Tony Breeds wrote: > > > On Mon, Oct 23, 2017 at 09:35:34AM +0100, Jean-Philippe Evrard wrote: > > > > > I agree, we should care about not repeating this Pike trend. It looks > > > like Queens is better in terms

Re: [openstack-dev] [all] [elections] Technical Committee Election Results

On 2017-10-25 12:18:59 -0400 (-0400), Zane Bitter wrote: [...] > Can we maybe calculate the electorate size using the old method as well so > that we can quantify how much of the dropoff (in theory it could be more > than 100%) was due to the change in effective eligibility criteria vs. > organic

Re: [openstack-dev] [stable] Preping for the stable/newton EOL

On Wed, Oct 25, 2017 at 10:24:59AM -0500, Matt Riedemann wrote: > On 10/24/2017 9:57 PM, Tony Breeds wrote: > > The timing of the next phase is uncertain right now but I'd like to take > > care of: > > > > - openstack/nova > > Just a status update, but the final nova newton release is waiting on

Re: [openstack-dev] [stable] Preping for the stable/newton EOL

On Wed, Oct 25, 2017 at 01:11:53PM +0200, Dmitry Tantsur wrote: > The last ironic newton release was done, we're ready for EOL. Thanks that must've happened overnight. Yours Tony. signature.asc Description: PGP signature

Re: [openstack-dev] [stable] Preping for the stable/newton EOL

On Wed, Oct 25, 2017 at 10:11:01AM +0100, Jean-Philippe Evrard wrote: > On 25 October 2017 at 03:57, Tony Breeds wrote: > > On Tue, Oct 24, 2017 at 05:11:15PM +1100, Tony Breeds wrote: > >> On Fri, Oct 06, 2017 at 10:15:56AM +1100, Tony Breeds wrote: > >> > On Wed, Oct

Re: [openstack-dev] [TripleO][infra][CI] Moving OVB jobs from RH1 cloud to RDO cloud, plan

We're currently running with a max-servers of 80 for the TripleO tenant. This number doesn't include OVB nodes. When taking into account OVB nodes, we are already nearing vCPU capacity and could consider raising the overcommit ratio from 2.0 to 4.0 to make use of the available RAM. See the rough

Re: [openstack-dev] [tripleo] Blocking gate - do not recheck / rebase / approve any patch now (please)

Quick update before being afk for some hours: - Still trying to land https://review.openstack.org/#/c/513701 (thanks Paul for promoting it in gate). - Disabling voting on scenario001 and scenario004 container jobs: https://review.openstack.org/#/c/515188/ - overcloudrc/keystone v2 workaround:

Re: [openstack-dev] [policy] AWS IAM session

I'm not sure how I didn't include -operators the first time around, but adding them to this thread now. TL;DR We're going through policy/RBAC for other systems to get an idea of how we want to shape OpenStack's policy and RBAC model. We're going to meet next Wednesday at 15:00 UTC. The meeting

Re: [openstack-dev] [policy] AWS IAM session

I've recapped the notes from today's session and I'll post a follow up with the recording as soon as it's available. All notes can be found in the etherpad (agreement and outcomes are in *bold*)**[0]. Next week at the same time (15:00 UTC) we will continue going through AWS IAM flows. While

Re: [openstack-dev] [TripleO][infra][CI] Moving OVB jobs from RH1 cloud to RDO cloud, plan

Overall sounds good. A couple of comments inline. On 10/23/2017 05:46 AM, Sagi Shnaidman wrote: Hi, as you know we prepare transition of all OVB jobs from RH1 cloud to RDO cloud, also a few long multinode upgrades jobs as well. We prepared a workflow of transition below, please feel free to

Re: [openstack-dev] [ironic] [Openstack-operators] replace node "tags" with node "traits"

Hi, On Wed, Oct 25, 2017 at 10:17 AM, Loo, Ruby wrote: > Hello ironic'ers, > > A while ago, we approved a spec to add node tag support to ironic [1]. The > feature itself did not land yet (although some of the code has). Now that > the (nova) community has come up with

Re: [openstack-dev] [release][infra][zuul][zuulv3][horizon][neutron] project-specific release job templates

Excerpts from Doug Hellmann's message of 2017-10-24 09:42:25 -0400: > The neutron queens milestone release is held up right now because > some of the repositories are using a release job template that isn't > recognized by the validation code in the releases repository. I'm > trying to decide

Re: [openstack-dev] [all] [elections] Technical Committee Election Results

On 20/10/17 20:20, Tony Breeds wrote: Hi All, With the election behind us it's somewhat traditional to look at some simple stats from the elections: +--+---+---+---+ | Election | Electorate (delta %) | Voted (delta %) |

Re: [openstack-dev] [stable] Preping for the stable/newton EOL

On 10/24/2017 9:57 PM, Tony Breeds wrote: The timing of the next phase is uncertain right now but I'd like to take care of: - openstack/nova Just a status update, but the final nova newton release is waiting on two changes: 1. https://review.openstack.org/#/c/514685/ - in the gate, should

[openstack-dev] [nova] Notification update week 43

Hi, Here is the status update / focus settings mail for w43. Bugs [High] https://bugs.launchpad.net/nova/+bug/1706563 TestRPC.test_cleanup_notifier_null fails with timeou [High] https://bugs.launchpad.net/nova/+bug/1685333 Fatal Python error: Cannot recover from stack overflow. - in py35

Re: [openstack-dev] [os-vif] [nova] Changes to os-vif cores

+1 On 10/24/2017 10:32 AM, Stephen Finucane wrote: Hey, I'm not actually sure what the protocol is for adding/removing cores to a library project without a PTL, so I'm just going to put this out there: I'd like to propose the following changes to the os-vif core team. - Add 'nova-core'

Re: [openstack-dev] [trove] retiring trove-integration?

Agreed, please also see[1]. -amrith [1] https://review.openstack.org/515084 On Wed, Oct 25, 2017 at 3:28 AM, Andreas Jaeger wrote: > Trove team, > > with the retirement of stable/newton, you can now retire > trove-integration AFAIU. > > For information on what to do, see: >

Re: [openstack-dev] [tripleo] Blocking gate - do not recheck / rebase / approve any patch now (please)

Status: - Heat Convergence switch *might* be a reason why overcloud timeout so much. Thomas proposed to disable it: https://review.openstack.org/515077 - Every time a patch fails in the tripleo gate queue, it reset the gate. I proposed to remove this common queue:

Re: [openstack-dev] [ironic] [Openstack-operators] replace node "tags" with node "traits"

Sending again, I don't think it went to openstack-operators@. --ruby On Wed, Oct 25, 2017 at 10:17 AM, Loo, Ruby wrote: > Hello ironic'ers, > > > > A while ago, we approved a spec to add node tag support to ironic [1]. The > feature itself did not land yet (although some of

[openstack-dev] [ironic] [Openstack-operators] replace node "tags" with node "traits"

Hello ironic'ers, A while ago, we approved a spec to add node tag support to ironic [1]. The feature itself did not land yet (although some of the code has). Now that the (nova) community has come up with traits, ironic wants to support node traits, and there is a spec proposing that [2]. At

Re: [openstack-dev] [ironic] Kernel parameters needed to boot from iscsi

This is a bit offtopic, but a couple of comments on BFV. On 10/25/2017 03:55 PM, Derek Higgins wrote: On 25 October 2017 at 13:03, Dmitry Tantsur wrote: (ooops, I somehow missed this email. sorry!) Hi Yolanda, On 10/16/2017 11:06 AM, Yolanda Robla Mota wrote: Hi

Re: [openstack-dev] [Swift] SPDK uses Swift as a target system to support k-v store

Hi, all I am so sorry. I might not be able to attend IRC meetings (#openstack-swift) tonight because of the bad Internet. I have tried many times but I still can not login. If you have any suggestions on my topic(“SPDK uses Swift as a target system to support k-v store"), please let me know.

Re: [openstack-dev] [ironic] Kernel parameters needed to boot from iscsi

On 25 October 2017 at 13:03, Dmitry Tantsur wrote: > (ooops, I somehow missed this email. sorry!) > > Hi Yolanda, > > On 10/16/2017 11:06 AM, Yolanda Robla Mota wrote: >> >> Hi >> Recently i've been helping some customers in the boot from ISCSI feature. >> So far everything

[openstack-dev] [acceleration]Cyborg Team Weekly Meeting 2017.10.25

Hi Team, Sorry again that due to my ongoing business trip i cannot lead the discussion for this week's team meeting, however as we discussed in the IRC channel, core members are more than welcomed to host the meeting and lead the discussions. i will try to join on my cell phone :P -- Zhipeng

Re: [openstack-dev] [ceilometer] the workload partition willcauseconsumer disappeared

I use 5.10.2 > I test newton 5.10.2, and in ceilometer agent notification, the log shows > 2017-10-21 03:33:19.779 225636 ERROR root [-] Unexpected exception > occurred 60 time(s)... retrying. > 2017-10-21 03:33:19.779 225636 ERROR root Traceback (most recent call last): > 2017-10-21

[openstack-dev] [tripleo] Blocking gate - do not recheck / rebase / approve any patch now (please)

We have been working very hard to get a package/container promotions (since 44 days) and now our blocker is https://review.openstack.org/#/c/513701/. Because the gate queue is huge, we decided to block the gate and kill all the jobs running there until we can get

Re: [openstack-dev] [ironic] Kernel parameters needed to boot from iscsi

> Hmm, are we talking about IPA or user images? IPA always PXE boots, no > matter what boot_option we use. For user images with boot_option=local our > only bet is using the ansible deploy interface, I think (please review it!) > User images, i'm talking about user images (specifically about

Re: [openstack-dev] [ceilometer] the workload partition will causeconsumer disappeared

On 25/10/17 03:25 AM, 李田清 wrote: > I test newton 5.10.2, and in ceilometer agent notification, the log shows > 2017-10-21 03:33:19.779 225636 ERROR root [-] Unexpected exception > occurred 60 time(s)... retrying. > 2017-10-21 03:33:19.779 225636 ERROR root Traceback (most recent call last): >

Re: [openstack-dev] [ironic] Kernel parameters needed to boot from iscsi

On 10/25/2017 02:15 PM, Yolanda Robla Mota wrote: Answering inline... Note that we only support BFV in the form of booting from a cinder volume officially. We haven't looked into iBFV in depth. I have been testing that on the context of booting from SAN. It is at deploy time, in the

Re: [openstack-dev] [ironic] Kernel parameters needed to boot from iscsi

Answering inline... Note that we only support BFV in the form of booting from a cinder volume > officially. We haven't looked into iBFV in depth. > I have been testing that on the context of booting from SAN. It is at deploy time, in the context of TripleO, in the undercloud. At that point no

Re: [openstack-dev] [tc] [all] TC Report 43

On 24/10/17 19:26 +0100, Chris Dent wrote: # TC Participation At last Thursday's [office hours](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2017-10-19.log.html#t2017-10-19T15:01:02) Emilien asked, as a thought experiment, what people thought of the idea of TC term

Re: [openstack-dev] [ironic] Ironic 3rd Party CI Meetings

Hi! Sorry, I've somehow lost this email. This slot will work for me personally. On 09/26/2017 10:23 PM, rajini.kart...@dell.com wrote: *Dell - Internal Use - Confidential * Hi all, It was actually discussed in irc, after the ironic meeting yesterday that we will have weekly/biweekly 3^rd

Re: [openstack-dev] [keystoneauth] [osc] [ironic] Usage of none loader in the CLI

Hi! Thanks for raising this. On 10/19/2017 01:11 PM, Vladyslav Drok wrote: Hi! I'd like to discuss the usage of the new noauth plugin to keystoneauth, which was introduced in [1]. The docstring of the loader says it is intended to be used during adapter initialization along with

Re: [openstack-dev] [ironic] Kernel parameters needed to boot from iscsi

(ooops, I somehow missed this email. sorry!) Hi Yolanda, On 10/16/2017 11:06 AM, Yolanda Robla Mota wrote: Hi Recently i've been helping some customers in the boot from ISCSI feature. So far everything was working, but we had a problem when booting the deployment image. It needed specifically

Re: [openstack-dev] [stable] Preping for the stable/newton EOL

On 10/25/2017 04:57 AM, Tony Breeds wrote: On Tue, Oct 24, 2017 at 05:11:15PM +1100, Tony Breeds wrote: On Fri, Oct 06, 2017 at 10:15:56AM +1100, Tony Breeds wrote: On Wed, Oct 04, 2017 at 02:51:06PM +1100, Tony Breeds wrote: I'll prep the list of repos that will be tagged EOL real soon now

Re: [openstack-dev] [all] [elections] Technical Committee Election Results

On Tue, 24 Oct 2017, Tony Breeds wrote: On Mon, Oct 23, 2017 at 09:35:34AM +0100, Jean-Philippe Evrard wrote: I agree, we should care about not repeating this Pike trend. It looks like Queens is better in terms of turnout (see the amazing positive delta!). However, I can't help but noticing

Re: [openstack-dev] [tc] [stable] [tripleo] [kolla] [ansible] [puppet] Proposing changes in stable policy for installers

On 24/10/17 15:35 -0700, Emilien Macchi wrote: I figured that Sydney would be a great opportunity to have face2face discussion around this topic, and I commit to be there and try to make progress on this discussion. I would love to get some people representing their deployment projects and

Re: [openstack-dev] [stable] Preping for the stable/newton EOL

On 25 October 2017 at 03:57, Tony Breeds wrote: > On Tue, Oct 24, 2017 at 05:11:15PM +1100, Tony Breeds wrote: >> On Fri, Oct 06, 2017 at 10:15:56AM +1100, Tony Breeds wrote: >> > On Wed, Oct 04, 2017 at 02:51:06PM +1100, Tony Breeds wrote: >> > > I'll prep the list of

Re: [openstack-dev] [TripleO] roles_data.yaml equivalent in containers

On Wed, Oct 25, 2017 at 6:41 AM, Abhishek Kane wrote: > > Hi, > > > > In THT I have an environment file and corresponding puppet service for > Veritas HyperScale. > >

Re: [openstack-dev] [os-vif] [nova] Changes to os-vif cores

> -Original Message- > From: Sahid Orentino Ferdjaoui [mailto:sferd...@redhat.com] > Sent: Wednesday, October 25, 2017 11:22 AM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [os-vif] [nova] Changes

Re: [openstack-dev] [os-vif] [nova] Changes to os-vif cores

On Tue, Oct 24, 2017 at 03:32:15PM +0100, Stephen Finucane wrote: > Hey, > > I'm not actually sure what the protocol is for adding/removing cores to a > library project without a PTL, so I'm just going to put this out there: I'd > like to propose the following changes to the os-vif core team. >

[openstack-dev] [trove] retiring trove-integration?

Trove team, with the retirement of stable/newton, you can now retire trove-integration AFAIU. For information on what to do, see: https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project I just pushed out two changes for stable/newton retirement that also take care of step 1 of

Re: [openstack-dev] [ceilometer] the workload partition will causeconsumer disappeared

On 2017-10-23 09:57 PM, 李田清 wrote: > We test ceilometer workload partition, and find even with one > rabbitmq server, the ceilometer-pipe > will lost its consumers. Does anyone know this? > I configure, batch_size =1, batch_timeout =1, > and pipeline_processing_queues = 1. >