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

Mine wasn't really a serious suggestion, Neutron's controlling logic is already bloated as it is, and my personal opinion would be in favor of a leaner Neutron Server rather than a more complex one; adding more controller-like logic to it certainly goes against that direction :) Having said that a

Re: [openstack-dev] [nova] locked instances and snaphot

On Jun 16, 2014, at 13:56, Michael Still wrote: > It is certainly my belief that the lock functionality for instances is > about avoiding accidental changes to the instance itself, not the > contents of the instance. I personally think that snapshots aren't a > change to the instance and therefo

Re: [openstack-dev] [Nova][QA] Disabling the v3 API tests in the gate

On Thu, Jun 12, 2014 at 12:10:23PM -0400, Sean Dague wrote: > On 06/12/2014 12:02 PM, Matt Riedemann wrote: > > > > > > On 6/12/2014 10:51 AM, Matthew Treinish wrote: > >> On Fri, Jun 13, 2014 at 12:41:19AM +0930, Christopher Yeoh wrote: > >>> On Fri, Jun 13, 2014 at 12:25 AM, Dan Smith wrote: >

Re: [openstack-dev] [nova] Reducing quota below utilisation

Just On 06/17/2014 08:18 PM, Tim Bell wrote: We have some projects which are dynamically creating VMs up to their quota. Under some circumstances, as cloud administrators, we would like these projects to shrink and make room for other higher priority work. We had investigated setting the projec

Re: [openstack-dev] [Murano] Package composition

