[openstack-dev] [oslo] Rocky PTG planning

Hi , The Dublin PTG is closing, It' time to collect topics before the PTG. Just put your idea or discussion in https://etherpad.openstack.org/p/oslo-ptg-rocky -- ChangBo Guo(gcb) Community Director @EasyStack __ OpenStack

Re: [openstack-dev] [oslo] proposing Stephen Finucan for oslo-core

+1 for stephenfin. 2018-01-09 1:34 GMT+08:00 Ben Nemec : > Definite +1 > > > On 01/08/2018 08:55 AM, Doug Hellmann wrote: > >> Stephen (sfinucan) has been working on pbr, oslo.config, and >> oslo.policy and reviewing several of the other Oslo libraries for >> a while now.

Re: [openstack-dev] [vitrage] rules in vitrage_aggregated_state()

Forgot to paste the link to the related code: https://git.openstack.org/cgit/openstack/vitrage/tree/vitrage/entity_graph/mappings/datasource_info_mapper.py#n61 On Tue, Jan 9, 2018 at 2:34 PM Yujun Zhang (ZTE) wrote: > Hi root causers > > I have been inspecting the

Re: [openstack-dev] [os-vif]

On 2018-01-09 07:00, Sriharsha Basavapatna wrote: > Hi, > > I've uploaded a patch for review: > https://review.openstack.org/#/c/531674/ > > This is the first time I'm submitting a patch on openstack. I'd like Welcome to OpenStack, Harsha. Please read

[openstack-dev] [vitrage] rules in vitrage_aggregated_state()

Hi root causers I have been inspecting the code about aggregated state recently and have a question regarding the rules. The "not" operator in the if clause confuses me. If it is not a configured data source, how do we apply the aggregation rules? It seems this is handled in else clause.

Re: [openstack-dev] [os-vif]

On 2018-01-09 07:00, Sriharsha Basavapatna wrote: > Hi, > > I've uploaded a patch for review: > https://review.openstack.org/#/c/531674/ > > This is the first time I'm submitting a patch on openstack. I'd like > to add code reviewers on this patch. I'd appreciate if you could point > me to any

Re: [openstack-dev] [os-vif]

Hi Sriharsha, You can check the core reviewers for os-vif here:- https://review.openstack.org/#/admin/groups/1175,members or from system:- ssh -p 29418 @review.openstack.org gerrit ls-members os-vif-core (This can be run from the system for which you have added the puplic keys to gerrit) To

Re: [openstack-dev] [requirements][mistral][vitrage][octavia][taskflow][watcher] Networkx version 2.0

