Re: [openstack-dev] [Neutron][LBaaS] Thursday subteam meeting

Hi Iwamoto, You are correct. Provider attribute will remain in the pool due to API compatibility reasons. Thanks, Eugene. On Mon, Dec 2, 2013 at 9:35 AM, IWAMOTO Toshihiro wrote: > At Fri, 29 Nov 2013 07:25:54 +0900, > Itsuro ODA wrote: > > > > Hi Eugene, > > > > Thank you for the response. >

Re: [openstack-dev] [oslo] maintenance policy for code graduating from the incubator

On 29/11/13 13:47 -0500, Eric Windisch wrote: Based on that, I would like to say that we do not add new features to incubated code after it starts moving into a library, and only provide "stable-like" bug fix support until integrated projects are moved over to the graduated library (although even

Re: [openstack-dev] [Neutron][LBaaS] Vote required for certificate as first-class citizen - SSL Termination (Revised)

LBaaS enthusiasts: Your vote on the revised model for SSL Termination? Here is a comparison between the original and revised model for SSL Termination: *** Original Basic Model that was proposed in summit *** * Certificate parameters introduced as part of VIP resource. *

Re: [openstack-dev] [oslo] maintenance policy for code graduating from the incubator

On Fri, Nov 29 2013, Doug Hellmann wrote: > Before we make this policy official, I want to solicit feedback from the > rest of the community and the Oslo core team. +1 I think it's a good idea. It'll push people forward migrating to the split library if they want the new features. -- Julien Da

Re: [openstack-dev] [tempest] list of negative tests that need to be separated from other tests.

Hi Adalberto, > -Original Message- > From: Adalberto Medeiros [mailto:adal...@linux.vnet.ibm.com] > Sent: Saturday, November 30, 2013 11:29 PM > To: OpenStack Development Mailing List > Subject: [openstack-dev] [tempest] list of negative tests that need to be > separated from other tests

Re: [openstack-dev] [Nova] Splitting up V3 API admin-actions plugin

agree with Alex, maybe 'reset_network' or 'inject_network_info' is just used by XenServer now. and I think the same functionality can be replaced with Neutron or Nova metadata service. am I right? 2013/12/2 Alex Xu > On 2013年12月01日 21:39, Christopher Yeoh wrote: > > Hi, > > At the summit

[openstack-dev] [Climate] Meeting minutes

Thanks everybody who joined us on our Climate weekly meeting. Here are logs/minutes from it: Minutes: http://eavesdrop.openstack.org/meetings/climate/2013/climate.2013-12-02-10.02.html Minutes (text): http://eavesdrop.openstack.org/meetings/climate/2013/climate.2013-12-02-10.02.txt Log: http:/

[openstack-dev] [Swift] Increase Swift ring partition power

Hello together, I'd like to discuss a way to increase the partition power of an existing Swift cluster. This is most likely interesting for smaller clusters that are growing beyond their original planed size. As discussed earlier [1] a rehashing is required after changing the partition power to m

Re: [openstack-dev] [tempest] list of negative tests that need to be separated from other tests.

Thanks Ken'ichi. I added my name to a couple of them in that list. Adalberto Medeiros Linux Technology Center Openstack and Cloud Development IBM Brazil Email: adal...@linux.vnet.ibm.com On Mon 02 Dec 2013 07:36:38 AM BRST, Kenichi Oomichi wrote: Hi Adalberto, -Original Message- From

[openstack-dev] [Nova] Tokens in memcache become unauthorized

Hi guys, I've faced with nova+memcache issue on the cluster in HA-mode. Issue is related to nova in case of using REST (that includes Horizon): it's impossible to use auth-token several times because it became unauthorized in cache. Logs: Nov 13 06:58:49 controller-1461 nova keystoneclient.midd

Re: [openstack-dev] [Neutron] Stop logging non-exceptional conditions as ERROR

On 11/27/2013 01:50 PM, Maru Newby wrote: > Just a heads up, the console output for neutron gate jobs is about to get a > lot noisier. Any log output that contains 'ERROR' is going to be dumped into > the console output so that we can identify and eliminate unnecessary error > logging. Once we

Re: [openstack-dev] [oslo] maintenance policy for code graduating from the incubator

On 12/01/2013 06:40 PM, Doug Hellmann wrote: > > > > On Sat, Nov 30, 2013 at 3:52 PM, Sandy Walsh > wrote: > > > > On 11/29/2013 03:58 PM, Doug Hellmann wrote: > > > > > > > > On Fri, Nov 29, 2013 at 2:14 PM, Sandy Walsh > mailto:sa

Re: [openstack-dev] [Neutron] Stop logging non-exceptional conditions as ERROR

On 02/12/13 15:05, gustavo panizzo wrote: > On 11/27/2013 01:50 PM, Maru Newby wrote: >> Just a heads up, the console output for neutron gate jobs is about to get a >> lot noisier. Any log output that contains 'ERROR' is going to be dumped >> into the console output so that we can identify and

Re: [openstack-dev] [Neutron] Stop logging non-exceptional conditions as ERROR

On Dec 2, 2013 3:39 AM, "Maru Newby" wrote: > > > On Dec 2, 2013, at 2:07 AM, Anita Kuno wrote: > > > Great initiative putting this plan together, Maru. Thanks for doing > > this. Thanks for volunteering to help, Salvatore (I'm thinking of asking > > for you to be cloned - once that becomes avail

Re: [openstack-dev] [oslo] maintenance policy for code graduating from the incubator

On 11/29/2013 01:39 PM, Doug Hellmann wrote: > We have a review up (https://review.openstack.org/#/c/58297/) to add > some features to the notification system in the oslo incubator. THe > notification system is being moved into oslo.messaging, and so we have > the question of whether to accept the

[openstack-dev] [Keystone] Store quotas in Keystone

Hello, I was wondering what was the status of Keystone being the central place across all OpenStack projects for quotas. There is already an implementation from Dmitry here : https://review.openstack.org/#/c/40568/ but hasn't seen activities since october waiting for icehouse development to be

Re: [openstack-dev] [Nova] Splitting up V3 API admin-actions plugin

On 12/01/2013 08:39 AM, Christopher Yeoh wrote: > Hi, > > At the summit we agreed to split out lock/unlock, pause/unpause, > suspend/unsuspend > functionality out of the V3 version of admin actions into separate > extensions to make it easier for deployers to only have loaded the > functionality t

Re: [openstack-dev] [oslo] maintenance policy for code graduating from the incubator

On Mon, Dec 2, 2013 at 8:08 AM, Sandy Walsh wrote: > > > On 12/01/2013 06:40 PM, Doug Hellmann wrote: > > > > > > > > On Sat, Nov 30, 2013 at 3:52 PM, Sandy Walsh > > wrote: > > > > > > > > On 11/29/2013 03:58 PM, Doug Hellmann wrote: > > > > > > > >

Re: [openstack-dev] [oslo] maintenance policy for code graduating from the incubator

On Mon, Dec 2, 2013 at 8:36 AM, Russell Bryant wrote: > On 11/29/2013 01:39 PM, Doug Hellmann wrote: > > We have a review up (https://review.openstack.org/#/c/58297/) to add > > some features to the notification system in the oslo incubator. THe > > notification system is being moved into oslo.me

Re: [openstack-dev] [oslo] maintenance policy for code graduating from the incubator

On Mon, Dec 2, 2013 at 8:46 AM, Doug Hellmann wrote: > > > > On Mon, Dec 2, 2013 at 8:36 AM, Russell Bryant wrote: > >> On 11/29/2013 01:39 PM, Doug Hellmann wrote: >> > We have a review up (https://review.openstack.org/#/c/58297/) to add >> > some features to the notification system in the oslo

Re: [openstack-dev] [eventlet] should we use spawn instead of spawn_n?

On 11/29/2013 01:01 AM, Jian Wen wrote: > eventlet.spawn_n is the same as eventlet.spawn, but it’s not possible > to know how the function terminated (i.e. no return value or exceptions)[1]. > If an exception is raised in the function, spawn_n prints a stack trace. > The stack trace will not be wri

Re: [openstack-dev] [Solum] Configuration options placement

On 11/28/2013 03:55 PM, Doug Hellmann wrote: > > > > On Wed, Nov 27, 2013 at 5:21 PM, Georgy Okrokvertskhov > mailto:gokrokvertsk...@mirantis.com>> wrote: > > Hi, > > I am working on the user-authentication BP implementation. I need to > introduce a new configuration option for ena

[openstack-dev] [Olso][DB] Remove eventlet from oslo.db

Hi folks! At the moment I and Roman Podoliaka are working on splitting of openstack.common.db code into a separate library. And it would be nice to drop dependency on eventlet before oslo.db is released. Currently, there is only one place in oslo.db where we use eventlet - wrapping of DB API meth

Re: [openstack-dev] [oslo] maintenance policy for code graduating from the incubator

On 12/02/2013 08:53 AM, Doug Hellmann wrote: > > > > On Mon, Dec 2, 2013 at 8:46 AM, Doug Hellmann > mailto:doug.hellm...@dreamhost.com>> wrote: > > > > > On Mon, Dec 2, 2013 at 8:36 AM, Russell Bryant > wrote: > > On 11/29/2013 01:39 PM, Doug Hel

Re: [openstack-dev] [Olso][DB] Remove eventlet from oslo.db

On 12/02/2013 09:02 AM, Victor Sergeyev wrote: > Hi folks! > > At the moment I and Roman Podoliaka are working on splitting of > openstack.common.db code into a separate library. And it would be nice > to drop dependency on eventlet before oslo.db is released. > > Currently, there is only one pla

Re: [openstack-dev] [Olso][DB] Remove eventlet from oslo.db

On 12/02/2013 09:02 AM, Victor Sergeyev wrote: Hi folks! At the moment I and Roman Podoliaka are working on splitting of openstack.common.db code into a separate library. And it would be nice to drop dependency on eventlet before oslo.db is released. Currently, there is only one place in oslo.d

[openstack-dev] [oslo][messaging]: some questions on the 'driver' API

The BaseDriver - which I take to be the API that must be fulfilled by any transport implementation - has a listen() method taking a target, but no way to stop listening on that specific target. Is this because there is no need to ever cancel a subscription? There is a cleanup() method on the B

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

On 11/29/2013 10:01 AM, Thierry Carrez wrote: > Robert Collins wrote: >> https://etherpad.openstack.org/p/icehouse-external-scheduler > > Just looked into it with release management / TC hat on and I have a > (possibly minor) concern on the deprecation path/timing. > > Assuming everything goes we

[openstack-dev] [Neutron][Tempest] Static IPv6 injection test case

Hi all stackers, Currently Neutron/Nova code has supported the static IPv6 injection, but there is no tempest scenario coverage to support IPv6 injection test case. So I finished the test case and run the it successfully in my local environment, and already submitted the code-review in communit

Re: [openstack-dev] [oslo] maintenance policy for code graduating from the incubator

On Mon, Dec 2, 2013 at 9:06 AM, Russell Bryant wrote: > On 12/02/2013 08:53 AM, Doug Hellmann wrote: > > > > > > > > On Mon, Dec 2, 2013 at 8:46 AM, Doug Hellmann > > mailto:doug.hellm...@dreamhost.com>> > wrote: > > > > > > > > > > On Mon, Dec 2, 2013 at 8:36 AM, Russell Bryant >

Re: [openstack-dev] [oslo] maintenance policy for code graduating from the incubator

On Mon, Dec 2, 2013 at 6:06 AM, Russell Bryant wrote: > On 12/02/2013 08:53 AM, Doug Hellmann wrote: > > > > > > > > On Mon, Dec 2, 2013 at 8:46 AM, Doug Hellmann > > mailto:doug.hellm...@dreamhost.com>> > wrote: > > > > > > > > > > On Mon, Dec 2, 2013 at 8:36 AM, Russell Bryant >

Re: [openstack-dev] [oslo] maintenance policy for code graduating from the incubator

On 02/12/13 09:06 -0500, Russell Bryant wrote: On 12/02/2013 08:53 AM, Doug Hellmann wrote: So, to clarify, possible flows would be: 1) An API moving to a library as-is, like rootwrap Status: Maintained -> Status: Graduating (short term) -> Code removed from oslo-incubator once library is

Re: [openstack-dev] [nova] why are we backporting low priority v3 api fixes to v2?

On Sat, Nov 30, 2013 at 2:25 PM, Christopher Yeoh wrote: > > On Sun, Dec 1, 2013 at 8:02 AM, Matt Riedemann > wrote: > >> I've seen a few bugs/reviews like this [1] lately which are essentially >> backporting fixes from the nova openstack v3 API to the v2 API. While this >> is goodness for the v

Re: [openstack-dev] [oslo] maintenance policy for code graduating from the incubator

On Mon, Dec 2, 2013 at 9:22 AM, Joe Gordon wrote: > > > > On Mon, Dec 2, 2013 at 6:06 AM, Russell Bryant wrote: > >> On 12/02/2013 08:53 AM, Doug Hellmann wrote: >> > >> > >> > >> > On Mon, Dec 2, 2013 at 8:46 AM, Doug Hellmann >> > mailto:doug.hellm...@dreamhost.com>> >> wrote: >> > >> > >> > >

Re: [openstack-dev] [nova] why are we backporting low priority v3 api fixes to v2?

On Mon, Dec 2, 2013 at 9:27 AM, Joe Gordon wrote: > > I don't think we should be blocking them per-se as long as they fit the API > change guidelines https://wiki.openstack.org/wiki/APIChangeGuidelines. Agreed, possibly not what one would assign developers to do but as an open project if it is i

Re: [openstack-dev] [oslo] maintenance policy for code graduating from the incubator

On Mon, Dec 2, 2013 at 9:25 AM, Flavio Percoco wrote: > On 02/12/13 09:06 -0500, Russell Bryant wrote: > >> On 12/02/2013 08:53 AM, Doug Hellmann wrote: >> So, to clarify, possible flows would be: >> >> 1) An API moving to a library as-is, like rootwrap >> >> Status: Maintained >> -> Status:

Re: [openstack-dev] [Swift] Increase Swift ring partition power

On Dec 2, 2013, at 5:19 AM, Christian Schwede wrote: > I'd like to discuss a way to increase the partition power of an existing > Swift cluster. Achieving this transparently is part of the ongoing plans, starting with things like the DiskFile refactoring and SSync. The idea is to isolate the d

Re: [openstack-dev] request-id in API response

On 12/01/2013 10:04 PM, John Dickinson wrote: Just to add to the story, Swift uses "X-Trans-Id" and generates it in the outer-most "catch_errors" middleware. Swift's catch errors middleware is responsible for ensuring that the transaction id exists on each request, and that all errors previously

Re: [openstack-dev] [Olso][DB] Remove eventlet from oslo.db

On 12/02/13 at 09:08am, Russell Bryant wrote: On 12/02/2013 09:02 AM, Victor Sergeyev wrote: Hi folks! At the moment I and Roman Podoliaka are working on splitting of openstack.common.db code into a separate library. And it would be nice to drop dependency on eventlet before oslo.db is released

Re: [openstack-dev] [oslo] maintenance policy for code graduating from the incubator

On 02/12/13 09:40 -0500, Doug Hellmann wrote: On Mon, Dec 2, 2013 at 9:25 AM, Flavio Percoco wrote: On 02/12/13 09:06 -0500, Russell Bryant wrote: On 12/02/2013 08:53 AM, Doug Hellmann wrote: So, to clarify, possible flows would be: 1) An API moving to a library as-

Re: [openstack-dev] [Nova] Splitting up V3 API admin-actions plugin

On 12/02/13 at 08:38am, Russell Bryant wrote: On 12/01/2013 08:39 AM, Christopher Yeoh wrote: Hi, At the summit we agreed to split out lock/unlock, pause/unpause, suspend/unsuspend functionality out of the V3 version of admin actions into separate extensions to make it easier for deployers to o

Re: [openstack-dev] [oslo] maintenance policy for code graduating from the incubator

On Mon, Dec 2, 2013 at 6:37 AM, Doug Hellmann wrote: > > > > On Mon, Dec 2, 2013 at 9:22 AM, Joe Gordon wrote: > >> >> >> >> On Mon, Dec 2, 2013 at 6:06 AM, Russell Bryant wrote: >> >>> On 12/02/2013 08:53 AM, Doug Hellmann wrote: >>> > >>> > >>> > >>> > On Mon, Dec 2, 2013 at 8:46 AM, Doug Hellm

Re: [openstack-dev] [ceilometer][qa] Punting ceilometer from whitelist

On Fri, Nov 29, 2013 at 11:07 AM, David Kranz wrote: > In preparing to fail builds with log errors I have been trying to make > things easier for projects by maintaining a whitelist. But these bugs in > ceilometer are coming in so fast that I can't keep up. So I am just > putting ".*" in the whi

Re: [openstack-dev] request-id in API response

On Mon, Dec 02, 2013 at 09:47:54AM -0500, Jay Pipes wrote: > On 12/01/2013 10:04 PM, John Dickinson wrote: > >Just to add to the story, Swift uses "X-Trans-Id" and generates it in > >the outer-most "catch_errors" middleware. > > > >Swift's catch errors middleware is responsible for ensuring that th

Re: [openstack-dev] request-id in API response

On Sun, Dec 1, 2013 at 7:04 PM, John Dickinson wrote: > Just to add to the story, Swift uses "X-Trans-Id" and generates it in the > outer-most "catch_errors" middleware. > > Swift's catch errors middleware is responsible for ensuring that the > transaction id exists on each request, and that all

[openstack-dev] Incubation Request for Barbican

All, Barbican is the OpenStack key management service and we’d like to request incubation for the Icehouse release. A Rackspace sponsored team has been working for about 9 months now, including following the Havana release cycle for our first release. Our incubation request is here: https://wi

Re: [openstack-dev] [Olso][DB] Remove eventlet from oslo.db

On 12/02/2013 09:51 AM, Andrew Laski wrote: > On 12/02/13 at 09:08am, Russell Bryant wrote: >> On 12/02/2013 09:02 AM, Victor Sergeyev wrote: >>> Hi folks! >>> >>> At the moment I and Roman Podoliaka are working on splitting of >>> openstack.common.db code into a separate library. And it would be n

Re: [openstack-dev] [ceilometer][qa] Punting ceilometer from whitelist

On Fri, Nov 29 2013, David Kranz wrote: > In preparing to fail builds with log errors I have been trying to make > things easier for projects by maintaining a whitelist. But these bugs in > ceilometer are coming in so fast that I can't keep up. So I am just putting > ".*" in the white list for an

[openstack-dev] [all-projects] PLEASE READ: Code to fail builds on new log errors is merging

As mentioned several times on this list, https://review.openstack.org/#/c/58848/ is in the process of merging. Once it does, builds will start failing if there are log ERRORs that are not filtered out by https://github.com/openstack/tempest/blob/master/etc/whitelist.yaml. There are too many is

Re: [openstack-dev] [oslo] maintenance policy for code graduating from the incubator

On Mon, Dec 2, 2013 at 10:05 AM, Joe Gordon wrote: > > > > On Mon, Dec 2, 2013 at 6:37 AM, Doug Hellmann > wrote: > >> >> >> >> On Mon, Dec 2, 2013 at 9:22 AM, Joe Gordon wrote: >> >>> >>> >>> >>> On Mon, Dec 2, 2013 at 6:06 AM, Russell Bryant wrote: >>> On 12/02/2013 08:53 AM, Doug Hellma

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

On 12/02/2013 09:13 AM, Russell Bryant wrote: > On 11/29/2013 10:01 AM, Thierry Carrez wrote: >> Robert Collins wrote: >>> https://etherpad.openstack.org/p/icehouse-external-scheduler >> >> Just looked into it with release management / TC hat on and I have a >> (possibly minor) concern on the dep

[openstack-dev] [ceilometer][qa] log errors

So the last two bugs I filed were coming from check builds that were not merged. It was necessary to look at all builds to get to the point where gate failing on errors could be turned on. Here is the current whitelist. If you folks think the ".*' entries are no longer needed then please let me

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

On 12/02/2013 10:33 AM, Monty Taylor wrote: > Just because I'd like to argue - if what we do here is an actual > forklift, do we really need a cycle of deprecation? > > The reason I ask is that this is, on first stab, not intended to be a > service that has user-facing API differences. It's a reor

Re: [openstack-dev] [Nova] Blueprint: standard specification of guest CPU topology

On Tue, Nov 19, 2013 at 12:15:51PM +, Daniel P. Berrange wrote: > For attention of maintainers of Nova virt drivers Anyone from Hyper-V or VMWare drivers wish to comment on this proposal > A while back there was a bug requesting the ability to set the CPU > topology (sockets/cores/thread

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

On 12/02/2013 10:39 AM, Russell Bryant wrote: > On 12/02/2013 10:33 AM, Monty Taylor wrote: >> Just because I'd like to argue - if what we do here is an actual >> forklift, do we really need a cycle of deprecation? >> >> The reason I ask is that this is, on first stab, not intended to be a >> ser

Re: [openstack-dev] [ceilometer][qa] Punting ceilometer from whitelist

On 12/02/2013 10:24 AM, Julien Danjou wrote: On Fri, Nov 29 2013, David Kranz wrote: In preparing to fail builds with log errors I have been trying to make things easier for projects by maintaining a whitelist. But these bugs in ceilometer are coming in so fast that I can't keep up. So I am ju

Re: [openstack-dev] [nova] Maintaining backwards compatibility for RPC calls

tl;dr - live upgrades are hard. oops. On 11/27/2013 07:38 AM, Day, Phil wrote: > I’m a bit confused about the expectations of a manager class to be able > to receive and process messages from a previous RPC version. I thought > the objective was to always make changes such that the manage can >

[openstack-dev] Incubation / Graduation / New program requirements

Hi! The TC has been working to formalize the set of the criteria it applies when considering project incubation and graduation to integrated status, and when considering new programs. The goal is to be more predictable and that candidate projects and teams know what is expected of them before they

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

On 12/2/13 5:39 PM, "Russell Bryant" wrote: >On 12/02/2013 10:33 AM, Monty Taylor wrote: >> Just because I'd like to argue - if what we do here is an actual >> forklift, do we really need a cycle of deprecation? >> >> The reason I ask is that this is, on first stab, not intended to be a >> ser

Re: [openstack-dev] [Swift] Increase Swift ring partition power

Am 02.12.13 15:47, schrieb Gregory Holt: > Achieving this transparently is part of the ongoing plans, starting > with things like the DiskFile refactoring and SSync. The idea is to > isolate the direct disk access from other servers/tools, something > that (for instance) RSync has today. Once the i

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

On 12/02/2013 10:53 AM, Gary Kotton wrote: > > > On 12/2/13 5:39 PM, "Russell Bryant" wrote: > >> On 12/02/2013 10:33 AM, Monty Taylor wrote: >>> Just because I'd like to argue - if what we do here is an actual >>> forklift, do we really need a cycle of deprecation? >>> >>> The reason I ask is

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

On 12/2/13 5:33 PM, "Monty Taylor" wrote: > > >On 12/02/2013 09:13 AM, Russell Bryant wrote: >> On 11/29/2013 10:01 AM, Thierry Carrez wrote: >>> Robert Collins wrote: https://urldefense.proofpoint.com/v1/url?u=https://etherpad.openstack.o rg/p/icehouse-external-scheduler&k=oIvRg1

Re: [openstack-dev] [neutron] [ml2] Proposing a new time for the ML2 sub-team meeting

FYI: I have moved the ML2 meeting per my email below. The new timeslot per the meeting page [1] is Wednesday at 1600UTC on #openstack-meeting-alt. Thanks! Kyle [1] https://wiki.openstack.org/wiki/Meetings#ML2_Network_sub-team_meeting On Nov 26, 2013, at 9:26 PM, Kyle Mestery (kmestery) wrote:

Re: [openstack-dev] [oslo] maintenance policy for code graduating from the incubator

On Mon, Dec 2, 2013 at 10:26 AM, Doug Hellmann wrote: > > > > On Mon, Dec 2, 2013 at 10:05 AM, Joe Gordon wrote: > >> >> >> >> On Mon, Dec 2, 2013 at 6:37 AM, Doug Hellmann < >> doug.hellm...@dreamhost.com> wrote: >> >>> >>> >>> >>> On Mon, Dec 2, 2013 at 9:22 AM, Joe Gordon wrote: >>>

Re: [openstack-dev] [Swift] Increase Swift ring partition power

On Dec 2, 2013, at 9:48 AM, Christian Schwede wrote: > That sounds great! Is someone already working on this (I know about the > ongoing DiskFile refactoring) or even a blueprint available? There is https://blueprints.launchpad.net/swift/+spec/ring-doubling though I'm uncertain how up to date

Re: [openstack-dev] [Oslo] Layering olso.messaging usage of config

On Mon, Nov 18 2013, Julien Danjou wrote: > https://blueprints.launchpad.net/oslo/+spec/messaging-decouple-cfg So I've gone through the code and started to write a plan on how I'd do things: https://wiki.openstack.org/wiki/Oslo/blueprints/messaging-decouple-cfg I don't think I missed too mu

Re: [openstack-dev] [oslo] maintenance policy for code graduating from the incubator

On Mon, Dec 2, 2013 at 7:26 AM, Doug Hellmann wrote: > > > > On Mon, Dec 2, 2013 at 10:05 AM, Joe Gordon wrote: > >> >> >> >> On Mon, Dec 2, 2013 at 6:37 AM, Doug Hellmann < >> doug.hellm...@dreamhost.com> wrote: >> >>> >>> >>> >>> On Mon, Dec 2, 2013 at 9:22 AM, Joe Gordon wrote: >>> >

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

1) Done 2) Done 3) Attaching a pool to a vip is a private use case. The 'action' can also 'reject the traffic' or something else. So the 'Action' ,ay tell that we need to attach Vip X to Pool Y 4) Not sure .. It is an open discussion for now. 5) See #4 Yes - C

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

