Re: [openstack-dev] [Cinder] Questions about proposed volume replication patch

Hi Bruce, Bruce Montague wrote on 02/23/2014 03:35:10 AM: > Hi, regarding the proposed Cinder volume replication patch, < > https://review.openstack.org/#/c/64026 >: > > The replication driver methods are create_replica(), swap_replica(), > delete_replica(), > replication_status_check(), enab

Re: [openstack-dev] [nova][libvirt] Is there anything blocking the libvirt driver from implementing the host_maintenance_mode API?

Hi, Plesae note that regarding the Vmware driver the maintenance mode only works with the ESX driver and not the VC driver. For the VC driver there is a patch in review - https://review.openstack.org/#/c/72143/ Thanks Gary From: Jay Lau mailto:jay.lau@gmail.com>> Reply-To: "OpenStack Develop

Re: [openstack-dev] [All] Fixed recent gate issues

On 2/19/14 10:31 PM, "Alan Pevec" wrote: >> Yeah it's pip weirdness where things falls apart because of version >>cap. It's >> basically installing bin/swift from 1.9 when it sees the version >>requirement >> but it leaves everything in python-swiftclient namespace from master. >> >> So I've ac

Re: [openstack-dev] [nova][libvirt] Is there anything blocking the libvirt driver from implementing the host_maintenance_mode API?

On Sun, 2014-02-23 at 09:14 +0800, Jay Lau wrote: > So there is no need to implement libvirt driver for the > host_maintenance_mode API as host_maintenance_mode is mainly for > VMWare and XenServer, also we can use evacuate and os-services/disable > for libvirt host maintain, right? At a minimum,

Re: [openstack-dev] [Heat][docs] Need more sample HOT templates for users

On 22/02/14 06:42, Mike Spreitzer wrote: > Zane Bitter wrote on 02/21/2014 12:23:05 PM: > > > Yeah, we are overloading the term 'developer' here, since that section > > contains both information that is only useful to developers working on > > Heat itself, and information useful to users developin

Re: [openstack-dev] [Heat][docs] Need more sample HOT templates for users

On Sun, Feb 23, 2014 at 1:23 PM, Steve Baker wrote: > On 22/02/14 06:42, Mike Spreitzer wrote: > > Zane Bitter wrote on 02/21/2014 > 12:23:05 PM: > > > Yeah, we are overloading the term 'developer' here, since that section > > contains both information that is only useful to developers working

Re: [openstack-dev] [Murano] Heat resource isolation withing single stack

On 22/02/14 03:37, Stan Lagun wrote: > Hi Everyone, > > While looking through Heat templates generation code in Murano I've > realized it has a major design flaw: there is no isolation between > Heat resources generated by different apps. > > Every app manifest can access and modify its environment

[openstack-dev] [qa] Can't interpret failure from XenServer CI

XenServer reported failure on https://review.openstack.org/#/c/73704. The pointer to the logs should look like a jenkins failure but does not in two ways. First, there is no console log, with a directory of other log files next to it. Second, the .gz log files are not set up to be downloaded as

Re: [openstack-dev] [Heat][docs] Need more sample HOT templates for users

On 24/02/14 08:44, Anne Gentle wrote: > > > > On Sun, Feb 23, 2014 at 1:23 PM, Steve Baker > wrote: > > On 22/02/14 06:42, Mike Spreitzer wrote: >> Zane Bitter >> wrote on 02/21/2014 12:23:05 PM: >> >> > Yeah, we are overloadin

Re: [openstack-dev] [qa] Can't interpret failure from XenServer CI

Hi David, That's a very strange error - it basically means the node has been used for running a test already (both the first error in run_tests.log about the git repository also existing, and the more fatal error about vif 3 existing) I believe this was my fault - I should have purged all negat

Re: [openstack-dev] [TripleO][review] Please treat -1s on check-tripleo-*-precise as voting.

On 22 February 2014 05:36, Derek Higgins wrote: > the ci cloud seems to be running today as expected, but we have a bit to > tuning todo > > check-tripleo-overcloud-precise is throwing out false negatives because > the testenv-worker has a timeout that is less then the timeout on the > jenkins jo

