Re: [openstack-dev] [Mistral] Proposal for the Resume Feature

On Fri, Mar 27, 2015 at 11:20 AM, W Chan wrote: > We assume WF is in paused/errored state when 1) user manually pause the WF, > 2) pause is specified on transition (on-condition(s) such as on-error), and > 3) task errored. > > The resume feature will support the following use cases. > 1) User resu

Re: [openstack-dev] [Devstack] What is neutron-legacy?

Hi Dean, Thank you for your response. I’ve forgotten the sprint. I looked etherpad log and got it clearly. thanks, Hirofumi 2015/03/27 12:46、Dean Troyer のメール： > On Thu, Mar 26, 2015 at 8:00 PM, Hirofumi Ichihara > wrote: > I found lib/neutron-legacy in master branch today. > I didn’t know th

Re: [openstack-dev] [swift] swift memory usage in centos7 devstack jobs

On 03/26/2015 04:07 PM, Ian Wienand wrote: > See [1] for some more details; but the short story is that the various > swift processes -- even just sitting around freshly installed from > devstack before anything happens -- take up twice as much space on > centos as ubuntu > > --- swift (% total sy

Re: [openstack-dev] [Devstack] What is neutron-legacy?

On Thu, Mar 26, 2015 at 8:00 PM, Hirofumi Ichihara < ichihara.hirof...@lab.ntt.co.jp> wrote: > I found lib/neutron-legacy in master branch today. > I didn’t know this important change because I couldn’t watch for the last > few days. > Could someone tell me what is neutron-legacy? > How do we mana

[openstack-dev] [Mistral] Proposal for the Resume Feature

We assume WF is in paused/errored state when 1) user manually pause the WF, 2) pause is specified on transition (on-condition(s) such as on-error), and 3) task errored. The resume feature will support the following use cases. 1) User resumes WF from manual pause. 2) In the case of task failure, us

Re: [openstack-dev] mox3 WAS Re: [nova] Do we have some guidelines for mock, stub, mox when writing unit test?

On 03/26/2015 09:47 PM, Alan Pevec wrote: > blast from the past... > > 2013-12-04 19:17 GMT+01:00 Chuck Short : >> On Wed, Dec 4, 2013 at 11:16 AM, Nikola Đipanov wrote: > ... >>> 1) Figure out what is the deal with mox3 and decide if owning it will >>> really be less trouble than porting nova. T

Re: [openstack-dev] [Fuel] Version bump in the beginning of a release cycle

Hi Roman, We are doing the same in a bit different way. Firstly, we are removing package build out of ISO build. These packages will flow the same way we do for MOS components. The will use the same build procedures as all other packages. Secondly, all packages will be put in repository in our mi

Re: [openstack-dev] [Heat] Decoupling Heat integration tests from Heat tree

On Fri, Mar 27, 2015 at 6:26 AM, Zane Bitter wrote: > On 26/03/15 10:38, Pavlo Shchelokovskyy wrote: > >> Hi all, >> >> following IRC discussion here is a summary of what I propose can be done >> in this regard, in the order of increased decoupling: >> >> 1) make a separate requirements.txt for i

[openstack-dev] mox3 WAS Re: [nova] Do we have some guidelines for mock, stub, mox when writing unit test?

blast from the past... 2013-12-04 19:17 GMT+01:00 Chuck Short : > On Wed, Dec 4, 2013 at 11:16 AM, Nikola Đipanov wrote: ... >> 1) Figure out what is the deal with mox3 and decide if owning it will >> really be less trouble than porting nova. To be hones - I was unable to >> even find the code re

Re: [openstack-dev] [nova] [libvirt] The risk of hanging when shutdown instance.

Yes, you are right, but we found our instance hang at first dom.shutdown() call, if the dom.shutdown() don't return, there is no chance to execute dom.destroy(), right? 2015-03-26 23:20 GMT+08:00 Chris Friesen : > On 03/25/2015 10:15 PM, Rui Chen wrote: > >> Hi all: >> >> I found a discuss a

Re: [openstack-dev] [Nova][Neutron] Status of the nova-network to Neutron migration work

On Thu, Mar 26, 2015 at 7:58 PM, Russell Bryant wrote: > On 03/26/2015 06:31 PM, Michael Still wrote: > > Hi, > > > > I thought it would be a good idea to send out a status update for the > > migration from nova-network to Neutron, as there hasn't been as much > > progress as we'd hoped for in Ki

Re: [openstack-dev] Cinder Third-Party CI: what next? (was Re: [cinder] Request exemption for removal of NetApp FC drivers (no voting CI))