On Sun Dec 1 00:27:30 2013, Tzu-Mainn Chen wrote: > I think it's far more important that we list out requirements and > create a design document that people agree upon first. Otherwise, we > run the risk of focusing on feature X for release 1 without ensuring > that our architecture supports fea

[openstack-dev] [nova][database] Update compute_nodes table

Hello, I'm looking for way to a add new attribute to the compute nodes by adding a column to the compute_nodes table in nova database in order to track a metric on the compute nodes and use later it in nova-scheduler. I checked the sqlalchemy/migrate_repo/versions and thought about adding my ow

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

Monty Taylor wrote: > On 12/02/2013 09:13 AM, Russell Bryant wrote: >> On 11/29/2013 10:01 AM, Thierry Carrez wrote: >>> Robert Collins wrote: https://etherpad.openstack.org/p/icehouse-external-scheduler >>> >>> Just looked into it with release management / TC hat on and I have a >>> (possibly

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

Clayton, good detail documentation of the design approach @ https://wiki.openstack.org/wiki/Solum/FeatureBlueprints/BuildingSourceIntoDeploymentArtifacts A few questions - 1. On the objective of supporting both heroku build packs and openshift cartridges: how compatible are these two with each o

Re: [openstack-dev] Incubation Request for Barbican

On 12/02/2013 10:19 AM, Jarret Raim wrote: > All, > > Barbican is the OpenStack key management service and we’d like to > request incubation for the Icehouse release. A Rackspace sponsored team > has been working for about 9 months now, including following the Havana > release cycle for our first

