Re: [openstack-dev] [all][oslo] official recommendations to handle oslo-incubator sync requests

Ihar Hrachyshka wrote: > [...] > I hope I've described the existing oral tradition correctly. Please > comment on that, and if we're ok with the way it's written above, I'd > like to update our wiki pages ([1] and [2]) with that. That matches my version of the oral tradition. One point to note is

Re: [openstack-dev] [oslo][db] Nominating Mike Bayer for the oslo.db core reviewers team

Sure, here is my +1 Folks, it looks like, that there is no no objection to this proposal. Welcome to the team, Mike! On Tue, Aug 19, 2014 at 12:02 PM, Flavio Percoco wrote: > On 08/15/2014 10:26 PM, Doug Hellmann wrote: > > > > On Aug 15, 2014, at 10:00 AM, Ben Nemec wrote: > > > >> On 08/15/

[openstack-dev] [MagnetoDB] OpenStack versioning adoption

Hello contributors, As it was already discussed in #magnetodb IRC channel we are making one more step forward to community processes and adopting OpenStack versioning approach. The development branch 2.0.x [1] stopped and is not going to be supported. The last released version is 2.0.5 [2] The c

Re: [openstack-dev] [Nova] Scheduler split wrt Extensible Resource Tracking

On 08/20/2014 08:27 AM, Joe Gordon wrote: > > On Aug 19, 2014 10:45 AM, "Day, Phil" > wrote: >> >> > -Original Message- >> > From: Nikola Đipanov [mailto:ndipa...@redhat.com > ] >> > Sent: 19 August 2014 17:50 >> > To: openstack-dev@li

Re: [openstack-dev] [Neutron][QoS] Request to be considered for neutron-incubator

Absolutely it's not a good idea to encourage vendor implementing their own attributes in vif-detail, and I just mean it is *possible* to do this, which make sense when some feature is wanted temporarily before it is approved by community. As for the conflicts, restriction can be made that certai

Re: [openstack-dev] [TripleO] Future CI jobs

On 19/08/14 20:55, Gregory Haynes wrote: > Excerpts from Derek Higgins's message of 2014-08-19 10:41:11 +: >> Hi All, >> >>I'd like to firm up our plans around the ci jobs we discussed at the >> tripleo sprint, at the time we jotted down the various jobs on an >> etherpad, to better visuali

Re: [openstack-dev] [TripleO] Future CI jobs

On 19/08/14 13:07, Giulio Fidente wrote: > On 08/19/2014 12:41 PM, Derek Higgins wrote: >> Hi All, >> >> I'd like to firm up our plans around the ci jobs we discussed at the >> tripleo sprint, at the time we jotted down the various jobs on an >> etherpad, to better visualize the matrix of cover

Re: [openstack-dev] [TripleO] Future CI jobs

On 19/08/14 20:58, Gregory Haynes wrote: > Excerpts from Giulio Fidente's message of 2014-08-19 12:07:53 +: >> One last comment, maybe a bit OT but I'm raising it here to see what is >> the other people opinion: how about we modify the -ha job so that at >> some point we actually kill one of

Re: [openstack-dev] [TripleO] Change of meeting time

On 24/05/14 01:21, James Polley wrote: > Following a lengthy discussion under the subject "Alternating meeting > tmie for more TZ friendliness", the TripleO meeting now alternates > between Tuesday 1900UTC (the former time) and Wednesday 0700UTC, for > better coverage across Australia, India, China

Re: [openstack-dev] [all] The future of the integrated release

> > > Additional cross-project resources can be ponied up by the large > > > contributor companies, and existing cross-project resources are not > > > necessarily divertable on command. > > > > Sure additional cross-project resources can and need to be ponied up, but I > > am doubtful that will

Re: [openstack-dev] [TripleO] Change of meeting time

- Original Message - > From: "Derek Higgins" > To: "OpenStack Development Mailing List (not for usage questions)" > > Sent: Wednesday, 20 August, 2014 10:15:51 AM > Subject: Re: [openstack-dev] [TripleO] Change of meeting time > > On 24/05/14 01:21, James Polley wrote: > > Following a l

Re: [openstack-dev] [Neutron][QoS] Request to be considered for neutron-incubator

Hi On Wed, Aug 20, 2014 at 12:12 AM, Salvatore Orlando wrote: > In the current approach QoS support is being "hardwired" into ML2. > > Maybe this is not the best way of doing that, as perhaps it will end up > requiring every mech driver which enforces VIF configuration should support > it. > I se

