Re: [openstack-dev] [heat] health maintenance in autoscaling groups

Just some random thoughts below ... On Tue, Jul 01, 2014 at 03:47:03PM -0400, Mike Spreitzer wrote: > In AWS, an autoscaling group includes health maintenance functionality --- > both an ability to detect basic forms of failures and an ability to react > properly to failures detected by itself o

Re: [openstack-dev] Inter Cloud Resource Federation (Alliance)

Will this work will be built to exploit the existing federated authentication and role mapping code in Icehouse ? Resource discover/access/provisioning is a natural next step but I hope it is built on the existing identity frameworks. Tim From: Tiwari, Arvind [mailto:arvind.tiw...@hp.com] Sen

[openstack-dev] Multiple API/RPC process behavior

Hello, I've installed the latest version of RHOS5, set multiple API\RPC workers within neutron.conf file to 8 (the amount of cores of the host) After I ran "openstack-service restart" I've got different result for ML2 and Openvswitch deployments. In ML2 deployment all 17 (1-parent and 16 ch

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

Shihazhang, I really believe we need the RPC refactor done for this cycle, and given the close deadlines we have (July 10 for spec submission and July 20 for spec approval). Don't you think it's going to be better to split the work in several specs? 1) ipset optimization (you) 2) s

[openstack-dev] [Nova} NFV patches

Hi, There are some patches that are relevant to the NFV support. There are as follows: 1. Current exception handling for interface attachment is broken - https://review.openstack.org/103091 2. The V2 port attach is a blocking call. This cannot be changed so a proposal to have the V3 as no

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 02/07/14 10:12, Miguel Angel Ajo wrote: > > Shihazhang, > > I really believe we need the RPC refactor done for this cycle, and > given the close deadlines we have (July 10 for spec submission and > July 20 for spec approval). > > Don't you thi

Re: [openstack-dev] [OpenStack][DevStack] Failed to install OpenStack with DevStack

? 2014/7/2 13:58, Jay Lau ??: Hi, Does any one encounter this error when install devstack? How did you resolve this issue? + [[ 1 -ne 0 ]] + echo 'Error on exit' Error on exit + ./tools/worlddump.py -d usage: worlddump.py [-h] [-d DIR] worlddump.py: error: argument -d/--dir: expected one argu

Re: [openstack-dev] [Nova] Mid-cycle sprint for remote people ?

On 07/01/2014 03:40 PM, Sylvain Bauza wrote: > Hi, > > I won't be able to attend the mid-cycle sprint due to a good family > reason (a new baby 2.0 release expected to land by these dates), so I'm > wondering if it's possible to webcast some of the sessions so people who > are not there can still

Re: [openstack-dev] [Fuel] Few hot questions related to patching for openstack

Hello, > Could you please clarify what exactly you mean by "our patches" / > "our first patch"? I mean which version should we use in 5.0.1, for example? As far as I understand @DmitryB, it have to be "2014.1-5.0.1". Am I right? Thanks, Igor On Tue, Jul 1, 2014 at 8:47 PM, Aleksandr Didenko

Re: [openstack-dev] [Nova} NFV patches

Le 02/07/2014 10:39, Gary Kotton a écrit : > Hi, > There are some patches that are relevant to the NFV support. There are > as follows: > > 1. Current exception handling for interface attachment is broken > - https://review.openstack.org/103091 > 2. The V2 port attach is a blocking call. This

Re: [openstack-dev] DVR and FWaaS integration

Carl, For the overlap IP, I was thinking about whether we could have a case where two VMs have the same subnet but belongs to different network. So if we create policy base on subnet, how will it work. Yi On 6/29/14, 12:43 PM, Carl Baldwin wrote: In line... On Jun 25, 2014 2:02 PM, "Yi Sun

Re: [openstack-dev] [oslo][messaging] Further improvements and refactoring

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 01/07/14 17:14, Alexei Kornienko wrote: > Hi, > > Please see some minor comments inline. Do you think we can schedule > some time to discuss this topic on one of the upcoming meetings? We > can come out with some kind of the summary and actions p

Re: [openstack-dev] Using tmux instead of screen in devstack

Sean Dague wrote: > On 07/01/2014 08:11 AM, Anant Patil wrote: >> Hi, >> >> I use tmux (an alternative to screen) a lot and I believe lot of other >> developers use it. I have been using devstack for some time now and >> would like to add the option of using tmux instead of screen for >> creating s