We (Mistral) are ready to react too whenever the version is bumped. IMO, the sooner the better. Thanks Renat Akhmerov @Nokia On 9 Jan 2018, 04:00 +0700, Matthew Thode , wrote: > On 17-12-20 10:56:50, Matthew Thode wrote: > > On 17-12-20 15:51:17, Afek, Ifat (Nokia -

[openstack-dev] [os-vif]

Hi, I've uploaded a patch for review: https://review.openstack.org/#/c/531674/ This is the first time I'm submitting a patch on openstack. I'd like to add code reviewers on this patch. I'd appreciate if you could point me to any guidelines on how to pick reviewers for a given project (os-vif

Re: [openstack-dev] [infra][tempest][devstack][congress] tempest.config.CONF.service_available changed on Jan 2/3?

On 1/7/18, 9:27 PM, "Ghanshyam Mann" wrote: >On Sat, Jan 6, 2018 at 3:41 PM, Chandan kumar >wrote: >> Hello Eric, >> >> On Sat, Jan 6, 2018 at 4:46 AM, Eric K wrote: >>> Seems that sometime between 1/2 and 1/3 this

[openstack-dev] [openstack-helm] normal team meeting tomorrow

OpenStack-Helm team: Due to availability of some folks who want to participate in our monthly CI/CD-focused meeting, we're going to push it back to 1/16. Tomorrow's (1/9) meeting will be a normal weekly meeting instead. Thanks! Matt

Re: [openstack-dev] [ResMgmt SIG]Proposal to form Resource Management SIG

Hi Eric, Glad to count you in :) On Tue, Jan 9, 2018 at 4:57 AM, Eric Fried wrote: > > I think having a bi-weekly cross-project (or even cross-ecosystem if > > we're talking about OpenStack+k8s) status email reporting any big events > > in the resource tracking world would

Re: [openstack-dev] [ResMgmt SIG]Proposal to form Resource Management SIG

Agree 100% to avoid regular meeting and it is better to have bi-weekly email report. Meeting should be arranged event based, and I think given the status of OpenStack community's work on resource provider, mostly what we need to do is attend k8s meetings (sig-scheduler, wg-resource-management,

[openstack-dev] [designate] state of pdns4 backend

Hi Stackers, I see that we moved from PowerDNS Backend to PDNS4 backend, I have a few questions in that regard: 1. Should powerdns 3.4 (with PowerDNS backend) continue to work fine on Pike OpenStack? 2. Why did we change the default backend to BIND9? 3. How feasible is moving from one backend

Re: [openstack-dev] [congress] generic push driver

From: Tim Hinrichs Date: Monday, January 8, 2018 at 7:31 AM To: Eric Kao Cc: "OpenStack Development Mailing List (not for usage questions)" Subject: Re: [congress] generic push driver > It's probably worth

Re: [openstack-dev] [congress] generic push driver

Hi Ifat, From: "Afek, Ifat (Nokia - IL/Kfar Sava)" Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Sunday, January 7, 2018 at 4:00 AM To: "OpenStack Development Mailing List (not for usage questions)"

[openstack-dev] [neutron] Rocky PTG planning

Hi, I have started an etherpad ( https://etherpad.openstack.org/p/neutron-ptg-rocky) to start planning the topics we are going to discuss in the Neutron sessions during the Rocky PTG in Dublin. At this point in time, it is entirely free form. Just make sure you put your name and / or IRC nickname

Re: [openstack-dev] [requirements][mistral][vitrage][octavia][taskflow][watcher] Networkx version 2.0

On 17-12-20 10:56:50, Matthew Thode wrote: > On 17-12-20 15:51:17, Afek, Ifat (Nokia - IL/Kfar Sava) wrote: > > Hi, > > > > There is an open bug in launchpad about the new release of Networkx 2.0, > > that is backward incompatible with versions 1.x [1]. > > Is there a plan to change the Networkx

Re: [openstack-dev] [ResMgmt SIG]Proposal to form Resource Management SIG

> I think having a bi-weekly cross-project (or even cross-ecosystem if > we're talking about OpenStack+k8s) status email reporting any big events > in the resource tracking world would be useful. As far as regular > meetings for a resource management SIG, I'm +0 on that. I prefer to have >

[openstack-dev] [Neutron] Bug deputy report

- https://bugs.launchpad.net/neutron/+bug/1741954: create_and_list_trunk_subports rally scenario failed with timeouts. Armando Migliaccio assigned to it - CRITICAL: https://bugs.launchpad.net/neutron/+bug/1741889 functional: DbAddCommand sometimes times out after 10 seconds. This is

Re: [openstack-dev] [ResMgmt SIG]Proposal to form Resource Management SIG

On 01/08/2018 12:26 PM, Zhipeng Huang wrote: Hi all, With the maturing of resource provider/placement feature landing in OpenStack in recent release, and also in light of Kubernetes community increasing attention to the similar effort, I want to propose to form a Resource Management SIG as a

Re: [openstack-dev] [nova] Working toward Queens feature freeze and RC1

> From: Matt Riedemann > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 01/03/2018 07:03 PM > Subject: [openstack-dev] [nova] Working toward Queens feature freeze and RC1 > ... snip ... > The rest of the

[openstack-dev] [neutron][all] nova_metadata_ip removal

Hi, As part of the normal deprecate/removal process, the 'nova_metadata_ip' option is being removed from neutron as it was replaced with 'nova_metadata_host' in the Pike cycle, https://review.openstack.org/#/c/518836/ Codesearch did find various repos still using the old value, so I posted

Re: [openstack-dev] [infra][requirements][cinder] Handling requirements for driverfixes branches

Excerpts from Eric Harney's message of 2018-01-08 14:05:35 -0500: > Hi all, > > I'm trying to sort out how to run unit tests on Cinder driverfixes branches. > > These branches are similar to stable branches, but live longer (and have > a different set of rules for what changes are appropriate).

[openstack-dev] [ironic] this week's priorities and subteam reports

Hi, We are glad to present this week's priorities and subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. This Week's Priorities (as of the weekly ironic meeting) 1. ironic-lib patches

[openstack-dev] [infra][requirements][cinder] Handling requirements for driverfixes branches

Hi all, I'm trying to sort out how to run unit tests on Cinder driverfixes branches. These branches are similar to stable branches, but live longer (and have a different set of rules for what changes are appropriate). In order for unit tests to work on these branches, requirements need to be

Re: [openstack-dev] [reno] questions about reno

Excerpts from Gaetan's message of 2018-01-08 17:59:55 +0100: > Hello > > Thanks for your answers! > > - unreleased notes appear in release note with a title such as "0.1.0-2". > > > Is it possible to not have any title or use "0.1.0-dev2" pattern like > > pbr ? > > > > I'm not sure why it

Re: [openstack-dev] [nova] [libvirt] [scaleio] ScaleIO libvirt volume driver native mode

On the surface, I have no problems with this. Can you send me the measurements and an idea of what the patch would look like? Please use my work email at eric.yo...@dell.com Eric On 1/8/18, 1:35 PM, "Matt Riedemann" wrote: >On 1/8/2018 8:59 AM, Balázs Gibizer wrote:

Re: [openstack-dev] [nova] [libvirt] [scaleio] ScaleIO libvirt volume driver native mode

On 1/8/2018 8:59 AM, Balázs Gibizer wrote: Two years ago a patch merged [1] that set AIO mode of some of the libivrt volume drivers to 'native' instead of the default 'threading'. At that time the ScaleIO driver was not modified. Recently we did some measurements (on Mitaka base) and we think

[openstack-dev] [nova] Rocky PTG early planning

As the Queens release winds to a close, I've started thinking about topics for Rocky that can be discussed at the PTG. I've created an etherpad [1] for just throwing various topics in there, completely free-form at this point; just remember to add your name next to any topic you add. [1]

Re: [openstack-dev] [oslo] proposing Stephen Finucan for oslo-core

Definite +1 On 01/08/2018 08:55 AM, Doug Hellmann wrote: Stephen (sfinucan) has been working on pbr, oslo.config, and oslo.policy and reviewing several of the other Oslo libraries for a while now. His reviews are always helpful and I think he would make a good addition to the oslo-core team.

[openstack-dev] [Women of OpenStack] Kicking Off a New Year!

Hello, Today, Monday January 8th, we will be kicking off a new year of meetings for the Women of OpenStack! Things have evolved a lot in the last few months and we are excited to get started on our continued refresh. If you are interested in what we are up to and want to get involved, or just

[openstack-dev] [ResMgmt SIG]Proposal to form Resource Management SIG

Hi all, With the maturing of resource provider/placement feature landing in OpenStack in recent release, and also in light of Kubernetes community increasing attention to the similar effort, I want to propose to form a Resource Management SIG as a contact point for OpenStack community to

Re: [openstack-dev] [os-api-ref][doc] Adding openstack-doc-core to os-api-ref

On Thu, 4 Jan 2018 16:06:53 + Graham Hayes wrote: > On 04/01/18 15:39, Stephen Finucane wrote: > > I'm not sure what the procedure for this is but here goes. > > > > I've noticed that the 'os-api-ref' project seems to have its own group > > of cores [1], many of whom are no

Re: [openstack-dev] [reno] questions about reno

Hello Thanks for your answers! - unreleased notes appear in release note with a title such as "0.1.0-2". > > Is it possible to not have any title or use "0.1.0-dev2" pattern like > pbr ? > > I'm not sure why it matters, but if you want to work on that patch I'll > help with reviews. > Ok, I'll

Re: [openstack-dev] [oslo] proposing Stephen Finucan for oslo-core

+1 for Stephen! On Mon, Jan 8, 2018 at 9:55 AM, Doug Hellmann wrote: > Stephen (sfinucan) has been working on pbr, oslo.config, and > oslo.policy and reviewing several of the other Oslo libraries for > a while now. His reviews are always helpful and I think he would > make

Re: [openstack-dev] [tripleo] FFE Select Roles TripleO-UI

On Mon, Jan 8, 2018 at 3:56 AM, Jiri Tomasek wrote: > Hello, > > I’d like to request an FFE to finish GUI work on roles management, > specifically listing of roles and selection of roles for deployment. This > feature is one of the main goals of current cycle. The pending

[openstack-dev] [magnum] fedora atomic image with kubernetes with a CRI = frakti or clear containers

Hey there, I am currently running magnum with the fedora-atomic image that is installed as part of the devstack installation of magnum. This fedora-atomic image has kubernetes with a CRI of the standard docker container. Where can i find (or how do i build) a fedora-atomic image with

Re: [openstack-dev] [congress] generic push driver

It's probably worth considering PATCH instead of PUT for updating the table. http://restcookbook.com/HTTP%20Methods/patch/ You could also think about using JSON-patch to describe the requested update. It provides fine-grained update semantics: https://tools.ietf.org/html/rfc6902 Tim On Fri,

Re: [openstack-dev] [oslo] proposing Stephen Finucan for oslo-core

Excerpts from Doug Hellmann's message of 2018-01-08 09:55:26 -0500: > Stephen (sfinucan) has been working on pbr, oslo.config, and Oops, that's stephenfin. Sorry for the confusion. Doug __ OpenStack Development Mailing List

Re: [openstack-dev] [oslo] proposing Stephen Finucan for oslo-core

+1 from an oslo.policy perspective, his reviews have really been helping me out there. On 01/08/2018 08:58 AM, Jay Pipes wrote: > big +1 from me. > > On 01/08/2018 09:55 AM, Doug Hellmann wrote: >> Stephen (sfinucan) has been working on pbr, oslo.config, and >> oslo.policy and reviewing several

Re: [openstack-dev] [oslo] proposing Stephen Finucan for oslo-core

+1 from me. Thanks, Dims On Mon, Jan 8, 2018 at 9:58 AM, Jay Pipes wrote: > big +1 from me. > > > On 01/08/2018 09:55 AM, Doug Hellmann wrote: >> >> Stephen (sfinucan) has been working on pbr, oslo.config, and >> oslo.policy and reviewing several of the other Oslo libraries

[openstack-dev] [nova] [libvirt] [scaleio] ScaleIO libvirt volume driver native mode

Hi, Two years ago a patch merged [1] that set AIO mode of some of the libivrt volume drivers to 'native' instead of the default 'threading'. At that time the ScaleIO driver was not modified. Recently we did some measurements (on Mitaka base) and we think that the ScaleIO volume driver could

Re: [openstack-dev] [oslo] proposing Stephen Finucan for oslo-core

big +1 from me. On 01/08/2018 09:55 AM, Doug Hellmann wrote: Stephen (sfinucan) has been working on pbr, oslo.config, and oslo.policy and reviewing several of the other Oslo libraries for a while now. His reviews are always helpful and I think he would make a good addition to the oslo-core

[openstack-dev] [oslo] proposing Stephen Finucan for oslo-core

Stephen (sfinucan) has been working on pbr, oslo.config, and oslo.policy and reviewing several of the other Oslo libraries for a while now. His reviews are always helpful and I think he would make a good addition to the oslo-core team. As per our usual practice, please reply here with a +1 or -1

Re: [openstack-dev] [reno] questions about reno

Excerpts from Gaetan's message of 2018-01-06 13:33:20 +0100: > Hello > > I played this week with reno and i really like it, but I have a bunch of > question: > - unreleased notes appear in release note with a title such as "0.1.0-2". > Is it possible to not have any title or use "0.1.0-dev2"

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

Hi, Here is the status update / focus settings mail for 2018 w2. Bugs [High] https://bugs.launchpad.net/nova/+bug/1737201 TypeError when sending notification during attach_interface Fix merged to master. Backports have been proposed: * Pike: https://review.openstack.org/#/c/531745/ *

Re: [openstack-dev] [puppet] Ubuntu problems + Help needed

Hi Tobias, I think that's mainly the biggest issue we were dealing with which forced us to stop Ubuntu from being voting. I'm really not sure why this is happening but it's happening only in Ubuntu. Thanks, Mohammed On Sun, Jan 7, 2018 at 8:39 AM, Tobias Urdin

[openstack-dev] [tripleo] FFE Select Roles TripleO-UI

Hello, I’d like to request an FFE to finish GUI work on roles management, specifically listing of roles and selection of roles for deployment. This feature is one of the main goals of current cycle. The pending patches are ready to be merged, mostly just waiting for tripleo-common patches to

Re: [openstack-dev] [manila] [NEEDACTION] CI changes due to manila tempest tests new repository

Hi all! Some late info for those not running DevStack gate, my migration took three additions: 1) add the git checkout command as recommended 2) add "enable_plugin manila-tempest-plugin https://github.com/openstack/manila-tempest-plugin; to DevStacks local.conf 3) add running the setup.py command