Re: [openstack-dev] [Glance] Regarding Glance's behaviour when updating an image ...

On 25/11/13 03:23 +, David koo wrote: Hi All, Newbie stacker here ... I have a basic question regarding the indended behaviour of Glance's image update API: What is the indended behaviour of Glance when updating an already uploaded image file? The functional test indicates that th

[openstack-dev] [Keystone][Marconi][Oslo] Discoverable home document for APIs (Was: Re: [Nova][Glance] Support of v1 and v2 glance APIs in Nova)

On 25/11/13 09:28 +1000, Jamie Lennox wrote: So the way we have this in keystone at least is that querying GET / will return all available API versions and querying /v2.0 for example is a similar result with just the v2 endpoint. So you can hard pin a version by using the versioned URL. I spoke

Re: [openstack-dev] [Nova][Schduler] Volunteers wanted for a modest proposal for an external scheduler in our lifetime

As said earlier, I also would love to join the team, triggering a few blueprints or so. By the way, I'm currently reviewing the Scheduler code. Do you began to design the API queries or do you need help for that ? -Sylvain Le 25/11/2013 08:24, Haefliger, Juerg a écrit : Hi Robert, I see

[openstack-dev] [Nova] Remove ratelimits from nova v3 api

Hi, guys, Looks like ratelimits is not really useful. The reason already pointed out by this patch: https://review.openstack.org/#/c/34821/ , Thanks Joe for point it out. So v3 API is a chance to cleanup those stuff. If there isn't anyone object it. I will send patch to get ride of ratelimit

Re: [openstack-dev] [Oslo] Improving oslo-incubator update.py

On 25/11/13 09:34 +0800, Zhongyue Luo wrote: Just a thought but couldn't the changes of a module update be calculated by comparing the last commit dates of the source and target module? For instance, if module A's update patch for Nova was uploaded on date XX then we can filter out the changes f

Re: [openstack-dev] [Oslo] Improving oslo-incubator update.py

On 23/11/13 11:54 -0500, Doug Hellmann wrote: Thanks for the reminder, Sandy. https://bugs.launchpad.net/oslo/+bug/1254300 On Sat, Nov 23, 2013 at 9:39 AM, Sandy Walsh wrote: Seeing this thread reminded me: We need support in the update script for entry points in olso setup.cfg to

Re: [openstack-dev] tenant or project

On 24/11/13 12:47 -0500, Doug Hellmann wrote: On Sun, Nov 24, 2013 at 12:08 AM, Morgan Fainberg wrote: In all honesty it doesn't matter which term we go with. As long as we are consistent and define the meaning. I think we can argue intuitive vs non-intuitive in this case unto the

Re: [openstack-dev] Unwedging the gate

Excerpts from Joe Gordon's message of 2013-11-24 21:00:58 -0800: > Hi All, > > TL;DR Last week the gate got wedged on nondeterministic failures. Unwedging > the gate required drastic actions to fix bugs. > > (great write-up, thank you for the details, and thank you for fixing it!) > > Now th

Re: [openstack-dev] Unwedging the gate

On 25 November 2013 22:23, Clint Byrum wrote: > I do wonder if we would be able to commit enough resources to just run > two copies of the gate in parallel each time and require both to pass. > Doubling the odds* that we will catch an intermittent failure seems like > something that might be wort

Re: [openstack-dev] [Neutron] Find the compute host on which a VM runs

