Re: [openstack-dev] [Solum] Command Line Interface for Solum

I have updated the blueprint for this feature, and approved the direction for the v0.1 milestone: https://blueprints.launchpad.net/solum/+spec/command-line The specification for the CLI is not intended to be complete at this stage. It only specified what I expect we will need for v0.1. Addition

Re: [openstack-dev] [qa] moratorium on new negative tests in Tempest

Great work! Now the test cases in Tempest are well-stocked so it's a good time to rearrange the design of test codes. I checked mailing lists, IRC log and etherpads relating to this topic. Let me leave my 5 thoughts below. How to handle: 1. Data type (e.g, int, bool) 2. Specific value or fo

[openstack-dev] A droidstack(android on top of openstack) powered by qemu - some thoughts and implementation

Dear list, This year I was working on the idea of building an android cloud on top of openstack. I call it it droidstack hereby. A typical usage could be using android apps without downloading them. For example, playing 3d games remotely. The implementation is thought to be consisted of feature

[openstack-dev] [All] [Climate]Where should we define Exceptions ?

Hi, Declaring Exceptions in Openstack projects is quite straightforward and identical for most of the projects : all of them are defined in a global exception.py module called each time a specific exception must be handled. I recently received a -1 for that, so I would like to come back to th

Re: [openstack-dev] [Cinder][Glance] OSLO update

On 21/11/13 16:14 -0500, Doug Hellmann wrote: So I would really appreciate any comments or pieces of advice. Is it sufficient to include just the short form of the original commit message, along with the commit id in the oslo-incubator repository for reference? I've done this and alse see

[openstack-dev] [Infrastructure ]Support for PCI Passthrough

Hi, We add the new feature of PCI passthrough in Nova enables assigning a PCI device to an instance in openstack. Now we want to add integration tests in Temptest to cover our module. We come up with several ideas like fade device or QEMU IOMMU emulator, but they are not possible. We talk to

Re: [openstack-dev] [All] [Climate]Where should we define Exceptions ?

On Fri, Nov 22 2013, Sylvain Bauza wrote: > Declaring Exceptions in Openstack projects is quite straightforward and > identical for most of the projects : all of them are defined in a global > exception.py module called each time a specific exception must be handled. No. Ceilometer doesn't have a

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

Greetings, Based on the recent discussion that came out about not having enough information in the commit message when syncing oslo-incubator modules, I was thinking that besides encouraging people to write better commit messages, we could also improve the script we use to sync those modules. So

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

Robert Collins wrote: > I don't understand why branches would be needed here *if* the breaking > changes don't impact any supported release of OpenStack. Right -- the trick is what does "supported" mean in that case. When the client libraries were first established as separate deliverables, they

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

Mark Washenberger wrote: > > My question is, is there a correct way to stage breaking changes in > > Gerrit? Has some other team already dealt with this problem? > > [...] > > It sounds like a case where we could use a feature branch. There have > been a number of them in the p

Re: [openstack-dev] Introducing the new OpenStack service for Containers

Tim Bell wrote: > Can we make sure that the costs for the end users are also considered as > part of this ? > > - Configuration management will need further modules > - Dashboard confusion as we get multiple tabs > - Accounting, Block Storage, Networking, Orchestration >

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

Russell Bryant wrote: > [...] > I'm not thrilled about the prospect of this going into a new project for > multiple reasons. > > - Given the priority and how long this has been dragging out, having to > wait for a new project to make its way into OpenStack is not very appealing. > > - A new pro

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

Great initiative! I would certainly be interested taking part in this -- although I wouldn't necessary claim to be among "people with the know-how to design and implement it well". For sure this is going to be a painful but exciting process. Regards, Alex From: Robert Collins To: Op

Re: [openstack-dev] Search Project - summit follow up

Dmitri, If you intend to make this middleware generic and reusable between different OpenStack services, your best shot, to my understanding, will be to propose a new library in oslo-incubator. -- Best regards, Oleg Gelbukh On Fri, Nov 22, 2013 at 4:05 AM, Dmitri Zimin(e) | StackStorm < d...@st

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

I will start reading documentation in order to integrate node in development, we also want to integrate its testing into the existing ones. I think a blueprint will be necessary. - Original Message - From: "Jiri Tomasek" To: openstack-dev@lists.openstack.org Sent: Thursday, November 21,

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