Re: [openstack-dev] [heat] health maintenance in autoscaling groups

On Wed, Jul 02, 2014 at 03:02:14PM +0800, Qiming Teng wrote: > Just some random thoughts below ... > > On Tue, Jul 01, 2014 at 03:47:03PM -0400, Mike Spreitzer wrote: > > In AWS, an autoscaling group includes health maintenance functionality --- > > both an ability to detect basic forms of failur

Re: [openstack-dev] [Nova] Mid-cycle sprint for remote people ?

Sylvain Bauza wrote: > Hi, > > I won't be able to attend the mid-cycle sprint due to a good family > reason (a new baby 2.0 release expected to land by these dates), so I'm > wondering if it's possible to webcast some of the sessions so people who > are not there can still share their voices ? It

Re: [openstack-dev] [heat] One more lifecycle plug point - in scaling groups

On Wed, Jul 02, 2014 at 02:41:19AM +, Adrian Otto wrote: >Zane, >If you happen to have a link to this blueprint, could you reply with it? I >took a look, but did not find it. >I'd like to suggest that the implementation allow apps to call >unauthenticated (signed) webhook UR

Re: [openstack-dev] Multiple API/RPC process behavior

I'd recommend you to go for ml2, as openvswitch alone plugin will be removed during Juno, making an upgrade path harder on your side. I suppose there could be a bug/noimplementation for multiplerpc workers within openvswitch plugin, but as it's deprecated there are high chances that it won't be f

Re: [openstack-dev] [OpenStack][DevStack] Failed to install OpenStack with DevStack

Thanks Ken'ichi, its working for me ;-) Eli, perhaps you can try again as Ken'ichi's solution. 2014-07-02 14:35 GMT+08:00 Ken'ichi Ohmichi : > Hi Jay, > > I faced the same problem and can pass it with adding the following line > into localrc: > > LOGFILE=/opt/stack/logs/stack.sh.log > > Thanks

Re: [openstack-dev] [Neutron] VMware networking

Hi, Sadly last night night we did not have enough people to make any progress. Lets try again next week Monday at 14:00 UTC. The meeting will take place on #openstack-vmware channel Alut a continua Gary On 6/30/14, 6:38 PM, "Kyle Mestery" wrote: >On Mon, Jun 30, 2014 at 10:18 AM, Armando M. wro

[openstack-dev] CI setup related request (devstack-gate)

all, i need to make some changes in my 3rd party CI system. specifically,  i need to override devstack-gate-vm.sh for the mysql path - i can do this by setting SKIP_DEVSTACK_GATE_PROJECT in my examples.yaml file, although this means i will need to manually update the devstack-gate directory howev

Re: [openstack-dev] [trove] guestagent config for overriding managers

Hi Craig. Seems like perfect task to use stevedore and its plugin system. I do agree that it looks very nasty to have huge dict of managers. I don't like the idea of placing 'manager' under config groups, because each config group should be registered, and when it's done only then you can use opti

Re: [openstack-dev] [all][specs] Please stop doing specs for any changes in projects

IMO, 'spec' is indeed a good idea and indeed useful for tracking features, although it's a little tough for us not using English as native language. But we still need to identify these 'small features', and core reviewers do some review, then approve them ASAP, so that we can avoid to waste a lot o

Re: [openstack-dev] [Nova} NFV patches

On 2 July 2014 10:39, Gary Kotton wrote: > There are some patches that are relevant to the NFV support. There are > as follows: > Additionally, we who are building Deutsche Telekom's open source NFV implementation will be able to make that available to the whole community if the VIF_VHOSTUSER s

Re: [openstack-dev] [all] milestone-proposed is dead, long lives proposed/foo

Hello. On Fri, Jun 27, 2014 at 4:44 PM, Thierry Carrez wrote: > For all those reasons, we decided at the last summit to use unique > pre-release branches, named after the series (for example, > "proposed/juno"). That branch finally becomes "stable/juno" at release > time. In parallel, we abandon

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

hi Miguel Ángel and Ihar Hrachyshka, I agree with you that split the work in several specs, I have finished the work ( ipset optimization), you can do 'sg rpc optimization (without fanout)'. as the third part(sg rpc optimization (with fanout)), I think we need talk about it, because just using

Re: [openstack-dev] [Nova] Mid-cycle sprint for remote people ?