Re: [openstack-dev] [Heat][docs] Need more sample HOT templates for users

On 02/23/2014 09:14 PM, Steve Baker wrote: > On 24/02/14 08:44, Anne Gentle wrote: >> >> >> >> On Sun, Feb 23, 2014 at 1:23 PM, Steve Baker > > wrote: >> >> On 22/02/14 06:42, Mike Spreitzer wrote: >>> Zane Bitter >>> wrote on 02/21

Re: [openstack-dev] [Heat][docs] Need more sample HOT templates for users

On 02/23/2014 01:14 PM, Steve Baker wrote: On 24/02/14 08:44, Anne Gentle wrote: On Sun, Feb 23, 2014 at 1:23 PM, Steve Baker > wrote: On 22/02/14 06:42, Mike Spreitzer wrote: Zane Bitter wrote on 02/21/2014 12:23:05 PM:

Re: [openstack-dev] [qa] Can't interpret failure from XenServer CI

On 02/23/2014 03:29 PM, Bob Ball wrote: Hi David, That's a very strange error - it basically means the node has been used for running a test already (both the first error in run_tests.log about the git repository also existing, and the more fatal error about vif 3 existing) I believe this was

Re: [openstack-dev] [qa] Can't interpret failure from XenServer CI

I believe I've identified the bug - it seems to have occurred when restarting the Citrix CI system while the tests were in the process of being run, leading it to believe that they had not been invoked yet and therefore triggering the tests on that node a second time. I've implemented a fix - t

Re: [openstack-dev] [qa] Can't interpret failure from XenServer CI

Agreed on both counts - I'd already updated the message to say that as well as supporting the standard "recheck" you can run "citrix recheck" to only trigger a recheck of XenServer and will try and fix the http headers tomorrow. Bob From: David Kranz [dkr

Re: [openstack-dev] [Heat][docs] Need more sample HOT templates for users

On Sun, Feb 23, 2014 at 2:14 PM, Steve Baker wrote: > On 24/02/14 08:44, Anne Gentle wrote: > > > > > On Sun, Feb 23, 2014 at 1:23 PM, Steve Baker wrote: > >> On 22/02/14 06:42, Mike Spreitzer wrote: >> >> Zane Bitter wrote on >> 02/21/2014 12:23:05 PM: >> >> > Yeah, we are overloading the

Re: [openstack-dev] [solum] async / threading for python 2 and 3

On 21/02/14 11:03 +0100, Victor Stinner wrote: Le vendredi 21 février 2014, 09:27:49 Angus Salkeld a écrit : >Honestly, I have no answer to your question right now ("How useful is >trollius ..."). >(...) >I asked your question on Tulip mailing list to see how a single code base >could support Tu

Re: [openstack-dev] False Positive testing for 3rd party CI

One Convergence CI did report the third party tests as failed, but is configured not to vote. Should we turn on the voting? Thanks, -hemanth On Fri, Feb 21, 2014 at 1:29 PM, Carl Baldwin wrote: > Aaron, > > I was thinking the same thing recently with this patch [1]. Patch > sets 1-5 should ha

Re: [openstack-dev] [Murano] Heat resource isolation withing single stack

> I would like the Murano project to evaluate the upcoming heat > software-config resources to represent app configuration. Yes, we are closely watching progress being made in Heat in that area and evaluating how all new great features can be used in Murano > Inferring from the above, it sounds l

Re: [openstack-dev] [nova][libvirt] Is there anything blocking the libvirt driver from implementing the host_maintenance_mode API?

On Sunday, February 23, 2014 12:41:15 PM, Jay Pipes wrote: On Sun, 2014-02-23 at 09:14 +0800, Jay Lau wrote: So there is no need to implement libvirt driver for the host_maintenance_mode API as host_maintenance_mode is mainly for VMWare and XenServer, also we can use evacuate and os-services/d

[openstack-dev] [OpenStack-dev][Nova] Can we add one configuration item for cache-using in libvirt/hypervisor?

Hi all, Recently, I met one scenario which needs to close the cache on linux hypervisor. But some codes written in libvirt/driver.py (including suspend/snapshot) are hard-coded. For example: --- def suspend(self, instance): """Suspend the specified instance.""" dom = s