Re: [openstack-dev] Using gerrymander, a client API and command line tool for gerrit

On Thu, Aug 14, 2014 at 05:54:27PM +0100, Daniel P. Berrange wrote: > > In terms of how I personally use it (assuming the above config file)... > Vish pointed out that I made a bunch of stupid typos in my examples here. Next time I'll actually double-check what I write :-) > At least once a day

Re: [openstack-dev] [all] The future of the integrated release

Eoghan Glynn wrote: > [...] >> And which cross-project concern do you think is most strained by the >> current set of projects in the integrated release? Is it: >> >> * QA >> * infra >> * release management >> * oslo >> * documentation >> * stable-maint >> >> or something else? >> >> >> Good quest

Re: [openstack-dev] [all] The future of the integrated release

Jay Pipes wrote: > [...] > If either of the above answers is NO, then I believe the Technical > Committee should recommend that the integrated project be removed from > the integrated release. > > HOWEVER, I *also* believe that the previously-integrated project should > not just be cast away back

[openstack-dev] [TripleO] 'qemu-img: error while reading sector xxxxxx: Input/Output error

Hi all, I have done a TripleO setup using RDO instack. Now, I am trying to deploy an overcloud on physical servers. I entered all the required parameters in deploy-baremetal-overcloudrc and when I ran instack-deploy-overcloud, I get the following  error in nova-compute logs: 2014-08-20 06:35:43.4

[openstack-dev] Thought on service plugin architecture (was [Neutron][QoS] Request to be considered for neutron-incubator)

As the original thread had a completely different subject, I'm starting a new one here. More specifically the aim of this thread is about: 1) Define when a service is best implemented with a service plugin or with a ML2 driver 2) Discuss how bindings between a "core" resource and the one provided

Re: [openstack-dev] Thought on service plugin architecture (was [Neutron][QoS] Request to be considered for neutron-incubator)

>From a data model perspective, I believe so if we follow the pattern we've followed so far. How will database setup work in this case? IIRC, the auto-generation of schema was just disabled in a recent merge. Will we have a big pile of various migration scripts that users will need to pick from de

Re: [openstack-dev] [pbr] help needed fixing bad version= lines in setup.cfg in many projects

On Wed, Aug 20, 2014 at 5:12 AM, Robert Collins wrote: > Hi, in working on pbr I have run into some bad data in our > setup.cfg's. Details are here: > https://etherpad.openstack.org/p/bad-setup-cfg-versions > > Short version: we need to do a missed step in the release project for > a bunch of stab

Re: [openstack-dev] [neutron]Performance of security group

I couldn't resist making a little benchmark test of the new RPC implementation shihanzhang wrote: http://www.ajo.es/post/95269040924/neutron-security-group-rules-for-devices-rpc-rewrite The results are awesome :-) We yet need to polish the tests a bit, and it's ready. Best regards, Miguel Ángel

[openstack-dev] generate Windows exe