On 07/02/2014 06:09 AM, Thierry Carrez wrote: Sylvain Bauza wrote: Hi, I won't be able to attend the mid-cycle sprint due to a good family reason (a new baby 2.0 release expected to land by these dates), so I'm wondering if it's possible to webcast some of the sessions so people who are not th

Re: [openstack-dev] [Keystone] [Swift] Question re. keystone domains

Thanks Dolph, that’s helpful. For backwards compatibility reasons we need to preserve legacy access control list behavior for projects/users in the default domain only. To achieve that, we need to persist the project’s domain id in Swift. If a project subsequently moved to/from the default doma

Re: [openstack-dev] [Nova] Mid-cycle sprint for remote people ?

Le 02/07/2014 14:51, Andrew Laski a écrit : > > On 07/02/2014 06:09 AM, Thierry Carrez wrote: >> Sylvain Bauza wrote: >>> Hi, >>> >>> I won't be able to attend the mid-cycle sprint due to a good family >>> reason (a new baby 2.0 release expected to land by these dates), so I'm >>> wondering if it's

[openstack-dev] Neutron ML2 Blueprints

Guys, as we are working on 2 separate implementations of ML2 plugin support, I suggest to split it into 2 blueprints: 1. https://blueprints.launchpad.net/fuel/+spec/ml2-neutron - this blueprint is initial ML2 support and is being implemented by Sergey Vasilenko (@xenolog) and is almost ready and b

Re: [openstack-dev] [oslo][messaging] Further improvements and refactoring

On 07/01/2014 03:52 PM, Ihar Hrachyshka wrote: On 01/07/14 15:55, Alexei Kornienko wrote: And in addition I've provided some links to existing implementation with places that IMHO cause bottlenecks. From my point of view that code is doing obviously stupid things (like closing/opening sockets fo

[openstack-dev] [Neutron][LBaaS] Flavor meeting log captured?

Hi, I didn't attend the flavor framework meeting that was scheduled on irc #openstack-meeting-3 last Friday. Will be interested to see the meeting log/minutes. Was it captured? Thanks, Vijay V ___ OpenStack-dev mailing list OpenStack-dev@lists.op

[openstack-dev] [Fuel] Neutron ML2 Blueprints

Guys, as we are working on 2 separate implementations of ML2 plugin support, I suggest to split it into 2 blueprints: 1. https://blueprints.launchpad.net/fuel/+spec/ml2-neutron - this blueprint is initial ML2 support and is being implemented by Sergey Vasilenko (@xenolog) and is almost ready and b

Re: [openstack-dev] Neutron ML2 Blueprints

Sorry, guys, forgot to prepend [Fuel] prefix. On Wed, Jul 2, 2014 at 5:24 PM, Vladimir Kuklin wrote: > Guys, as we are working on 2 separate implementations of ML2 plugin > support, I suggest to split it into 2 blueprints: > > 1. https://blueprints.launchpad.net/fuel/+spec/ml2-neutron - this >

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

Nice Shihanzhang, Do you mean the ipset implementation is ready, or just the spec?. For the SG group refactor, I don't worry about who does it, or who takes the credit, but I believe it's important we address this bottleneck during Juno trying to match nova's scalability. Best regards,

Re: [openstack-dev] [Neutron] VMware networking

1400UTC works for me, and I've put it on my calendar. Thanks! On Wed, Jul 2, 2014 at 6:27 AM, Gary Kotton wrote: > Hi, > Sadly last night night we did not have enough people to make any progress. > Lets try again next week Monday at 14:00 UTC. The meeting will take place > on #openstack-vmware ch

Re: [openstack-dev] [Neutron][LBaaS] Flavor meeting log captured?

Hi Vijay, Yes, it was logged under advanced service: http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-06-27-17.30.log.html http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-06

[openstack-dev] [sahara] team meeting July 3 1800 UTC

Hi folks, We'll be having the Sahara team meeting as usual in #openstack-meeting-alt channel. Agenda: https://wiki.openstack.org/wiki/Meetings/SaharaAgenda#Next_meetings http://www.timeanddate.com/worldclock/fixedtime.html?msg=Sahara+Meeting&iso=20140703T18 -- Sincerely yours, Sergey Lukjanov

Re: [openstack-dev] Using tmux instead of screen in devstack

On 07/01/2014 08:52 AM, CARVER, PAUL wrote: > Anant Patil wrote: >> I use tmux (an alternative to screen) a lot and I believe lot of other >> developers use it. >> I have been using devstack for some time now and would like to add the >> option of >> using tmux instead of screen for creating sess