Mike, This effort has taken quite some time and was going to require hard decisions to be made at some point. You have been more than patient in this process and I commend you for that as well as all the communication. Thank you for continuing to drive this! Jay On Mar 24, 2015 10:55 PM, "Mont

Re: [openstack-dev] [Neutron] initial OVN testing

On 03/26/2015 08:22 PM, Salvatore Orlando wrote: > To set this up outside of ovs-sandbox, you need to first create the OVN > northbound database: > > $ ovsdb-tool create ovnnb.db ovs-git-tree/ovn/ovn-nb.ovsschema > > Then you need to tell ovsdb-server to use it. By default ovsd

Re: [openstack-dev] [Nova][Neutron] Status of the nova-network to Neutron migration work

On 03/26/2015 06:31 PM, Michael Still wrote: > Hi, > > I thought it would be a good idea to send out a status update for the > migration from nova-network to Neutron, as there hasn't been as much > progress as we'd hoped for in Kilo. There are a few issues which have > been slowing progress down.

[openstack-dev] [Devstack] What is neutron-legacy?

Hi Devstack folks, I found lib/neutron-legacy in master branch today. I didn’t know this important change because I couldn’t watch for the last few days. Could someone tell me what is neutron-legacy? How do we manage and develop it? I would also like to know where is the change decided, IRC or

Re: [openstack-dev] Fwd: PCI passthrough of 40G ethernet interface

在 2015年03月11日 22:15, jacob jacob 写道: Hi, jacob we now find przemyslaw.czesnowicz have same NIC, hope will help a little bit. Yongli He -- Forwarded message -- From: *jacob jacob* mailto:opstk...@gmail.com>> Date: Tue, Mar 10, 2015 at 6:00 PM Subject: PCI passthrough of 40

Re: [openstack-dev] [cinder] Deadline For Volume Drivers to Be Readded

Thanks for clarifying! Ryan On Mar 26, 2015, at 5:29 PM, Mike Perez wrote: > On 00:24 Fri 27 Mar , Ryan Hsu wrote: >> Rightfully so, but it doesn't hurt to offer suggestions that might improve >> the community. It would just be nice to have exclusions reconsidered if there >> are legitimate

Re: [openstack-dev] [cinder] Deadline For Volume Drivers to Be Readded

Mike, I am communicating this problem with my teams and will get it resolved asap. Jay On Mar 26, 2015 1:23 PM, "Mike Perez" wrote: > On 09:39 Thu 26 Mar , Mike Perez wrote: > > As discussed in the last Cinder meeting [1], in order to have your volume > > driver readded into the Kilo releas

[openstack-dev] What's Up Doc? March 26, 2015 [all]

Here's the latest news installment from docsland. Install Guides updates - We've got a spec ready for the changes to the Install Guides now published at: http://specs.openstack.org/openstack/docs-specs/specs/kilo/installguide-kilo.html I'm sure the keystone team will re

Re: [openstack-dev] [cinder] Deadline For Volume Drivers to Be Readded

On 00:24 Fri 27 Mar , Ryan Hsu wrote: > Rightfully so, but it doesn't hurt to offer suggestions that might improve > the community. It would just be nice to have exclusions reconsidered if there > are legitimate bugs behind them. You see them all the time in the tempest > tests ala "SKIPPED: Sk

Re: [openstack-dev] [cinder] Deadline For Volume Drivers to Be Readded

Rightfully so, but it doesn't hurt to offer suggestions that might improve the community. It would just be nice to have exclusions reconsidered if there are legitimate bugs behind them. You see them all the time in the tempest tests ala "SKIPPED: Skipped until Bug: 1373513 is resolved" so it's

Re: [openstack-dev] [cinder] Deadline For Volume Drivers to Be Readded

On 00:11 Fri 27 Mar , Ryan Hsu wrote: > Thanks Mike. The wiki still showing the old edit when I had sent out my > earlier email but I see it's been updated now. I've tested running with "tox > -e all -- volume" and that gets us to 291 tests now. Ah gotcha. That's great to hear, thank you! --

Re: [openstack-dev] [Neutron] initial OVN testing

Thanks for starting this Russell. Some answers inline. Salvatore On 27 March 2015 at 00:54, Russell Bryant wrote: > Gary and Kyle, I saw in my IRC backlog that you guys were briefly > talking about testing the Neutron ovn ml2 driver. I suppose it's time > to add some more code to the devstack

Re: [openstack-dev] [cinder] Deadline For Volume Drivers to Be Readded

Thanks Mike. The wiki still showing the old edit when I had sent out my earlier email but I see it's been updated now. I've tested running with "tox -e all -- volume" and that gets us to 291 tests now. -Ryan On Mar 26, 2015, at 4:28 PM, Mike Perez wrote: > On 21:45 Thu 26 Mar , Ryan Hsu w

