Re: [openstack-dev] [TripleO] TripleO/Ansible PTG session

On Thu, Sep 21, 2017 at 8:53 AM, Jiří Stránský wrote: > On 21.9.2017 12:31, Giulio Fidente wrote: > >> On 09/20/2017 07:36 PM, James Slagle wrote: >> >>> On Tue, Sep 19, 2017 at 8:37 AM, Giulio Fidente >>> wrote: >>> On 09/18/2017 05:37 PM, James

Re: [openstack-dev] [ptg] Simplification in OpenStack

> On Sep 25, 2017, at 16:52, Clint Byrum wrote: > > Excerpts from Jonathan D. Proulx's message of 2017-09-25 11:18:51 -0400: >> On Sat, Sep 23, 2017 at 12:05:38AM -0700, Adam Lawson wrote: >> >> :Lastly, I do think GUI's make deployments easier and because of that, I >> :feel

[openstack-dev] [OpenStack][Cinder][third-party][ci] Tintri Cinder CI failure

Hello, Tintri's Cinder CI started failing around Sept 19, 2017. There are 29 tests failing[1] with following errors [2][3][4]. Tintri Cinder driver inherit nfs cinder driver and it's available here[5]. Please let me know if anyone has recently seen these failures or has any pointers on how to

[openstack-dev] [keystone]] Trello board update

Hey all, I went through the Trello board for all our Queens work and updated all cards that needed "fleshing out". Each should have an accurate description of the work, why it's needed, and a checklist if applicable. If a card still doesn't make sense, please ping me or add the "needs fleshing

Re: [openstack-dev] [ptg] Simplification in OpenStack

Excerpts from Jonathan D. Proulx's message of 2017-09-25 11:18:51 -0400: > On Sat, Sep 23, 2017 at 12:05:38AM -0700, Adam Lawson wrote: > > :Lastly, I do think GUI's make deployments easier and because of that, I > :feel they're critical. There is more than one vendor whose built and >

Re: [openstack-dev] [stable][release] Last release date vs End of Life date

On Thu, Jun 29, 2017 at 01:34:05PM +0800, ChangBo Guo wrote: > Thanks tony for raising up this, better document this in some place :-) For the record this was just added to the queens schedule [1]. The deadline is this week but in reality early nest week would probably also be accepted. Yours

Re: [openstack-dev] [devstack] etcd v3.2.0?

On Fri, Jun 16, 2017 at 12:06:47PM +1000, Tony Breeds wrote: > Hi All, > I just push a review [1] to bump the minimum etcd version to > 3.2.0 which works on intel and ppc64le. I know we're pretty late in the > cycle to be making changes like this but releasing pike with a dependacy > on

[openstack-dev] [all][infra] Zuul v3 migration update

Hi, We started to migrate to Zuul v3 today, but ran into some problems which delayed us sufficiently that we're going to suspend activity until tomorrow. In the mean time, please consider the project-config repository frozen to all changes except those which are necessary for the migration. We

Re: [openstack-dev] [tc][nova][ironic][mogan] Evaluate Mogan project

Thanks Dmitry for the feedback, please see my response inline. On Mon, Sep 25, 2017 at 8:35 PM, Dmitry Tantsur wrote: > Hi! > > Thanks for raising this. I was interested in the project for some time, > but I never got a chance to wrap my head around. I also have a few

Re: [openstack-dev] [infra][docs][i18n][ptls] PDFs for project-specific docs with unified doc builds

[Topic tags added to subject line] Excerpts from Ian Y. Choi's message of 2017-09-22 07:29:23 +0900: > Hello, > > "Build PDF docs from rst-based guide documents" [1] was implemented in Ocata > cycle, and I have heard that there were a small conversation at the > Denver PTG > regarding getting

Re: [openstack-dev] [puppet][puppet-ceph] missing dependencies for openstacklib::openstackclient in metadata.json

On Mon, Sep 25, 2017 at 5:42 AM, Emil Enemærke wrote: > There is also missing dependency for openstack/keystone, which is also used > in ceph::rgw::keystone::auth line 63, 68, 75, 85 > > On Mon, Sep 25, 2017 at 1:00 PM, Emil Enemærke wrote: >> >> Hi >> >>

Re: [openstack-dev] vGPUs support for Nova

On 9/25/2017 5:40 AM, Jay Pipes wrote: On 09/25/2017 05:39 AM, Sahid Orentino Ferdjaoui wrote: There is a desire to expose the vGPUs resources on top of Resource Provider which is probably the path we should be going in the long term. I was not there for the last PTG and you probably already