Re: [openstack-dev] [oslo][messaging] Further improvements and refactoring

On 07/01/2014 04:14 PM, Alexei Kornienko wrote: A lot of driver details leak outside the API and it makes it hard to improve driver without changing the API. I agree that some aspects of specific driver implementations leak into the public API for the messaging library as a whole. There are al

Re: [openstack-dev] [all] milestone-proposed is dead, long lives proposed/foo

On 2014-07-02 16:14:52 +0400 (+0400), Yuriy Taraday wrote: > Why do we need these short-lived 'proposed' branches in any form? > Why can't we just use release branches for this and treat them as > stable when appropriate tag is added to some commit in them? The primary reasons are: 1. People inte

Re: [openstack-dev] [cinder] 3rd party ci names for use by official cinder mandated tests

On 07/01/2014 01:13 PM, Asselin, Ramy wrote: > 3rd party ci names is currently becoming a bit controversial for what we're > trying to do in cinder: https://review.openstack.org/#/c/101013/ > The motivation for the above change is to aid developers understand what the > 3rd party ci systems are t

Re: [openstack-dev] [all] 3rd Party CI vs. Gerrit

On 07/01/2014 12:27 PM, Asselin, Ramy wrote: > Anita, > > This line [1] is effectively a sub-set of tempest-dsm-full, and what we're > currently running manually now. I far as I understood, this is the current > minimum. The exact sub-set (or full set, or if additional tests are allowed) > is

Re: [openstack-dev] [all] 3rd Party CI vs. Gerrit

On 07/01/2014 10:03 AM, Duncan Thomas wrote: > On 1 July 2014 14:44, Anita Kuno wrote: > >> On 07/01/2014 05:56 AM, Duncan Thomas wrote: >>> For the record, cinder gave a very clear definition of success in our >>> 3rd party guidelines: Passes every test in tempest-dsm-full. If that >>> needs doc

Re: [openstack-dev] [oslo][messaging] Further improvements and refactoring

On Wed, Jul 2, 2014 at 5:46 AM, Ihar Hrachyshka wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 01/07/14 17:14, Alexei Kornienko wrote: >> Hi, >> >> Please see some minor comments inline. Do you think we can schedule >> some time to discuss this topic on one of the upcoming meeti

Re: [openstack-dev] [Neutron][ML2] Modular L2 agent architecture

Hi, sorry for the late reply, I was out of office for 3 weeks. I also love the idea of having a single thread in charge of writing dataplane actions. As Zang described, this thread would read events in a queue, which could be populated by agent_drivers. The main goal would be to avoid desynchroniz

Re: [openstack-dev] [Keystone] [Swift] Question re. keystone domains

On 07/01/2014 12:15 PM, Dolph Mathews wrote: > > On Tue, Jul 1, 2014 at 11:20 AM, Coles, Alistair > wrote: > > We have a change [1] under review in Swift to make access control > lists compatible with migration to keystone v3 domains. The change > make

[openstack-dev] [Neutron][LBaaS] Analyzing the critical path

To reiterate the Juno release plan from: https://wiki.openstack.org/wiki/Juno_Release_Schedule Feature freeze is at: 21st August. I am listing tasks which we should consider to be done for Juno and who should handle them. The following might be considered as critical path to get anything for Ju

Re: [openstack-dev] [third party] - minimum response time for 3rd party CI responses

On 06/30/2014 03:04 PM, Kevin Benton wrote: > Hello all, > > The subject of 3rd party CI voting responses came up in the 3rd-party IRC > meeting today.[1] We would like to get feedback from the larger dev > community on what acceptable response times are for third party CI systems. > > As a maint

Re: [openstack-dev] [heat] health maintenance in autoscaling groups

Mike Spreitzer/Watson/IBM@IBMUS wrote on 07/02/2014 02:41:48 AM: > Zane Bitter wrote on 07/01/2014 06:58:47 PM: > > > On 01/07/14 15:47, Mike Spreitzer wrote: > > > In AWS, an autoscaling group includes health maintenance functionality > > > --- both an ability to detect basic forms of failures

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