[openstack-dev] [Neutron] initial OVN testing

Gary and Kyle, I saw in my IRC backlog that you guys were briefly talking about testing the Neutron ovn ml2 driver. I suppose it's time to add some more code to the devstack integration to install the current ovn branch and set up ovsdb-server to serve up the right database for this. I'll try to

Re: [openstack-dev] How to do once off/infrequent meetings?

On Wed, Mar 25, 2015 at 03:23:29PM +, Bailey, Darragh wrote: > > > I was looking at using the meetings service > (https://wiki.openstack.org/wiki/Meetings) to run and log a meeting on a > stackforge project (git-upstream - > http://git.openstack.org/cgit/stackforge/git-upstream), which seems

Re: [openstack-dev] [cinder] Deadline For Volume Drivers to Be Readded

On 03/26/2015 06:48 PM, Ryan Hsu wrote: > Exclusions are legitimate and will always be necessary at some point. In the > case of the linked bug, this was once a known issue for the VMware driver and > we had excluded affected tests so that CI could continue to run. This is the > same way we do i

Re: [openstack-dev] [cinder] Deadline For Volume Drivers to Be Readded

On 21:45 Thu 26 Mar , Ryan Hsu wrote: > Hmm, that's what I thought at first but when I looked at the "What tests do > I use" FAQ, the tests that it says to use links to: > http://git.openstack.org/cgit/openstack/tempest/tree/tempest/api/volume, > which is exactly what we're running. Even so, I

Re: [openstack-dev] [cinder] Deadline For Volume Drivers to Be Readded

On 22:42 Thu 26 Mar , Ryan Hsu wrote: > Like I mentioned earlier, these numbers are going to be different for > everyone depending on their testbed set up or driver capabilities. Just by > disabling Heat in devstack you're going to miss some tests. As long as people > are transparent about this

Re: [openstack-dev] [cinder] Deadline For Volume Drivers to Be Readded

Exclusions are legitimate and will always be necessary at some point. In the case of the linked bug, this was once a known issue for the VMware driver and we had excluded affected tests so that CI could continue to run. This is the same way we do it in Nova CI and oslo.vmware CI. Thanks, Ryan

Re: [openstack-dev] [infra] What do people think of YAPF (like gofmt, for python)?

On 27 March 2015 at 09:14, Ryan Brown wrote: > Ooof, that's huge. If we can configure it to be less aggressive I love > the *idea* of having everything formatted semantically, but that's a > pretty major burden for everyone involved. It's huge today. It wouldn't be if we did it :). I suggest th

Re: [openstack-dev] [cinder] Deadline For Volume Drivers to Be Readded

Like I mentioned earlier, these numbers are going to be different for everyone depending on their testbed set up or driver capabilities. Just by disabling Heat in devstack you're going to miss some tests. As long as people are transparent about this, I don't see the harm here. -Ryan On Mar 26

[openstack-dev] [Nova][Neutron] Status of the nova-network to Neutron migration work

Hi, I thought it would be a good idea to send out a status update for the migration from nova-network to Neutron, as there hasn't been as much progress as we'd hoped for in Kilo. There are a few issues which have been slowing progress down. First off, creating an all encompassing turn key upgrade

Re: [openstack-dev] [cinder] Deadline For Volume Drivers to Be Readded

On 22:28 Thu 26 Mar , Tom Swanson wrote: > I just ran it and got ... > > Ran: 304 tests in 412. sec. > - Passed: 293 > - Skipped: 11 That looks good to me then and might've been a mistake in looking at everyone's logs. Thanks Tom. -- Mike Perez _

Re: [openstack-dev] [cinder] Deadline For Volume Drivers to Be Readded

On 20:49 Thu 26 Mar , Ryan Hsu wrote: > Hi Mike, > > We (VMware CI) run "testr run tempest.api.volume" for our Cinder CI and this > runs about ~240 tests for us. I'm guessing that the rest of the ~60 tests are > not being run due to skips and disabled features. For example, here is > a samplin

Re: [openstack-dev] [cinder] Deadline For Volume Drivers to Be Readded

I just ran it and got ... Ran: 304 tests in 412. sec. - Passed: 293 - Skipped: 11 From: Ryan Hsu [mailto:r...@vmware.com] Sent: Thursday, March 26, 2015 4:45 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [cinder] Deadline For Volume Drivers t

Re: [openstack-dev] [cinder] Deadline For Volume Drivers to Be Readded

Hmm, that's what I thought at first but when I looked at the "What tests do I use" FAQ, the tests that it says to use links to: http://git.openstack.org/cgit/openstack/tempest/tree/tempest/api/volume, which is exactly what we're running. Even so, I ran the "tox -e all -- volume" command and tha