Re: [openstack-dev] [TripleO] TripleO/Ansible PTG session

On 18/09/17 09:37 -0600, James Slagle wrote: On Wednesday at the PTG, TripleO held a session around our current use of Ansible and how to move forward. I'll summarize the results of the session. Feel free to add anything I forgot and provide any feedback or questions. We discussed the existing

Re: [openstack-dev] patches for simple typo fixes

Excerpts from Sean Dague's message of 2017-09-25 08:24:18 -0400: > On 09/25/2017 07:56 AM, Chris Dent wrote: > > On Fri, 22 Sep 2017, Paul Belanger wrote: > > > >> This is not a good example of encouraging anybody to contribute to the > >> project. > > > > Yes. This entire thread was a bit

Re: [openstack-dev] patches for simple typo fixes

On 09/25/2017 09:28 AM, Doug Hellmann wrote: > I'm less concerned with the motivation of someone submitting the > patches than I am with their effect. Just like the situation we had > with the bug squash days a year or so ago, if we had a poorly timed > set of these trivial patches coming in at

Re: [openstack-dev] patches for simple typo fixes

Excerpts from Sean Dague's message of 2017-09-25 09:42:08 -0400: > On 09/25/2017 09:28 AM, Doug Hellmann wrote: > > > I'm less concerned with the motivation of someone submitting the > > patches than I am with their effect. Just like the situation we had > > with the bug squash days a year or so

Re: [openstack-dev] [Release-job-failures][infra] Release of openstack-infra/zuul-sphinx failed

I assume someone has already noticed that this release failed, but I'm forwarding it to the dev list just in case. Excerpts from jenkins's message of 2017-09-25 14:46:58 +: > Build failed. > > - zuul-sphinx-tarball >

[openstack-dev] Forum Reminder! Submissions due by Sept 29th

Hello! This is a friendly reminder that all proposed Forum session leaders must submit their abstracts at: http://odsreg.openstack.org before 11:59PM UTC on Friday, September 29th! Cheers, Jimmy __ OpenStack

Re: [openstack-dev] [Openstack-operators] Forum Reminder! Submissions due by Sept 29th

Argh! Sorry everyone. We changed the link: http://forumtopics.openstack.org/cfp/create Mea culpa!! AMIT KUMAR JAISWAL September 25, 2017 at 8:34 AM Hi Jimmy. The above link you have given is broken and is saying "Internal Server Error". Please re-check the

Re: [openstack-dev] [octavia][sqlalchemy] Specify 'extend_existing=True' to redefine options and columns on an existing Table object.

I have sorted out the issue. There was fault in my code. Thanks for the time. On Sat, Sep 23, 2017 at 2:48 PM, Pradeep Singh wrote: > Hello All, > > I added two tables schema in patch https://review. > openstack.org/#/c/486499/, and when i run unit tests i am getting

[openstack-dev] [octavia] haproxy fails to receive datagram

Hi, all, I encounter some problems when using Octavia. After installing octavia with devstack, I create a load balancer named lb1 (VIP: 10.0.1.9, IP of VRRP port: 10.0.1.3) for a subnet (10.0.1.0/24), then a listener, a pool, and two members. All the resources are created successfully. The two

Re: [openstack-dev] vGPUs support for Nova

On 09/25/2017 05:39 AM, Sahid Orentino Ferdjaoui wrote: There is a desire to expose the vGPUs resources on top of Resource Provider which is probably the path we should be going in the long term. I was not there for the last PTG and you probably already made a decision about moving in that

[openstack-dev] [puppet][puppet-ceph] missing dependencies for openstacklib::openstackclient in metadata.json

