Re: [openstack-dev] [nova] Distributed locking

On 06/13/2014 05:01 AM, Julien Danjou wrote: On Thu, Jun 12 2014, Jay Pipes wrote: This is news to me. When was this decided and where can I read about it? Originally https://wiki.openstack.org/wiki/Oslo/blueprints/service-sync has been proposed, presented and accepted back at the Icehouse su

[openstack-dev] [Neutron][ServiceVM] servicevm IRC meeting reminder (June 17 Tuesday 5:00(AM)UTC-)

Hi. This is a reminder mail for the servicevm IRC meeting June 17, 2014 Tuesdays 5:00(AM)UTC- #openstack-meeting on freenode https://wiki.openstack.org/wiki/Meetings/ServiceVM Maybe some won't make it because of mid-cycle meet up, though. agenda: (feel free to add your items) * announcement * act

[openstack-dev] [Neutron][LBaaS] Layer 7 switching RST document on Gerrit

Hi Please review. https://review.openstack.org/#/c/99709/ Thanks Avishay ___ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Starting contributing to project

Hi, I would suggest that you start from the master branch. Good luck. Thanks HGary On 6/15/14, 11:10 PM, "Sławek Kapłoński" wrote: >Hello, > >I want to start contributing to neutron project. I found bug which I >want to try fix: >https://urldefense.proofpoint.com/v1/url?u=https://bugs.launchpad

[openstack-dev] [sahara] 2014.1.1 (stable/icehouse) released

Hey folks, I'm glad to announce the release of the 2014.1.1 (stable/icehouse). You can find more info at launchpad page: https://launchpad.net/sahara/+milestone/2014.1.1 The next stable/icehouse release is planned for Aug 7. Thanks. -- Sincerely yours, Sergey Lukjanov Sahara Technical Lead (O

Re: [openstack-dev] Fwd: [Eventletdev] Eventlet 0.15 pre-release testers needed