[openstack-dev] Volunteers Needed for OpenStack Booth at PyCon

Volunteers Needed for OpenStack Booth We are looking for 3 more knowledgeable volunteers who can staff the OpenStack booth in shifts (see the booth schedule below). If you are available and have at least one year of experience contributing to or using OpenStack, please email ridolfoden...@gmail.c

[openstack-dev] [Nova] Tracking ideas for summit sessions

Hi, let's start tracking ideas for summit sessions in this etherpad: https://etherpad.openstack.org/p/liberty-nova-summit-ideas Have at it! Cheers, Michael -- Rackspace Australia __ OpenStack Development Mailing List

Re: [openstack-dev] [cinder] Deadline For Volume Drivers to Be Readded

You want to run the "volume" tests and not "tempest.api.volume" tests. -Original Message- From: Ryan Hsu [mailto:r...@vmware.com] Sent: Thursday, March 26, 2015 3:50 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [cinder] Deadline For Volu

Re: [openstack-dev] [cinder] Deadline For Volume Drivers to Be Readded

Hi Mike, We (VMware CI) run "testr run tempest.api.volume" for our Cinder CI and this runs about ~240 tests for us. I'm guessing that the rest of the ~60 tests are not being run due to skips and disabled features. For example, here is a sampling of tests that are skipped in a recent run (note t

Re: [openstack-dev] [heat] heat delete woes in Juno

On 26/03/15 15:56, Matt Fischer wrote: We don't have heat stack-abandon enabled. It's marked as a "preview feature", have you had any issues? It's fairly safe for this use case. If it's important for you that you don't lose track of your resources and you want to adopt them again later, it's

Re: [openstack-dev] [API] Do we need to specify "follow the HTTP RFCs"?

Top posting the relevant review https://review.openstack.org/#/c/161946/ Everett On Feb 13, 2015, at 8:44 AM, michael mccune mailto:m...@redhat.com>> wrote: On 02/12/2015 02:20 PM, Ryan Brown wrote: +1 I think the way to go would be: "We suggest (pretty please) that you comply with RFCs 7230-

Re: [openstack-dev] [Heat] Decoupling Heat integration tests from Heat tree

On 26/03/15 10:38, Pavlo Shchelokovskyy wrote: Hi all, following IRC discussion here is a summary of what I propose can be done in this regard, in the order of increased decoupling: 1) make a separate requirements.txt for integration tests and modify the tox job to use it. The code of these tes

Re: [openstack-dev] [Heat][qa][tempest] Decoupling Heat integration tests from Heat tree

On 27/03/15 03:38, Pavlo Shchelokovskyy wrote: Hi all, following IRC discussion here is a summary of what I propose can be done in this regard, in the order of increased decoupling: 1) make a separate requirements.txt for integration tests and modify the tox job to use it. The code of these

[openstack-dev] [nova][stable][OSSA 2015-005] Nova console Cross-Site WebSocket hijacking (CVE-2015-0259)

On 2015-03-26 14:29:03 -0400 (-0400), Lars Kellogg-Stedman wrote: [...] > The solution, of course, is to make sure that the value of > novncproxy_base_url is set explicitly where the nova-novncproxy > service is running. This is a bit of a hack, since the service > *really* only cares about the pro

Re: [openstack-dev] [infra] What do people think of YAPF (like gofmt, for python)?

On 03/26/2015 02:15 PM, Kiall Mac Innes wrote: > I have no clue how I managed to send that last email encrypted - > Apologies :) > > Re YAPF, or autofomatting, I've very little opinion.. > > But - I gave YAPF a go against the Designate codebase with the stock config: > > 258 files changed, 524

Re: [openstack-dev] [Heat] Decoupling Heat integration tests from Heat tree

On 03/26/2015 10:38 AM, Pavlo Shchelokovskyy wrote: > Hi all, > > following IRC discussion here is a summary of what I propose can be > done in this regard, in the order of increased decoupling: > > 1) make a separate requirements.txt for integration tests and modify > the tox job to use it. The

Re: [openstack-dev] [heat] heat delete woes in Juno

Regarding item #3: I have mainly seen this issue on stacks that have been snapshotted: https://bugs.launchpad.net/heat/+bug/1412965 In such cases, the only way to avoid (afaik) is for the owner to manually delete the snapshots prior to deleting the stack. Heat tries to auto-delete snapshots an

Re: [openstack-dev] [heat] heat delete woes in Juno