On Wed, Jul 2, 2014 at 3:43 AM, Ihar Hrachyshka wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 02/07/14 10:12, Miguel Angel Ajo wrote: >> >> Shihazhang, >> >> I really believe we need the RPC refactor done for this cycle, and >> given the close deadlines we have (July 10 for spe

Re: [openstack-dev] [Neutron][QA] Enabling full neutron Job

Hi again, >From my analysis most of the failures affecting the neutron full job are because of bugs [1] and [2] for which patch [3] and [4] have been proposed. Both patches address the nova side of the neutron/nova notification system for vif plugging. It is worth noting that these bugs did manife

[openstack-dev] [all] SpecProposalDeadline and SpecApprovalDeadline

Hi everyone, During this cycle we experiment with using -specs repositories. Those proved very popular, and busy projects have now built a healthy backlog of -specs reviews. However, there will come a time when reviewing specs will become a distraction. At some point in the cycle, we'll know that

Re: [openstack-dev] [Neutron][LBaaS] Analyzing the critical path

Hi Sam, I'll comment on what I know in-line. On Wed, 2014-07-02 at 15:29 +, Samuel Bercovici wrote: > To reiterate the Juno release plan from: > https://wiki.openstack.org/wiki/Juno_Release_Schedule > > Feature freeze is at: 21st August. > > > > I am listing tasks which we should consider

Re: [openstack-dev] [all][specs] Please stop doing specs for any changes in projects

On Wed, Jul 2, 2014 at 7:08 AM, Lingxian Kong wrote: > IMO, 'spec' is indeed a good idea and indeed useful for tracking > features, although it's a little tough for us not using English as > native language. But we still need to identify these 'small features', > and core reviewers do some review

Re: [openstack-dev] [heat] health maintenance in autoscaling groups

Qiming Teng wrote on 07/02/2014 03:02:14 AM: > Just some random thoughts below ... > > On Tue, Jul 01, 2014 at 03:47:03PM -0400, Mike Spreitzer wrote: > > ... > > I have not found design discussion of this; have I missed something? > > > > I suppose the natural answer for OpenStack would be cen

Re: [openstack-dev] [heat] health maintenance in autoscaling groups

Steven Hardy wrote on 07/02/2014 06:02:36 AM: > On Wed, Jul 02, 2014 at 03:02:14PM +0800, Qiming Teng wrote: > > Just some random thoughts below ... > > > > On Tue, Jul 01, 2014 at 03:47:03PM -0400, Mike Spreitzer wrote: > > > ... > > > The resource signal interface used by ceilometer can carry

Re: [openstack-dev] [all][specs] Please stop doing specs for any changes in projects

Excerpts from Dolph Mathews's message of 2014-07-01 10:02:13 -0700: > The argument has been made in the past that small features will require > correspondingly small specs. If there's a counter-argument to this example > (a "small" feature requiring a relatively large amount of spec effort), I'd >

Re: [openstack-dev] [heat] health maintenance in autoscaling groups

Excerpts from Qiming Teng's message of 2014-07-02 00:02:14 -0700: > Just some random thoughts below ... > > On Tue, Jul 01, 2014 at 03:47:03PM -0400, Mike Spreitzer wrote: > > In AWS, an autoscaling group includes health maintenance functionality --- > > both an ability to detect basic forms of f

Re: [openstack-dev] [trove] guestagent config for overriding managers

I’m a fan of the later suggestion. Thanks, Tim From: Craig Vyvial [mailto:cp16...@gmail.com] Sent: Tuesday, July 01, 2014 11:35 PM To: OpenStack Development Mailing List Subject: [openstack-dev] [trove] guestagent config for overriding managers If you want to override the trove guestagent manage

Re: [openstack-dev] [QA][Infra] Mid-Cycle Meet-up Registration Closed

On Mon, Jun 09, 2014 at 02:08:58PM -0400, Matthew Treinish wrote: > On Thu, May 29, 2014 at 12:07:07PM -0400, Matthew Treinish wrote: > > > > Hi Everyone, > > > > So we'd like to announce to everyone that we're going to be doing a combined > > Infra and QA program mid-cycle meet-up. It will be t

Re: [openstack-dev] Using tmux instead of screen in devstack

One problem that comes to mind is that screen tries to reopen your terminal when you attach to existing session or run a new one. So if you have one user you log in to a test server (ubuntu? root?) and another user that runs screen session (stack), you won't be able to attach to the session unless

[openstack-dev] [QA] Meeting Thursday July 3rd at 17:00 UTC

Hi Everyone, Just a quick reminder that the weekly OpenStack QA team IRC meeting will be this Thursday, July 3rd at 17: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 add an

Re: [openstack-dev] [all] milestone-proposed is dead, long lives proposed/foo

Thanks for clarification. On Wed, Jul 2, 2014 at 6:59 PM, Jeremy Stanley wrote: > On 2014-07-02 16:14:52 +0400 (+0400), Yuriy Taraday wrote: > > Why do we need these short-lived 'proposed' branches in any form? > > Why can't we just use release branches for this and treat them as > > stable when

[openstack-dev] What's Up Doc? July 2, 2014

The doc team met this week for the APAC time zone. Minutes: http://eavesdrop.openstack.org/meetings/docteam/2014/docteam.2014-07-02-03.06.html Log: http://eavesdrop.openstack.org/meetings/docteam/2014/docteam.2014-07-02-03.06.log.html __In review and merged this past week__ The security guide has

Re: [openstack-dev] [third party] - minimum response time for 3rd party CI responses

On 30 June 2014 21:04, Kevin Benton wrote: > As a maintainer of a small CI system that tends to get backed up during > milestone rush hours, it would be nice if we were allowed up to 12 hours. > However, as a developer this seems like too long to have to wait for the > results of a patch. > Inter

Re: [openstack-dev] [nova] Two questions about 'backup' API

On Jun 26, 2014, at 6:58 PM, wu jiang wrote: > Hi Vish, thanks for your reply. > > About Q1, I mean that Nova doesn't have extra processions/works for > 'daily'/'weekly' than other backup_types like '123'/'test'. > The 'daily' & 'weekly' don't have unique places in the API than any other > el

[openstack-dev] [qa][nova] Please run 'check experimental' on changes to nova v3 tests in tempest

Due to the status of nova v3, to save time, running the tempest v3 tests has been moved out of the gate/check jobs to the experimental queue. So please run 'check experimental' on v3-related patches. -David ___ OpenStack-dev mailing list OpenStack-d

[openstack-dev] [all] oslo.i18n 0.1.0 released

The Oslo team is pleased to announce the first release of oslo.i18n, the library that replaces the gettextutils module from oslo-incubator. The new library has been uploaded to PyPI, and there is a changeset in the queue update the global requirements list and our package mirror: https://review.op

Re: [openstack-dev] [TripleO] Time to break backwards compatibility for *cloud-password file location?

> -Original Message- > From: Giulio Fidente [mailto:gfide...@redhat.com] > Sent: 01 July 2014 13:08 > Subject: Re: [openstack-dev] [TripleO] Time to break backwards > compatibility for *cloud-password file location? > > On 06/25/2014 11:25 AM, mar...@redhat.com wrote: > > On 25/06/14 10:52

Re: [openstack-dev] [third party] - minimum response time for 3rd party CI responses

On 2 July 2014 20:33, Luke Gorrie wrote: > I'd love to see links to such reviews, if anybody has some? (I've only > seen positive reviews and false-negative reviews from 3rd party CIs so far > in my limited experience.) > I didn't say what I meant: reviews where a 3rd party CI has genuinely obje