I'd very much like to take part in the discussions. Depending on the outcome of said discussion, I may or may not want to participate in the implementation :) Soren Hansen | http://linux2go.dk/ Ubuntu Developer | http://www.ubuntu.com/ OpenStack Developer | http://www.open

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

On 11/22/13 12:16 PM, "Soren Hansen" wrote: >I'd very much like to take part in the discussions. Depending on the >outcome of said discussion, I may or may not want to participate in >the implementation :) > >Soren Hansen | >https://urldefense.proofpoint.com/v1/url?u=http://linux2go

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

>> On Fri, Nov 15, 2013 at 2:21 PM, Russell Bryant wrote: In particular, has there been a decision made about whether it will definitely be deprecated in some (as yet unspecified) future release, or whether it will continue to be supported for the foreseeable future? >>> >>> We want

Re: [openstack-dev] [Nova] V3 API Review Checklist and style guide

On 19 November 2013 11:40, Christopher Yeoh wrote: > I've updated the Nova review check list with some details for reviewing V3 > API changesets and started a bit of a style guide for the API. > > Checklist: > https://wiki.openstack.org/w/index.php?title=ReviewChecklist#Nova_Review_Checklist Look

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

"Maxime Vidori" wrote: > Hi all, I know it is pretty annoying but I have to resurrect this subject. > > With the integration of Angularjs into Horizon we will encounter a lot of > issues with javascript. I ask you to reconsider to bring back Nodejs as a > development platform. I am not talking ab

Re: [openstack-dev] [Swift] Server Side Encryption

Gregory Holt wrote on 20/11/2013 05:46:41 PM: > From: Gregory Holt > To: "OpenStack Development Mailing List (not for usage questions)" > , > Date: 20/11/2013 05:49 PM > Subject: Re: [openstack-dev] [Swift] Server Side Encryption > > On Nov 20, 2013, at 5:26 AM, David Hadas wrote: > > > >

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

On 11/21/2013 01:55 PM, Jiri Tomasek wrote: > Hi, > > Regarding less, I don't really care what compiler we use as long as it > works. And if we need to provide uncompiled less for production, then > let's use Lesscpy. > There is at least one bug open against Ubuntu[1], asking to install python-

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

On 11/22/2013 11:10 AM, Maxime Vidori wrote: > I will start reading documentation in order to integrate node in development, > we also want to integrate its testing into the existing ones. I think a > blueprint will be necessary. > Since it was such a pain to get rid of nodejs, I'd love to see o

Re: [openstack-dev] [Cinder][Glance] OSLO update

But what if I want to update some module that consists of ten or even more files (like rpc or db) and each of these files has quite a long change log? In that case the commit message may turn out to be really long even if only commit ids and names are included. On Wed, Nov 20, 2013 at 12:37 PM, E