We don't have heat stack-abandon enabled. It's marked as a "preview feature", have you had any issues? Once you abandon the stack I assume you remove the resources outside of heat using nova/neutron etc? On Thu, Mar 26, 2015 at 1:15 PM, Ala Rezmerita wrote: > Hi Matt > > I had similar problems w

Re: [openstack-dev] [heat] heat delete woes in Juno

I will try to gather up these templates and post them somewhere once I scrub any company specific stuff. Might be a day or so. Thanks! On Thu, Mar 26, 2015 at 12:40 PM, Pavlo Shchelokovskyy < pshchelokovs...@mirantis.com> wrote: > Hi Matt, > > if it would be feasible/appropriate, could you provid

Re: [openstack-dev] [heat] heat delete woes in Juno

I attached an example of the template which is hanging right now in my Juno environment. I believe it hangs because of floating ip stuff and the way how it is attached to a VM. It is autogenerated, so please don't be disturbed by strange resource names. Thanks Gosha On Thu, Mar 26, 2015 at 12:15

Re: [openstack-dev] [Nova][cells] Meeting time change

Le 26 mars 2015 17:20, "Andrew Laski" a écrit : > > Daylight saving time has made it so that the 2200UTC meeting time is fairly inconvenient for a few of us and the 2100UTC timeslot is open so we're going to shift the meeting up by an hour. I have already spoken with many of the people in regular

Re: [openstack-dev] [heat] heat delete woes in Juno

Hi Matt I had similar problems with heat, and the work-around that i used is to abandon the stack (heat stack-abandon), and then I delete stack resources created one by one. Hope this helps. Ala Rezmerita Software Engineer || Cloudwatt M: (+33) 06 77 43 23 91 Immeuble Etik 892 rue Yves

[openstack-dev] [all] FYI:VPNaaS APIs moving from experimental to current

The VPNaaS APIs have been unchanged for over a year and were last marked as "experimental". Bug 1433561 is restoring the VPNaaS API reference documentation (was lost in a site update). As part of the review [1], there was some discussion about the experimental status, and so the status was changed

Re: [openstack-dev] [heat] heat delete woes in Juno

Hi Matt, if it would be feasible/appropriate, could you provide us with templates for stacks that show this behavior (try to get them with "heat template-show ")? This would help us to test and understand the problem better. And yes, just the day before I was contacted by one of my colleagues who

[openstack-dev] [heat] heat delete woes in Juno

Nobody on the operators list had any ideas on this, so re-posting here. We've been having some issues with heat delete-stack in Juno. The issues generally fall into three categories: 1) it takes multiple calls to heat to delete a stack. Presumably due to heat being unable to figure out the orderi

Re: [openstack-dev] [infra] What do people think of YAPF (like gofmt, for python)?

I have no clue how I managed to send that last email encrypted - Apologies :) Re YAPF, or autofomatting, I've very little opinion.. But - I gave YAPF a go against the Designate codebase with the stock config: 258 files changed, 5242 insertions(+), 5691 deletions(-) Getting changes like that i

Re: [openstack-dev] [cinder] Deadline For Volume Drivers to Be Readded

I'm not sure if I was clear... The driver is OK and snapshots are working as expected. I'm working on get all CI tests back (304 tests). On Thu, Mar 26, 2015 at 3:10 PM, Marcus Vinícius Ramires do Nascimento < marcus...@gmail.com> wrote: > Hi Mike, > > I'm working on it! The bug was fixed and now

Re: [openstack-dev] [cinder] Deadline For Volume Drivers to Be Readded

Hi Mike, I'm working on it! The bug was fixed and now I'm working to get all tempest.api.volume tests back again on our CI, including also the tests that were missing. On Thu, Mar 26, 2015 at 3:00 PM, Mike Perez wrote: > On 14:38 Thu 26 Mar , Erlon Cruz wrote: > > > > Our HBSD drivers are

Re: [openstack-dev] [cinder] Deadline For Volume Drivers to Be Readded

On 14:38 Thu 26 Mar , Erlon Cruz wrote: > Our HBSD drivers are only running 211 because we remove the snapshots tests > that were failing due a patch that broken our driver. Whats being done about that in Kilo? That's a minimum feature required for all drivers in Cinder: http://docs.openst

Re: [openstack-dev] [api][neutron] Best API for generating subnets from pool

Right now we force tenants choose a CIDR even if they don't care what address they get. This allows them to skip that required input. More importantly, if the network is fully routed, not only do tenants not know which CIDR to configure, allowing them to choose arbitrary CIDRs can disrupt the enti

Re: [openstack-dev] [cinder] Deadline For Volume Drivers to Be Readded