Hello Folks! AFAIK, new eventlet version have limited PY3 support. So, unfortunately, it is not ready for work with python 3 in production. See issue [1] on github. Anyway, at least we will be in able to install eventlet in PY3 environment and (I hope) to test some openstack features (or mock even

Re: [openstack-dev] Gate proposal - drop Postgresql configurations in the gate

Robert Collins wrote: > [...] > C - If we can't make it harder to get races in, perhaps we can make it > easier to get races out. We have pretty solid emergent statistics from > every gate job that is run as check. What if set a policy that when a > gate queue gets a race: > - put a zuul stop all

Re: [openstack-dev] [Fuel] Using saltstack as orchestrator for fuel

Guys, First of all we need to agree about what orchestration is. In terms of Fuel orchestration is task management (or scheduling) + task running. In other words an orchestrator needs to be able to get data (yaml, json, etc.) and to decide what to do, when and where and then do that. For task mana

Re: [openstack-dev] [Fuel] Symlinks to new stuff for OpenStack Patching

Hi Igor, The repo directory its is too large to fit in a docker container and work reliably. It is just a symlink inside the repo storage container from host:/var/www/nailgun to repo-container:/repo. This /repo folder is shared out to containers, such as nginx, and then symlinks are created for ea

[openstack-dev] An alternative approach to enforcing "expected election behaviour"

TL;DR: how about we adopt a "soft enforcement" model, relying on sound judgement and good faith within the community? Hi Folks, I'm concerned that the "expected election behaviour" review[1] is not converging on the optimal approach, partially due to the initial concentration on the pro

Re: [openstack-dev] [marconi] replicate messages among servers

Hi If you are using the mongodb, then you can leverage the replication sets, for example ,the uri for mongodb uri = mongodb://mydb1,mydb2,mydb3:27017/?replicaSet=catalog... for some more, you can refer to http://docs.openstack.org/developer/marconi/installing.html On Sun, Jun 15,

Re: [openstack-dev] [Neutron][L3] BGP Dynamic Routing Proposal

Hi all, We've just released our implementation of BGP VPN extensions (called 'BaGPipe'), under a opensource license : https://github.com/Orange-OpenSource/bagpipe-bgp It reuses some code from ExaBGP, but with a dedicated engine for VPN instance creation through a rest API, and a modular archite

Re: [openstack-dev] [Fuel] Symlinks to new stuff for OpenStack Patching

Hi, In case of OpenStack patching you don't need to create any symlinks and mount new directories, you can just create new subdirectory in /var/www/nailgun with specific version of openstack, like /var/www/nailgun/ 5.0.1. And then use it as a repository path for new OpenStack releases. On Mon, J

Re: [openstack-dev] [marconi] replicate messages among servers

On 16/06/14 17:06 +0800, wpf wrote: Hi    If you are using the mongodb, then you can leverage the replication sets,  for example ,the uri for mongodb    uri = mongodb://mydb1,mydb2,mydb3:27017/?replicaSet=catalog...   for some more, you can refer to http://docs.openstack.org/developer/marc

Re: [openstack-dev] Rethink how we manage projects? (was Gate proposal - drop Postgresql configurations in the gate)

David Kranz wrote: > [...] > There is a different way to do this. We could adopt the same methodology > we have now around gating, but applied to each project on its own > branch. These project branches would be integrated into master at some > frequency or when some new feature in project X is nee

Re: [openstack-dev] [nova] Do any hyperviors allow disk reduction as part of resize ?

Beyond what is and isn’t technically possible at the file system level there is always the problem that the user may have more data than can fit into the reduced disk. I don’t want to take away useful functionality from folks if there are cases where it already works – mostly I just want to imp

Re: [openstack-dev] [nova][ironic] what to do with unit test failures from ironic api contract

From: David Shrewsbury [mailto:[email protected]] Sent: 14 June 2014 02:10 To: OpenStack Development Mailing List (not for usage questions) Cc: Shrewsbury, David; Van Der Veen, Devananda Subject: Re: [openstack-dev] [nova][ironic] what to do with unit test failures from ironic api contrac

[openstack-dev] [FUEL] Authentication in FUEL meeting notes

16.07.2014 meeting results: Participants: L. Oles N. Markov V. Kramskikh A. Kislitsky Acceptance points of authentication in FUEL: 1. Each project (nailgun, CLI, UI, OSTF) should authenticate in Keystone and use received token in other services requests 2. Authentication can be

Re: [openstack-dev] [Fuel] Symlinks to new stuff for OpenStack Patching

Hello, Thanks for input, guys. So we need to prepare infrastructure for that. - Igor On Mon, Jun 16, 2014 at 12:23 PM, Evgeniy L wrote: > Hi, > > In case of OpenStack patching you don't need to create any symlinks and > mount new directories, you can just create new subdirectory in > /var/www

Re: [openstack-dev] An alternative approach to enforcing "expected election behaviour"

On Mon, Jun 16, 2014 at 05:04:51AM -0400, Eoghan Glynn wrote: > How about we rely instead on the values and attributes that > actually make our community strong? > > Specifically: maturity, honesty, and a self-correcting nature. > > How about we simply require that each candidate for a TC or PTL

Re: [openstack-dev] Gate proposal - drop Postgresql configurations in the gate

On 06/16/2014 04:33 AM, Thierry Carrez wrote: > Robert Collins wrote: >> [...] >> C - If we can't make it harder to get races in, perhaps we can make it >> easier to get races out. We have pretty solid emergent statistics from >> every gate job that is run as check. What if set a policy that when a

[openstack-dev] [Fuel] ML2 support in Fuel deployment risks

Fuelers, Andrew, I've talked to Sergey V. today about ML2 support in Fuel. Our current approach [1] is to port upstream puppet module for Neutron which has support of ML2, however our Neutron module is significantly diverged from upstream one (at least for Neutron HA deployment capabilities), as fa

Re: [openstack-dev] Fwd: Fwd: Debian people don't like bash8 as a project name (Bug#748383: ITP: bash8 -- bash script style guide checker)

Sean Dague writes: > bashate ftw. +1 to bashate Chmouel ___ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Tuskar-UI] Two new tests in jenkins

Hi all, Just some info, recently two new test jobs have been added to jenkins for tuskar-ui: - selenium for running qunit tests (javascript unit tests) - jshint for javascript linting The jobs are currently non-voting, I'll change them to voting if they seem to work fine. -- Kind Regards, Pét

Re: [openstack-dev] [Neutron] REST API - entity level validation

Salvatore Will Neutron is going to follow Nova? https://blueprints.launchpad.net/nova/+spec/nova-api-validation-fw Avishay From: Salvatore Orlando [mailto:[email protected]] Sent: Monday, June 16, 2014 12:36 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [opens

Re: [openstack-dev] [Nova] VMware ESX Driver Deprecation

+1 to Option #2. -- dims On Sun, Jun 15, 2014 at 11:15 AM, Gary Kotton wrote: > Hi, > In the Icehouse cycle it was decided to deprecate the VMware ESX driver. The > motivation for the decision was: > > The driver is not validated by Minesweeper > It is not clear if there are actually any users o

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