Now bin\swift can only be started by python Scripts\swift Windows does not support extensionless scripts. Maybe I did it wrong, this is my first encounter with distutil. Please consider modifying setup.py import setuptools setuptools.setup( setup_requires=['pbr'], pbr=True, entry_

Re: [openstack-dev] [neutron]Performance of security group

On 08/20/2014 07:34 AM, Miguel Angel Ajo Pelayo wrote: I couldn't resist making a little benchmark test of the new RPC implementation shihanzhang wrote: http://www.ajo.es/post/95269040924/neutron-security-group-rules-for-devices-rpc-rewrite The results are awesome :-) Indeed, fantastic news.

Re: [openstack-dev] Thought on service plugin architecture (was [Neutron][QoS] Request to be considered for neutron-incubator)

I was merely suggesting that this is the approach that we've followed so far. The incubator is not even a real thing at the moment, so it's still too early to make any statement as we do not even know if the stuff in the incubator will use the same database or not. This is a necessary discussion to

[openstack-dev] [Neutron] Mellanox plugin deprecation

Hi, As announced in the last neutron meeting [1], the Mellanox plugin is being deprecated. Juno is the last release to support Mellanox plugin. The Mellanox ML2 Mechanism Driver is replacing the plugin and introduced since Icehouse release. [1] http://eavesdrop.openstack.org/meetings/networ

Re: [openstack-dev] [TripleO] Change of meeting time

On 20/08/14 05:15, Derek Higgins wrote: > On 24/05/14 01:21, James Polley wrote: >> Following a lengthy discussion under the subject "Alternating meeting >> tmie for more TZ friendliness", the TripleO meeting now alternates >> between Tuesday 1900UTC (the former time) and Wednesday 0700UTC, for >>

Re: [openstack-dev] [Nova] Scheduler split wrt Extensible Resource Tracking

On 08/20/2014 04:48 AM, Nikola Đipanov wrote: On 08/20/2014 08:27 AM, Joe Gordon wrote: On Aug 19, 2014 10:45 AM, "Day, Phil" mailto:philip@hp.com>> wrote: -Original Message- From: Nikola Đipanov [mailto:ndipa...@redhat.com ] Sent: 19 August 2014 17:5

[openstack-dev] oslo.db 0.4.0 released

Hello Folks! Oslo team is pleased to announce the new Oslo database handling library release - oslo.db 0.4.0 Thanks all for contributions to this release. Feel free to report issues using the launchpad tracker: https://bugs.launchpad.net/oslo and mark them with ``db`` tag. See the full list of c

Re: [openstack-dev] oslo.db 0.4.0 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Thanks! And I'm immediately bumping the version [1] to utilize raise_on_warnings=False for my mysql-connector effort. :) [1]: https://review.openstack.org/115626 On 20/08/14 14:38, Victor Sergeyev wrote: > Hello Folks! > > Oslo team is pleased to

Re: [openstack-dev] [QA] Picking a Name for the Tempest Library

On 08/18/2014 04:57 PM, Matthew Treinish wrote: On Sat, Aug 16, 2014 at 06:27:19PM +0200, Marc Koderer wrote: Hi all, Am 15.08.2014 um 23:31 schrieb Jay Pipes : I suggest that "tempest" should be the name of the import'able library, and that the integration tests themselves should be what is

[openstack-dev] [Fuel] Enable SSL between client and API exposed via public URL with HAProxy

Hi all, I wrote a "design" to enable SSL between external client and OpenStack public endpoints that provide APIs on public network. This design is available for reviewing here: https://review.openstack.org/#/c/102273/ Of course all comments are welcome :) I also started to work on puppet manif

Re: [openstack-dev] [all] The future of the integrated release

Hi Thierry, thanks for the reply. Comments inline. :) On 08/20/2014 06:32 AM, Thierry Carrez wrote: Jay Pipes wrote: [...] If either of the above answers is NO, then I believe the Technical Committee should recommend that the integrated project be removed from the integrated release. HOWEVER,

Re: [openstack-dev] [Nova] Scheduler split wrt Extensible Resource Tracking

On Wed, Aug 20, 2014 at 08:33:31AM -0400, Jay Pipes wrote: > On 08/20/2014 04:48 AM, Nikola Đipanov wrote: > >On 08/20/2014 08:27 AM, Joe Gordon wrote: > >>On Aug 19, 2014 10:45 AM, "Day, Phil" >>> wrote: > >>> > -Original Message- > From: Nikola Đipanov [

Re: [openstack-dev] [Fuel] Enable SSL between client and API exposed via public URL with HAProxy

Hi, Guillaume. Yes, we are looking forward to removing simple non-HA mode On Wed, Aug 20, 2014 at 5:14 PM, Guillaume Thouvenin wrote: > Hi all, > > I wrote a "design" to enable SSL between external client and OpenStack > public endpoints that provide APIs on public network. This design is > av

[openstack-dev] [Neutron][LBaaS] Error at context exit for subnet in unit test case

Hi, I am writing a unit testcase with context as subnet, code here [1]. When the context exits a delete of subnet is attempted and I am getting a MismatchError . Traceback posted here [2]. What could be going wrong here? Testcase is written like the following -- with self.

Re: [openstack-dev] [Nova] Scheduler split wrt Extensible Resource Tracking

On 08/20/2014 02:33 PM, Jay Pipes wrote: > On 08/20/2014 04:48 AM, Nikola Đipanov wrote: >> Fair enough - I will WIP the revert until Phil is back. It's the right >> thing to do seeing that he is away. > > Well, it's as much (or more?) Paul Murray and Andrea Rosa :) > Yes sorry - meant to say Pa

Re: [openstack-dev] [Neutron][LBaaS] Error at context exit for subnet in unit test case

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 20/08/14 15:42, Vijay Venkatachalam wrote: > Hi, > > I am writing a unit testcase with context as subnet, code here [1]. > When the context exits a delete of subnet is attempted and I am > getting a MismatchError . Traceback posted here [2]. >

Re: [openstack-dev] [Neutron][LBaaS] Error at context exit for subnet in unit test case