Hi Mike, The majority of the CIs don't run all 304 tests mostly because of these tempest problems. I remember there was a list in the Thirdparty CI Wiki with the common tests that used to fails to everyone, or at least most of people. IMO its better to have a more consistent CI than CIs with full

Re: [openstack-dev] [OpenStack-Infra][cinder] Could you please re-consider Oracle ZFS/SA Cinder drivers (iSCSI and NFS)

Hi Mike, The CI has been adjusted to run 304 tests since 3/24/2015 evening: https://review.openstack.org/#/q/reviewer:%22Oracle+ZFSSA+CI%22,n,z Here are examples of recent success runs: https://review.openstack.org/#/c/167080/ https://review.openstack.org/#/c/165763/ https://review.openstack.or

Re: [openstack-dev] [cinder] Deadline For Volume Drivers to Be Readded

On 09:39 Thu 26 Mar , Mike Perez wrote: > As discussed in the last Cinder meeting [1], in order to have your volume > driver readded into the Kilo release, you must have a CI reporting and stable > for five days prior to 4/6. > > This includes: > > 1) Providing logs to screen sessions, etc co

Re: [openstack-dev] [api][neutron] Best API for generating subnets from pool

Salvatore Orlando writes: > Neutron is adding a new concept of "subnet pool". [...] > http://specs.openstack.org/openstack/neutron-specs/specs/kilo/subnet-allocation.html I apologize for asking this question so long after this spec has been proposed and discussed - but what is the problem that

[openstack-dev] [puppet] Coordinator(s)/PTL tasks description

Hi, Following our Tuesday meeting, we decided to create a sort of PTL / Coordinators tasks list with the essence of https://wiki.openstack.org/wiki/PTL_Guide I list some point here, but feel free to add discuss about them, it's not (yet) written in stone. - Community (group) manager: The PTL

Re: [openstack-dev] [puppet] Moving under the "big tent"

On Mon, Mar 16, 2015 at 08:13:19AM (-0700), Colleen Murphy wrote: This thread is to follow up on our IRC discussion today. In today's meeting we started discussing whether we want to pursue applying to move under the OpenStack namespace and what pros and cons are. One concern that was brought up

Re: [openstack-dev] [puppet] Release management and bug triage

On Tue, Mar 17, 2015 at 01:46:06PM (-0700), Colleen Murphy wrote: Cons: * I think some people don't go on Launchpad because there is so many projects (one per module), so they did not subscribe emails or don't visit the page very often. * Each time we create a module (it's not every day, I would

Re: [openstack-dev] [puppet] Moving under the "big tent"

On Mon, Mar 16, 2015 at 05:06:14PM (+0100), Yanis Guenane wrote: To match user expectations, I think we should -as much as possible- act as a layer on top of the project themselves. So if the project the module installs is an official Openstack project, the module should be supported. Else 'incub

Re: [openstack-dev] [infra] What do people think of YAPF (like gofmt, for python)?

> On Mar 25, 2015, at 4:22 PM, Monty Taylor wrote: > > On 03/25/2015 05:50 PM, Maru Newby wrote: >> I am excited by the release of YAPF [1], a gofmt-like too for python. >> I think it has the potential to simplify style enforcement, and as >> much as I appreciate our current hacking checks, I’d

Re: [openstack-dev] [cinder] FCoE support in openstack

Hi rujing, When we implemented FC in Cinder and Nova, we had tested FCoE against the nova and cinder code we implemented and it just worked. As far as what nova sees in terms of volumes showing up in /dev/disk/by-path, and the HBA’s, there was no difference. If you test it and find issues, pl

[openstack-dev] [cinder] Deadline For Volume Drivers to Be Readded

As discussed in the last Cinder meeting [1], in order to have your volume driver readded into the Kilo release, you must have a CI reporting and stable for five days prior to 4/6. This includes: 1) Providing logs to screen sessions, etc configs, tempest output [2]. 2) You should be running around

Re: [openstack-dev] [infra] What do people think of YAPF (like gofmt, for python)?

binv2ijTsg9Fd.bin Description: PGP/MIME version identification encrypted.asc Description: OpenPGP encrypted message __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.op

Re: [openstack-dev] [infra] What do people think of YAPF (like gofmt, for python)?

On Thu, Mar 26, 2015 at 5:02 PM, James E. Blair wrote: > This is purposefully done to ensure that developers do not inadvertently > run code on their workstations from a source they may not trust. > Sure, but is that really make a difference between having some scripts in a tox.ini that are ru

Re: [openstack-dev] [Fuel] Nominate Irina Povolotskaya for fuel-docs core

+1 definitely On 03/25/2015 10:10 PM, Dmitry Borodaenko wrote: Fuelers, I'd like to nominate Irina Povolotskaya for the fuel-docs-core team. She has contributed thousands of lines of documentation to Fuel over the past several months, and has been a diligent reviewer: http://stackalytics.com/

