Re: [openstack-dev] [neutron][stadium] Query regarding procedure for inclusion in Neutron Stadium

hi, On Fri, Sep 23, 2016 at 4:20 AM, Armando M. wrote: > > > On 22 September 2016 at 00:46, reedip banerjee wrote: >> >> Dear Neutron Core members, >> >> I have a query regarding the procedure for inclusion in the Neutron >> Stadium. >> I wanted to know if

[openstack-dev] What's Up, Doc? 23 September

Hi everyone, Newton goes out in just two weeks, and the release team and I have been busy working through release tasks in preparation. Don't forget that you can contact any of us (or just send mail to the docs mailing list) if you have any questions about the Newton docs release. I'm also

Re: [openstack-dev] floating IP is DOWN

Probably that LOG statement is a line added for debugging purposes. There are several probable causes for a floating ip being down. If you see any traceback in the neutron server or l3-agent that will probably immediately reveal the root cause. On the other hand, lack of any traceback might

Re: [openstack-dev] [security] [salt] Removal of Security and OpenStackSalt project teams from the Big Tent

Steven, Fair point. Thanks, Dims On Thu, Sep 22, 2016 at 11:04 PM, Steven Dake (stdake) wrote: > Dims, > > This isn’t any of my particular business except it could affect emerging > technology projects (which I find important to OpenStack’s future) negatively > – so I

Re: [openstack-dev] [security] [salt] Removal of Security and OpenStackSalt project teams from the Big Tent

Dims, This isn’t any of my particular business except it could affect emerging technology projects (which I find important to OpenStack’s future) negatively – so I thought I’d chime in. A lack of activity in a specs repo doesn’t mean much to me. For example, as Kolla was an emerging project

Re: [openstack-dev] [Neutron] Adding ihrachys to the neutron-drivers team

Congrats Ihar! On Sat, 2016-09-17 at 09:40 -0700, Armando M. wrote: > Hi folks, > > I would like to propose Ihar to become a member of the Neutron > drivers team [1]. > > Ihar wide knowledge of the Neutron codebase, and his longstanding > duties as stable core, downstream package whisperer, 

Re: [openstack-dev] [tricircle]freeze date and patches to be merged for Newton release

Good idea, Two patches got merged yesterday. Reorganized the items as follows, updated in https://etherpad.openstack.org/p/TricircleNewtonFreeze: MUST TO HAVE: subnet deletion * https://review.openstack.org/355847 * MUST TO HAVE: router deletion *

[openstack-dev] [horizon] gate failures (fragile integrated tests)