Re: [openstack-dev] [nova][heat][[keystone] RFC: introducing "request identification"

On Tue, 19 Nov 2013 12:03:57 -0500 Adam Young wrote: > On 11/19/2013 08:21 AM, Dolph Mathews wrote: > > Related BP: > > > > Create a unified request identifier > > https://blueprints.launchpad.net/nova/+spec/cross-service-request-id I interested in cross-service-request-id because it has pote

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

2013/11/22 John Garbutt : > Another approach to help with (1) is in Icehouse we remove the > features from nova-network that neutron does not implement. We have > warned about deprecation for a good few releases, so its almost OK. You want to motivate Neutron developers by punishing users of nova-

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

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 whether it will > definitely be deprecated in some (as yet unspecified) future release, or > whether it wil

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

On Friday 22 November 2013 13:13:29 Matthias Runge wrote: > On 11/21/2013 01:55 PM, Jiri Tomasek wrote: > > Hi, > > > > > > Regarding less, I don't really care what compiler we use as long as it > > works. And if we need to provide uncompiled less for production, then > > let's use Lesscpy. > >

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

>There is at least one bug open against Ubuntu[1], asking to install >python-lesscpy as well, as customers "often" need to re-create or change >stylesheets. > >This would imply nodejs in a production environment, when going back to >less. As long as the css will be the only one included into the p

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

On 11/22/2013 04:47 AM, 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 whether it will >> definitely be deprecated in some (as yet u

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/22/2013 02:19 PM, Sascha Peilicke wrote: > On Friday 22 November 2013 13:13:29 Matthias Runge wrote: >> On 11/21/2013 01:55 PM, Jiri Tomasek wrote: >>> Hi, >>> >>> >>> Regarding less, I don't really care what compiler we use as >>> long as it w

Re: [openstack-dev] [Neutron][LBaaS] Subteam meeting on Thursday, 21

Meeting logs from the latest meeting: Minutes: http://eavesdrop.openstack.org/meetings/neutron_lbaas/2013/neutron_lbaas.2013-11-21-14.00.html Minutes (text): http://eavesdrop.openstack.org/meetings/neutron_lbaas/2013/neutron_lbaas.2013-11-21-14.00.txt Log: http://eavesdrop.openstack.org/meetings/

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

On Fri, Nov 22, 2013 at 3:31 AM, Thierry Carrez wrote: > Robert Collins wrote: > > I don't understand why branches would be needed here *if* the breaking > > changes don't impact any supported release of OpenStack. > > Right -- the trick is what does "supported" mean in that case. > > When the cli

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

On 2013-11-22 03:11, Flavio Percoco wrote: Greetings, Based on the recent discussion that came out about not having enough information in the commit message when syncing oslo-incubator modules, I was thinking that besides encouraging people to write better commit messages, we could also improve

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

On 11/22/2013 02:49 PM, Maxime Vidori wrote: It seems a bit crazy to me to introduce NodeJS as a dependency just for the sake of an easy way to run jslint. There are other options available that run without NodeJS as a dependency. Sadly, the only solutions which try to implement jslint in pure

[openstack-dev] [Neutron][LBaaS] L7 rules design

Hi Avishay, lbaas folks, I've reviewed the wiki and have some questions/suggestions: 1) Looks like L7Policy is lacking 'name' attribute in it's description. However i see little benefit of having a name for this object 2) lbaas-related neutron client commands start with lb-, please fix this. 3) H

[openstack-dev] FreeBSD hypervisor (bhyve) driver

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 We were considering libvirt support for bhyve hypervisor as well, only wouldn't want to do this as the first approach for

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

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 > > We were considering libvirt support for bhyve hypervisor as we

Re: [openstack-dev] Introducing the new OpenStack service for Containers

On Thu, Nov 21, 2013 at 11:07 AM, Tim Bell wrote: > > > Can we make sure that the costs for the end users are also considered as > part of this ? > > > > - Configuration management will need further modules > > - Dashboard confusion as we get multiple tabs > > - Account

Re: [openstack-dev] Introducing the new OpenStack service for Containers

On Thu, Nov 21, 2013 at 9:58 AM, Sam Alba wrote: > On Thu, Nov 21, 2013 at 9:39 AM, Krishna Raman wrote: > > > > On Thu, Nov 21, 2013 at 8:57 AM, Sam Alba wrote: > >> > >> I wish we can make a decision during this meeting. Is it confirmed for > >> Friday 9am pacific? > > > > > > Friday 9am Paci

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

I'm still a newbie here, so can not claim my Nova skills are even "modest". But I'd like to track this, if nothing more. Thanks, Mike___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/op

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

To add to the screams of others removing features from nova-network to achieve parity with neutron is a non starter, and it rather scares me to hear it suggested. I do try not to rant in public, especially about things I'm not competent to really help fix, but I can't really contain this one any l

Re: [openstack-dev] [Cinder][Glance] OSLO update

On 22 November 2013 12:27, Elena Ezhova wrote: > But what if I want to update some module that consists of ten or even more > files (like rpc or db) and each of these files has quite a long change log? > In that case the commit message may turn out to be really long even if only > commit ids and n

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

On 11/22/2013 11:17 AM, Jonathan Proulx wrote: > To add to the screams of others removing features from nova-network to > achieve parity with neutron is a non starter, and it rather scares me > to hear it suggested. -1 from me too, so everyone can take a deep breath on this. :-) > Providing feat

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