I observed the following text as well "One or more ports have an IP allocation from this subnet." Looks like loadbalancer context exit at "blah2" is not cleaning up the port that was created. This ultimately resulted in failure of delete subnet at "blah3". -- with self.subne

[openstack-dev] oslo.utils 0.2.0 release

The Oslo team is pleased to announce the release of version 0.2.0 of oslo.utils, the catch-all library containing small tool modules used throughout OpenStack. This release adds the mask_password() from the incubator to oslo.utils.strutils, along with some bug fixes and enhancements to the inc

Re: [openstack-dev] [Neutron][QoS] Request to be considered for neutron-incubator

On 19 August 2014 23:15, Alan Kavanagh wrote: > +1, I am hoping this is just a short term holding point and this will > eventually be merged into main branch as this is a feature a lot of > companies, us included would definitely benefit from having supported and > many thanks to Sean for stickin

[openstack-dev] [nova][neutron] Migration from nova-network to Neutron for large production clouds

Michael has been posting very informative blogs on the summary of the mid-cycle meetups for Nova. The one on the Nova Network to Neutron migration was of particular interest to me as it raises a number of potential impacts for the CERN production cloud. The blog itself is at http://www.stillhq.

[openstack-dev] [QA] Meeting Thursday August 21st at 22:00 UTC

Hi everyone, Just a quick reminder that the weekly OpenStack QA team IRC meeting will be tomorrow Thursday, August 21st at 22:00 UTC in the #openstack-meeting channel. The agenda for tomorrow's meeting can be found here: https://wiki.openstack.org/wiki/Meetings/QATeamMeeting Anyone is welcome to

[openstack-dev] [neutron] Incubator concerns from packaging perspective

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi all, I've read the proposal for incubator as described at [1], and I have several comments/concerns/suggestions to this. Overall, the idea of giving some space for experimentation that does not alienate parts of community from Neutron is good. I

Re: [openstack-dev] [all] The future of the integrated release

On 19/08/14 10:37, Jay Pipes wrote: By graduating an incubated project into the integrated release, the Technical Committee is blessing the project as "the OpenStack way" to do some thing. If there are projects that are developed *in the OpenStack ecosystem* that are actively being developed to

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On 18 August 2014 11:18, Thierry Carrez wrote: > Doug Hellmann wrote: >> On Aug 13, 2014, at 4:42 PM, Russell Bryant wrote: >>> Let me try to say it another way. You seemed to say that it wasn't much >>> to ask given the rate at which things happen in OpenStack. I would >>> argue that given the

Re: [openstack-dev] [Neutron][LBaaS] Error at context exit for subnet in unit test case

Hey Vijay, Figured out the issue you are having. In that particular test you are creating the same subnet twice. The first time you create it is in the contextlib.nested, the second time is the self.loadbalancer method that will create a subnet if you do not pass it. So you should pass subnet=su

Re: [openstack-dev] [Nova] Scheduler split wrt Extensible Resource Tracking

Le 20/08/2014 15:13, Daniel P. Berrange a écrit : On Wed, Aug 20, 2014 at 08:33:31AM -0400, Jay Pipes wrote: On 08/20/2014 04:48 AM, Nikola Đipanov wrote: On 08/20/2014 08:27 AM, Joe Gordon wrote: On Aug 19, 2014 10:45 AM, "Day, Phil" mailto:philip@hp.com>> wrote: -Original Message--

Re: [openstack-dev] [neutron] Incubator concerns from packaging perspective

Some comments inline. Salvatore On 20 August 2014 17:38, Ihar Hrachyshka wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Hi all, > > I've read the proposal for incubator as described at [1], and I have > several comments/concerns/suggestions to this. > > Overall, the idea of givi

Re: [openstack-dev] [all] The future of the integrated release

On 11/08/14 05:24, Thierry Carrez wrote: So the idea that being (and remaining) in the integrated release should also be judged on technical merit is a slightly different effort. It's always been a factor in our choices, but like Devananda says, it's more difficult than just checking a number of

Re: [openstack-dev] [oslo] Issues with POSIX semaphores and other locks in lockutils

On 08/20/2014 01:40 AM, Angus Lees wrote: > On Mon, 18 Aug 2014 10:05:28 PM Pádraig Brady wrote: >> On 08/18/2014 03:38 PM, Julien Danjou wrote: >>> On Thu, Aug 14 2014, Yuriy Taraday wrote: >>> >>> Hi Yuriy, >>> >>> […] >>> Looking forward to your opinions. >>> >>> This looks like a good summ