[openstack-dev] [Nova][cells] Meeting time change

Daylight saving time has made it so that the 2200UTC meeting time is fairly inconvenient for a few of us and the 2100UTC timeslot is open so we're going to shift the meeting up by an hour. I have already spoken with many of the people in regular attendance at the meetings so this should come a

Re: [openstack-dev] [infra] What do people think of YAPF (like gofmt, for python)?

Chmouel Boudjnah writes: > On Thu, Mar 26, 2015 at 12:22 AM, Monty Taylor wrote: > >> git review is used by a ton of people who write in non-python. I think >> adding openstack-specific style enforcement to it would make it way less >> generally useful. >> > > > I think if we wanted to do that w

[openstack-dev] [QA] No Meeting this Week

Hi Everyone, There will be no QA meeting this week/today because a large contingent of people are at the QA code sprint this week. We will have the meeting next Thurs. at 22:00 UTC. Thanks, Matt Treinish pgpwbqXGouzlB.pgp Description: PGP signature ___

Re: [openstack-dev] [nova] [libvirt] The risk of hanging when shutdown instance.

On 03/25/2015 10:15 PM, Rui Chen wrote: Hi all: I found a discuss about the libvirt shutdown API maybe hang when shutdown instance in libvirt community, https://www.redhat.com/archives/libvir-list/2015-March/msg01121.html I'm not sure that whether there are some risks when we shutdown

[openstack-dev] [Heat] Decoupling Heat integration tests from Heat tree

Hi all, following IRC discussion here is a summary of what I propose can be done in this regard, in the order of increased decoupling: 1) make a separate requirements.txt for integration tests and modify the tox job to use it. The code of these tests is pretty much decoupled already, not using an

[openstack-dev] [horizon] FFE request

Hi. I would like to request a FFE for the following change request https://review.openstack.org/#/c/158715/ The blueprint for it has been approved for kilo. This change has a dependency on a change in python-saharaclient which has been recently merged.

Re: [openstack-dev] [depfreeze][horizon] Update to Django-1.7.x

On Thu, Mar 26, 2015 at 06:02:41AM -0400, Sean Dague wrote: > > Yes, just approved. Thank you, much appreciated! -- Matthias Runge __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-

Re: [openstack-dev] Mellanox request for permission for Nova CI

On Thu, Mar 19, 2015 at 5:52 AM, Nurit Vilosny wrote: > Hi Joe, > > Sorry for the late response. > > Here are some latest logs for the Nova CI: > > > http://144.76.193.39/ci-artifacts/Check-MLNX-Nova-ML2-Sriov-driver_20150318_1650/ > > > http://144.76.193.39/ci-artifacts/Check-MLNX-Nova-ML2-Srio

[openstack-dev] [Murano] Roadmap for Liberty (specs & blueprints)

Hi everyone, Kilo cycle is almost finished, and we are ready to accept specs & blueprints for Liberty. I would like to mention that our experiment with murano-specs is considered fairly successful, therefore starting from Liberty every blueprint for a new feature should be proposed with a spec su

Re: [openstack-dev] [barbican] Using KMIP with Barbican (Utkarsh Simha)

Hi Utkarsh, I am also happy to help figure out whats going in here, as Kaitlin says, the first step is get some more log info. -- Tim Kelsey Cloud Security Engineer HP Helion On 25/03/2015 15:24, "Farr, Kaitlin M." wrote: >Hi Utkarsh, > >Specifying "kmip_plugin" in the barbican-api.conf

Re: [openstack-dev] [devstack] Overriding settings file for devstack plugin

On Thu, Mar 26, 2015 at 5:09 PM, Deepak Shetty wrote: > > > On Thu, Mar 26, 2015 at 4:40 PM, Sean Dague wrote: > >> On 03/25/2015 09:26 AM, Dean Troyer wrote: >> > On Wed, Mar 25, 2015 at 6:04 AM, Deepak Shetty > > > wrote: >> > >> > Had a question here, why is th

Re: [openstack-dev] [devstack] Overriding settings file for devstack plugin

On Thu, Mar 26, 2015 at 4:40 PM, Sean Dague wrote: > On 03/25/2015 09:26 AM, Dean Troyer wrote: > > On Wed, Mar 25, 2015 at 6:04 AM, Deepak Shetty > > wrote: > > > > Had a question here, why is this source in the end ? > > > > > > More often than not, you will wan

Re: [openstack-dev] [devstack] Overriding settings file for devstack plugin