[openstack-dev] 答复: [OpenStack-dev][Nova] Can we add one configuration item for cache-using in libvirt/hypervisor?

Sure, hard-coding seems weird… However, a global configuration here dominates all domains. It might be a little too strong in cases in which we want to apply various configurations to different domains. Could we add any new attributes in the info for creating a domain for this? Or any other su

Re: [openstack-dev] False Positive testing for 3rd party CI

Thanks Aaron, it is really interesting. > The Hyper-V CI is non-voting (as required for new third-party CIs) and this > is the reason why any post from it will show “build succeeded”. As published > in other threads, AFAIK the only way to get rid > of this issue is to have the CI as voting.

[openstack-dev] [nova] Question about USB passthrough

Hi, Boris and all other guys: I have found a BP about USB device passthrough in https://blueprints.launchpad.net/nova/+spec/host-usb-passthrough. I have also read the latest nova code and make sure it doesn't support USB passthrough by now. Are there any progress or plan for USB passthrough?

Re: [openstack-dev] HDD-type config-drive and Windows VM

Hi Alessandro, Thank you for your description. You are right. I'm now using Nova-2013.1.3 on Ubuntu 12.04 and going to upgrade to 2013.1.4 soon. Best regards, Akira On 2014年2月23日 6:38:24 GMT+09:00, Alessandro Pilotti wrote: >Please check also this bug fixed in Havana: >https://bugs.launchpad.

Re: [openstack-dev] Cinder Stability Hack-a-thon

On Fri, Feb 7, 2014 at 6:51 PM, Mike Perez wrote: > Google hangout has a limit of 10 people, but that might be fine with the > participation. If someone has a better suggestion > for video/voice chat (we don't really need video), that works with > windows/linux/mac, suggest it on the ether pad.

Re: [openstack-dev] [Nova][glance] Question about evacuate with no shared storage..

I think we are running away from the original question here, 'live-migration' and 'evacuate' aim to handle different scenarios. When you use 'live migration', you have a plan that when your compute node will shutdown. IMHO, The only way to provide VM high availability automatically by using 'evacua

[openstack-dev] [Solum] Notice: Team meeting cancelled for 2014-02-25

Team, Due to the planned absence of the chair, and several key contributors, I have cancelled our Tuesday team meeting for this week. Our normal schedule will resume next week on 2014-03-04. I apologize for the short notice. https://wiki.openstack.org/wiki/Meetings/Solum Regards, Adrian _

[openstack-dev] [python-openstacksdk] Sessions and keystoneclient

I promised Jesse after the openstack-sdk meeting that I would do a write up of the direction of keystoneclient's auth plugins and Sessions. Have a look here: http://www.jamielennox.net/blog/2014/02/24/client-session-objects/ I know that this is different to the way Dean was looking at using them

[openstack-dev] [nova] Future of the Nova API

Hi, There has recently been some speculation around the V3 API and whether we should go forward with it or instead backport many of the changes to the V2 API. I believe that the core of the concern is the extra maintenance and test burden that supporting two APIs means and the length of time befor

Re: [openstack-dev] [nova] Future of the Nova API

On Mon, 2014-02-24 at 17:20 +1030, Christopher Yeoh wrote: > - Proposed way forward: > - Release the V3 API in Juno with nova-network and tasks support > - Feature freeze the V2 API when the V3 API is released > - Set the timeline for deprecation of V2 so users have a lot > of warning

[openstack-dev] Win 2008 R2 VMDK upload to glance

Hi All, I wanted to upload a new Win 2k8 R2 VMDK file to glance. I have created a new windows VM with 20 GB hdd on ESXi 5.1 and then uploaded the flat file to Glance. But when ever VM boots from openstack, it goes to recovery mode. Any help or point to correct solution document will be of great

[openstack-dev] [neutron]Can somebody describe the all the rolls about networks' admin_state_up

Hi, I want to know the admin_state_up attribute about networks but I have not found any describes. Can you help me to understand it? Thank you very much. Regard, Lee Li ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://list