[openstack-dev] [ceilometer] indicating sample provenance

One of the outcomes from Juno will be horizontal scalability in the central agent and alarm evaluator via partitioning[1]. The compute agent will get the same capability if you choose to use it, but it doesn't make quite as much sense. I haven't investigated the alarm evaluator side closely yet,

Re: [openstack-dev] [TripleO] Future CI jobs

Excerpts from Derek Higgins's message of 2014-08-20 09:06:48 +: > On 19/08/14 20:58, Gregory Haynes wrote: > > Excerpts from Giulio Fidente's message of 2014-08-19 12:07:53 +: > >> One last comment, maybe a bit OT but I'm raising it here to see what is > >> the other people opinion: how ab

Re: [openstack-dev] [oslo] Issues with POSIX semaphores and other locks in lockutils

This may be slightly off-topic but it is worth mentioning that the use of threading.Lock[1] which was included to make the locks thread safe seems to be leading to a deadlock in eventlet[2]. It seems like we have rewritten this too many times in order to fix minor pain points and are adding risk

Re: [openstack-dev] [Nova] Scheduler split wrt Extensible Resource Tracking

> -Original Message- > From: Daniel P. Berrange [mailto:berra...@redhat.com] > Sent: 20 August 2014 14:13 > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [Nova] Scheduler split wrt Extensible Resource > Tracking > > On Wed, Aug 20, 2014 a

Re: [openstack-dev] generate Windows exe

Is it the right list? The PR was rejected: https://github.com/openstack/python-swiftclient/pull/14 Idézem/Quoting Szépe Viktor : Now bin\swift can only be started by python Scripts\swift Windows does not support extensionless scripts. Maybe I did it wrong, this is my first encounter with set

Re: [openstack-dev] [ceilometer] indicating sample provenance

> a) Am I right that no indicator is there? > > b) Assuming there should be one: > > * Where should it go? Presumably it needs to be an attribute of > each sample because as agents leave and join the group, where > samples are published from can change. > > * How should it be named? The never-en

Re: [openstack-dev] generate Windows exe