On 03/25/2015 09:26 AM, Dean Troyer wrote: > On Wed, Mar 25, 2015 at 6:04 AM, Deepak Shetty > wrote: > > Had a question here, why is this source in the end ? > > > More often than not, you will want the variables defined by the other > plugins (including the buil

Re: [openstack-dev] [Fuel] Let's stick to OpenStack global requirements

So guys, I think it’s reasonable to find a consensus on this thread. > I think this rule fits fine within the general frame of Roman's proposal: > > - if the base distro already has a package that satisfies OpenStack > global requirements (or Fuel requirements), the distro package is > used; > -

Re: [openstack-dev] [depfreeze][horizon] Update to Django-1.7.x

On 03/26/2015 03:40 AM, Matthias Runge wrote: > On Wed, Mar 25, 2015 at 12:00:11PM +0100, Matthias Runge wrote: >> On 25/03/15 11:34, Sean Dague wrote: >> Could you make this one "Depends on" https://review.openstack.org/#/c/167515/ so that we check that all Django 1.7 related issues

Re: [openstack-dev] [nova] CI report formatting (citrix / hyperv / vmware )

On 03/26/2015 03:41 AM, Gary Kotton wrote: > > > On 3/25/15, 3:21 PM, "Sean Dague" wrote: > >> On 03/25/2015 09:03 AM, Gary Kotton wrote: >>> >>> From: Jordan Pittier >> > >>> Reply-To: OpenStack List >> > >>> Date: We

[openstack-dev] [Fuel] Version bump in the beginning of a release cycle

Hi folks, This end of the release cycle I realized that due to different reasons bumping a version of Fuel’s components takes much more than just updating a set of text files. In fact it causes different kinds of cross-component problems which of course must be fixed. This email is not about f

Re: [openstack-dev] [Fuel] Nominate Irina Povolotskaya for fuel-docs core

+1 On Wed, Mar 25, 2015 at 10:10 PM, Dmitry Borodaenko < dborodae...@mirantis.com> wrote: > Fuelers, > > I'd like to nominate Irina Povolotskaya for the fuel-docs-core team. > She has contributed thousands of lines of documentation to Fuel over > the past several months, and has been a diligent r

Re: [openstack-dev] [neutron] [stringfreeze] request for SFE

Itsuro ODA wrote: > Neutron cores, > > I request SFE for the fix: > https://review.openstack.org/147032/ > https://bugs.launchpad.net/neutron/+bug/1408488 > > I believe there is consensus that this change is valuable > through the discussion on the thread [1]. +1, especially so early in the proc

Re: [openstack-dev] [Fuel] Nominate Irina Povolotskaya for fuel-docs core

+1. She's doing great job! On Thu, Mar 26, 2015 at 6:09 AM, Sergii Golovatiuk wrote: > +1 > > > > Best Regards, > Sergii Golovatiuk > >> On 25 Mar 2015, at 12:10, Dmitry Borodaenko wrote: >> >> Fuelers, >> >> I'd like to nominate Irina Povolotskaya for the fuel-docs-core team. >> She has contrib

Re: [openstack-dev] [nova] CI report formatting (citrix / hyperv / vmware )

On 3/25/15, 3:21 PM, "Sean Dague" wrote: >On 03/25/2015 09:03 AM, Gary Kotton wrote: >> >> From: Jordan Pittier > > >> Reply-To: OpenStack List > > >> Date: Wednesday, March 25, 2015 at 1:47 PM >> To: OpenStack List >

Re: [openstack-dev] [nova]Reviews for #164308 - Expand valid server group name character set

On 3/25/15, 10:27 PM, "Matt Riedemann" wrote: > > >On 3/25/2015 3:01 PM, Jennifer Mulsow wrote: >> Would anyone be willing to review >> https://review.openstack.org/#/c/164308/ (Expand valid server group name >> character set)? It has a few +1s, but there hasn't been any activity on >> it in a

Re: [openstack-dev] [depfreeze][horizon] Update to Django-1.7.x

On Wed, Mar 25, 2015 at 12:00:11PM +0100, Matthias Runge wrote: > On 25/03/15 11:34, Sean Dague wrote: > > >>Could you make this one "Depends on" > >>https://review.openstack.org/#/c/167515/ so that we check that all > >>Django 1.7 related issues are fixed ? > > > >I don't think it was ever suffic

Re: [openstack-dev] [infra] What do people think of YAPF (like gofmt, for python)?

On Thu, Mar 26, 2015 at 12:22 AM, Monty Taylor wrote: > git review is used by a ton of people who write in non-python. I think > adding openstack-specific style enforcement to it would make it way less > generally useful. > I think if we wanted to do that we could just extend git-review run_scr

  1   2   >