Hi horizoners, The current horizon gate is half broken as both integrated tests are 30-40% failure rate. (See https://bugs.launchpad.net/horizon/+bug/1626536 and https://bugs.launchpad.net/horizon/+bug/1626643) Fixes for these bugs are now under the gate. Please avoid using 'recheck' if one of

Re: [openstack-dev] [kolla] when we use yum install ansible to install ansible2.1.1.0， I deploy failed with mitaka ，and actually precheck limit version to 2.0.0.

Mitaka only supports ansible < 2 version. You can install ansible 1.9 by `yum install ansible1.9` On Thu, Sep 22, 2016 at 8:41 PM, wrote: > when we use yum install ansible to install ansible2.1.1.0， I deploy failed > with mitaka ，and actually precheck limit version to

Re: [openstack-dev] [Security] Picking a new tag

On 2016-09-23 08:35:54 +1000 (+1000), Tony Breeds wrote: [...] > I had a look at > http://lists.openstack.org/cgi-bin/mailman/options/openstack-dev > which will list the topics setup and it's far from exhustive, for > example '[all]' isn't there :( [...] It actually is, but Mailman (unhelpfully)

Re: [openstack-dev] [ptl] code churn and questionable changes

On 23/09/16 11:19, Lana Brindley wrote: On 23/09/16 02:19, Amrith Kumar wrote: Joshua, I think Steve and you may be missing the point of my email. It *IS* because I want to be open and inviting that I even asked the question, and what I'm asking for is how to deal with it. All Steve says

Re: [openstack-dev] [ptl] code churn and questionable changes

On 23/09/16 02:19, Amrith Kumar wrote: > Joshua, > > I think Steve and you may be missing the point of my email. It *IS* because I > want to be open and inviting that I even asked the question, and what I'm > asking for is how to deal with it. > > All Steve says is " The fact that a

Re: [openstack-dev] [AODH] event-alarm timeout discussion

On 22/09/2016 2:40 AM, Zhai, Edwin wrote: > > See > https://github.com/openstack/aodh/blob/master/aodh/evaluator/event.py#L158 > > evaluate_events is the handler of the endpoint for 'alarm.all', it > iterates the event list and evaluate them one by one with project > alarms. If both

Re: [openstack-dev] [Security] Picking a new tag

On Thu, Sep 22, 2016 at 11:03:31PM +0100, Dave Walker wrote: > Hi, > > I'm not convinced it needs changing. [security] is a pretty logical topic > tag, and rolls off the keyboard quite easily. > > So the real issue is filtering on headers. Most mail providers do provide > this, and certainly

Re: [openstack-dev] [Security] Picking a new tag

On 22 September 2016 at 19:52, Ian Cordasco wrote: > During the OpenStack Security Project (OSSP) meeting today we > discussed the fact that some MUAs don't filter the "[Security]" tag > very well and this causes a bit of an overload for people trying to > follow the

Re: [openstack-dev] [ptl] code churn and questionable changes

FWIW, No, this is *not* just an problem for OpenStack https://youtu.be/wf-BqAjZb8M?t=531 ^ Raymond Hettinger Ultimately the problem is mis-aligned goals between the individual and the project maintainers. They want to "do stuff" and get a change landed; we want to maximize the positive results

Re: [openstack-dev] [security] [salt] Removal of Security and OpenStackSalt project teams from the Big Tent

On 16-09-21 01:11 PM, Doug Hellmann wrote: Excerpts from Clint Byrum's message of 2016-09-21 08:56:24 -0700: Excerpts from Filip Pytloun's message of 2016-09-21 14:58:52 +0200: Hello, it's definately our bad that we missed elections in OpenStackSalt project. Reason is similar to Rob's - we

Re: [openstack-dev] [stackalytics] [deb] [packaging] OpenStack contribution stats skewed by deb-* projects

On 09/21/2016 03:44 PM, Ian Cordasco wrote: > Thomas, > > As you already pointed out, where it matters, the analysis of > commits is correct. I'm sure the Stackalytics team has prioritized > this as they see appropriate. I've asked because I would like to attempt to fix it myself, considering

Re: [openstack-dev] [kolla] when we use yum install ansible to install ansible2.1.1.0， I deploy failed with mitaka ，and actually precheck limit version to 2.0.0.

Lu, The kolla documentation specifically states Newton has a pin on ansible < 2.0.0.0 From: "lu.yao...@zte.com.cn" Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Thursday, September 22, 2016 at 5:41 AM

Re: [openstack-dev] [kolla][fuel][tripleo] Reference architecture to deploy OpenStack on k8s

Flavio, Apologies for delay in response – my backlog is large. Forgive me if I parsed your message incorrectly. It came across to me as “How do I blaze a trail for OpenStack on Kubernetes?”. That was asked of me personally 3 years ago which led to the formation of the Kolla project inside

Re: [openstack-dev] [ptl] code churn and questionable changes

Sean Dague wrote: > If this is the bug that triggered this discussion, yes, please never do > anything like that - > https://bugs.launchpad.net/python-openstacksdk/+bug/1475722 > Here was another fun one. https://bugs.launchpad.net/python-cinderclient/+bug/1586268 I commented as such that we

Re: [openstack-dev] [all] call for help debugging release-critical upgrade issue

On 09/22/2016 03:13 PM, Doug Hellmann wrote: > One of the steps we need to go through to finish this release is > to set up the stable/newton branch in devstack-gate. The patch to > do that [1] is consistently hitting timeout errors in some of the > jobs, waiting for VMs to be visible after they

[openstack-dev] [Manila] [Documentation] Manila Documentation Blitz

Hey all, TL;DR: Go to [0], sign up for a part of the docs to verify/review, prioritize the Installation Guide and the "Steps to Perform" section of the Administration Reference! As Newton comes to a close it is a good time to go though our myriad documentation and make sure that it is up to

Re: [openstack-dev] [neutron][stadium] Query regarding procedure for inclusion in Neutron Stadium

On 22 September 2016 at 00:46, reedip banerjee wrote: > Dear Neutron Core members, > > I have a query regarding the procedure for inclusion in the Neutron > Stadium. > I wanted to know if a project can apply for Big Tent and Neutron Stadium > together ( means can a project be

Re: [openstack-dev] [Neutron] Broken port rule masking: let's have it fixed?

On 22 September 2016 at 05:50, Inessa Vasilevskaya < ivasilevsk...@mirantis.com> wrote: > Hello, > > Apologies for multiple posts, forgot to set proper subject in previous one. > > I'd like to turn attention to the broken port rule masking problem [1], > which affects 2 projects so far: > neutron

[openstack-dev] [all] call for help debugging release-critical upgrade issue

One of the steps we need to go through to finish this release is to set up the stable/newton branch in devstack-gate. The patch to do that [1] is consistently hitting timeout errors in some of the jobs, waiting for VMs to be visible after they boot, as well as another issue that looks like a race

[openstack-dev] [nova] Can all virt drivers provide a disk 'id' for the diagnostics API?

Sergey is working on a spec to use the standardized virt driver instance diagnostics in the os-diagnostics API. A question came up during review of the spec about how to define a disk 'id': https://review.openstack.org/#/c/357884/2/specs/ocata/approved/restore-vm-diagnostics.rst@140 The

[openstack-dev] [Security] Picking a new tag

During the OpenStack Security Project (OSSP) meeting today we discussed the fact that some MUAs don't filter the "[Security]" tag very well and this causes a bit of an overload for people trying to follow the internal workings of the OSSP. We were briefly side-tracked trying to come up with a

Re: [openstack-dev] [vote][kolla] deprecation for debian distro support

Michal, I don’t think setting a gate expectation on upstream distros is appropriate considering our plans to expand our CI coverage. This would present a mission impossible to the debian maintainers in Kolla. We want to preserve choice, and locking out an upstream disro because of a lack of

[openstack-dev] [release] Release countdown for week R-1, 26-30 Sept

Focus - All teams should be working on release-critical bugs before the final release. General Notes - 29 Sept is the deadline for new release candidates or releases from intermediary projects. After that point we will enter a quiet period before tagging the last release

Re: [openstack-dev] [tripleo][ci] Temporary increase for the OVB undercloud instance memory

On Thu, Sep 22, 2016 at 1:40 PM, Steven Hardy wrote: > On Thu, Sep 22, 2016 at 04:36:30PM +0200, Gabriele Cerami wrote: >> Hi, >> >> As reported on this bug >> >> https://bugs.launchpad.net/tripleo/+bug/1626483 >> >> HA gate and periodic jobs for master and sometimes newton

Re: [openstack-dev] [ptl] code churn and questionable changes

On 2016-09-22 08:55:04 -0700 (-0700), Joshua Harlow wrote: [...] > And yes I understand it's not always easy, and some of it can be a PITA > based on (new) contributors experience (or lack of) and so on and so forth > but that's the way the world works folks (and everyone was likely >

Re: [openstack-dev] [ironic] Next API meeting cancelled

Considering I'm the only one currently working on it / bringing up new topics, I think biweekly is a better match to the pace I'm working on this. However, I hope that changes after the summit / once we start implementing these changes. --d On 09/22/2016 08:38 AM, Jim Rollenhagen wrote: > We

Re: [openstack-dev] [ptl] code churn and questionable changes

Gotcha, thanks for the clarification :) -Josh Amrith Kumar wrote: Joshua, I think Steve and you may be missing the point of my email. It *IS* because I want to be open and inviting that I even asked the question, and what I'm asking for is how to deal with it. All Steve says is " The fact

[openstack-dev] [all][summit][kolla] Returning one workroom session to the foundation

OpenStack summit planning team, We have been planning summit for approximately 2-3 months here: https://etherpad.openstack.org/p/kolla-O-summit-planning We further codified this into a vote via civs: http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_8368e1e74f8a0049 As you can see from the

Re: [openstack-dev] [ptl] code churn and questionable changes

On Wed, Sep 21, 2016 at 12:43:06PM +, Dolph Mathews wrote: > > > > And as a general rule, there is zero benefit to filing bugs in Launchpad if > there is no end-user impact (especially against 20+ projects). Close the > bug as Opinion (if Launchpad hasn't already broken) and focus on the >

[openstack-dev] [new][murano] murano-pkg-check 0.1.1 release

We are glowing to announce the release of: murano-pkg-check 0.1.1: Murano package validator tool With source available at: http://git.openstack.org/cgit/openstack/murano-pkg-check With package available at: https://pypi.python.org/pypi/murano-pkg-check Please report issues through

Re: [openstack-dev] [tripleo][ci] Temporary increase for the OVB undercloud instance memory

On Thu, Sep 22, 2016 at 04:36:30PM +0200, Gabriele Cerami wrote: > Hi, > > As reported on this bug > > https://bugs.launchpad.net/tripleo/+bug/1626483 > > HA gate and periodic jobs for master and sometimes newton started to > fail for errors related to memory shortage. Memory on undercloud >

Re: [openstack-dev] [oslo][nova] Anyone interested in writing a policy generator sphinx extension?

Andrew, the idea is to shift existing RBAC implementation: currently policy is enforced in the service (Nova, for instance) against the result of token validation, which is, in general, an access check; I'm thinking about performing policy enforcement along with access check in a single

[openstack-dev] [all][api] POST /api-wg/news

Greetings OpenStack community, Today's meeting was lightly attended and somewhat short, due to scheduling conflicts. Thanks to those who were able attend. To those who weren't able to make it: we missed you. The main new area of business was a need to discuss the planned API usability

Re: [openstack-dev] [security] [salt] Removal of Security and OpenStackSalt project teams from the Big Tent

  -Original Message- From: Filip Pytloun Reply: OpenStack Development Mailing List (not for usage questions) Date: September 22, 2016 at 10:34:00 To: OpenStack Development Mailing List (not for usage questions)

[openstack-dev] [Security] Blog Post: Maturing the security project

I wrote a blog post based on the recent thread about the future of the Security Project, it's published here: https://openstack-security.github.io/organization/2016/09/22/maturing-the-security-project.html Cheers -Rob __

Re: [openstack-dev] [tripleo][ci] Temporary increase for the OVB undercloud instance memory

Hi, On Thu, Sep 22, 2016 at 1:48 PM, James Slagle wrote: > On Thu, Sep 22, 2016 at 10:36 AM, Gabriele Cerami > wrote: > > Hi, > > > > As reported on this bug > > > > https://bugs.launchpad.net/tripleo/+bug/1626483 > > > > HA gate and periodic jobs

Re: [openstack-dev] [ptl] code churn and questionable changes

Joshua, I think Steve and you may be missing the point of my email. It *IS* because I want to be open and inviting that I even asked the question, and what I'm asking for is how to deal with it. All Steve says is " The fact that a new-to-openstack contributor would make such and error doesn’t

Re: [openstack-dev] [tripleo][ci] Temporary increase for the OVB undercloud instance memory

On Thu, Sep 22, 2016 at 10:36 AM, Gabriele Cerami wrote: > Hi, > > As reported on this bug > > https://bugs.launchpad.net/tripleo/+bug/1626483 > > HA gate and periodic jobs for master and sometimes newton started to > fail for errors related to memory shortage. Memory on

Re: [openstack-dev] [ptl] code churn and questionable changes

Steven Dake (stdake) wrote: Folks, We want to be inviting to new contributors even if they are green. New contributors reflect on OpenStack’s growth in a positive way. The fact that a new-to-openstack contributor would make such and error doesn’t warrant such a negative response even if it

Re: [openstack-dev] [tripleo][ci] Temporary increase for the OVB undercloud instance memory

On 09/22/2016 09:36 AM, Gabriele Cerami wrote: Hi, As reported on this bug https://bugs.launchpad.net/tripleo/+bug/1626483 HA gate and periodic jobs for master and sometimes newton started to fail for errors related to memory shortage. Memory on undercloud instance was increased to 8G less

Re: [openstack-dev] [ptl] code churn and questionable changes

On 22/09/2016 11:18 AM, Amrith Kumar wrote: > [amrith] Actually, not true. Some of the changes I'm seeing are from people > who have a track record of these kinds of changes. And if there is a knob in > Launchpad somewhere, I sure as hell can't find it. no way to block actions but as a

Re: [openstack-dev] [security] [salt] Removal of Security and OpenStackSalt project teams from the Big Tent

On 16-09-22 11:32 AM, Filip Pytloun wrote: If there's more we can do, we are available at Freenode/#openstack-salt. I think this right here is your issue. Believing it is the responsibility of the tc or other leaders to find you. It isn't. Be available on #openstack-dev at the very least.

Re: [openstack-dev] [kolla][fuel][tripleo] Reference architecture to deploy OpenStack on k8s

So issue is, I know of few other openstacks on k8s and everyone does that slightly differently. So far we lack proof points and real world data to determine best approaches to stuff. This is still not-to-well researched field. Right now it's mostly opinions and assumptions. We're not ready to make

[openstack-dev] [ironic] Next API meeting cancelled

We decided in the last meeting to cancel next week's meeting. So we'll meet again October 4. Side question: should we just make this meeting biweekly always? // jim __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [security] [salt] Removal of Security and OpenStackSalt project teams from the Big Tent

Thank you for your feedback - this is first one since we joined Big Tent and very useful. On 2016/09/21 17:08, Davanum Srinivas wrote: > Data points so far are: > 1. No response during Barcelona planning for rooms > 2. Lack of candidates for PTL election > 3. No activity in the releases/

Re: [openstack-dev] [ptl] code churn and questionable changes

Excerpts from Amrith Kumar's message of 2016-09-22 15:18:06 +: > > > -Original Message- > > From: Boris Bobrov [mailto:bbob...@mirantis.com] > > Sent: Wednesday, September 21, 2016 10:35 AM > > To: OpenStack Development Mailing List (not for usage questions) > >

[openstack-dev] [glance] design summit proposal deadline approaching

Quick reminder to Glancers and People Interested in Glance that the Glance Ocata design summit session proposals close at 14:00 UTC Wednesday Sept 28 and voting closes at 13:59 UTC Thursday Sept 29 (that is, just before next week's Glance meeting). We'll have final discussion during the Glance

Re: [openstack-dev] [nova][stable/liberty] Backport impasse: "virt: set address space & CPU time limits when running qemu-img"

2016-09-22 15:58 GMT+02:00 Matt Riedemann : > 1. We don't bump minimums just because a new thing comes out in a given > release, we only bump minimums when something that uses that dependency > needs a higher minimum version. > > 2. Looking at this: > >

Re: [openstack-dev] [vote][kolla] deprecation for debian distro support

I agree with Michal and Martin. I was a little reluctant to respond here because the Debian additions are new, while Fedora has been around since the beginning and never got a ton of testing. Berendt what's your take here? Thanks, Ryan - Original Message - From: "Michał Jastrzębski"

Re: [openstack-dev] [ptl] code churn and questionable changes

> -Original Message- > From: Boris Bobrov [mailto:bbob...@mirantis.com] > Sent: Wednesday, September 21, 2016 10:35 AM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [ptl] code churn and questionable

Re: [openstack-dev] [ptl] code churn and questionable changes

I agree. I am not saying new contributors are not welcome. They are. But there are also things that we are not comfortable with. But our leadership cannot prevent them from making such error. There should be a way to lure them to mentors before doing things that we consider bad. On 09/22/2016

Re: [openstack-dev] [nova][stable/liberty] Backport impasse: "virt: set address space & CPU time limits when running qemu-img"

On Tue, Sep 20, 2016 at 12:48:49PM +0200, Kashyap Chamarthy wrote: > The said patch in question fixes a CVE[x] in stable/liberty. > > We currently have two options, both of them have caused an impasse with > the Nova upstream / stable maintainers. We've had two-ish months to > mull over this.

Re: [openstack-dev] [kolla][fuel][tripleo] Reference architecture to deploy OpenStack on k8s

On 22/09/16 09:39 -0500, Michał Jastrzębski wrote: Flavio, So as you surely know k8s is an orchiestration tools, docker is container engine. If you are running k8s, you still run docker:) I know this (although, if we really want to nitpick you could technically use something else than docker

Re: [openstack-dev] floating IP is DOWN

On 09/22/2016 10:19 AM, Barber, Ofer wrote: when i assign a floating IP to a server, i see that the status of the floating IP is "down" why is that so ? *_code:_* LOG.info("\n<== float IP address: %s and status: %s ==>" % (float_ip['floating_ip_address'],float_ip['status']))

Re: [openstack-dev] [Cinder] FFE request for RBD replication

On 12/09, Sean McGinnis wrote: > On Mon, Sep 12, 2016 at 10:24:23AM +0200, Michał Dulko wrote: > > +1, thanks for taking care of that! > > > > On 09/12/2016 03:35 AM, Huang Zhiteng wrote: > > > +1 for this long-waited feature to land in Newton. > > > > > > On Sun, Sep 11, 2016 at 1:09 AM, Jay S.

[openstack-dev] [heat] Jenkins Openstack Heat Plugin

Hi, We developed a plugin jenkins to facilate the piloting of Heat API from Jenkins. This plugin permits to generate automaticaly an ihm from the HOT template to populate the inputs and to get the outputs. You can chain the differents templates, pass data between them to create complex

Re: [openstack-dev] [kolla][fuel][tripleo] Reference architecture to deploy OpenStack on k8s

On 22/09/16 10:09 -0400, Davanum Srinivas wrote: Flavio Please see below: On Thu, Sep 22, 2016 at 7:04 AM, Flavio Percoco wrote: Greetings, I've recently started looking into the container technologies around OpenStack. More specifically, I've been looking into the tools

Re: [openstack-dev] [vote][kolla] deprecation for debian distro support

I'm also reluctant to deprecation of debian.There are few changes to ubuntu and it might just work:) However, I'd love to ask whoever would like us to keep using debian to create gates for it. I would like to give debian one more release to go and deprecate it if we fail to create gates in Ocata

Re: [openstack-dev] [kolla][fuel][tripleo] Reference architecture to deploy OpenStack on k8s

Flavio, So as you surely know k8s is an orchiestration tools, docker is container engine. If you are running k8s, you still run docker:) Kolla-kubernetes is a part of Big Tent, is project developed by Kolla community and we're close to our big showdown:) Come over to our session in Barcelona, in

[openstack-dev] [tripleo][ci] Temporary increase for the OVB undercloud instance memory

Hi, As reported on this bug https://bugs.launchpad.net/tripleo/+bug/1626483 HA gate and periodic jobs for master and sometimes newton started to fail for errors related to memory shortage. Memory on undercloud instance was increased to 8G less than a month ago, so the problem needs a different

[openstack-dev] floating IP is DOWN

when i assign a floating IP to a server, i see that the status of the floating IP is "down" why is that so ? code: LOG.info("\n<== float IP address: %s and status: %s ==>" % (float_ip['floating_ip_address'],float_ip['status'])) Output: <== float IP address: 10.63.101.225 and

Re: [openstack-dev] [kolla][fuel][tripleo] Reference architecture to deploy OpenStack on k8s

Flavio Please see below: On Thu, Sep 22, 2016 at 7:04 AM, Flavio Percoco wrote: > Greetings, > > I've recently started looking into the container technologies around > OpenStack. > More specifically, I've been looking into the tools that allow for deploying > OpenStack on

Re: [openstack-dev] [nova][stable/liberty] Backport impasse: "virt: set address space & CPU time limits when running qemu-img"

On 9/22/2016 8:05 AM, Alan Pevec wrote: We have: * global-requirements.txt: origin/stable/liberty : oslo.concurrency>=2.3.0 # Apache-2.0 But wasn't that wrong from the start? First Liberty release of oslo.concurrency was 2.6.0 why was that not bumped in g-r ? Cheers, Alan

Re: [openstack-dev] [security] [salt] Removal of Security and OpenStackSalt project teams from the Big Tent

On 16-09-21 05:08 PM, Davanum Srinivas wrote: Jakub, Please see below. On Wed, Sep 21, 2016 at 3:46 PM, Jakub Pavlik wrote: Hello all, it took us 2 years of hard working to get these official. OpenStack-Salt is now used by around 40 production deployments and it is

[openstack-dev] [cinder][db] lazy loading of an attribute impossible

Hi, I've just noticed another Cinder bug [1], similar to past bugs [2], [3]. All of them have a common exception causing them: sqlalchemy.orm.exc.DetachedInstanceError: Parent instance <{$SQLAlchemyObject} at {$MemoryLocation}> is not bound to a Session; lazy load operation of attribute

Re: [openstack-dev] [ptl] code churn and questionable changes

  -Original Message- From: Steven Dake (stdake) Reply: OpenStack Development Mailing List (not for usage questions) Date: September 22, 2016 at 01:29:14 To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [nova] Is there any reason we shouldn't remove nova.image.s3 now?

On 09/22/2016 09:08 AM, Matt Riedemann wrote: > On 9/22/2016 8:01 AM, Andrey Pavlov wrote: >> I've tried to do it some time ago - >> https://review.openstack.org/#/c/266425/ >> But I tried to remove more than s3_image >> But there was no consensus... >> >> Regards, >> Andrey. > > Yeah I think we

Re: [openstack-dev] [nova] Is there any reason we shouldn't remove nova.image.s3 now?

On 9/22/2016 8:01 AM, Andrey Pavlov wrote: I've tried to do it some time ago - https://review.openstack.org/#/c/266425/ But I tried to remove more than s3_image But there was no consensus... Regards, Andrey. On Thu, Sep 22, 2016 at 3:01 PM, Sean Dague >

Re: [openstack-dev] [nova][stable/liberty] Backport impasse: "virt: set address space & CPU time limits when running qemu-img"

> We have: > * global-requirements.txt: > origin/stable/liberty : oslo.concurrency>=2.3.0 # Apache-2.0 But wasn't that wrong from the start? First Liberty release of oslo.concurrency was 2.6.0 why was that not bumped in g-r ? Cheers, Alan

Re: [openstack-dev] [nova] Is there any reason we shouldn't remove nova.image.s3 now?

I've tried to do it some time ago - https://review.openstack.org/#/c/266425/ But I tried to remove more than s3_image But there was no consensus... Regards, Andrey. On Thu, Sep 22, 2016 at 3:01 PM, Sean Dague wrote: > On 09/22/2016 02:53 AM, Clint Byrum wrote: > > Excerpts from

[openstack-dev] [QA] The end-user test suite for OpenStack clusters

Hi team, we have an idea to create the test suite with destructive/HA and advanced end-user scenarios for the OpenStack clusters. This test suite will contains advanced scenario integration tests for OpenStack clusters to make sure that the cluster is ready for the production. The test cases

[openstack-dev] [neutron] [classifier] Common Classifier + OVS Flow Management Meeting

Hi Common Classifier and OVS Flow Management community, Cathy has kindly allowed me to drive the next common classifier/flow management IRC meetings. Time, location and recurrence are unchanged, so the next meeting will be next Tuesday (27th September) at 17:00 UTC [1] on #openstack-meeting

[openstack-dev] [Neutron] Broken port rule masking: let's have it fixed?

Hello, Apologies for multiple posts, forgot to set proper subject in previous one. I'd like to turn attention to the broken port rule masking problem [1], which affects 2 projects so far: neutron (mitaka+ with ovs firewall driver configuration) and networking-ovs-dpdk [2]. To keep it short: the

[openstack-dev] [kolla] when we use yum install ansible to install ansible2.1.1.0， I deploy failed with mitaka ，and actually precheck limit version to 2.0.0.

when we use yum install ansible to install ansible2.1.1.0， I deploy failed with mitaka ，and actually precheck limit version to 2.0.0. so I want to know if kolla with mitaka suppout ansible2.1.1.0，can you help me？ thanks！ __

Re: [openstack-dev] [infra][tripleo] status of tripleo-test-cloud-rh1

On Mon, Aug 8, 2016 at 1:47 PM, James Slagle wrote: > On Mon, Aug 8, 2016 at 1:06 PM, Jeremy Stanley wrote: >> On 2016-08-08 11:47:56 -0400 (-0400), James Slagle wrote: >> [...] >>> I suppose it's also possible that we might be pushing too strongly >>>

[openstack-dev] [new][ironic] ironic-python-agent 1.5.0 release (newton)

We are grateful to announce the release of: ironic-python-agent 1.5.0: Ironic Python Agent Ramdisk This release is part of the newton release series. For more details, please see below. 1.5.0 ^ New Features * Add 'vendor' and 'product' fields to interfaces data for future

[openstack-dev] [new][ironic] bifrost 2.1.0 release (newton)

We are amped to announce the release of: bifrost 2.1.0: Deployment of physical machines using OpenStack Ironic and Ansible This release is part of the newton release series. For more details, please see below. 2.1.0 ^ New Features * Allows install of ironic-inspector and

Re: [openstack-dev] [nova] Is there any reason we shouldn't remove nova.image.s3 now?

On 09/22/2016 02:53 AM, Clint Byrum wrote: > Excerpts from Matt Riedemann's message of 2016-09-21 18:43:06 -0500: >> The s3 image configuration options were deprecated for removal in newton >> [1]. >> >> Clint has a patch up to remove the boto dependency from nova [2] which >> is only used in

Re: [openstack-dev] [vote][kolla] deprecation for fedora distro support

My vote goes to option 2. It's common knowledge Kolla's Fedora base image is in bad shape and doesn't get any attention from developers. It's time to deprecated it. Martin On Mon, Sep 19, 2016 at 7:40 PM, Jeffrey Zhang wrote: > Kolla core reviewer team, > > Kolla

Re: [openstack-dev] [vote][kolla] deprecation for debian distro support

I'm -1 on deprecating Debian base image considering it's a recent addition to Kolla and we can legitimately assume the person who contributed it had plans to use it. I would love to get Benedikt’s input. Martin On Tue, Sep 20, 2016 at 7:27 PM, Steven Dake (stdake) wrote: >

Re: [openstack-dev] [nova][stable/liberty] Backport impasse: "virt: set address space & CPU time limits when running qemu-img"

On Thu, Sep 22, 2016 at 04:25:00PM +1000, Tony Breeds wrote: > On Wed, Sep 21, 2016 at 02:05:51PM -0400, Sean Dague wrote: > > > Well, the risk profile of what has to be changed for stable/liberty > > (given that all the actual code is buried in libraries which have tons > > of other changes).

Re: [openstack-dev] [kolla][fuel][tripleo][openstack-ansible] Reference architecture to deploy OpenStack on k8s

On Thu, Sep 22, 2016 at 7:04 AM, Flavio Percoco wrote: > Greetings, > > I've recently started looking into the container technologies around > OpenStack. > More specifically, I've been looking into the tools that allow for deploying > OpenStack on containers, which is what I'm

[openstack-dev] [kolla][fuel][tripleo] Reference architecture to deploy OpenStack on k8s

Greetings, I've recently started looking into the container technologies around OpenStack. More specifically, I've been looking into the tools that allow for deploying OpenStack on containers, which is what I'm the most interested in right now as part of the TripleO efforts. I'm familiar with

Re: [openstack-dev] [tricircle]freeze date and patches to be merged for Newton release

Please add 1 line above description of each patch. MUST TO HAVE or GOOD TO HAVE e.g., https://review.openstack.org/#/c/356187/ MUST TO HAVE The framework of dynamic pod binding. So that we can prioritize clearly and easily. Ideally we should have made priority for each *MUST* case.

Re: [openstack-dev] [ptl] code churn and questionable changes

On Thu, Sep 22, 2016 at 8:26 AM, Steven Dake (stdake) wrote: > Folks, > > We want to be inviting to new contributors even if they are green. New > contributors reflect on OpenStack’s growth in a positive way. The fact > that a new-to-openstack contributor would make such and

[openstack-dev] [daisycloud-core] Agenda for IRC meeting 0800UTC Sep. 23 2016

1) Roll Call 2) Core Code Abstraction 3) Bifrost/Ironic Integration 4) OPNFV: Daisy4nfv CI Framework Progress 5) Bare Metal Deployment(PXE/IPMI) Test B.R., Zhijiang __ OpenStack Development Mailing List (not for usage

[openstack-dev] [watcher] Barcelona design sessions

Hi Watcher team, As discussed on IRC, you are welcome to suggest topics for watcher design sessions in Barcelona: https://etherpad.openstack.org/p/watcher-ocata-design-session Thanks, Antoine __ OpenStack Development

Re: [openstack-dev] tempest tests in Horizon GUI

Hi Ofer, As Andrea said, Tempest shouldn't leave any test resource after a Tempest run. And Horizon is not mandatory in a Tempest run. But if you want to verify it, you can do that through your openstack-client or Horizon dashboard just in case. And you can find your credentials in your

[openstack-dev] [neutron][stadium] Query regarding procedure for inclusion in Neutron Stadium

Dear Neutron Core members, I have a query regarding the procedure for inclusion in the Neutron Stadium. I wanted to know if a project can apply for Big Tent and Neutron Stadium together ( means can a project be accepted in the Neutron Stadium and as a result into the Big Tent ) I was checking

Re: [openstack-dev] [nova] Is there any reason we shouldn't remove nova.image.s3 now?

Excerpts from Matt Riedemann's message of 2016-09-21 18:43:06 -0500: > The s3 image configuration options were deprecated for removal in newton > [1]. > > Clint has a patch up to remove the boto dependency from nova [2] which > is only used in the nova.image.s3 module. > > Rather than remove

Re: [openstack-dev] [AODH] event-alarm timeout discussion

Gordon, Thanks for your comments. Pls. check my answer and flow chart below. On Wed, 21 Sep 2016, gordon chung wrote: === event-alarm timeout implementation = As it's for event-alarm, we need keep it as event-driven. Furthermore, for quick response, we need use event for

Re: [openstack-dev] [ptl] code churn and questionable changes

Folks, We want to be inviting to new contributors even if they are green. New contributors reflect on OpenStack’s growth in a positive way. The fact that a new-to-openstack contributor would make such and error doesn’t warrant such a negative response even if it a hassle for the various PTLs

Re: [openstack-dev] [nova][stable/liberty] Backport impasse: "virt: set address space & CPU time limits when running qemu-img"

On Wed, Sep 21, 2016 at 02:05:51PM -0400, Sean Dague wrote: > Well, the risk profile of what has to be changed for stable/liberty > (given that all the actual code is buried in libraries which have tons > of other changes). Special cherry-picked library versions would be > needed to fix this

  1   2   >