Curious, did you follow the link and follow the Gerrit workflow? Seems your rejection letter (unlike mine I received from my sweetheart in high school) was due to process rather than merit. ( http://wiki.openstack.org/GerritWorkflow) *Adam Lawson* AQORN, Inc. 427 North Tatnall Street Ste. 58461 W

Re: [openstack-dev] generate Windows exe

Thank you for your answer. That workflow seems a huge job for me. I leave this patch up to you. Idézem/Quoting Adam Lawson : Curious, did you follow the link and follow the Gerrit workflow? Seems your rejection letter (unlike mine I received from my sweetheart in high school) was due to proce

Re: [openstack-dev] [Neutron][LBaaS] Error at context exit for subnet in unit test case

Hey Brandon, Thanks for looking into it. Yes I figured this out too and passed the pre-created subnet to loadbalancer method. Issue here is slightly different, please have a look at the review https://review.openstack.org/#/c/114173/ Inorder to make it work; I have made network, subnet and load

Re: [openstack-dev] [ceilometer] indicating sample provenance

On Wed, 20 Aug 2014, gordon chung wrote: disclaimer: i'm just riffing and the following might be nonsense. /me is a huge fan of riffing i guess also to extend your question about agents leaving/joining. i'd expect there is some volatility to the agents where an agent may or may not exist at

Re: [openstack-dev] generate Windows exe

Hi Szepe, On Wed 20 Aug 2014 11:33:47 AM PDT, Szépe Viktor wrote: > Thank you for your answer. > That workflow seems a huge job for me. > > I leave this patch up to you. thanks for sending this fix. You've stumbled upon one of the known issues of OpenStack's way to deal with small patches like yo

[openstack-dev] [Octavia] Proposal to support multiple listeners on one HAProxy instance

I am proposing that Octavia should support deployment models that enable multiple listeners to be configured inside the HAProxy instance. The model I am proposing is: 1. One or more VIP per Octavia VM (propose one VIP in 0.5 release) 2. One or more HAProxy instance per Octavia VM 3. One or more l

Re: [openstack-dev] [all] The future of the integrated release

On 08/20/2014 11:41 AM, Zane Bitter wrote: On 19/08/14 10:37, Jay Pipes wrote: By graduating an incubated project into the integrated release, the Technical Committee is blessing the project as "the OpenStack way" to do some thing. If there are projects that are developed *in the OpenStack ecos

Re: [openstack-dev] [Ceilometer] Way to get wrapped method's name/class using Pecan secure decorators?

Hi Ryan, We tried globally applying the hook but could not get execution to enter the hook class. Perhaps we made a mistake, but we concluded the Controller still had to inherit from HookController using the project-wide method. Otherwise we would have been satisfied applying it project-wide.

Re: [openstack-dev] generate Windows exe

Thank you! https://bugs.launchpad.net/python-swiftclient/+bug/1359360 Idézem/Quoting Stefano Maffulli : Hi Szepe, On Wed 20 Aug 2014 11:33:47 AM PDT, Szépe Viktor wrote: Thank you for your answer. That workflow seems a huge job for me. I leave this patch up to you. thanks for sending th

[openstack-dev] [Neutron][L3] Team Meeting Thursday at 1500 UTC

The Neutron L3 Subteam will meet tomorrow at the regular time in #openstack-meeting-3. The agenda [1] is posted, please update as needed. Carl [1] https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam#Agenda ___ OpenStack-dev mailing list OpenSt

Re: [openstack-dev] [oslo] Issues with POSIX semaphores and other locks in lockutils

On 08/20/2014 01:03 PM, Vishvananda Ishaya wrote: > This may be slightly off-topic but it is worth mentioning that the use of > threading.Lock[1] > which was included to make the locks thread safe seems to be leading to a > deadlock in eventlet[2]. > It seems like we have rewritten this too many

[openstack-dev] [Glance][Heat] Murano split dsicussion

During last Atlanta summit there were couple discussions about Application Catalog and Application space projects in OpenStack. These cross-project discussions occurred as a result of Murano incubation request [1] during Icehouse cycle. On the TC meeting devoted to Murano incubation there was an i

Re: [openstack-dev] [oslo] Issues with POSIX semaphores and other locks in lockutils

Ben, +1 to the plan you outlined. -- dims On Wed, Aug 20, 2014 at 4:13 PM, Ben Nemec wrote: > On 08/20/2014 01:03 PM, Vishvananda Ishaya wrote: >> This may be slightly off-topic but it is worth mentioning that the use of >> threading.Lock[1] >> which was included to make the locks thread safe s

Re: [openstack-dev] [all] The future of the integrated release

On 08/20/2014 07:21 AM, Jay Pipes wrote: Hi Thierry, thanks for the reply. Comments inline. :) On 08/20/2014 06:32 AM, Thierry Carrez wrote: If we want to follow your model, we probably would have to dissolve programs as they stand right now, and have blessed categories on one side, and teams o

Re: [openstack-dev] generate Windows exe

Hi Viktor, I just submitted the patch, adding you as co-author with the email address that you used here, please let me know if this is ok for you: https://review.openstack.org/#/c/115782/ The patch is even easier compared to what you sent as all we need is to add declaratively the requested en

Re: [openstack-dev] [all] The future of the integrated release

On 08/20/2014 05:06 PM, Chris Friesen wrote: On 08/20/2014 07:21 AM, Jay Pipes wrote: Hi Thierry, thanks for the reply. Comments inline. :) On 08/20/2014 06:32 AM, Thierry Carrez wrote: If we want to follow your model, we probably would have to dissolve programs as they stand right now, and ha

[openstack-dev] [Ceilometer] Ceilometer API RBAC enhancement proposal (work in progress)

To anyone who's interested, we're working on a proposal and implementation of a fine-grained v3 compatible RBAC scheme for the API. The WIP spec change is here: https://review.openstack.org/#/c/112137/ I realize this will need to move from Juno to Kilo because it won't make Juno. And the code

[openstack-dev] [Neutron] How to handle blocking bugs/changes in Neutron 3rd party CI

Preface: I posed this problem on the #openstack-infra IRC, and they couldn't offer an easy or obvious solution, and suggested that I get some consensus from the Neutron community as to how we want to handle this situation. So I'd like to bounce this around, get some ideas, and maybe bring this u

[openstack-dev] [Heat] Improve /validate call

Hey folks, I just submitted a new spec to change the behavior of our current /validate call. TL;DR: we should at least add a request param to allow the user to change the format of the output they get back or, possibly refactor it into two separate calls. You can see the blueprint and spec here:

[openstack-dev] Help with sql upgrade and downgrade

