[openstack-dev] [infra] [devstack] [smaug] gate-smaug-dsvm-fullstack-nv is failed with exit code: 2

Hello team, The gate-smaug-dsvm-fullstack-nv is failed with exit code: 2. The console.html [1] includes the below information: Running devstack ERROR: the main setup script run by this job failed - exit code: 2 The devstacklog.txt.gz [2] includes the below information:+

Re: [openstack-dev] [horizon] Horizon in devstack is broken, rechecks are futile

The final patch https://review.openstack.org/#/c/321640/ has just merged, Devstack Horizon is fully functional and integration tests should be passing from this moment. If any of your patches are still failing due to dsvm-integration job's multiple failures, please rebase them. On Fri, May 27,

Re: [openstack-dev] [gate] [nova] live migration, libvirt 1.3, and the gate

On Tue, May 24, 2016 at 01:59:17PM -0400, Sean Dague wrote: > The team working on live migration testing started with an experimental > job on Ubuntu 16.04 to try to be using the latest and greatest libvirt + > qemu under the assumption that a set of issues we were seeing are > solved. The short

Re: [openstack-dev] [ironic] Tooling for recovering nodes

On 05/31/2016 10:25 AM, Tan, Lin wrote: Hi, Recently, I am working on a spec[1] in order to recover nodes which get stuck in deploying state, so I really expect some feedback from you guys. Ironic nodes can be stuck in deploying/deploywait/cleaning/cleanwait/inspecting/deleting if the node

Re: [openstack-dev] [vitrage] vitrage - how much links model in API is permanent?

Good to know. Thank you very much. -Original Message- From: Afek, Ifat (Nokia - IL) [mailto:ifat.a...@nokia.com] Sent: Tuesday, May 31, 2016 11:15 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev]

[openstack-dev] [ironic] Tooling for recovering nodes

Hi, Recently, I am working on a spec[1] in order to recover nodes which get stuck in deploying state, so I really expect some feedback from you guys. Ironic nodes can be stuck in deploying/deploywait/cleaning/cleanwait/inspecting/deleting if the node is reserved by a dead conductor (the

Re: [openstack-dev] [vitrage] vitrage - how much links model in API is permanent?

Hi Eylon, This dictionary is created by NetworkX, and is not about to be changed. You can definitely rely on this API to be permanent. And we should make sure we have a tempest test for verifying it. Best regards, Ifat. > -Original Message- > From: Malin, Eylon (Nokia - IL)

Re: [openstack-dev] [nova] I'm going to expire open bug reports older than 18 months.

Clint Byrum wrote: I 100% support those who are managing bugs doing whatever they need to do to make sure users' issues are being addressed as well as can be done with the resources available. However, I would also urge everyone to remember that the bug tracker is not only a way for developers

Re: [openstack-dev] [Monasca] influxDB clustering and HA will be "commercial option".

On Mon, May 30 2016, Jaesuk Ahn wrote: > It seems like “clustering” and “high availablity” of influxDB will be > available only in commercial version. > Monasca is currently leveraging influxDB as a metrics and alarm database. > Beside vertical, influxDB is currently only an open source option to

Re: [openstack-dev] [oslo] [keystone] rolling dogpile.core into dogpile.cache, removing namespace packaging (PLEASE REVIEW)

On 05/31/2016 12:17 AM, Mike Bayer wrote: > Hi all - > > Just a heads up what's happening for dogpile.cache, in version 0.6.0 we > are rolling the functionality of the dogpile.core package into > dogpile.cache itself, and retiring the use of namespace package naming > for dogpile.cache. > >

Re: [openstack-dev] [qa] [Tempest] Abondoned old code reviews

+1! But I think we can leave patches created in 2016 and abandon others. Regards, Yaroslav Lobankov. On Mon, May 30, 2016 at 8:20 PM, Ken'ichi Ohmichi wrote: > Hi, > > There are many patches which are not updated in Tempest review queue > even if having gotten negative

Re: [openstack-dev] Call for Commiters & Contributors for daisycloud-core project

Hi Zhijiang I think you can put Daisy into docker, then use ansible or kolla deploy Daisy. On Tue, May 31, 2016 at 9:43 AM, wrote: > Hi All, > > I would like to introduce to you a new OpenStack installer project > Daisy(project name: daisycloud-core). Daisy used to be

Re: [openstack-dev] [Openstack-operators] [glance] Proposal for a mid-cycle virtual sync on operator issues

Hi Nikhil, 2000UTC might catch a few kiwis, but it's 6am everywhere on the east coast of Australia, and even earlier out west. 0800UTC, on the other hand, would be more sociable. On 26 May 2016 at 15:30, Nikhil Komawar wrote: > Thanks Sam. We purposefully chose that time

<    1   2