Hi Steve, It is very simple: one application per package. If something can be deployed on its own (can be a top level component in environment and must be visible in app catalog) then it is application and deserves a separate package. The composition (in your example distribution of hosts between

Re: [openstack-dev] [TC] [Murano] Follow up on cross-project session

On Wed, Jun 11, 2014 at 8:07 PM, Thierry Carrez wrote: > I had a question about Murano's remaining feature set though. If the > application catalog lives in Glance and the application deployment lives > in Heat, what functionality does Murano end up providing ? Could you > elaborate on the "compos

[openstack-dev] [python-openstacksdk] Meeting Minutes for Tuesday June 17

Meeting ended Tue Jun 17 19:59:32 2014 UTC. Minutes: http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-06-17-19.00.html Minutes (text): http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-06-17-19.00.txt Log: http://

Re: [openstack-dev] [nova] locked instances and snaphot

On 06/17/2014 03:03 PM, melanie witt wrote: On Jun 16, 2014, at 13:56, Michael Still wrote: It is certainly my belief that the lock functionality for instances is about avoiding accidental changes to the instance itself, not the contents of the instance. I personally think that snapshots aren

[openstack-dev] [oslo][all] Liaisons: App agnostic logging parameters

Hi Oslo liaisons (and anyone else reading this because of the [all] tag), For the oslo.log graduation, we're trying to make the default logging parameters generic enough to be useful to all projects, instead of the generally Nova-centric ones we have today. The reason I'm sending this is to bring

Re: [openstack-dev] OpenStack Designate DNSaaS

Unfortunately #1 is not a real option - designate needs the storage layer to operate. I would guess #2 or #3 would be the more feasible options. Graham "MIDGLEY, BRAD" wrote: PK, I’d agree with pursuing #1 or with a simple reference implementation like minidns if ripping it out is disrup

Re: [openstack-dev] [metrics] How to group activity in git/gerrit repositories

On 16/06/14 21:25, Ilya Shakhat wrote: Let me explain how Stackalytics grouping works. Thanks for the clarification here. Stefano, given that it's simple to group projects, a Most of groups are created from the official programs .yaml. Every program turns into item in t

Re: [openstack-dev] [metrics] How to group activity in git/gerrit repositories

On 17/06/14 23:53, Daniel Izquierdo wrote: On 16/06/14 21:25, Ilya Shakhat wrote: Let me explain how Stackalytics grouping works. Thanks for the clarification here. Stefano, given that it's simple to group projects, a Sorry about this incomplete email u_u. I was trying to wrap up ideas but

Re: [openstack-dev] [taskflow] Recommendations for the granularity of tasks and their "stickiness" to workers

Thanks to Joshua and Sandy for the clarifications on the finer points of taskflow features and usage. I'll consume the docco linked, and will be back to annoy ye with further questions :) Cheers, Eoghan > Back on the distributed subject (since this deserves a different email), > > In the newe

Re: [openstack-dev] [oslo] versioning and releases

On 11 June 2014 04:24, Doug Hellmann wrote: ... > Incubated libraries have been released at the end of a release cycle, > as with the rest of the integrated packages. Adopted libraries have > historically been released "as needed" during their development. We > would like to synchronize these so t

Re: [openstack-dev] [oslo] versioning and releases

On Tue, Jun 17, 2014 at 6:42 PM, Robert Collins wrote: > On 11 June 2014 04:24, Doug Hellmann wrote: > ... >> Incubated libraries have been released at the end of a release cycle, >> as with the rest of the integrated packages. Adopted libraries have >> historically been released "as needed" duri

Re: [openstack-dev] [taskflow] Recommendations for the granularity of tasks and their "stickiness" to workers

Cool, feel free to jump on IRC[1] if u need in-person details/questions or other (consultation is free, haha). [1] irc://chat.freenode.net/openstack-state-management -Josh -Original Message- From: Eoghan Glynn Reply-To: "OpenStack Development Mailing List (not for usage questions)" Dat

Re: [openstack-dev] [nova] locked instances and snaphot

Hi there, Le 2014-06-16 15:28, melanie witt a écrit : Hi all, [...] During the patch review, a reviewer raised a concern about the purpose of instance locking and whether prevention of snapshot while an instance is locked is appropriate. From what we understand, instance lock is meant to pre

Re: [openstack-dev] [metrics] How to group activity in git/gerrit repositories

On 06/16/2014 12:25 PM, Ilya Shakhat wrote: > Most of groups are created from the official programs > .yaml. Every program turns into item in the module > list (colored in violet), for example 'Nova Compute' is a group > containing 'nova', 'python-novaclient' and 'nova-specs'.

Re: [openstack-dev] [metrics] How to group activity in git/gerrit repositories

On 2014-06-17 17:32:25 -0700 (-0700), Stefano Maffulli wrote: [...] > On the infra program, how do you separate OpenStack-related > contributions to a repository like - repo: openstack-infra/gerrit, which > is a fork of upstream gerrit, from the commits of upstream, non > openstack people? In the p

Re: [openstack-dev] [glance] Unifying configuration file

On 17/06/14 23:43, Julien Danjou wrote: On Tue, Jun 17 2014, Arnaud Legendre wrote: @ZhiYan: I don't like the idea of removing the sample configuration file(s) from the git repository. Many people do not want to have to checkout the entire codebase and tox every time they have to verify a varia

Re: [openstack-dev] [nova][qa] Do all turbo-hipster jobs fail in stable/havana?

On 6/18/14 12:52 AM, Matt Riedemann wrote: On 6/16/2014 11:58 PM, Joshua Hesketh wrote: Hi there, Very sorry for the mishap. I manually enqueued our zuul to run tests on changes that turbo-hipster had recently missed and did not pay attention to the branch they were for. Turbo-Hipster doesn'

[openstack-dev] Release notes as we go?

Hi, Remembering the last minute rush to get release notes ready for Icehouse, I was very pleased to see that the Juno release notes page has been already started! https://wiki.openstack.org/wiki/ReleaseNotes/Juno Perhaps if people are working on release-note worthy things, they could add a

[openstack-dev] DVR IRC Meeting for June 18th 2014. - Cancelled.

Hi Folks, The DVR IRC Meeting for June 18th 2014 will be cancelled. I will be travelling on these dates so will not be able to run the meeting. Some of our team members are also busy during this time slot. So I will be cancelling this meeting. The reviews are still in progress. Thanks Swaminath

Re: [openstack-dev] [nova] locked instances and snaphot

On Wed, Jun 18, 2014 at 10:21 AM, Ahmed RAHAL wrote: > Le 2014-06-16 15:28, melanie witt a écrit : > The more I think about it, the more I get to think that locking is just > there to avoid mistakes, not voluntary misbehaviour. I agree. You have a really important instance, so you lock it to avo

Re: [openstack-dev] [Fuel] Bug squashing day on June, 17

Thanks for participation, folks. Current count: New - 12 Incomplete - 30 Confirmed / Triaged / in progress for 5.1 - 368 I've not logged how many bugs we had, but calculated that 26 bugs were filed over last 24 hours. Overall, seems to be we did a good job in triaging, but results for fixing bugs

[openstack-dev] [Cinder][Driver] Delete snapshot

Hi Stackers, I have been implementing a Cinder driver for our storage solution & facing issues with below scenario. Scenario - When a user/admin tries to delete a snapshot that has associated clone(s), an error message/log should be shown to the user stating that '*There are clones associated to

Re: [openstack-dev] [Mistral] Cleaning up configuration settings

Ooh, alright :) It passed by me why I was off. Renat Akhmerov @ Mirantis Inc. On 18 Jun 2014, at 01:20, W Chan wrote: > I figured. I implemented it in https://review.openstack.org/#/c/97684/. > > > On Mon, Jun 16, 2014 at 9:35 PM, Renat Akhmerov > wrote: > I don’t think we have them. You