Hi, I am trying to add two new columns to backups table in cinder. I created the new version file as follows: from sqlalchemy import Column, MetaData, String, Table, Boolean def upgrade(migrate_engine): meta = MetaData() meta.bind = migrate_engine backups = Table('backups', me

Re: [openstack-dev] [Heat] Improve /validate call

On 21/08/14 10:27, Anderson Mesquita wrote: > Hey folks, > > I just submitted a new spec to change the behavior of our current > /validate call. > > TL;DR: we should at least add a request param to allow the user to > change the format of the output they get back or, possibly refactor it > into two

Re: [openstack-dev] Help with sql upgrade and downgrade

On 2014-08-20 6:42 PM, Murali Balcha wrote: I can successfully add string column parent_id without any problem. However adding a boolean column is vexing. Adding a boolean column adds a check constraint on the table but when I remove the column in the downgrade, the check constraint for snapshot

Re: [openstack-dev] [all] The future of the integrated release

On Thu, Aug 21, 2014 at 2:37 AM, Zane Bitter wrote: > On 11/08/14 05:24, Thierry Carrez wrote: > >> So the idea that being (and remaining) in the integrated release should >> also be judged on technical merit is a slightly different effort. It's >> always been a factor in our choices, but like De

[openstack-dev] [Neutron][LBaaS] Weekly IRC Agenda

Hey LBaaS folks, This is you friendly reminder to provide any agenda items for tomorrow's weekly IRC meeting. Please add them to the agenda wiki ==> https://wiki.openstack.org/wiki/Network/LBaaS#Agenda. Cheers, --Jorge ___ OpenStack-dev mailing list O

Re: [openstack-dev] Help with sql upgrade and downgrade

Thanks for the help Mathieu. Now I know why that script exists :) On 8/20/14, 6:55 PM, "Mathieu Gagné" wrote: >On 2014-08-20 6:42 PM, Murali Balcha wrote: >> >> I can successfully add string column parent_id without any problem. >> However adding a boolean column is vexing. Adding a boolean colu

Re: [openstack-dev] [neutron][all] switch from mysqldb to another eventlet aware mysql client

On Mon, Aug 18, 2014, at 01:59 AM, Ihar Hrachyshka wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 17/08/14 02:09, Angus Lees wrote: > > > > On 16 Aug 2014 06:09, "Doug Hellmann" > > wrote: > >> > >> > >> On Aug 15, 2014, at 9:29 AM, Ihar Hrachys

Re: [openstack-dev] [All] Switching default test node to Trusty for all projects and upgrading tox to version 1.7.2

On Tue, Aug 5, 2014, at 05:04 PM, Clark Boylan wrote: > Hello, > > On August 20th the Infra team will be switching the default test node > from Ubuntu Precise to Ubuntu Trusty. This means that `tox -epy27`, `tox > -ecover`, `tox -epep8`, `tox -evenv -- python setup.py build_sphinx` > will run on T

Re: [openstack-dev] [nova][libvirt] Non-readonly connection to libvirt in unit tests

On 8/11/2014 4:42 AM, Daniel P. Berrange wrote: On Mon, Aug 04, 2014 at 06:46:13PM -0400, Solly Ross wrote: Hi, I was wondering if there was a way to get a non-readonly connection to libvirt when running the unit tests on the CI. If I call `LibvirtDriver._connect(LibvirtDriver.uri())`, it wor

Re: [openstack-dev] [nova][libvirt] Non-readonly connection to libvirt in unit tests

On 8/11/2014 4:42 AM, Daniel P. Berrange wrote: On Mon, Aug 04, 2014 at 06:46:13PM -0400, Solly Ross wrote: Hi, I was wondering if there was a way to get a non-readonly connection to libvirt when running the unit tests on the CI. If I call `LibvirtDriver._connect(LibvirtDriver.uri())`, it wor

Re: [openstack-dev] Thought on service plugin architecture (was [Neutron][QoS] Request to be considered for neutron-incubator)

On Wed, Aug 20, 2014 at 7:03 PM, Salvatore Orlando wrote: > As the original thread had a completely different subject, I'm starting a > new one here. > > More specifically the aim of this thread is about: > 1) Define when a service is best implemented with a service plugin or with > a ML2 driver

Re: [openstack-dev] [neutron]Performance of security group

Great！ We met similar problems. The current mechanisms produce too many iptables rules, and it's hard to debug. Really look forward to seeing a more efficient security group design. On Thu, Jul 10, 2014 at 11:44 PM, Kyle Mestery wrote: > On Thu, Jul 10, 2014 at 4:30 AM, shihanzhang > wrote: >

Re: [openstack-dev] [neutron]Performance of security group

