[openstack-dev] Election Season, PTL January 2017

Hello all! Election season is nearly here! Election details: https://governance.openstack.org/election/ Please read the stipulations and timelines for candidates and electorate contained in this governance documentation. Be aware, in the PTL elections if the program only has one candidate,

Re: [openstack-dev] [tc] Re: [kolla] A new kolla-salt deliverable

WFM – I’d be partly in favor of such an approach although I can’t speak for others. I think we should require some larger set then 2 individuals from the kolla-policy-core; perhaps a majority of active reviewers for some definition of active reviewers. Regards -steve -Original

Re: [openstack-dev] [tc] Re: [kolla] A new kolla-salt deliverable

So I agree with you that we need policy established here. What I'm getting at - which core teams will vote on inclusion of new deliverable? All of them? Just Kolla? This is grey area I'm referring to. What's kolla-k8s core team's business if somebody would like to add saltstack support? What I

Re: [openstack-dev] [all] Using \ for multiline statements

On Fri, Dec 23, 2016 at 1:11 PM, Monty Taylor wrote: > I think this is the most important point. We have automated style tools. > Humans should not be doing code review on code style. Humans should be > doing code review on logic and intent and whether a design is a good >

[openstack-dev] [tc] Re: [kolla] A new kolla-salt deliverable

Michal, Really what I was getting at was placing in the governance repository as a kolla deliverable. In days past we *always* voted on additions and removals of deliverables. It doesn’t seem like a gray area to me – we have always followed a voting pattern for adding and removal of

Re: [openstack-dev] [all] Using \ for multiline statements

On 12/22/2016 07:42 PM, Ian Cordasco wrote: > On Thu, Dec 22, 2016 at 6:02 PM, Sean McGinnis wrote: >>> >>> By the way, can we finally all agree that commit message titles need to be a >>> proper ('merican) English grammatically correct sentence that begins with a >>>

Re: [openstack-dev] [kolla] Collaboration between kolla and Helm upstream

Yes, thanks Steve. I already sent Lachlan this link, I hope recording will appear there:) Brandon, thank you for that! Cheers, Michal On 23 December 2016 at 08:23, Steven Dake (stdake) wrote: > Hey folks, > > > > Brandon Jozsa was kind enough to get some collaboration going

[openstack-dev] [freezer] No IRC meeting next week

Hi everyone, There will be no Freezer IRC meeting next week (29/12) because of the holidays. Next meeting will be in 2017 (06/01). I hope you all have very good holidays. Kind Regards, Pierre __ OpenStack Development

[openstack-dev] [neutron] neutron-server high CPU and RAM load when updating DHCP ports

We noticed an issue in one of our larger clouds (~700 hypervisors and ovs agents) where (Liberty) neutron-server CPU and RAM load would spike up quite a bit whenever a DHCP agent port was updated. So much load that processes were getting OOM killed on our API servers, and so many queries were

Re: [openstack-dev] [kolla] A new kolla-salt deliverable

Hello, Ok this is grey area we haven't had proper discussion yet, I agree. Since we decided to have separate core teams, I personally don't really see *why* we should have any form of vote for projects to use kolla containers. Things change when we talk about it being kolla deliverable, but what

[openstack-dev] [kolla] Collaboration between kolla and Helm upstream

Hey folks, Brandon Jozsa was kind enough to get some collaboration going between the OpenStack Kolla community and the Helm community within CNCF. My hope out of this effort is to build bridges between the OpenStack foundation and CNCF hosted by the Linux Foundation. We are starting small,

Re: [openstack-dev] [all] Intermittent gate failures across multiple projects

Proposed revert: https://review.openstack.org/414621 On Fri, Dec 23, 2016 at 4:56 PM, Valeriy Ponomaryov < vponomar...@mirantis.com> wrote: > Bug report for problem Andrey and Goutham mentioned is here: > https://bugs.launchpad.net/python-openstackclient/+bug/1652317 > > Valeriy > > On Fri, Dec