Re: [openstack-dev] Incubation Request for Barbican

On 12/02/2013 11:53 AM, Russell Bryant wrote: >> ** Project must have no library dependencies which effectively restrict how >> the project may be distributed [1] > > http://git.openstack.org/cgit/stackforge/barbican/tree/tools/pip-requires > > It looks like the only item here not in the glo

[openstack-dev] [Mistral] Community meeting meetings - 12/02/2013

Hi, Thanks for joining our community meeting today at #openstack-meeting! Here’re the links to the meeting minutes and the full log: Minutes: http://eavesdrop.openstack.org/meetings/mistral/2013/mistral.2013-12-02-16.00.html Logs: http://eavesdrop.openstack.org/meetings/mistral/2013/mistral.20

Re: [openstack-dev] [nova][database] Update compute_nodes table

On 12/02/2013 11:47 AM, Abbass MAROUNI wrote: > Hello, > > I'm looking for way to a add new attribute to the compute nodes by > adding a column to the compute_nodes table in nova database in order to > track a metric on the compute nodes and use later it in nova-scheduler. > > I checked the sql

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

On 12/02/2013 11:41 AM, Thierry Carrez wrote: > I don't really care that much about deprecation in that case, but I care > about which release the new project is made part of. Would you make it > part of the Icehouse common release ? That means fast-tracking through > incubation *and* integration i

