Re: [openstack-dev] [qa] Lack of consistency in returning response from tempest clients

2014-08-30 Thread Andrea Frittoli
+1 keeping the body as a ~dict will help with all existing asserts comparing dicts in tests. Andrea On 30 Aug 2014 06:45, Christopher Yeoh cbky...@gmail.com wrote: On Fri, 29 Aug 2014 11:13:39 -0400 David Kranz dkr...@redhat.com wrote: On 08/29/2014 10:56 AM, Sean Dague wrote: On

Re: [openstack-dev] [qa] Lack of consistency in returning response from tempest clients

2014-08-30 Thread GHANSHYAM MANN
+1. That will also help full for API coming up with microversion like Nova. On Fri, Aug 29, 2014 at 11:56 PM, Sean Dague s...@dague.net wrote: On 08/29/2014 10:19 AM, David Kranz wrote: While reviewing patches for moving response checking to the clients, I noticed that there are places

[openstack-dev] Launch of a instance failed in juno

2014-08-30 Thread Nikesh Kumar Mahalka
Launch of a instance failed in juno devstack on ubuntu server 14.04 virtual machine. I am getting error Host not found. Below is part of /opt/stack/logs/screen/screen-n-cond.log 2014-08-30 12:06:51.721 ERROR nova.scheduler.utils [req-744ba1cf-7433-46b4-9771-9600a87e8c28 admin admin] [instance:

Re: [openstack-dev] Review change to nova api pretty please?

2014-08-30 Thread Alex Leonhardt
Thanks Flavio, that was sent to this list a long time before I joined, so my apologies to not have known. Is there a list of things not to send to this list somewhere accessible (link?) that I could review, to not send another (different) request by mistake and possibly upset or annoy people on

Re: [openstack-dev] Review change to nova api pretty please?

2014-08-30 Thread Chmouel Boudjnah
On Sat, Aug 30, 2014 at 11:28 AM, Alex Leonhardt aleonhardt...@gmail.com wrote: Is there a list of things not to send to this list somewhere accessible (link?) that I could review, to not send another (different) request by mistake and possibly upset or annoy people on here ? There is this

Re: [openstack-dev] [qa] Lack of consistency in returning response from tempest clients

2014-08-30 Thread Boris Pavlovic
Sean, class ResponseBody(dict): def __init__(self, body={}, resp=None): self.update(body) self.resp = resp Are you sure that you would like to have default value {} for method argument and not something like: class ResponseBody(dict): def __init__(self, body=None,

Re: [openstack-dev] Review change to nova api pretty please?

2014-08-30 Thread Alex Leonhardt
Thanks Choumel! Alex On 30 August 2014 11:49, Chmouel Boudjnah chmo...@enovance.com wrote: On Sat, Aug 30, 2014 at 11:28 AM, Alex Leonhardt aleonhardt...@gmail.com wrote: Is there a list of things not to send to this list somewhere accessible (link?) that I could review, to not send

[openstack-dev] [nova] libvirt version_cap, a postmortem

2014-08-30 Thread Mark McLoughlin
Hey The libvirt version_cap debacle continues to come up in conversation and one perception of the whole thing appears to be: A controversial patch was ninjaed by three Red Hat nova-cores and then the same individuals piled on with -2s when a revert was proposed to allow further

Re: [openstack-dev] [neutron][lbaas][octavia]

2014-08-30 Thread Adam Harwell
Only really have comments on two of your related points: [Susanne] To me Octavia is a driver so it is very hard to me to think of it as a standalone project. It needs the new Neutron LBaaS v2 to function which is why I think of them together. This of course can change since we can add whatever

Re: [openstack-dev] [nova] nova backup not working in stable/icehouse?

2014-08-30 Thread Preston L. Bannister
You are thinking of written-for-cloud applications. For those the state should not persist with the instance. There are a very large number of existing applications, not written to the cloud model, but which could be deployed in a cloud. Those applications are not all going to get re-written (as

Re: [openstack-dev] [nova][NFV] VIF_VHOSTUSER

2014-08-30 Thread Ian Wells
The problem here is that you've removed the vif_driver option and now you're preventing the inclusion of named VIF types into the generic driver, which means that rather than adding a package to an installation to add support for a VIF driver it's now necessary to change the Nova code (and

[openstack-dev] [openstack][neutron][jenkins]Merge failure in jenkins : gate-tempest-dsvm-neutron-full and

2014-08-30 Thread Nader Lahouti
Hi, There are failure in jenkins that not related to the patch: https://review.openstack.org/#/c/89211/ The console log shows errors as below. Has anybody seen these error? Is it a known issue. Please advise what needs to be done? 2014-08-30 15:26:11.789