Hi In class ceph::rgw::keystone::auth there is an include for ::openstacklib::openstackclient (line 61), but there is no dependency for it in the metadata.json file. Cheers Emil __ OpenStack Development Mailing List (not for

Re: [openstack-dev] vGPUs support for Nova

On Mon, Sep 25, 2017 at 09:29:25AM -0500, Matt Riedemann wrote: > On 9/25/2017 5:40 AM, Jay Pipes wrote: > > On 09/25/2017 05:39 AM, Sahid Orentino Ferdjaoui wrote: > > > There is a desire to expose the vGPUs resources on top of Resource > > > Provider which is probably the path we should be going

Re: [openstack-dev] Garbage patches for simple typo fixes

On 22/09/17 14:20 +, Jeremy Stanley wrote: On 2017-09-22 08:30:21 -0400 (-0400), Amrith Kumar wrote: [...] When can we take some concrete action to stop these same kinds of things from coming up again and again? Technical solutions to social problems rarely do more than increase

Re: [openstack-dev] [Release-job-failures][infra] Release of openstack-infra/zuul-sphinx failed

Jeremy Stanley writes: > On 2017-09-25 10:51:42 -0400 (-0400), Doug Hellmann wrote: >> I assume someone has already noticed that this release failed, but I'm >> forwarding it to the dev list just in case. > > Thanks for the heads up! And yes, it's currently under discussion in

Re: [openstack-dev] Garbage patches for simple typo fixes

On 2017-09-22 06:11 PM, Mike Perez wrote: On 21:21 Sep 21, Matt Riedemann wrote: I just wanted to highlight to people that there seems to be a series of garbage patches in various projects [1] which are basically doing things like fixing a single typo in a code comment, or very narrowly

Re: [openstack-dev] [octavia] haproxy fails to receive datagram

Hi Yipei, I just tried to reproduce this and was not successful. I setup a tenant network, added a web server to it, created a loadbalancer VIP on the tenant network, added the webserver as a member on the load balancer. I can curl from the tenant network qdhcp- netns without issue. Are you

Re: [openstack-dev] [Release-job-failures][infra] Release of openstack-infra/zuul-sphinx failed

On 2017-09-25 10:51:42 -0400 (-0400), Doug Hellmann wrote: > I assume someone has already noticed that this release failed, but I'm > forwarding it to the dev list just in case. Thanks for the heads up! And yes, it's currently under discussion in #openstack-infra but we're still trying to nail

Re: [openstack-dev] patches for simple typo fixes

On Mon, Sep 25 2017, Doug Hellmann wrote: >> I was trying to ignore the thread in the hopes it would die out quick. >> But torches and pitchforks all came out from the far corners, so I'm >> going to push back on that a bit. >> >> I'm not super clear why there is always so much outrage about

Re: [openstack-dev] [TripleO] TripleO/Ansible PTG session

- The ceph-ansible implementation done in Pike could be reworked to use this model. "config download" could generate playbooks that have hooks for calling external playbooks, or those hooks could be represented in the templates directly. The result would be the same either way though in that Heat

Re: [openstack-dev] [ptg] Simplification in OpenStack

On Sat, Sep 23, 2017 at 12:05:38AM -0700, Adam Lawson wrote: :Lastly, I do think GUI's make deployments easier and because of that, I :feel they're critical. There is more than one vendor whose built and :distributes a free GUI to ease OpenStack deployment and management. That's :a good start but

Re: [openstack-dev] patches for simple typo fixes

On 25/09/17 09:28 -0400, Doug Hellmann wrote: Excerpts from Sean Dague's message of 2017-09-25 08:24:18 -0400: On 09/25/2017 07:56 AM, Chris Dent wrote: > On Fri, 22 Sep 2017, Paul Belanger wrote: > >> This is not a good example of encouraging anybody to contribute to the >> project. > > Yes.

Re: [openstack-dev] Garbage patches for simple typo fixes

On 23/09/17 12:25 -0400, Doug Hellmann wrote: Excerpts from Qiming Teng's message of 2017-09-23 23:55:34 +0800: To some extent, I think Zhipeng is right. There are times we as a community have to do something beyond mentoring new developers. One of the reasons behind these patches are from the

Re: [openstack-dev] Garbage patches for simple typo fixes

On 22/09/17 14:47 -0400, Doug Hellmann wrote: Excerpts from Davanum Srinivas (dims)'s message of 2017-09-22 13:47:06 -0400: Doug, Howard (cc'ed) already did a bunch of reaching out especially on wechat. We should request his help. Howard, Can you please help with communications and follow up?

[openstack-dev] [nova] Running large instances with CPU pinning and OOM

Hello everyone, We're experiencing issues with running large instances (~60GB RAM) on fairly large NUMA nodes (4 CPUs, 256GB RAM) while using cpu pinning. The problem is that it seems that in some extreme cases qemu/KVM can have significant memory overhead (10-15%?) which nova-compute service

Re: [openstack-dev] vGPUs support for Nova

Sahid, Just share some background. XenServer doesn't expose vGPUs as mdev or pci devices. I proposed a spec about one year ago to make fake pci devices so that we can use the existing PCI mechanism to cover vGPUs. But that's not a good design and got strongly objection. After that, we

Re: [openstack-dev] Garbage patches for simple typo fixes

On 2017-09-25 12:12:23 -0400 (-0400), Anita Kuno wrote: > When I click this link I see two items. Perhaps the list can be > named 'help wanted list' and the point about it being the top 5 or > having a maximum of 5 items can be made in the text. Having a top > 5 list with 2 items may confuse the