Re: [openstack-dev] [nova] Compute Node Interfaces configuration in Nova Configuration file

Hi, Can anyone share the current deployment use case for compute Node Interfaces configuration in Nova configuration file where hundreads of compute nodes [with two or more physical interfaces] in DC network has to be configured with IPAddress for Management Networks and Data Networks. Is ther

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

On 12/02/2013 10:59 AM, Gary Kotton wrote: > I think that this is certainly different. It is something that we we want > and need a user facing API. > Examples: > - aggregates > - per host scheduling > - instance groups > > Etc. > > That is just taking the nova options into account and not the

Re: [openstack-dev] [Solum] [Security]

On Wed, Nov 27, 2013 at 10:58 AM, Paul Montgomery < paul.montgom...@rackspace.com> wrote: > I created some relatively high level security best practices that I > thought would apply to Solum. I don't think it is ever too early to get > mindshare around security so that developers keep that in min

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

Le 02/12/2013 18:12, Russell Bryant a écrit : On 12/02/2013 10:59 AM, Gary Kotton wrote: I think that this is certainly different. It is something that we we want and need a user facing API. Examples: - aggregates - per host scheduling - instance groups Etc. That is just taking the nova

[openstack-dev] [infra] Meeting Tuesday December 3rd at 19:00 UTC