On 06/13/2014 02:06 PM, Ihar Hrachyshka wrote: On 10/06/14 15:40, Alexei Kornienko wrote: On 06/10/2014 03:59 PM, Gordon Sim wrote: >>> I think there could be a lot of work required to significantly improve that driver, and I wonder if that would be better spent on e.g. the AMQP 1.0 driver whi

[openstack-dev] revert hacking to 0.8 series

Hacking 0.9 series was released pretty late for Juno. The entire check queue was flooded this morning with requirements proposals failing pep8 because of it (so at 6am EST we were waiting 1.5 hrs for a check node). The previous soft policy with pep8 updates was that we set a pep8 version basically

[openstack-dev] [mistral] Weekly community meeting - 06/16/2014

Hi, This is a reminder about another community IRC meeting at #openstack-meeting today at 16.00 UTC. The agenda is usual: Review action items Current status (quickly by team members) Further plans Open discussion Looking forward to see you there. [0] https://wiki.openstack.org/wiki/Meetings/Mi

Re: [openstack-dev] Need help on developing Neutron application to receive messages from Open Day Light

Hi, I am new to both open stack and open daylight. I have to write an application / plugin to receive messages >From open daylight neutron interface, can you please provide a reference or >an example of how to go about it ? Many thanks, Venkatesh The information contained in this electronic

Re: [openstack-dev] [OpenStack-Dev][Cinder] Review days? (open to ANYBODY and EVERYBODY)

+1 Andrew Kerr On 6/13/14, 10:30 AM, "Duncan Thomas" wrote: >Same as Jay, for much the same reasons. Having a fixed calendar time >makes it easy for me to put up a 'do not disturb' sign. > >On 13 June 2014 05:10, Jay Bryant wrote: >> John, >> >> +2 >> >> I am guilty of falling behind on revie

Re: [openstack-dev] [Ceilometer][Horizon] Exposing and showing associated resource_id within alarms/combined alarms

> Hello guys, > > I was taking a look at the proposed alarm-page designs [1] for the bp: > https://blueprints.launchpad.net/horizon/+spec/ceilometer-alarm-management-page > and I saw that the alarms table has a column named “Resource Name”. The > intention of that column is to show the resources

Re: [openstack-dev] no tap interface on compute node

On Mon, Jun 16, 2014 at 11:31:50AM +0530, abhishek jain wrote: > Hi > > I'm not able to get tap interface up on compute node when I boot VM > from controller node onto compute node. Please help regarding this. For such usage questions, please post (with more verbose details including Neutron inv

Re: [openstack-dev] no tap interface on compute node

Hi I posted it on ask.openstack.org but I got no response. On Mon, Jun 16, 2014 at 6:41 PM, Kashyap Chamarthy wrote: > On Mon, Jun 16, 2014 at 11:31:50AM +0530, abhishek jain wrote: > > Hi > > > > I'm not able to get tap interface up on compute node when I boot VM > > from controller node ont

[openstack-dev] [oslo][messaging] messaging vs. messagingv2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi all, I'm currently pushing Neutron to oslo.messaging, and while at it, a question popped up. So in oslo-rpc, we have the following notification drivers available: neutron.openstack.common.notifier.log_notifier neutron.openstack.common.notifier.n

Re: [openstack-dev] [Nova] Nominating Ken'ichi Ohmichi for nova-core

+1 On 06/13/2014 06:40 PM, Michael Still wrote: Greetings, I would like to nominate Ken'ichi Ohmichi for the nova-core team. Ken'ichi has been involved with nova for a long time now. His reviews on API changes are excellent, and he's been part of the team that has driven the new API work we'v

Re: [openstack-dev] revert hacking to 0.8 series

Sean Dague wrote: > Hacking 0.9 series was released pretty late for Juno. The entire check > queue was flooded this morning with requirements proposals failing pep8 > because of it (so at 6am EST we were waiting 1.5 hrs for a check node). > > The previous soft policy with pep8 updates was that we

Re: [openstack-dev] An alternative approach to enforcing "expected election behaviour"

On Mon, 2014-06-16 at 10:56 +0100, Daniel P. Berrange wrote: > On Mon, Jun 16, 2014 at 05:04:51AM -0400, Eoghan Glynn wrote: > > How about we rely instead on the values and attributes that > > actually make our community strong? > > > > Specifically: maturity, honesty, and a self-correcting nature

Re: [openstack-dev] [neutron] [third-party] Current status of Neutron 3rd Party CI and how to move forward