On 22 November 2013 14:59, Ben Nemec wrote: > One other thought I had was to add the ability to split one Oslo sync up > into multiple commits, either one per module, or even one per Oslo commit > for some really large module changes (I'm thinking of the 1000 line db sync > someone mentioned rece

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

On Fri, Nov 22, 2013 at 11:24:18AM -0500, Russell Bryant wrote: > On 11/22/2013 11:17 AM, Jonathan Proulx wrote: > > To add to the screams of others removing features from nova-network to > > achieve parity with neutron is a non starter, and it rather scares me > > to hear it suggested. > > -1 fro

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

I have updated the language pack (name subject to change) blueprint with the outcomes from the face2face meetings, and drafted a specification that captures the discussion so far. The spec is centered around the core idea of transitioning base images into deployable images (that can be stored i

Re: [openstack-dev] Introducing the new OpenStack service for Containers

Excerpts from Thierry Carrez's message of 2013-11-22 01:50:39 -0800: > Tim Bell wrote: > > Can we make sure that the costs for the end users are also considered as > > part of this ? > > > > - Configuration management will need further modules > > - Dashboard confusion as we get

Re: [openstack-dev] Introducing the new OpenStack service for Containers

Reminder: We are meting in about 15 minutes on #openstack-meeting channel. --Krishna On Fri, Nov 22, 2013 at 7:53 AM, Krishna Raman wrote: > > > > On Thu, Nov 21, 2013 at 11:07 AM, Tim Bell wrote: > >> >> >> Can we make sure that the costs for the end users are also considered as >> part of t

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

"Daniel P. Berrange" wrote on 11/22/2013 11:32:59 AM: > > A good example is the current discussion around a new scheduling > > service. There have been lots of big ideas around this. Robert Collins > > just started a thread about a proposal to start this project but with a > > very strict sc

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

Dear all, I'm very interested in this subject as well. Actually there is also a discussion of the possibility of an independent scheduler in the mailisg list: http://lists.openstack.org/pipermail/openstack-dev/2013-November/019518.html Would it be possible to discuss about this subject in the ne

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

"Maxime Vidori" wrote: > >There is at least one bug open against Ubuntu[1], asking to install > >python-lesscpy as well, as customers "often" need to re-create or change > >stylesheets. > > > >This would imply nodejs in a production environment, when going back to > >less. > > As long as the css

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

"Imre Farkas" wrote: > On 11/22/2013 02:49 PM, Maxime Vidori wrote: > >> It seems a bit crazy to me to introduce NodeJS as a dependency just for > >> the sake of an easy way to run jslint. There are other options > >> available that run without NodeJS as a dependency. > > > > Sadly, the only solut

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

On 11/21/13, 7:51 PM, "Jamie Lennox" wrote: >So i've a feeling that this was proposed and dismissed once before. I >don't remember why. > >So my concern with barbican is that i'm under the impression that >barbican was going to be an 'overcloud' service. That's a really bad way >of putting it, b

Re: [openstack-dev] L3 advanced features blueprint mapping to IETF and IEEE standards

Nachi, I'm sorry to have missed this meeting. In my jet-lagged state, I somehow got it on my calendar for last night rather than last Tuesday night (my local time, MST). I have an interest in the dynamic routing area of neutron and I would like to be involved. Will this meeting be weekly? I'll

Re: [openstack-dev] [Cinder][Glance] OSLO update

On Fri, Nov 22, 2013 at 11:21 AM, Duncan Thomas wrote: > On 22 November 2013 12:27, Elena Ezhova wrote: > > But what if I want to update some module that consists of ten or even > more > > files (like rpc or db) and each of these files has quite a long change > log? > > In that case the commit me

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

On Fri, Nov 22, 2013 at 4:11 AM, Flavio Percoco wrote: > Greetings, > > Based on the recent discussion that came out about not having enough > information in the commit message when syncing oslo-incubator modules, > I was thinking that besides encouraging people to write better commit > messages,

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

Starting from the existing code also makes migration for production environments currently using the code much easier. Support those of us running production OpenStack clouds needs to be one of the major development concerns as people reflect on refactoring along with making sure we don't make

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

On Fri, Nov 22, 2013 at 11:24 AM, Duncan Thomas wrote: > On 22 November 2013 14:59, Ben Nemec wrote: > > > One other thought I had was to add the ability to split one Oslo sync up > > into multiple commits, either one per module, or even one per Oslo commit > > for some really large module change

Re: [openstack-dev] [Ceilometer] meaning of resource_id in a meter

On Thu, Nov 21, 2013 at 2:37 PM, Gordon Chung wrote: > > > In all cases, these are free string fields. `user_id' and `project_id' > > map to Keystone _most of the time_, > > i'm sort of torn between the two -- which is why i brought it up i guess. > i like the flexibility of having resource as a

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

On Fri, Nov 22, 2013 at 12:39 PM, Tim Bell wrote: > > Support those of us running production OpenStack clouds needs to be one of > the major development concerns as people reflect on refactoring along with > making sure we don't make OpenStack more difficult to > install/manage/configure. > > To

Re: [openstack-dev] RFC: Potential to increase min required libvirt version to 0.9.11 ?

On Wed, Nov 20, 2013 at 04:02:02PM +0100, Ralf Haferkamp wrote: > On Wed, Nov 20, 2013 at 04:33:22PM +1300, Robert Collins wrote: > > On 20 November 2013 08:02, Daniel P. Berrange wrote: > > > Currently the Nova libvirt driver is declaring that it wants a minimum > > > of libvirt 0.9.6. > > ... >

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

On Fri, Nov 22, 2013 at 12:55:48PM -0500, Lorin Hochstein wrote: > On Fri, Nov 22, 2013 at 12:39 PM, Tim Bell wrote: > > > > > Support those of us running production OpenStack clouds needs to be one of > > the major development concerns as people reflect on refactoring along with > > making sure

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

On 22/11/13 12:06 -0500, Julie Pichon wrote: I don't think Selenium is going away, and efforts have started around using it as well for our integration tests [0]. Looking at the current AngularJS patch up for review, it is testable without requiring NodeJS. While the Angular modules are testab

Re: [openstack-dev] Introducing the new OpenStack service for Containers

On Fri, Nov 22, 2013 at 11:49 AM, Krishna Raman wrote: > Reminder: We are meting in about 15 minutes on #openstack-meeting channel. I wasn't able to make it. Was meeting-bot triggered? Is there a log of today's discussion? Thank you, Eric Windisch ___

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

On Fri, 2013-11-22 at 11:04 +0100, Thierry Carrez wrote: > Russell Bryant wrote: > > [...] > > I'm not thrilled about the prospect of this going into a new project for > > multiple reasons. > > > > - Given the priority and how long this has been dragging out, having to > > wait for a new project

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

I would definitely like to take part in this discussion and also contribute where I can. I was part of the scheduler sessions in the recent summit along with Debo Dutta, Gary Kotton, and Mike Spreitzer and we had proposed sessions on smart resource placement, and also the instance group API work f

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

Hey guys, just starting out with Ironic, had a silly question. Can we attach bootable or non bootable plain cinder volumes during either provisioning of the baremetal instance or after provisioning the baremetal instance? I have seen a "attach_volume" method in the "LibvirtVolumeDriver" of the no

Re: [openstack-dev] Introducing the new OpenStack service for Containers

On Nov 22, 2013, at 10:26 AM, Eric Windisch wrote: > On Fri, Nov 22, 2013 at 11:49 AM, Krishna Raman wrote: >> Reminder: We are meting in about 15 minutes on #openstack-meeting channel. > > I wasn't able to make it. Was meeting-bot triggered? Is there a log of > today's discussion? Yes. Logs

Re: [openstack-dev] [Nova] [Infra] Support for PCI Passthrough

On 2013-11-22 08:59:16 + (+), Tan, Lin wrote: [...] > Our module only works on the compute node that enables VT-d and > contains special PCIs which support the SR-IOV. > > So is it possible to > > 1. setup compute node which enables pci passthrough. > > 2. modify the testing schedule log

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

That is a fact all client side development is based on javascript, Node allow us to easily execute javascript without a browser. Every time we will have a reflexion on the client side, Node will show up, what we are doing is just delaying something inevitable and wasting our forces in compromise

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

On 2013-11-22 10:34:40 +0100 (+0100), Thierry Carrez wrote: > It can be created on request by release management members (or > infra-core team). I /think/ that by default it would get tested against > master in other branches. More details at... https://wiki.openstack.org/wiki/GerritJenkinsGithub

Re: [openstack-dev] RFC: Potential to increase min required libvirt version to 0.9.11 ?

On 2013-11-20 03:50:03 + (+), Tom Fifield wrote: > Just confirming that the documentation for Ubuntu sets users up > with the Cloud Archive. In Havana, Libvirt is 1.1.1 and qemu is > 1.5.0. I've added a row to the table. There's a change currently up for review to (yet once more) try using

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

On 11/22/2013 12:55 PM, Lorin Hochstein wrote: > > On Fri, Nov 22, 2013 at 12:39 PM, Tim Bell > wrote: > > > Support those of us running production OpenStack clouds needs to be > one of the major development concerns as people reflect on > refactoring along

Re: [openstack-dev] Introducing the new OpenStack service for Containers

On 11/22/2013 02:29 PM, Krishna Raman wrote: > > On Nov 22, 2013, at 10:26 AM, Eric Windisch > wrote: > >> On Fri, Nov 22, 2013 at 11:49 AM, Krishna Raman > > wrote: >>> Reminder: We are meting in about 15 minutes on #openstack-meeting >>> c

[openstack-dev] [Nova] Proposal to add Matt Riedemann to nova-core

Greetings, I would like to propose adding Matt Riedemann to the nova-core review team. Matt has been involved with nova for a long time, taking on a wide range of tasks. He writes good code. He's very engaged with the development community. Most importantly, he provides good code reviews and h

Re: [openstack-dev] [Nova] Proposal to add Matt Riedemann to nova-core

+1 On Fri, Nov 22, 2013 at 12:53 PM, Russell Bryant wrote: > Greetings, > > I would like to propose adding Matt Riedemann to the nova-core review team. > > Matt has been involved with nova for a long time, taking on a wide range > of tasks. He writes good code. He's very engaged with the deve

Re: [openstack-dev] [Nova] Proposal to add Matt Riedemann to nova-core

> Please respond with +1/-1, or any further comments. +1 from me -- Matt has been helping a lot lately. --Dan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

On 22 November 2013 22:31, Thierry Carrez wrote: > Robert Collins wrote: >> I don't understand why branches would be needed here *if* the breaking >> changes don't impact any supported release of OpenStack. > > Right -- the trick is what does "supported" mean in that case. > > When the client libr

Re: [openstack-dev] [Nova] Proposal to add Matt Riedemann to nova-core

+1 > On Nov 22, 2013, at 12:53 PM, Russell Bryant wrote: > > Greetings, > > I would like to propose adding Matt Riedemann to the nova-core review team. > > Matt has been involved with nova for a long time, taking on a wide range > of tasks. He writes good code. He's very engaged with the dev

Re: [openstack-dev] [Nova] Proposal to add Matt Riedemann to nova-core

+1 On Sat, Nov 23, 2013 at 8:11 AM, Dan Smith wrote: >> Please respond with +1/-1, or any further comments. > > +1 from me -- Matt has been helping a lot lately. > > --Dan > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http:/

Re: [openstack-dev] [Nova] Proposal to add Matt Riedemann to nova-core

+1 On 11/22/13 at 03:53pm, Russell Bryant wrote: Greetings, I would like to propose adding Matt Riedemann to the nova-core review team. Matt has been involved with nova for a long time, taking on a wide range of tasks. He writes good code. He's very engaged with the development community. M

Re: [openstack-dev] RFC: Potential to increase min required libvirt version to 0.9.11 ?

Could we push to 1.0.0? That would give us live snapshotting... Michael On Sat, Nov 23, 2013 at 7:29 AM, Jeremy Stanley wrote: > On 2013-11-20 03:50:03 + (+), Tom Fifield wrote: >> Just confirming that the documentation for Ubuntu sets users up >> with the Cloud Archive. In Havana, Libvi

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

On Thursday, November 21, 2013 9:56:41 AM, Matt Riedemann wrote: On 11/3/2013 5:22 AM, Joe Gordon wrote: On Nov 1, 2013 6:46 PM, "John Garbutt" mailto:j...@johngarbutt.com>> wrote: > > On 29 October 2013 16:11, Eddie Sheffield mailto:eddie.sheffi...@rackspace.com>> wrote: > > > > "John

[openstack-dev] [OSSG][OSSN] Authenticated users are able to update passwords without providing their current password

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Authenticated users are able to update passwords without providing their current password - --- ### Summary ### An authenticated user is able to change their password without providing their current password. This allows compromised authentication tok

Re: [openstack-dev] [Nova] Proposal to add Matt Riedemann to nova-core

On Fri, 2013-11-22 at 15:53 -0500, Russell Bryant wrote: > Greetings, > > I would like to propose adding Matt Riedemann to the nova-core review team. > > Matt has been involved with nova for a long time, taking on a wide range > of tasks. He writes good code. He's very engaged with the developm

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

> > De : Robert Collins [robe...@robertcollins.net] > Date d'envoi : jeudi 21 novembre 2013 21:58 > À : OpenStack Development Mailing List > Objet : [openstack-dev] [Nova][Schduler] Volunteers wanted for a modest > proposal for an external scheduler in our l

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

Hello all, I would like to kickoff the Git integration discussion. Goal of this subgroup is to go through the git-integration blueprint [1] and break it up into smaller blueprints that we can execute on. We have to consider 2 workflows: 1) For Milestone 1, pull based git workflow where user

Re: [openstack-dev] [Nova] Proposal to add Matt Riedemann to nova-core

+1 On Sat, Nov 23, 2013 at 7:23 AM, Russell Bryant wrote: > Greetings, > > I would like to propose adding Matt Riedemann to the nova-core review team. > > Matt has been involved with nova for a long time, taking on a wide range > of tasks. He writes good code. He's very engaged with the develo

Re: [openstack-dev] [Nova] Proposal to add Matt Riedemann to nova-core

+1 On Fri, Nov 22, 2013 at 2:41 PM, Christopher Yeoh wrote: > > > +1 > > > On Sat, Nov 23, 2013 at 7:23 AM, Russell Bryant wrote: > >> Greetings, >> >> I would like to propose adding Matt Riedemann to the nova-core review >> team. >> >> Matt has been involved with nova for a long time, taking o

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

On Sat, Nov 23, 2013 at 8:33 AM, Matt Riedemann wrote: > ... > 21:51:42 i just hope that the version discovery mechanism is > smart enough to realize when it's handed a versioned endpoint, and happily > run with that > ... > 21:52:00 (by calling that endpoint and doing proper discovery) > ... >

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

The breakout meeting schedule poll is published here (dates will be published here once they are selected): https://wiki.openstack.org/wiki/Solum/BreakoutMeetings#Language_Pack_Working_Group_Series If you would like to join the working group, please: 1) Subscribe to the lang-pack blueprint: htt

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

On 11/22/2013 02:29 PM, Russell Bryant wrote: I honestly don't understand why openstack@ and openstack-operators@ are different lists. Perhaps openstack@ just needs better use of topic tagging ... Wouldn't openstack@ be the logical place for end-users to hang out, while openstack-operators@

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

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:51:42 i just hope that the version discovery mechanism > is smart enough to realize when it's handed a versioned endpoint, >

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

On Fri, Nov 22, 2013 at 1:13 PM, Robert Collins wrote: > On 22 November 2013 22:31, Thierry Carrez wrote: > > Robert Collins wrote: > >> I don't understand why branches would be needed here *if* the breaking > >> changes don't impact any supported release of OpenStack. > > > > Right -- the trick

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

On Fri, Nov 22, 2013 at 12:03 PM, Jeremy Stanley wrote: > On 2013-11-22 10:34:40 +0100 (+0100), Thierry Carrez wrote: > > It can be created on request by release management members (or > > infra-core team). I /think/ that by default it would get tested against > > master in other branches. > > Mo

Re: [openstack-dev] [Nova] Proposal to add Matt Riedemann to nova-core

+1 Solid reviewer! Sent from my iPad > On Nov 22, 2013, at 2:53 PM, Russell Bryant wrote: > > Greetings, > > I would like to propose adding Matt Riedemann to the nova-core review team. > > Matt has been involved with nova for a long time, taking on a wide range > of tasks. He writes good co

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

On 2013-11-22 16:18:10 -0800 (-0800), Mark Washenberger wrote: > Cool. Is this documentation essentially explaining how to keep a > feature branch up to date with master? (spoiler warning: > carefully use merge commits?) Yes, the assumption there is that you want to do development work on your 2.0

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

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:51:42 i just hope that the version discovery mechanism is smart eno

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

On 11/22/2013 05:37 PM, Krishna Raman wrote: > Hello all, > > I would like to kickoff the Git integration discussion. Goal of this > subgroup is to go through the git-integration blueprint [1] and break it > up into smaller blueprints that we can execute on. > > We have to consider 2 workflows:

  1   2   >