On Thu, Nov 21, 2013 at 6:03 PM, Aaron Rosen wrote: > > > > On Thu, Nov 21, 2013 at 8:12 AM, Robert Kukura wrote: >> >> On 11/21/2013 04:20 AM, Stefan Apostoaie wrote: >> > Hello again, >> > >> > I studied the portbindings extension (the quantum.db.portbindings_db and >> > quantum.extensions.port

Re: [openstack-dev] [horizon] adding jshint to qunit tests (was: Javascript development improvement)

On 22/11/13 16:08, Imre Farkas wrote: > There's a jslint fork called jshint which is able to run in the browser > without any node.js dependency. > > I created a POC patch [1] long time ago to demonstrate its capabilities. > It's integrated with qunit and runs automatically with the horizon test >

Re: [openstack-dev] [horizon] Javascript development improvement

On 11/22/2013 04:08 PM, Imre Farkas wrote: > > There's a jslint fork called jshint which is able to run in the browser > without any node.js dependency. > > I created a POC patch [1] long time ago to demonstrate its capabilities. > It's integrated with qunit and runs automatically with the horiz

Re: [openstack-dev] [nova] future fate of nova-network?

Russell Bryant wrote: > On 11/22/2013 12:55 PM, Lorin Hochstein wrote: >> To that end, I recommend posting questions like "We're thinking of >> making large change 'X', how will that affect existing OpenStack >> deployments?" to the openstack-operators mailing list. >> >> I know there are several

Re: [openstack-dev] [Keystone][Oslo] Future of Key Distribution Server, Trusted Messaging

Adam Young wrote: > Keep KDS configuration separate from the Keystone configuration: the > fact that they both point to the same host and port is temporary. In > fact, we should probably spin up a separate wsgi service/port inside > Keystone for just the KDS. This is not hard to do, and will supp

Re: [openstack-dev] [nova] future fate of nova-network?

On Sun, Nov 24, 2013 at 11:10:23AM +1300, Robert Collins wrote: > On 23 November 2013 05:32, Daniel P. Berrange wrote: > > On Fri, Nov 22, 2013 at 11:24:18AM -0500, Russell Bryant wrote: > >> A good example is the current discussion around a new scheduling > >> service. There have been lots of bi

Re: [openstack-dev] [nova] who wants to own docker bug triage?

Matt Riedemann wrote: > On Saturday, November 23, 2013 3:28:28 PM, Robert Collins wrote: >> Cool; also, if it's not, we should add that as an official tag so that >> it type-completes in LP. >> > Good idea. I don't know how to do that though. Any guides I can follow > to make that happen? I adde

Re: [openstack-dev] [nova] future fate of nova-network?

"I've moved my cloud neutron already, but while it provides many advanced features it still really falls down on providing simple solutions for simple use cases" it is my feeling as well. I am not able to easily achieve my running neutron smoothly, and there are a lot of tricks. Compare to nova-net

[openstack-dev] [Climate] Today's meeting minutes

Hi, You can find our today's meeting minutes here : http://eavesdrop.openstack.org/meetings/climate/2013/climate.2013-11-25-09.59.html Thanks, -Sylvain ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin

Re: [openstack-dev] [nova] python-novaclient: uses deprecated keyring.backend.$keyring

On 11/25/2013 03:57 AM, Morgan Fainberg wrote: > Hi Thomas, > > How pressing is this issue? It seems it's blocking some python package transition from Sid to Jessie, and impacting the Gnome guys, so it's quite annoying for Debian. So much that some wanted to NMU the novaclient package. At least,

Re: [openstack-dev] FreeBSD hypervisor (bhyve) driver

On Fri, Nov 22, 2013 at 4:46 PM, Russell Bryant wrote: > On 11/22/2013 10:43 AM, Rafał Jaworowski wrote: >> Russell, >> First, thank you for the whiteboard input regarding the blueprint for >> FreeBSD hypervisor nova driver: >> https://blueprints.launchpad.net/nova/+spec/freebsd-compute-node >> >>

Re: [openstack-dev] [Nova] Remove ratelimits from nova v3 api

Hi Alex, Is removing the ratelimiting code part of the roadmap? I fear that if it's removed now, it may have to be re-implemented in the future as the cloud deployments become more mainstream ... Without ratelimit, some evil users could DOS Openstack ! Dave __

Re: [openstack-dev] [Glance] Regarding Glance's behaviour when updating an image ...

Hey David, I noticed the same thing a couple of days ago and had filed this bug: https://bugs.launchpad.net/glance/+bug/1249409 Glance v2 api should not be allowing re-uploads IMO. Feel free to add to the comments there. Thanks, Iccha -Original Message- From: "David koo" Sent: Sunday

Re: [openstack-dev] Unwedging the gate

Many thanks to everyone who helped with the many fixes. Kudos to Joe/Clark for spear heading the effort! -- dims On Mon, Nov 25, 2013 at 12:00 AM, Joe Gordon wrote: > Hi All, > > TL;DR Last week the gate got wedged on nondeterministic failures. Unwedging > the gate required drastic actions to fi

[openstack-dev] [Tempest] Drop python 2.6 support

Hi all, I saw that Tempest will drop python 2.6 support in design summit https://etherpad.openstack.org/p/icehouse-summit-qa-parallel. Drop tempest python 2.6 support:Remove all nose hacks in the codeDelete nose, use unittest2 with testr/testtools and everything *should* just work (tm) Does tha

Re: [openstack-dev] [nova] future fate of nova-network?

On 11/23/2013 10:44 AM, Gary Kotton wrote: > > > On 11/22/13 2:47 PM, "Daniel P. Berrange" wrote: > >> On Fri, Nov 22, 2013 at 11:25:51AM +, John Garbutt wrote: > On Fri, Nov 15, 2013 at 2:21 PM, Russell Bryant >>> wrote: >>> In particular, has there been a decision made about whet

Re: [openstack-dev] [horizon / keystone] Marker could not be found?

Hi I filed this under https://bugs.launchpad.net/horizon/+bug/1247752 and commented out the the 'else' of the 'if marker is not None:' branch in _format_project_list to fix this on my installation. def _format_project_list(self, tenant_refs, **kwargs): marker = kwargs.get('marker') first_i

[openstack-dev] EC2 Filter

Hi Folks. I stumbled over the lacking of EC2 Api filter support on Openstack and justinsb¹s (and the other people I forgot to mention here) attempt [1] to implement this against diabolo. I¹m highly interested in this feature and would like (to try) to implement this features against the latest ba

[openstack-dev] [Openstack-dev][Neutron] Handling of ovs command errors

Hi, I've been recently debugging some issues I've had with the OVS agent, and I found out that in many cases (possibly every case) the code just logs errors from ovs-vsctl and ovs-ofctl without taking any action in the control flow. For instance, the routine which should do the wiring for a port

Re: [openstack-dev] FreeBSD hypervisor (bhyve) driver

> So just to clarify: the native driver for another hypervisor (bhyve) > would not be accepted into Nova even if it met testing coverage > criteria? As I said the libvirt route is an option we consider, but we > would like to have the possibility of a native FreeBSD api integration > as well, simil

Re: [openstack-dev] FreeBSD hypervisor (bhyve) driver

On Fri, Nov 22, 2013 at 10:46:19AM -0500, Russell Bryant wrote: > On 11/22/2013 10:43 AM, Rafał Jaworowski wrote: > > Russell, > > First, thank you for the whiteboard input regarding the blueprint for > > FreeBSD hypervisor nova driver: > > https://blueprints.launchpad.net/nova/+spec/freebsd-comput

Re: [openstack-dev] Unwedging the gate

On 11/25/2013 04:23 AM, Clint Byrum wrote: > Excerpts from Joe Gordon's message of 2013-11-24 21:00:58 -0800: >> Hi All, >> >> TL;DR Last week the gate got wedged on nondeterministic failures. Unwedging >> the gate required drastic actions to fix bugs. >> >> > > > (great write-up, thank you for

Re: [openstack-dev] [Openstack-dev][Neutron] Handling of ovs command errors

On Nov 25, 2013, at 8:28 AM, Salvatore Orlando wrote: > > Hi, > > I've been recently debugging some issues I've had with the OVS agent, and I > found out that in many cases (possibly every case) the code just logs errors > from ovs-vsctl and ovs-ofctl without taking any action in the control

[openstack-dev] [Nova] Icehouse mid-cycle meetup

Greetings, Other groups have started doing mid-cycle meetups with success. I've received significant interest in having one for Nova. I'm now excited to announce some details. We will be holding a mid-cycle meetup for the compute program from February 10-12, 2014, in Orem, UT. Huge thanks to B

[openstack-dev] [nova] remote debugging

Hi Folks - i am trying to add a patch to enable remote debugging in the nova services. I can make this work very simply, but it requires a change to monkey_patching - i.e. eventlet.monkey_patch(os=False, select=True, socket=True, thread=False, time=True, psycopg=True)

[openstack-dev] [Ironic][Ceilometer] get IPMI data for ceilometer

Hello all: Basically, I understand the solution is - Our Ironic will implement an IPMI driver(extendable framework for more drivers) to collect hardware sensor data(cpu temp, fan speed, volts, etc) via IPMI protocol from hardware server node, and emit the AMQP message to Ceilometer Collector

Re: [openstack-dev] [nova] remote debugging

On 11/25/2013 10:28 AM, Tracy Jones wrote: > Hi Folks - i am trying to add a patch to enable remote debugging in the > nova services. I can make this work very simply, but it requires a > change to monkey_patching - i.e. > > eventlet.monkey_patch(os=False, select=True, socket=True, thread=Fal

[openstack-dev] Adding notifications to Horizon

Hi, I am interested in adding AMQP notifications to the Horizon dashboard, as described in the following blueprint: https://blueprints.launchpad.net/horizon/+spec/horizon-notifications There are currently several implementations in Openstack. While Nova and Cinder define `notify_about_*` methods

Re: [openstack-dev] [Nova][Glance] Support of v1 and v2 glance APIs in Nova

On 11/22/2013 09:07 PM, Matt Riedemann wrote: > > > On Friday, November 22, 2013 5:52:17 PM, Russell Bryant wrote: >> On 11/22/2013 06:01 PM, Christopher Yeoh wrote: >>> >>> On Sat, Nov 23, 2013 at 8:33 AM, Matt Riedemann >>> mailto:mrie...@linux.vnet.ibm.com>> wrote: >>> >>> ... >>> 21

[openstack-dev] [Keystone][Oslo] Future of Key Distribution Server, Trusted Messaging

Hello folks, FWIW, I've created a wiki page here aimed at easing the code transition to barbican for the KDS patch: https://github.com/cloudkeep/barbican/wiki/Blueprint:-KDS-Service Please let us know if we can be of further help. Thanks, John ___ Op

Re: [openstack-dev] [horizon / keystone] Marker could not be found?

This is indeed a bug in the Horizon code base. The use of marker in the API call is incorrect in this case. This should be fixed in i-1. -David > -Original Message- > From: Sebastian Porombka [mailto:porom...@uni-paderborn.de] > Sent: Monday, November 25, 2013 7:15 AM > To: OpenStack D

[openstack-dev] [horizon] JavaScript use policy

Hello everyone, there has been some talks about this behind the stage for a while, but I think that we need to have this discussion here at last and make a deicsion. We need a clear, concrete and enforcable policy about the use of client-side JavaScript in Horizon. The current guideline "it would

Re: [openstack-dev] Adding notifications to Horizon

+1 on the inline method. It makes it clear when a notification should be emitted and, as you say, handles the exception handling better. Also, if it makes sense for Horizon, consider bracketing long-running operations in .start/.end pairs. This will help with performance tuning and early error det

Re: [openstack-dev] [Neutron][IPv6] Meeting logs from the first IRC meeting

Great! Let's try and schedule a time for an IRC meeting that works for everyone so we can discuss the patch. I'm happy to do the meeting on an Asia friendly time, since it's hard to do the scheduled time at 2100UTC, and we'll just post the logs. -- Sean M. Collins

Re: [openstack-dev] How to best make User Experience a priority in every project

On Nov 21, 2013, at 10:20 AM, Jesse Noller wrote: > I’ve spoken to Everett and others about discussions had at the summit around > ideas like developer.openstack.org - and I think the idea is a good start > towards improving the lives of downstream application developers. Blueprint started by T

Re: [openstack-dev] Unwedging the gate

Excerpts from Robert Collins's message of 2013-11-25 01:30:11 -0800: > On 25 November 2013 22:23, Clint Byrum wrote: > > > I do wonder if we would be able to commit enough resources to just run > > two copies of the gate in parallel each time and require both to pass. > > Doubling the odds* that

[openstack-dev] [marconi] New meeting time

Hi folks, To make it easier on our friends joining the project from across the world, I’d like to propose moving our weekly meeting time back one hour to 1500 UTC: http://www.timeanddate.com/worldclock/fixedtime.html?hour=15&min=0&sec=0 Any objections or alternate suggestions? --- @kgriffs Kur

Re: [openstack-dev] [marconi] New meeting time

Works for me. Amit. From: Kurt Griffiths mailto:kurt.griffi...@rackspace.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Monday, November 25, 2013 at 11:59 AM To: OpenStack Dev mailto:openstack-dev@lists.openstack

Re: [openstack-dev] [nova] remote debugging

Hi, http://debugopenstack.blogspot.in/ I have done Openstack remote debugging with eclipse and pydev. only change is to exclude python thread library from monkey patch at service start up. Regards, Yatin On Mon, Nov 25, 2013 at 9:10 PM, Russell Bryant wrote: > On 11/25/2013 10:28 AM, Tracy

[openstack-dev] [Mistral] Community meeting minutes - 11/25/2013

Hi, Thanks to everyone who joined the meeting today, here’s the minutes and the full log: Minutes: http://eavesdrop.openstack.org/meetings/mistral/2013/mistral.2013-11-25-16.00.html Log: http://eavesdrop.openstack.org/meetings/mistral/2013/mistral.2013-11-25-16.00.log.html Join us next week!

Re: [openstack-dev] [nova] remote debugging

Thanks Yatin - that is the change I am proposing in my patch On Nov 25, 2013, at 9:09 AM, yatin kumbhare wrote: > Hi, > > http://debugopenstack.blogspot.in/ > > I have done Openstack remote debugging with eclipse and pydev. > > only change is to exclude python thread library from monkey patc

Re: [openstack-dev] [Nova] Remove ratelimits from nova v3 api

On Mon, 2013-11-25 at 07:38 -0500, David Hill wrote: >Is removing the ratelimiting code part of the roadmap? I fear that > if it's removed now, it may have to be re-implemented in the future as > the cloud deployments become more mainstream ... Without ratelimit, > some evil users could DOS Op

[openstack-dev] [savanna] summit wrap-up: Heat integration

Hi guys, There was the Design Summit session in Hong Kong about Heat integration and Savanna scalability [0]. We discussed some details about it, approved integration plan and decided to use guest agents. First of all, or the Icehouse release cycle, we’ll implement resources orchestration usin

Re: [openstack-dev] Adding notifications to Horizon

Sandy Walsh wrote on 11/25/2013 10:30:05 AM: > From: Sandy Walsh > To: , > Date: 11/25/2013 10:34 AM > Subject: Re: [openstack-dev] Adding notifications to Horizon > > +1 on the inline method. It makes it clear when a notification should be > emitted and, as you say, handles the exception han

Re: [openstack-dev] [Solum] git-Integration working group

- Original Message - > > > On 11/22/2013 09:51 PM, Adrian Otto wrote: > > Monty, > > > > On Nov 22, 2013, at 6:24 PM, Monty Taylor > > wrote: > > > >> On 11/22/2013 05:37 PM, Krishna Raman wrote: > >>> Hello all, > >>> > >>> I would like to kickoff the Git integration discussion. Go

Re: [openstack-dev] [horizon] JavaScript use policy

We have been having this discussion here on the mailing list [1][2] and also in the Horizon team meetings [3]. The overall consensus has been that we are going to move forward with a JavaScript requirement. Most of the pushback to support non-JavaScript is based on web-accessibility standards

Re: [openstack-dev] [Nova] Remove ratelimits from nova v3 api

+2 Turnstile seems to be a good middle ground (other companies I know have solutions for this problem via other software), does anyone have operational knowledge they can share about how turnstile has worked out for them? Sent from my really tiny device... > On Nov 25, 2013, at 9:22 AM, "Kevin

Re: [openstack-dev] [marconi] New meeting time

On 25/11/13 17:05 +, Amit Gandhi wrote: Works for me. Works for me! -- @flaper87 Flavio Percoco pgpkFlvVx8sKs.pgp Description: PGP signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mai

Re: [openstack-dev] Unwedging the gate

+2 Sent from my really tiny device... > On Nov 25, 2013, at 5:02 AM, "Davanum Srinivas" wrote: > > Many thanks to everyone who helped with the many fixes. Kudos to > Joe/Clark for spear heading the effort! > > -- dims > >> On Mon, Nov 25, 2013 at 12:00 AM, Joe Gordon wrote: >> Hi All, >> >>

Re: [openstack-dev] [Trove] configuration groups using overrides file

Denis, I'm proposing that #3 and #4 sorta be swapped from your list where we merge the config group parameters into the main config and send down the file like we do now. So the guest does not need to handle the merging. The logic is the same just the location of the logic to merge be handled by t

Re: [openstack-dev] [Solum] Working group on language packs

Hi, Just for clarification for Windows images, I think Windows image creation is closer to Docker approach. In order to create a special Windows image we use KVM\QEMU VM with initial base image, then install all necessary components, configure them and then run special tool sysprep to remove all m

Re: [openstack-dev] Unwedging the gate

Excerpts from Monty Taylor's message of 2013-11-25 06:52:02 -0800: > > On 11/25/2013 04:23 AM, Clint Byrum wrote: > > Excerpts from Joe Gordon's message of 2013-11-24 21:00:58 -0800: > >> Hi All, > >> > >> TL;DR Last week the gate got wedged on nondeterministic failures. Unwedging > >> the gate re

Re: [openstack-dev] [Trove] configuration groups using overrides file

I disagree. Guest should be able to do (for now two things): 1. Installing db, post-install configuration (dpkg reconfigure, etc.) 2. Allowing to apply outcome configuration in dictionary format. As i mentioned earlier. There could be a problem with updating full config file. Reason is simple: pos

[openstack-dev] [Swift] Pete Zaitcev added to core

Pete Zaitcev has been involved with Swift for a long time, both by contributing patches and reviewing patches. I'm happy to announce that he's accepted the responsibility of being a core reviewer for Swift. Congrats, Pete. --John signature.asc Description: Message signed with OpenPGP using

Re: [openstack-dev] Reg : Security groups implementation using openflows in quantum ovs plugin

Adding Jun to this thread since gmail is failing him. On Tue, Nov 19, 2013 at 10:44 AM, Amir Sadoughi wrote: > Yes, my work has been on ML2 with neutron-openvswitch-agent. I’m > interested to see what Jun Park has. I might have something ready before he > is available again, but would like to

Re: [openstack-dev] Unwedging the gate

On 2013-11-25 09:55:03 -0800 (-0800), Clint Byrum wrote: > Excerpts from Monty Taylor's message of 2013-11-25 06:52:02 -0800: [...] > > recheck no bug still has a host of valid use cases. Often times > > I use it when I upload a patch, it fails because of a thing > > somewhere else, we fix that, an

Re: [openstack-dev] [Openstack-dev][Neutron] Handling of ovs command errors

Thanks Kyle, More comments inline. Salvatore On 25 November 2013 16:03, Kyle Mestery (kmestery) wrote: > On Nov 25, 2013, at 8:28 AM, Salvatore Orlando > wrote: > > > > Hi, > > > > I've been recently debugging some issues I've had with the OVS agent, > and I found out that in many cases (pos

Re: [openstack-dev] [Trove][Savanna][Murano][Heat] Unified Agent proposal discussion at Summit

I am sorry I missed that session, but am interested in the topic. This is very relevant to Heat, where we are working on software configuration in general. I desire that Heat's ability to configure software will meet the needs of Trove, Savanna, and Murano. At IBM we worked several Hadoop exa

[openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

All, So, lately we've been seeing more patches posted proposing added functionality to Heat (the API and template syntax) related to development of UI functionality. This makes me both happy (because folks want to use Heat!) and sad (because it's evident there are several proprietary UI's being d

Re: [openstack-dev] [TripleO] Summit session wrapup

Hey Rob, can we add 'Slick Overcloud deployment through the UI' to the list? There was no session about that, but we discussed it afterwords and agreed that it is high priority for Icehouse as well. I just want to keep it on the list, so we are aware of that. Thanks -- Jarda On 2013/25/11 0

Re: [openstack-dev] [Nova] Remove ratelimits from nova v3 api

On Mon, Nov 25, 2013 at 4:38 AM, David Hill wrote: > Hi Alex, > >Is removing the ratelimiting code part of the roadmap? I fear that if > it's removed now, it may have to be re-implemented in the future as the > cloud deployments become more mainstream ... Without ratelimit, some evil > users

Re: [openstack-dev] [Openstack-docs] What's Up Doc? Nov 20 2013

On Thu, Nov 21, 2013 at 1:53 AM, Michael Still wrote: > On Thu, Nov 21, 2013 at 7:54 AM, Anne Gentle wrote: > > > 5. Doc tools updates: > > > > David Cramer tells me he'll cut one more release of the clouddocs-tools > > maven plugin then it'll be put into Gerrit workflow in the OpenStack > > org

Re: [openstack-dev] EC2 Filter

On Mon, Nov 25, 2013 at 6:22 AM, Sebastian Porombka < porom...@uni-paderborn.de> wrote: > Hi Folks. > > I stumbled over the lacking of EC2 Api filter support on Openstack and > justinsb¹s (and the other people I forgot to mention here) attempt [1] to > implement this against diabolo. > > I¹m highl

[openstack-dev] [infra] Meeting Tuesday November 26th at 19:00 UTC

The OpenStack Infrastructure (Infra) team is hosting our weekly meeting tomorrow, Tuesday November 26th, at 19:00 UTC in #openstack-meeting Meeting agenda available here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting (anyone is welcome to to add agenda items) Everyone interested in in

Re: [openstack-dev] [qa] Plan for failing "successful" tempest jobs when new ERRORs appear in logs

On Mon, Nov 18, 2013 at 2:58 PM, David Kranz wrote: > So we are close to being able to start doing this. The current whitelist > is here https://github.com/openstack/tempest/blob/master/etc/ > whitelist.yaml. I have a "find-errors" script that watches for successful > builds and pulls out the non

Re: [openstack-dev] [keystone] Service scoped role definition

Hi Arvind I have just added some comments to your blueprint page regards David On 19/11/2013 00:01, Tiwari, Arvind wrote: > Hi, > > > > Based on our discussion in design summit , I have redone the service_id > binding with roles BP >

Re: [openstack-dev] [qa] Plan for failing "successful" tempest jobs when new ERRORs appear in logs

On Mon, Nov 25, 2013 at 11:06 AM, Joe Gordon wrote: > > > > On Mon, Nov 18, 2013 at 2:58 PM, David Kranz wrote: > >> So we are close to being able to start doing this. The current whitelist >> is here https://github.com/openstack/tempest/blob/master/etc/ >> whitelist.yaml. I have a "find-errors"

Re: [openstack-dev] [nova] python-novaclient: uses deprecated keyring.backend.$keyring

On Mon, Nov 25, 2013 at 2:48 AM, Thomas Goirand wrote: > On 11/25/2013 03:57 AM, Morgan Fainberg wrote: > > Hi Thomas, > > > > How pressing is this issue? > > It seems it's blocking some python package transition from Sid to > Jessie, and impacting the Gnome guys, so it's quite annoying for Debia

Re: [openstack-dev] How to stage client major releases in Gerrit?

On Fri, Nov 22, 2013 at 6:28 PM, Monty Taylor wrote: > > > On 11/22/2013 06:55 PM, Mark Washenberger wrote: > > > > > > > > On Fri, Nov 22, 2013 at 1:13 PM, Robert Collins > > mailto:robe...@robertcollins.net>> wrote: > > > > On 22 November 2013 22:31, Thierry Carrez >

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

Top-posting *and* replying to myself today :D I realised that I could have implemented this in less time than I've spent arguing about it already, so I did: https://review.openstack.org/#/c/58357/ https://review.openstack.org/#/c/58358/ cheers, Zane. On 19/11/13 23:27, Zane Bitter wrote: O

[openstack-dev] [Nova] No meeting this week

Greetings, Since Thursday this week is a holiday in the US, we will skip the Nova meeting. We'll meet again next week. Thanks, -- Russell Bryant ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mail

Re: [openstack-dev] Unwedging the gate

On 11/25/2013 11:54 AM, Clint Byrum wrote: > Excerpts from Robert Collins's message of 2013-11-25 01:30:11 -0800: >> On 25 November 2013 22:23, Clint Byrum wrote: >> >>> I do wonder if we would be able to commit enough resources to just run >>> two copies of the gate in parallel each time and requ

[openstack-dev] [QA] no meeting this week

QA meeting this week would be on the Thanksgiving Holiday in the US, and as it's still not at an Asia friendly time, I suspect attendance would be *very* low. Canceling this week, see you all at the December meeting. -Sean -- Sean Dague http://dague.net signature.asc Description: Ope

Re: [openstack-dev] Unwedging the gate

On Sun, Nov 24, 2013 at 10:48 PM, Robert Collins wrote: > On 25 November 2013 19:25, Joe Gordon wrote: > > > > > > > > On Sun, Nov 24, 2013 at 9:58 PM, Robert Collins < > robe...@robertcollins.net> > > wrote: > >> > >> I have a proposal - I think we should mark all recheck bugs critical, > >> and

Re: [openstack-dev] [qa] Plan for failing "successful" tempest jobs when new ERRORs appear in logs

On Mon, Nov 25, 2013 at 11:06:36AM -0800, Joe Gordon wrote: > On Mon, Nov 18, 2013 at 2:58 PM, David Kranz wrote: > > > So we are close to being able to start doing this. The current whitelist > > is here https://github.com/openstack/tempest/blob/master/etc/ > > whitelist.yaml. I have a "find-err

Re: [openstack-dev] [Trove][Savanna][Murano][Heat] Unified Agent proposal discussion at Summit

Hi Mike, thank you for comments. Could you, please, add a section about Heat requirements for guest agents to the https://etherpad.openstack.org/p/UnifiedAgents? BTW The initial idea was to have some kind of skeleton for building guest agents with pluggable transports (message queue, http, met

Re: [openstack-dev] [Ironic][Cinder] Attaching Cinder volumes to baremetal instance

No -- attach volumes is not implemented in Ironic yet. I think it would be great if someone wants to work on it. There was some discussion at the summit about cinder support, in particular getting boot-from-volume to work with Ironic, but no one has come forward since then with code or blueprints.

[openstack-dev] [Keystone] Keystone client support for Py3K

Greetings, I noticed there's no Py3K gate for keysotneclient so, I just wanted to know what's the state of $subject and if there's any milestone for it. We're working on keeping Marconi's client Py3K compliant and this is, unfortunately, the only bit that's not supported. As for now, we disable

Re: [openstack-dev] [Tempest] Drop python 2.6 support

On Monday, November 25, 2013 7:35:51 AM, Zhi Kun Liu wrote: Hi all, I saw that Tempest will drop python 2.6 support in design summit https://etherpad.openstack.org/p/icehouse-summit-qa-parallel. Drop tempest python 2.6 support:Remove all nose hacks in the code Delete nose, use unit

Re: [openstack-dev] [Keystone] Keystone client support for Py3K

Hi, There is a gate for python-keystoneclient for py33. I have been trying to port it over to python3 but its blocked on httpretty right now not being pyhon3 compatible. Regards chuck On Mon, Nov 25, 2013 at 3:25 PM, Flavio Percoco wrote: > Greetings, > > I noticed there's no Py3K gate for ke

Re: [openstack-dev] [Ironic][Ceilometer] get IPMI data for ceilometer

Hi! Very good questions. I think most of them are directed towards the Ceilometer team, but I have answered a few bits inline. On Mon, Nov 25, 2013 at 7:24 AM, wanghaomeng wrote: > > Hello all: > > Basically, I understand the solution is - Our Ironic will implement an > IPMI driver > We will

[openstack-dev] [nova] Should the server create API return 404 errors?

Aaron Rosen is working a patch [1] to handle a NetworkNotFound exception in the server create API. For the V2 API this will return a 400 error. For the V3 API this will return a 404 because of a V3-specific patch [2]. The API docs list 404 as a valid response code, but is it intuitive for a

Re: [openstack-dev] [Openstack-dev][Neutron] Handling of ovs command errors

On Nov 25, 2013, at 12:36 PM, Salvatore Orlando wrote: > > Thanks Kyle, > > More comments inline. > > Salvatore > > > On 25 November 2013 16:03, Kyle Mestery (kmestery) wrote: > On Nov 25, 2013, at 8:28 AM, Salvatore Orlando wrote: > > > > Hi, > > > > I've been recently debugging some issue

Re: [openstack-dev] [nova] Should the server create API return 404 errors?

+1 on this sentiment. >From the perspective of the client, I typically imagine a web browser. A 404 >means that a "thing was not found" and this **implies** that I might specify a >different "thing" so that I do *not* get a 404. But in many of the >circumstances the 404 root cause is a server-s

Re: [openstack-dev] [nova] python-novaclient: uses deprecated keyring.backend.$keyring

On Nov 24, 2013, at 7:37 AM, Thomas Goirand wrote: > Someone sent a bug report against the python-novaclient package: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728470 > > Could someone take care of this? FYI to the thread, this patch is now up for this issue: https://review.openstack.

Re: [openstack-dev] [Neutron] Race condition between DB layer and plugin back-end implementation

On Thu, Nov 21, 2013 at 12:34:33PM -0800, Gary Duan wrote: > Advanced service plugins don't have two-step transition today. IMO, If > vendor plugins/drivers don't maintain their own databases for these > services, it might not be urgent to add these steps in the plugin. I agree. OVS/linux bridge

Re: [openstack-dev] [Nova] Hypervisor CI requirement and deprecation plan

On 11/15/2013 9:28 AM, Dan Smith wrote: Hi all, As you know, Nova adopted a plan to require CI testing for all our in-tree hypervisors by the Icehouse release. At the summit last week, we determined the actual plan for deprecating non-compliant drivers. I put together a page detailing the spec

Re: [openstack-dev] [Keystone][Marconi][Oslo] Discoverable home document for APIs (Was: Re: [Nova][Glance] Support of v1 and v2 glance APIs in Nova)

To most of your questions i don't know the answer as the format was in place before i started with the project. I know that it is similar (though not exactly the same) as nova's but not where they are documented (as they are version independent) I can tell you it looks like: { "versions": {

Re: [openstack-dev] [Nova] Hypervisor CI requirement and deprecation plan

On 11/25/2013 05:19 PM, Matt Riedemann wrote: > I'll play devil's advocate here and ask this question before someone > else does. I'm assuming that the requirement of a 'full' tempest run > means running this [1]. Is that correct? It's just confusing sometimes > because there are other things in

Re: [openstack-dev] [Keystone][Marconi][Oslo] Discoverable home document for APIs (Was: Re: [Nova][Glance] Support of v1 and v2 glance APIs in Nova)

On Mon, Nov 25, 2013 at 2:41 AM, Flavio Percoco wrote: > On 25/11/13 09:28 +1000, Jamie Lennox wrote: > >> So the way we have this in keystone at least is that querying GET / will >> return all available API versions and querying /v2.0 for example is a >> similar result with just the v2 endpoint.

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

Hi Steve, As one of the UI developers driving the requirements behind these new blueprints I wanted to take a moment to assure you and the rest of the Openstack community that the primary purpose of pushing these requirements out to the community is to help improve the User Experience for Heat for

  1   2   >