Re: [openstack-dev] [all] Intermittent gate failures across multiple projects

Bug report for problem Andrey and Goutham mentioned is here: https://bugs.launchpad.net/python-openstackclient/+bug/1652317 Valeriy On Fri, Dec 23, 2016 at 4:30 PM, Ravi, Goutham wrote: > Yes. It’s affecting manila tests as well: > > > > Patch:

Re: [openstack-dev] [all] Intermittent gate failures across multiple projects

Hi Steve, It looks like latest OSC is not the root of issue - the failure appeared several ours ago(5?!) and upper-constrains for OSC was updated several days ago(lxml was blocked more than 5 hours ago). Possibly, update of openstacksdk(https://review.openstack.org/#/c/414366/ ) causes new

Re: [openstack-dev] [all] Intermittent gate failures across multiple projects

Yes. It’s affecting manila tests as well: Patch: https://review.openstack.org/#/c/414286/ Failure: http://logs.openstack.org/86/414286/2/gate/gate-manila-tempest-minimal-dsvm-lvm-ubuntu-xenial/a79dc50/logs/devstacklog.txt.gz#_2016-12-23_13_26_11_470 Version of OSC:

Re: [openstack-dev] [tripleo] Adding a LateServices ResourceChain

On Thu, Dec 22, 2016 at 02:02:12PM -0500, Lars Kellogg-Stedman wrote: > I've been working along with a few others on some "opstools" > composable services for TripleO: that is, services that provide > things like centralized logging, performance monitoring, or > availability/health monitoring. >

Re: [openstack-dev] [all] Intermittent gate failures across multiple projects

Those look like they were introduced in the latest release, and related to the OpenStackSDK refactoring that hit openstackclient networking commands. We actually released the new version because folks were hitting similar errors, but for more often used commands (like listing security groups or

Re: [openstack-dev] Issues with libvirt transition 1.2.7 -> 2.0.0 (CentOS 7.3)

On Fri, Dec 23, 2016 at 1:37 PM Steve Gordon wrote: > - Original Message - > > From: "Neil Jerram" > > To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > > > > I appreciate that even libvirt

Re: [openstack-dev] [all] Using \ for multiline statements

There is a problem with the use of backslash at the end of the line, where if you also put a space after it, it no longer does what it seemingly should. Together with the fact, that you can achieve the same thing using () in pretty much all instances (it used to not be true for imports, but that

Re: [openstack-dev] Issues with libvirt transition 1.2.7 -> 2.0.0 (CentOS 7.3)

- Original Message - > From: "Neil Jerram" > To: "OpenStack Development Mailing List (not for usage questions)" > > > I appreciate that even libvirt 2.0.0 will be ancient history by now, to its > developers, but I am seeing further

[openstack-dev] [kolla] A new kolla-salt deliverable

Michal, I was thinking about kolla-salt and our Wednesday team meeting and the declaration you made about how it should be done. I personally feel it is mandatory we hold a vote of the core review teams to add a new deliverable. We have voted on the addition of every deliverable we have ever

Re: [openstack-dev] [all] Intermittent gate failures across multiple projects

Hi eveyone! I found two more failures related to openstackclient which had appeared recently: - "HttpException: Bad Request" while trying to set quotas via openstackclient

[openstack-dev] [kolla] Please use reno for all blueprints

Hey folks, I have seen many reviews hitting the queue without reno release notes. Its very simple and straightforward to create a reno release note. Simply run: reno –n blurb This creates a file in the releasenotes directory with a hash. Releasenotes should be committed with the commit in

Re: [openstack-dev] [all] Using \ for multiline statements

On Thu, 2016-12-22 at 17:52 -0600, Matt Riedemann wrote: > On 12/22/2016 5:28 PM, Sean McGinnis wrote: > > > > Looking for input from everyone, particularly those with more in- > > depth > > Python knowledge. > > > > In Cinder for some time we have been trying to enforce using () or > >