+1 "NFTablesDriver"! Also, NFTables, AFAIK, improves IDS systems, like Suricata, for example: https://home.regit.org/2014/02/suricata-and-nftables/ Then, I'm wondering here... What benefits might come for OpenStack Nova / Neutron, if it comes with a NFTables driver, instead of the current IPTable

Re: [openstack-dev] [neutron]Performance of security group

hi neutroner! my patch about BP:https://blueprints.launchpad.net/openstack/?searchtext=add-ipset-to-security need install ipset in devstack, I have commit the patch:https://review.openstack.org/#/c/113453/, who can help me review it, thanks very much! Best regards, shihanzhang A

Re: [openstack-dev] [all] The future of the integrated release

Excerpts from Robert Collins's message of 2014-08-18 23:41:20 -0700: > On 18 August 2014 09:32, Clint Byrum wrote: > > I can see your perspective but I don't think its internally consistent... > > > Here's why folk are questioning Ceilometer: > > > > Nova is a set of tools to abstract virtualiza

Re: [openstack-dev] [all] The future of the integrated release

Excerpts from Jay Pipes's message of 2014-08-20 14:53:22 -0700: > On 08/20/2014 05:06 PM, Chris Friesen wrote: > > On 08/20/2014 07:21 AM, Jay Pipes wrote: > >> Hi Thierry, thanks for the reply. Comments inline. :) > >> > >> On 08/20/2014 06:32 AM, Thierry Carrez wrote: > >>> If we want to follow y

Re: [openstack-dev] [ceilometer] indicating sample provenance

On 08/20/2014 09:25 PM, Chris Dent wrote: On Wed, 20 Aug 2014, gordon chung wrote: disclaimer: i'm just riffing and the following might be nonsense. /me is a huge fan of riffing i guess also to extend your question about agents leaving/joining. i'd expect there is some volatility to the a

[openstack-dev] [ceilometer] repackage ceilometer and ceilometerclient

Folks, I wrote the following BP regarding repackaging ceilometer and ceilometerclient. https://blueprints.launchpad.net/ceilometer/+spec/repackaging-ceilometerclient I need to install the ceilometer package when the swift_middlware middleware uses. And the ceilometer package has dependencies w

Re: [openstack-dev] [neutron]Performance of security group

Thank you shihanzhang!, I can't believe I didn't realize the ipset part spec was accepted I live on my own bubble... I will be reviewing and testing/helping on that part too during the next few days, I was too concentrated in the RPC part. Best regards, - Original Message - > hi neutr

Re: [openstack-dev] [ceilometer] repackage ceilometer and ceilometerclient

On 08/21/2014 07:50 AM, Osanai, Hisashi wrote: Folks, I wrote the following BP regarding repackaging ceilometer and ceilometerclient. https://blueprints.launchpad.net/ceilometer/+spec/repackaging-ceilometerclient I need to install the ceilometer package when the swift_middlware middleware

Re: [openstack-dev] [neutron] Incubator concerns from packaging perspective

On Thu, Aug 21, 2014 at 12:28 AM, Salvatore Orlando wrote: > Some comments inline. > > Salvatore > > On 20 August 2014 17:38, Ihar Hrachyshka wrote: > >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA512 >> >> Hi all, >> >> I've read the proposal for incubator as described at [1], and I have >>

Re: [openstack-dev] [Octavia] Proposal to support multiple listeners on one HAProxy instance

Hi Michael! Just to give others some background on this: The current proposal (by me) is to have each Listener object, (as defined in the Neutron LBaaS v2 code base) correspond with one haproxy process on the Octavia VM in the currently proposed Octavia design document. Michael's proposal is to ha

Re: [openstack-dev] [all] The future of the integrated release

On 08/20/2014 09:54 PM, Clint Byrum wrote: Excerpts from Jay Pipes's message of 2014-08-20 14:53:22 -0700: On 08/20/2014 05:06 PM, Chris Friesen wrote: On 08/20/2014 07:21 AM, Jay Pipes wrote: Hi Thierry, thanks for the reply. Comments inline. :) On 08/20/2014 06:32 AM, Thierry Carrez wrote:

Re: [openstack-dev] [ceilometer] repackage ceilometer and ceilometerclient

Thank you for your quick response. On Thursday, August 21, 2014 3:12 PM, Nejc Saje wrote: > I don't think there's any way the modules you mention in the BP can be > moved into ceilometerclient. I think the best approach to resolve this > would be to rewrite swift middleware to use oslo.messaging