Re: [openstack-dev] [Fuel] Bug squashing day on June, 17

Fuelers, please pay attention to stalled in progress bugs too - those which are In progress for more than a week. See [1]. [1] https://bugs.launchpad.net/fuel/+bugs?field.searchtext=&orderby=date_last_updated&search=Search&field.status%3Alist=INPROGRESS&assignee_option=any&field.assignee=&field.b

Re: [openstack-dev] [Mistral] Refine engine <-> executor protocol

Hi Winson, Sorry, I haven’t responded so far for I was on vacation. So getting back to you now.. It’s my fault that the notes in the BP are not fairly clear. 1. By “worker parallelism” we meant that one worker (which is called “executor" now) can poll and handle more than one task from the tas

[openstack-dev] DevStack hacks requirements.txt et al

I have noticed that lately DevStack has been hacking requirements.txt in most projects and test-requirements.txt in many. Why is this being done? Thanks, Mike___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cg

Re: [openstack-dev] DevStack hacks requirements.txt et al

On Tue, Jun 17, 2014 at 10:33 PM, Mike Spreitzer wrote: > I have noticed that lately DevStack has been hacking requirements.txt in > most projects and test-requirements.txt in many. Why is this being done? > > Thanks, > Mike > ___ > OpenStack-dev mailin

Re: [openstack-dev] [glance] Unifying configuration file

Hey On Tue, 2014-06-17 at 17:43 +0200, Julien Danjou wrote: > On Tue, Jun 17 2014, Arnaud Legendre wrote: > > > @ZhiYan: I don't like the idea of removing the sample configuration file(s) > > from the git repository. Many people do not want to have to checkout the > > entire codebase and tox ever

Re: [openstack-dev] [Mistral] Refine engine <-> executor protocol

On 13 Jun 2014, at 07:03, W Chan wrote: > Design proposal for blueprint > https://blueprints.launchpad.net/mistral/+spec/mistral-engine-executor-protocol > Rename Executor to Worker. I’d be ok with Worker but would prefer ActionRunner since it reflects the purpose a little better although being

Re: [openstack-dev] [Mistral] Integration tests discussion

Thanks Timur, that’s a good doc. Anastasia and Sergey were supposed to start working on a proposal devoted to our approaches to integration testing. I hope we’ll see them soon. Renat Akhmerov @ Mirantis Inc. On 11 Jun 2014, at 13:55, Timur Nurlygayanov wrote: > Hi team, > > Tomorrow we dis

[openstack-dev] [Fuel] Support for plugins in fuel client

Hi folks, I am wondering what our story/vision for plugins in fuel client [1]? We can benefit from using cliff [2] as framework for fuel cli, apart from common code for building cli applications on top of argparse, it provides nice feature that allows to dynamicly add actions by means of entry po

<    1   2