Re: [openstack-dev] [Neutron][LBaaS] Analyzing the critical path

Hi Sam, > Anything else? I assume you mean for Juno. Under “In addition”: * Contact current driver owners, to update to new driver interface (some things will break with the shim, e.g. when the drivers are reaching around the plugin to the neutron db.) Also let them know about the upcomi

Re: [openstack-dev] [OpenStack-Infra] Nomination for python-jenkins

Le 23/06/2014 10:42, Antoine Musso a écrit : > Hello, > > The python-jenkins module is a thin wrapper to interact with Jenkins. It > has been migrated from Launchpad to Stackforge a couple months ago to > attract more developers and easily upstream work down being done in over > OpenStack projects

[openstack-dev] [Neutron][LBaaS] Agenda for weekly IRC meeting

Hey LBaaS folks! Please send me any agenda items you would like discussed tomorrow so I can organize the meeting. And as usual, please update the weekly standup etherpad. Everything should be organized on the main wiki page now ==> https://wiki.openstack.org/wiki/Neutron/LBaaS :) Cheers, --Jor

Re: [openstack-dev] DVR and FWaaS integration

All, After talk to Carl and FWaaS team , Both sides suggested to call a meeting to discuss about this topic in deeper detail. I heard that Swami is traveling this week. So I guess the earliest time we can have a meeting is sometime next week. I will be out of town on monday, so any day after Monday

[openstack-dev] [blazar] py26 and py27 jobs failing