The OpenStack Infrastructure (Infra) team is hosting our weekly meeting tomorrow, Tuesday December 3rd, 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 inf

Re: [openstack-dev] [Hacking] License headers in empty files

On Thu, Nov 28 2013, Julien Danjou wrote: > On Thu, Nov 28 2013, Sean Dague wrote: > >> I'm totally in favor of going further and saying "empty files shouldn't >> have license headers, because their content of emptiness isn't >> copyrightable" [1]. That's just not how it's written today. > > I wen

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

On 12/02/2013 11:53 AM, Russell Bryant wrote: > On 12/02/2013 10:19 AM, Jarret Raim wrote: >> All, >> >> Barbican is the OpenStack key management service and we’d like to >> request incubation for the Icehouse release. A Rackspace sponsored team >> has been working for about 9 months now, includi

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

On 12/02/2013 12:46 PM, Monty Taylor wrote: > On 12/02/2013 11:53 AM, Russell Bryant wrote: >>> * Scope >>> ** Project must have a clear and defined scope >> >> This is missing >> >>> ** Project should not inadvertently duplicate functionality present in >>> other >>> OpenStack projects. If

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

- Original Message - > Clayton, good detail documentation of the design approach @ > https://wiki.openstack.org/wiki/Solum/FeatureBlueprints/BuildingSourceIntoDeploymentArtifacts > > A few questions - > 1. On the objective of supporting both heroku build packs and openshift > cartridges:

Re: [openstack-dev] problems with rabbitmq on HA controller failure...anyone seen this?

On Nov 29, 2013, at 9:24 PM, Chris Friesen wrote: > On 11/29/2013 06:37 PM, David Koo wrote: >> On Nov 29, 02:22:17 PM (Friday), Chris Friesen wrote: >>> We're currently running Grizzly (going to Havana soon) and we're >>> running into an issue where if the active controller is ungracefully >>>

Re: [openstack-dev] [nova] why are we backporting low priority v3 api fixes to v2?

On Monday, December 02, 2013 8:38:54 AM, Jonathan Proulx wrote: On Mon, Dec 2, 2013 at 9:27 AM, Joe Gordon wrote: I don't think we should be blocking them per-se as long as they fit the API change guidelines https://wiki.openstack.org/wiki/APIChangeGuidelines. Agreed, possibly not what

Re: [openstack-dev] VMware Workstation / Fusion / Player Nova driver

Very cool stuff! Seeing your special glance properties for iso and floppy connections made me think of something. They seem, but it would be nice if they were done in a way that would work in any hypervisor. I "think" we have sufficient detail in block_device_mapping to do essentially the same

Re: [openstack-dev] [ceilometer][qa] Punting ceilometer from whitelist

On 12/02/2013 10:24 AM, Julien Danjou wrote: On Fri, Nov 29 2013, David Kranz wrote: In preparing to fail builds with log errors I have been trying to make things easier for projects by maintaining a whitelist. But these bugs in ceilometer are coming in so fast that I can't keep up. So I am ju