I will probably be unable, as usual, to attend today's CI meeting (falls right around my dinner time). I think it's a good idea to starting keeping track of the status of the various CI systems, but I feel the etherpad will not work very well in the long term. However, it would be great if we coul

Re: [openstack-dev] [Horizon] Specs repo

On 06/11/2014 05:22 PM, Jason Rist wrote: > On Wed 11 Jun 2014 06:54:53 AM MDT, Ana Krivokapic wrote: >> Hi Horizoners, >> >> A lot of other projects have already adopted and started using a specs >> repo. Do we want to have one for Horizon? >> > I'm still not quite clear how this works, but I'm o

Re: [openstack-dev] [Neutron] Implementing new LBaaS API

On Mon, Jun 16, 2014 at 2:27 AM, Eugene Nikanorov wrote: > Salvatore, > >> Also - since it seems to me that there is also consensus regarding having >> load balancing move away into a separate project > To me it seems that there was no such a consensus; core team members were > advocating keeping

Re: [openstack-dev] Need help on developing Neutron application to receive messages from Open Day Light

On Mon, Jun 16, 2014 at 7:17 AM, wrote: > > > Hi, > > > > I am new to both open stack and open daylight. I have to write an > application / plugin to receive messages > > From open daylight neutron interface, can you please provide a reference or > an example of how to go about it ? > Hi Venkate

Re: [openstack-dev] [neutron] [third-party] Current status of Neutron 3rd Party CI and how to move forward

On Mon, Jun 16, 2014 at 8:52 AM, Salvatore Orlando wrote: > I will probably be unable, as usual, to attend today's CI meeting (falls > right around my dinner time). > I think it's a good idea to starting keeping track of the status of the > various CI systems, but I feel the etherpad will not work

Re: [openstack-dev] Gate proposal - drop Postgresql configurations in the gate

On Fri, 13 Jun 2014, Sean Dague wrote: So if we can't evolve the system back towards health, we need to just cut a bunch of stuff off until we can. +1 This is kind of the crux of the biscuit. As things stand there's so much noise that it's far too easy to think and act like it is somebody else

Re: [openstack-dev] Rethink how we manage projects? (was Gate proposal - drop Postgresql configurations in the gate)

On 06/16/2014 05:33 AM, Thierry Carrez wrote: David Kranz wrote: [...] There is a different way to do this. We could adopt the same methodology we have now around gating, but applied to each project on its own branch. These project branches would be integrated into master at some frequency or wh

Re: [openstack-dev] [neutron] [third-party] Current status of Neutron 3rd Party CI and how to move forward

On 16 June 2014 15:58, Kyle Mestery wrote: > On Mon, Jun 16, 2014 at 8:52 AM, Salvatore Orlando > wrote: > > I will probably be unable, as usual, to attend today's CI meeting (falls > > right around my dinner time). > > I think it's a good idea to starting keeping track of the status of the > >

Re: [openstack-dev] [neutron] [third-party] Current status of Neutron 3rd Party CI and how to move forward

On Mon, Jun 16, 2014 at 9:11 AM, Salvatore Orlando wrote: > > > > On 16 June 2014 15:58, Kyle Mestery wrote: >> >> On Mon, Jun 16, 2014 at 8:52 AM, Salvatore Orlando >> wrote: >> > I will probably be unable, as usual, to attend today's CI meeting (falls >> > right around my dinner time). >> > I

Re: [openstack-dev] [neutron] [third-party] Current status of Neutron 3rd Party CI and how to move forward