Blazar cores, Please review https://review.openstack.org/99389. We need this merged ASAP in order to get a +1 from Jenkins in our py26 and py27 jobs. Pecan new version returns a 204 instead 200 in one case (when the API returns and empty dictionary) and one test case is failing for this rea

Re: [openstack-dev] [blazar] py26 and py27 jobs failing

That's a pretty notable review to accommodate the pecan change. In the meantime, wouldn't something like this would get the py26 and py27 tests passing? index 9aced3f..4051fad 100644 --- a/climate/tests/api/test_root.py +++ b/climate/tests/api/test_root.py @@ -22,8 +22,7 @@ class TestRoot(api.API

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

July 4 is a holiday here in the US, and I think most of the core team and liaisons will be off. Our next meeting will be 11 July 2014. Thanks, Doug ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailm

Re: [openstack-dev] [heat] One more lifecycle plug point - in scaling groups

On 01/07/14 21:09, Mike Spreitzer wrote: Zane Bitter wrote on 07/01/2014 07:05:15 PM: > On 01/07/14 16:30, Mike Spreitzer wrote: > > Thinking about my favorite use case for lifecycle plug points for cloud > > providers (i.e., giving something a chance to make a holistic placement > > decisi

Re: [openstack-dev] [heat] health maintenance in autoscaling groups

On 02/07/14 02:41, Mike Spreitzer wrote: Zane Bitter wrote on 07/01/2014 06:58:47 PM: > On 01/07/14 15:47, Mike Spreitzer wrote: > > In AWS, an autoscaling group includes health maintenance functionality > > --- both an ability to detect basic forms of failures and an ability to > > react p

Re: [openstack-dev] [Neutron][LBaaS] Agenda for weekly IRC meeting

Hi, Please take the time to fill out the weekly standup info: https://etherpad.openstack.org/p/neutron-lbaas-weekly-standup Thanks, German From: Jorge Miramontes [mailto:jorge.miramon...@rackspace.com] Sent: Wednesday, July 02, 2014 1:20 PM To: OpenStack Development Mailing List (not for usage

[openstack-dev] [all] oslo.vmware 0.4.0 released

This is an announcement that oslo.vmware 0.4.0 has been released for the Juno cycle. It is available on PyPI and shoudl show up in our mirror shortly. The changes since the previous release include: $ git log --abbrev-commit --pretty=oneline --no-merges 0.3..0.4.0 df06729 Sync excutils fro

Re: [openstack-dev] [Neutron][LBaaS] Agenda for weekly IRC meeting

Some things I can think of for the agenda: New API - Are shim layers really needed for Juno? - If the old API and new API will coexist independently, why is a shim layer needed? - Has the caveat that the pools resource can exist independently in both APIs. This can be acco

Re: [openstack-dev] [TripleO] Time to break backwards compatibility for *cloud-password file location?

On Thu, Jul 3, 2014 at 5:33 AM, Sullivan, Jon Paul wrote: > > -Original Message- > > From: Giulio Fidente [mailto:gfide...@redhat.com] > > Sent: 01 July 2014 13:08 > > Subject: Re: [openstack-dev] [TripleO] Time to break backwards > > compatibility for *cloud-password file location? > > >

[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. DVR is our priority. I have had some encouraging success this week deploying my own two-node devstack with distributed routers. I would like to discuss that

[openstack-dev] [Glance] Anyone using owner_is_tenant = False with image members?

Hi folks, Background: Among all services, I think glance is unique in only having a single 'owner' field for each image. Most other services include a 'user_id' and a 'tenant_id' for things that are scoped this way. Glance provides a way to change this behavior by setting "owner_is_tenant" to fal

Re: [openstack-dev] Using tmux instead of screen in devstack

On 2014-07-02 2:10 PM, Yuriy Taraday wrote: One problem that comes to mind is that screen tries to reopen your terminal when you attach to existing session or run a new one. So if you have one user you log in to a test server (ubuntu? root?) and another user that runs screen session (stack), you

Re: [openstack-dev] [Nova} NFV patches

1. [NFV] is a tag. 2. This would appear to be a set of 'review me' mails to the mailing list, which I believe is frowned upon. 3. garyk's stuff is only questionably [NFV], I would argue, though all worthwhile patches. (That's a completely subjective judgement, so take it as you will.) Might be a b

Re: [openstack-dev] [third party] - minimum response time for 3rd party CI responses

On Thu, Jul 3, 2014 at 4:33 AM, Luke Gorrie wrote: > > On 30 June 2014 21:04, Kevin Benton wrote: >> >> As a maintainer of a small CI system that tends to get backed up during >> milestone rush hours, it would be nice if we were allowed up to 12 hours. >> However, as a developer this seems like t

Re: [openstack-dev] [all] milestone-proposed is dead, long lives proposed/foo

On 2014-07-02 22:19:29 +0400 (+0400), Yuriy Taraday wrote: [...] > It looks like mirrors will have to bear having a number of dead branches in > them - one for each release. A release manager will delete proposed/juno when stable/juno is branched from it, and branch deletions properly propagate to

[openstack-dev] [ceilometer] Do we have IRC meeting this week?

Looks like many are in Paris midcycle meet-up. Do we have the weekly IRC meeting today? -Lianhao ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [oslo] Openstack and SQLAlchemy

I've just added a new section to this wiki, "MySQLdb + eventlet = sad", summarizing some discussions I've had in the past couple of days about the ongoing issue that MySQLdb and eventlet were not meant to be used together. This is a big one to solve as well (though I think it's pretty easy to so

[openstack-dev] [barbican] Consumer Registration API

I was looking through some Keystone docs and noticed that for version 3.0 of their API [1] Keystone merged the Service and Admin API into a single core API. I haven’t gone digging through mail archives, but I imagine they had a pretty good reason to do that. Adam, I know you’ve already implemente

Re: [openstack-dev] DVR and FWaaS integration

Hello, It’s hard to integrate DVR and FWaaS. My proposal is to split the FWaaS into two parts: one part is for east-west FWaaS, this part could be done on DVR side, and make it become distributed manner. The other part is for north-south part, this part could be done on Network Node side, that

[openstack-dev] [neutron] Flavor framework: Conclusion

We're coming down to the wire here with regards to Neutron BPs in Juno, and I wanted to bring up the topic of the flavor framework BP. This is a critical BP for things like LBaaS, FWaaS, etc. We need this work to land in Juno, as these other work items are dependent on it. There are still two propo

[openstack-dev] [Neutron] [ML2] [L2GW] multiple l2gw project in ml2 team?

I read the ml2 tracking reviews, find two similar spec for l2 gateway: 1) GW API: L2 bridging API - Piece 1: Basic use cases https://review.openstack.org/#/c/93613/ 2) API Extension for l2-gateway https://review.openstack.org/#/c/100278/ also neutron external port spec has some relationship htt

Re: [openstack-dev] [heat] health maintenance in autoscaling groups

On Wed, Jul 02, 2014 at 11:02:36AM +0100, Steven Hardy wrote: > On Wed, Jul 02, 2014 at 03:02:14PM +0800, Qiming Teng wrote: > > Just some random thoughts below ... > > > > On Tue, Jul 01, 2014 at 03:47:03PM -0400, Mike Spreitzer wrote: > > > In AWS, an autoscaling group includes health maintenanc

Re: [openstack-dev] Using tmux instead of screen in devstack

I am sure there are many developers learning screen in order to work with devstack and I don't want to rob them off of their efforts. However, there are developers (like me :) ) who use tmux everyday. I had used screen for some duration and moved to tmux as it provided some features that helped me

Re: [openstack-dev] Using tmux instead of screen in devstack

I'm not going to get into a screen vs tmux debate, we removed tmux support two years ago and changing that now is going to be a high bar to get over...but it seems some expectations should be set here. On Wed, Jul 2, 2014 at 11:05 PM, Anant Patil wrote: [...] > I understand that the changes wil

Re: [openstack-dev] [heat] health maintenance in autoscaling groups

On Wed, Jul 02, 2014 at 12:29:31PM -0400, Mike Spreitzer wrote: > Qiming Teng wrote on 07/02/2014 03:02:14 AM: > > > Just some random thoughts below ... > > > > On Tue, Jul 01, 2014 at 03:47:03PM -0400, Mike Spreitzer wrote: > > > ... > > > I have not found design discussion of this; have I miss

Re: [openstack-dev] Using tmux instead of screen in devstack

On Thu, Jul 3, 2014 at 12:55 AM, Anita Kuno wrote: > On 07/01/2014 08:52 AM, CARVER, PAUL wrote: > > Anant Patil wrote: > >> I use tmux (an alternative to screen) a lot and I believe lot of other > developers use it. > >> I have been using devstack for some time now and would like to add the > op

  1   2   >