[openstack-dev] [Neutron][qa] Parallel testing update

Hi, As you might have noticed, there has been some progress on parallel tests for neutron. In a nutshell: * Armando fixed the issue with IP address exhaustion on the public network [1] * Salvatore has now a patch which has a 50% success rate (the last failures are because of me playing with it) [2

Re: [openstack-dev] [Nova] New API requirements, review of GCE

I'd like to move this conversation along. It seems to have both stalled and digressed. > Just like with compute drivers, the raised bar applies to existing > drivers, not just new ones. We just gave a significant amount of > lead-time to reach it. I agree with this. The bar needs to be raised. T

Re: [openstack-dev] [Solum] [Security]

Yep, certainly interested in a broader OpenStack view of security; sign me up. :) On 11/27/13 9:06 PM, "Adrian Otto" wrote: > >On Nov 27, 2013, at 11:39 AM, Nathan Kinder > wrote: > >> On 11/27/2013 08:58 AM, Paul Montgomery wrote: >>> I created some relatively high level security best practic

[openstack-dev] [ceilometer] [marconi] Notifications brainstorming session tomorrow @ 1500 UTC

Folks, Want to surface events to end users? Following up on some conversations we had at the summit, I’d like to get folks together on IRC tomorrow to crystalize the design for a notifications project under the Marconi program. The project’s goal is to create a service for surfacing events to

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