> > > However, it would be great if we could start devising a solution for > having > > "health" reports from the various CI systems. > > This report should report the following kind of information: > > - timestamp of last run > > - timestamp of last vote (a system might start job which then get ab

Re: [openstack-dev] An alternative approach to enforcing "expected election behaviour"

On Mon, Jun 16, 2014 at 9:41 AM, Mark McLoughlin wrote: > On Mon, 2014-06-16 at 10:56 +0100, Daniel P. Berrange wrote: >> On Mon, Jun 16, 2014 at 05:04:51AM -0400, Eoghan Glynn wrote: >> > How about we rely instead on the values and attributes that >> > actually make our community strong? >> > >>

Re: [openstack-dev] NFV in OpenStack use cases and context

Hi Sylvain, The Smart Scheduler work should work along withGantt easily, as it is just another scheduler driver, instead of using the Filters, it will have a separate mechanism of solving the placement problem all at once. So just like how it currently works along with Nova scheduler, it should e

Re: [openstack-dev] An alternative approach to enforcing "expected election behaviour"

> On Mon, 2014-06-16 at 10:56 +0100, Daniel P. Berrange wrote: > > On Mon, Jun 16, 2014 at 05:04:51AM -0400, Eoghan Glynn wrote: > > > How about we rely instead on the values and attributes that > > > actually make our community strong? > > > > > > Specifically: maturity, honesty, and a self-cor

[openstack-dev] [qa] Clarification of policy for qa-specs around adding new tests

I have been reviewing some of these specs and sense a lack of clarity around what is expected. In the pre-qa-specs world we did not want tempest blueprints to be used by projects to track their tempest test submissions because the core review team did not want to have to spend a lot of time dea

Re: [openstack-dev] [Horizon] [UX] Design for Alarming and Alarm Management

Apologies for the top-posting, but just wanted to call out some potential confusion that arose on the #os-ceilometer channel earlier today. TL;DR: the UI shouldn't assume a 1:1 mapping between alarms and resources, since this mapping does not exist in general Background: See ML post[1] D

Re: [openstack-dev] [qa] Clarification of policy for qa-specs around adding new tests

On Mon, Jun 16, 2014 at 10:46:51AM -0400, David Kranz wrote: > I have been reviewing some of these specs and sense a lack of clarity around > what is expected. In the pre-qa-specs world we did not want tempest > blueprints to be used by projects to track their tempest test submissions > because the

Re: [openstack-dev] [Nova] Nominating Ken'ichi Ohmichi for nova-core

+1 On Monday, June 16, 2014, Andrew Laski wrote: > +1 > > On 06/13/2014 06:40 PM, Michael Still wrote: > >> Greetings, >> >> I would like to nominate Ken'ichi Ohmichi for the nova-core team. >> >> Ken'ichi has been involved with nova for a long time now. His reviews >> on API changes are excell

Re: [openstack-dev] [Neutron][LBaaS] Consolidated metrics proposal

Hi Jorge, thanks for your reply! You are right about summarizing too much. The idea is to identify which kinds of data could be retrieved in a summarized way without losing detail (i.e.: uptime can be better described with start-end timestamps than with lots of samples with up/down status) or si

Re: [openstack-dev] [neutron] [third-party] Current status of Neutron 3rd Party CI and how to move forward

On 06/16/2014 10:25 AM, Ilya Shakhat wrote: >> >>> However, it would be great if we could start devising a solution for >> having >>> "health" reports from the various CI systems. >>> This report should report the following kind of information: >>> - timestamp of last run >>> - timestamp of last vo

Re: [openstack-dev] [neutron] [third-party] Current status of Neutron 3rd Party CI and how to move forward

On 06/16/2014 09:52 AM, Salvatore Orlando wrote: > I will probably be unable, as usual, to attend today's CI meeting (falls > right around my dinner time). I'm sorry to hear that, since I value your input in these matters. Your CI system is doing an excellent job and I use it as an example for othe

[openstack-dev] [barbican] Meeting Monday June 16 at 20:00 UTC

Hi Everyone, The Barbican team is hosting our weekly meeting today, Monday June 16nd, at 20:00 UTC in #openstack-meeting-alt Meeting agenda is available here https://wiki.openstack.org/wiki/Meetings/Barbican and everyone is welcomed to add agenda items. You can check this link http://time.is/080

[openstack-dev] [TripleO] Backwards compatibility policy for our projects

All, After having proposed some changes[1][2] to tripleo-heat-templates[3], reviewers suggested adding a deprecation period for the merge.py script. While TripleO is an official OpenStack program, none of the projects under its umbrella (including tripleo-heat-templates) have gone through incubat

[openstack-dev] [FWD] KVM Forum 2014 Call for Participation

- Forwarded message from Paolo Bonzini - > Date: Mon, 16 Jun 2014 18:08:17 +0200 > From: Paolo Bonzini > To: qemu-devel > Subject: [Qemu-devel] KVM Forum 2014 Call for Participation = KVM Forum 2014: Call For Participation

Re: [openstack-dev] [TripleO] Backwards compatibility policy for our projects

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon 16 Jun 2014 10:19:40 AM MDT, Tomas Sedovic wrote: > All, > > After having proposed some changes[1][2] to > tripleo-heat-templates[3], reviewers suggested adding a deprecation > period for the merge.py script. > > While TripleO is an official O

Re: [openstack-dev] Gate proposal - drop Postgresql configurations in the gate

On Sat, Jun 14, 2014 at 3:46 AM, Sean Dague wrote: > On 06/13/2014 06:47 PM, Joe Gordon wrote: > > > > > > > > On Thu, Jun 12, 2014 at 7:18 PM, Dan Prince > > wrote: > > > > On Thu, 2014-06-12 at 09:24 -0700, Joe Gordon wrote: > > > > > > On Jun 12, 2014 8:

Re: [openstack-dev] [nova][cinder] Refactor ISCSIDriver to support other iSCSI transports besides TCP

On Thu, Mar 27, 2014 at 10:45 AM, Shlomi Sasson wrote: > Of course I’m aware of that.. I’m the one who pushed it there in the > first place J > > But it was not the best way to handle this.. I think that the right/better > approach is as suggested. > > > > I’m planning to remove the existing ISE

Re: [openstack-dev] [TripleO] Backwards compatibility policy for our projects

On 16 June 2014 17:30, Jason Rist wrote: > I'm going to have to agree with Tomas here. There doesn't seem to be > any reasonable expectation of backwards compatibility for the reasons > he outlined, despite some downstream releases that may be impacted. Backward compatibility is a hard habit to

Re: [openstack-dev] revert hacking to 0.8 series

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/16/2014 08:37 AM, Thierry Carrez wrote: > Sean Dague wrote: >> Hacking 0.9 series was released pretty late for Juno. The entire >> check queue was flooded this morning with requirements proposals >> failing pep8 because of it (so at 6am EST we we

Re: [openstack-dev] [TripleO] Backwards compatibility policy for our projects

Why is OOO being singled out for backwards compatibility? -Original Message- From: Duncan Thomas [mailto:[email protected]] Sent: Monday, June 16, 2014 11:42 AM To: [email protected]; OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [TripleO]

Re: [openstack-dev] [TripleO] Backwards compatibility policy for our projects

Excerpts from Tomas Sedovic's message of 2014-06-16 09:19:40 -0700: > All, > > After having proposed some changes[1][2] to tripleo-heat-templates[3], > reviewers suggested adding a deprecation period for the merge.py script. > > While TripleO is an official OpenStack program, none of the projects

Re: [openstack-dev] [TripleO] Backwards compatibility policy for our projects

Excerpts from Duncan Thomas's message of 2014-06-16 09:41:49 -0700: > On 16 June 2014 17:30, Jason Rist wrote: > > I'm going to have to agree with Tomas here. There doesn't seem to be > > any reasonable expectation of backwards compatibility for the reasons > > he outlined, despite some downstrea

Re: [openstack-dev] revert hacking to 0.8 series

On 06/16/2014 12:44 PM, Ben Nemec wrote: > On 06/16/2014 08:37 AM, Thierry Carrez wrote: >> Sean Dague wrote: >>> Hacking 0.9 series was released pretty late for Juno. The entire >>> check queue was flooded this morning with requirements proposals >>> failing pep8 because of it (so at 6am EST we we

[openstack-dev] [Manila] GenericDriver cinder volume error during manila create

I am trying devstack on F20 setup with Manila sources. When i am trying to do *manila create --name cinder_vol_share_using_nfs2 --share-network-id 36ec5a17-cef6-44a8-a518-457a6f36faa0 NFS 2 * I see the below error in c-vol due to which even tho' my service VM is started, manila create errors out

Re: [openstack-dev] Gate proposal - drop Postgresql configurations in the gate

On Thu, 2014-06-12 at 11:36 -0400, Sean Dague wrote: > If someone can point me to a case where we've actually found this kind > of bug with tempest / devstack, that would be great. I've just *never* > seen it. I was the one that did most of the fixing for pg support in > Nova, and have helped other

Re: [openstack-dev] [TripleO] Backwards compatibility policy for our projects

Hi Clint This looks like a special pleading here - all OpenStack projects (or 'program' if you prefer - I'm honestly not seeing a difference) have bits that they've written quickly and would rather not have to maintain, but in order to allow people to make use of them downstream have to do that wo

Re: [openstack-dev] revert hacking to 0.8 series

Excerpts from Sean Dague's message of 2014-06-16 05:15:54 -0700: > Hacking 0.9 series was released pretty late for Juno. The entire check > queue was flooded this morning with requirements proposals failing pep8 > because of it (so at 6am EST we were waiting 1.5 hrs for a check node). > > The prev

Re: [openstack-dev] revert hacking to 0.8 series

This sounds totally reasonable. +1 to keeping style-specific changes consistent across a release. — Morgan Fainberg From: Clint Byrum [email protected] Reply: OpenStack Development Mailing List (not for usage questions) [email protected] Date: June 16, 2014 at 10:51:31 To: openst

Re: [openstack-dev] [Trove] Heat integration

Denis Makogon writes: > Good day, Stackers, Trove community. > > > I'd like to start thread related to orchestration based resource > management. At current state Heat support in Trove is nothing else than > experimental. Trove should be able to fully support Trove as resource > management driver

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

On Fri 13 Jun 2014 10:51:24 AM PDT, Stangel, Dan wrote: > You can also refer to the example of Stackalytics, who have created > their own hierarchy and groupings for metrics reporting: > https://github.com/stackforge/stackalytics/blob/master/etc/default_data.json It's a very neat grouping. It seem

Re: [openstack-dev] [Fuel] Using saltstack as orchestrator for fuel

Mistral doesn't have to be married to RabbitMQ, there's a ZeroMQ driver in oslo.messaging, so in theory Mistral should be able to make use of that. On Mon, Jun 16, 2014 at 1:42 AM, Vladimir Kozhukalov wrote: > Guys, > > First of all we need to agree about what orchestration is. In terms of Fuel >

Re: [openstack-dev] Gate proposal - drop Postgresql configurations in the gate

On 16 Jun 2014 20:33, "Thierry Carrez" wrote: > > Robert Collins wrote: > > [...] > > C - If we can't make it harder to get races in, perhaps we can make it > > easier to get races out. We have pretty solid emergent statistics from > > every gate job that is run as check. What if set a policy that

Re: [openstack-dev] Gate proposal - drop Postgresql configurations in the gate

On Mon, Jun 16, 2014 at 11:38 AM, Joe Gordon wrote: > > > > On Sat, Jun 14, 2014 at 3:46 AM, Sean Dague wrote: >> >> On 06/13/2014 06:47 PM, Joe Gordon wrote: >> > >> > >> > >> > On Thu, Jun 12, 2014 at 7:18 PM, Dan Prince > > > wrote: >> > >> > On Thu, 2014-06-12 a

Re: [openstack-dev] Gate proposal - drop Postgresql configurations in the gate

On 16 Jun 2014 22:33, "Sean Dague" wrote: > > On 06/16/2014 04:33 AM, Thierry Carrez wrote: > > Robert Collins wrote: > >> [...] > >> C - If we can't make it harder to get races in, perhaps we can make it > >> easier to get races out. We have pretty solid emergent statistics from > >> every gate j

Re: [openstack-dev] how to install fuel on a esxi vm

Hi, Wang. Could you provide a network topology of your installation (incliding hardware and virtual L2/L3 parts of it)? Also, please, check this instruction http://vbyron.com/blog/deploy-openstack-on-vsphere-with-fuel/ On Thu, Jun 12, 2014 at 8:20 AM, Wang Liming wrote: > hi all: > I install

Re: [openstack-dev] [TripleO] Backwards compatibility policy for our projects

Excerpts from Duncan Thomas's message of 2014-06-16 10:46:12 -0700: > Hi Clint > > This looks like a special pleading here - all OpenStack projects (or > 'program' if you prefer - I'm honestly not seeing a difference) have > bits that they've written quickly and would rather not have to > maintain

Re: [openstack-dev] revert hacking to 0.8 series

On Jun 16, 2014 9:44 AM, "Ben Nemec" wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 06/16/2014 08:37 AM, Thierry Carrez wrote: > > Sean Dague wrote: > >> Hacking 0.9 series was released pretty late for Juno. The entire > >> check queue was flooded this morning with requirements

Re: [openstack-dev] revert hacking to 0.8 series

On Jun 16, 2014 10:02 AM, "Sean Dague" wrote: > > On 06/16/2014 12:44 PM, Ben Nemec wrote: > > On 06/16/2014 08:37 AM, Thierry Carrez wrote: > >> Sean Dague wrote: > >>> Hacking 0.9 series was released pretty late for Juno. The entire > >>> check queue was flooded this morning with requirements pr

Re: [openstack-dev] Rethink how we manage projects? (was Gate proposal - drop Postgresql configurations in the gate)

On 06/16/2014 03:33 AM, Thierry Carrez wrote: David Kranz wrote: [...] There is a different way to do this. We could adopt the same methodology we have now around gating, but applied to each project on its own branch. These project branches would be integrated into master at some frequency or wh

Re: [openstack-dev] [Trove] Heat integration

On 16/06/14 13:56, Nikhil Manchanda wrote: Denis Makogon writes: Because Trove should not do what it does now (cloud service orchestration is not the part of the OS Database Program). Trove should delegate all tasks to Cloud Orchestration Service (Heat). Agreed that Trove should delegate pro

Re: [openstack-dev] [Horizon] [UX] Design for Alarming and Alarm Management

On Jun 16, 2014, at 10:56 AM, Eoghan Glynn wrote: > > Apologies for the top-posting, but just wanted to call out some > potential confusion that arose on the #os-ceilometer channel earlier > today. > > TL;DR: the UI shouldn't assume a 1:1 mapping between alarms and > resources, since thi

Re: [openstack-dev] [Neutron][LBaaS] Barbican Neutron LBaaS Integration Ideas

I would like to see something more sophisticated than a simple counter (it's so easy for a counter to get off when dealing with non-atomic asynchronous commands). But a counter is a good place to start. On Jun 13, 2014 6:54 AM, "Jain, Vivek" wrote: > +2. I totally agree with your comments Doug.

Re: [openstack-dev] Gate proposal - drop Postgresql configurations in the gate

On Jun 14, 2014 11:12 AM, "Robert Collins" wrote: > > You know its bad when you can't sleep because you're redesigning gate > workflows in your head so I apologise that this email is perhaps > not as rational, nor as organised, as usual - but , . :) > > Obviously this is very important to

Re: [openstack-dev] [Horizon] [UX] Design for Alarming and Alarm Management

> On Jun 16, 2014, at 10:56 AM, Eoghan Glynn wrote: > > > > > Apologies for the top-posting, but just wanted to call out some > > potential confusion that arose on the #os-ceilometer channel earlier > > today. > > > > TL;DR: the UI shouldn't assume a 1:1 mapping between alarms and > > r

[openstack-dev] [nova][vmwareapi] Spawn Refactor progress

Our phase 1 of spawn refactor merged a week or 2 ago and we are hard at work on phase 2 and 3. The patch set has been posted. Here is the list in order to review for your convenience not a refactor by a trivial fix to clean up some code before the refactor https://review.openstack.org/#/c/9923

Re: [openstack-dev] [nova] Do any hyperviors allow disk reduction as part of resize ?

This is a fix in flight for the vmware driver. It also throws an exception on disk size reduction. https://review.openstack.org/#/c/85804/ On Jun 13, 2014, at 3:02 AM, "Day, Phil" wrote: > Hi Folks, > > I was looking at the resize code in libvirt, and it has checks which raise an > exce

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

Let me explain how Stackalytics grouping works. 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'. E

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

Hi all, Recently a nova bug [1] was opened where the user describes a scenario where an instance that is locked is still able to be snapshotted (create image and backup). In the case of Trove, instances are locked "...to ensure integrity and protect secrets which are needed by the resident Trov

Re: [openstack-dev] [Cinder] Mid-cycle meetup for Cinder devs

On Thu, Jun 12, 2014 at 3:58 PM, John Griffith wrote: > > > > On Wed, Jun 11, 2014 at 3:16 PM, D'Angelo, Scott > wrote: > >> During the June 11 #openstack-cinder meeting we discussed a mid-cycle >> meetup. The agenda is To be Determined. >> >> I have inquired and HP in Fort Collins, CO has room

Re: [openstack-dev] [nova][ceilometer] FloatingIp pollster spamming n-api logs (bug 1328694)

On Sat, Jun 14, 2014 at 7:33 AM, Eoghan Glynn wrote: > > > - Original Message - > > On 11 June 2014 20:07, Joe Gordon wrote: > > > On Wed, Jun 11, 2014 at 11:38 AM, Matt Riedemann > > > wrote: > > >> On 6/11/2014 10:01 AM, Eoghan Glynn wrote: > > >>> Thanks for bringing this to the list

Re: [openstack-dev] [Neutron][LBaaS] Barbican Neutron LBaaS Integration Ideas

Excerpts from Doug Wiegley's message of 2014-06-10 14:41:29 -0700: > Of what use is a database that randomly delete rows? That is, in effect, > what you’re allowing. > > The secrets are only useful when paired with a service. And unless I’m > mistaken, there’s no undo. So you’re letting users

Re: [openstack-dev] [NFV] Specific example NFV use case for a data plane app

- Original Message - > From: "Calum Loudon" > To: "OpenStack Development Mailing List (not for usage questions)" > > > Hello all > > At Wednesday's meeting I promised to supply specific examples to help > illustrate the NFV use cases and also show how they map to some of the > blueprin

Re: [openstack-dev] [TripleO] Backwards compatibility policy for our projects

On Mon, Jun 16, 2014 at 12:19 PM, Tomas Sedovic wrote: > All, > > After having proposed some changes[1][2] to tripleo-heat-templates[3], > reviewers suggested adding a deprecation period for the merge.py script. > > While TripleO is an official OpenStack program, none of the projects > under its u

  1   2   >