Re: [openstack-dev] [all][QA][group-based-policy][zaqar][packaging_deb][fuel][networking-*] Marking <= mitaka EOL

On 2017-09-24 12:48:41 -0400 (-0400), Paul Belanger wrote: [...] > I just noticed our DIB image git cache is still referencing old > branches we have EOL'd. This is because we haven't deleted the > cache in some time. The fact that the cache needs manual cleaning is a bug, in my opinion. It would

Re: [openstack-dev] [ptg] Simplification in OpenStack

Hey Jay, I think a GUI with a default config is a good start. Much would need to happen to enable that of course but that's where my mind goes. Any talk about 'default' kind of infringes on what we've all strived to embrace; a cloud architecture without bakes in assumptions. A default-anything

[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. Decide on the

[openstack-dev] [neutron] Ocata moving to phase II

Hi all, with the latest Ocata release[1], stable/ocata branches now officially move to phase II support. The phase is defined in [2] as: "Only critical bugfixes and security patches are acceptable." In Neutron, it usually means that we may now allow fixes for High and Critical bugs only. (Plus

[openstack-dev] vGPUs support for Nova

There is a desire to expose the vGPUs resources on top of Resource Provider which is probably the path we should be going in the long term. I was not there for the last PTG and you probably already made a decision about moving in that direction anyway. My personal feeling is that it is premature.

Re: [openstack-dev] [TripleO] TripleO/Ansible PTG session

On Fri, Sep 22, 2017 at 4:17 PM, Jiří Stránský wrote: > On 22.9.2017 13:44, Giulio Fidente wrote: > >> On 09/21/2017 07:53 PM, Jiří Stránský wrote: >> >>> On 21.9.2017 18:04, Marios Andreou wrote: >>> On Thu, Sep 21, 2017 at 3:53 PM, Jiří Stránský

Re: [openstack-dev] [docs][ptls][install] Install guide vs. tutorial

> I completely agree consistency is more important, than bike shedding over the > name :) > To be honest, it would be easier to change everything to ‘guide’ – seeing as > all our URLs are ‘install-guide’. > But that’s the lazy in me speaking. > > Industry wise –

Re: [openstack-dev] [neutron][oslo.messaging][femdc]Topic names for every resource type RPC endpoint

Yeah, you could may be segment messages by zones/cells etc. Or group resources by buckets, for example taking the last 2-3 bytes of each object identifier. But you may need to do the math on how that's going to work, the more objects an agent needs to process, the more likely that it will

[openstack-dev] [nova] notification update week 39

Hi, Here is the status update / focus settings mail for w39. Bugs [Medium] https://bugs.launchpad.net/nova/+bug/1699115 api.fault notification is never emitted We still have to figure out what is the expected behavior here based on:

[openstack-dev] [tc][nova][ironic][mogan] Evaluate Mogan project

Hi folks, First of all, thanks for the audiences for Mogan project update in the TC room during Denver PTG. Here we would like to get more suggestions before we apply for inclusion. Speaking only for myself, I find the current direction of one API+scheduler for vm/baremetal/container

Re: [openstack-dev] [puppet][puppet-ceph] missing dependencies for openstacklib::openstackclient in metadata.json

There is also missing dependency for openstack/keystone, which is also used in ceph::rgw::keystone::auth line 63, 68, 75, 85 On Mon, Sep 25, 2017 at 1:00 PM, Emil Enemærke wrote: > Hi > > In class ceph::rgw::keystone::auth there is an include for >

Re: [openstack-dev] Garbage patches for simple typo fixes

On Fri, 22 Sep 2017, Paul Belanger wrote: This is not a good example of encouraging anybody to contribute to the project. Yes. This entire thread was a bit disturbing to read. Yes, I totally agree that mass patches that do very little are a big cost to reviewer and CI time but a lot of the

Re: [openstack-dev] patches for simple typo fixes

On 09/25/2017 07:56 AM, Chris Dent wrote: > On Fri, 22 Sep 2017, Paul Belanger wrote: > >> This is not a good example of encouraging anybody to contribute to the >> project. > > Yes. This entire thread was a bit disturbing to read. Yes, I totally > agree that mass patches that do very little are

Re: [openstack-dev] [tc][nova][ironic][mogan] Evaluate Mogan project

Hi! Thanks for raising this. I was interested in the project for some time, but I never got a chance to wrap my head around. I also have a few concerns - please see inline. On 09/25/2017 01:27 PM, Zhenguo Niu wrote: Hi folks, First of all, thanks for the audiences for Mogan project update