On 01/12/13 00:27 -0500, Tzu-Mainn Chen wrote: I think we may all be approaching the planning of this project in the wrong way, because of confusions such as: Well, I think there is one small misunderstanding. I've never said that manual way should be primary workflow for us. I agree that we sh

Re: [openstack-dev] VMware Workstation / Fusion / Player Nova driver

On 02 Dec 2013, at 04:52 , Kyle Mestery (kmestery) wrote: > On Dec 1, 2013, at 4:10 PM, Alessandro Pilotti > wrote: >> >> Hi all, >> >> At Cloudbase we are heavily using VMware Workstation and Fusion for >> development, demos and PoCs, so we thought: why not replacing our automation >> scr

[openstack-dev] [Cinder] Cloning vs copying images

Hi OpenStack, particularly Cinder backend developers, Please consider the following two competing fixes for the same problem: https://review.openstack.org/#/c/58870/ https://review.openstack.org/#/c/58893/ The problem being fixed is that some backends, specifically Ceph RBD, can only boot from v

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

Thank you - that'll work great for the short term until Nachi's patch lands. We still need a +2 from another Nova dev for a patch that disables hairpinning when Neutron is being used [1]. The patch to allow ICMPv6 into instances for SLAAC just landed today[2]. So we're making progress. [1] https

Re: [openstack-dev] VMware Workstation / Fusion / Player Nova driver

On 02 Dec 2013, at 20:54 , Vishvananda Ishaya mailto:vishvana...@gmail.com>> wrote: Very cool stuff! Seeing your special glance properties for iso and floppy connections made me think of something. They seem, but it would be nice if they were done in a way that would work in any hypervisor.

Re: [openstack-dev] [Neutron][qa] Parallel testing update

On Dec 2, 2013 9:04 PM, "Salvatore Orlando" wrote: > > Hi, > > As you might have noticed, there has been some progress on parallel tests for neutron. > In a nutshell: > * Armando fixed the issue with IP address exhaustion on the public network [1] > * Salvatore has now a patch which has a 50% succ

  1   2   >