Re: [openstack-dev] [Glance] Recall for previous iscsi backend BP

On 19/11/14 15:21 +0800, henry hly wrote: In the Previous BP [1], support for iscsi backend is introduced into glance. However, it was abandoned because of Cinder backend replacement. The reason is that all storage backend details should be hidden by cinder, not exposed to other projects. Howeve

Re: [openstack-dev] Dynamic VM Consolidation Agent as part of Nova

Where do you suggest as the best place for such a service? On Tue, Nov 18, 2014 at 11:49 PM, Joe Gordon wrote: > > > On Tue, Nov 18, 2014 at 7:40 AM, Mehdi Sheikhalishahi < > mehdi.alish...@gmail.com> wrote: > >> Hi, >> >> I would like to bring Dynamic VM Consolidation capability into Nova. That

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

On 18/11/14 14:48, Thomas Goirand wrote: > > And then, does selenium continues to work for testing Horizon? If so, > then the solution could be to send the .dll and .xpi files in non-free, > and remove them from Selenium in main. > Yes, it still works; that leaves the question, why they are incl

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

On 19/11/14 05:25, Richard Jones wrote: > I've just had a long discussion with #infra folk about the > global-requirements thing, which deviated (quite naturally) into a > discussion about packaging (and their thoughts were in line with where > Radomir and I are heading). > > In their view, bower

Re: [openstack-dev] [Glance] Recall for previous iscsi backend BP

I think that having a stand-alone (client of cinder) rich data streaming service (http put/get with offset support, which can be used for conventional glance plus volume upload/download directly), and rich data-source semantics exposed so that it can be used in an optimal way by/for nova, need not

Re: [openstack-dev] [Glance] Recall for previous iscsi backend BP

Hi Flavio, Thanks for your information about Cinder Store, Yet I have a little concern about Cinder backend: Suppose cinder and glance both use Ceph as Store, then if cinder can do instant copy to glance by ceph clone (maybe not now but some time later), what information would be stored in glance

Re: [openstack-dev] [Glance][stable] Review request

Please, abstain to send review requests to the mailing list http://lists.openstack.org/pipermail/openstack-dev/2013-September/015264.html Thanks, Flavio Hi All, On 18/11/14 17:42 +, Kekane, Abhishek wrote: Greetings!!! Can anyone please review this patch [1]. It requires one more +2

Re: [openstack-dev] Dynamic VM Consolidation Agent as part of Nova

I'd be interested in the opposite, the ability to rebalance the vm's across the fleet to even out load. Agreed it should live outside of Nova tho BR, Stuart On Nov 19, 2014 12:15 AM, "Mehdi Sheikhalishahi" wrote: > Where do you suggest as the best place for such a service? > > On Tue, Nov 18, 20

Re: [openstack-dev] [Glance] Poll for change in weekly meeting time.

On 18/11/14 18:55 +, Nikhil Komawar wrote: We've had a few responses to this poll however, they do not seem to cover the entire set of developers including many of the cores and developers who are going to be actively working on the features this cycle. Based on the responses received, I'd l

[openstack-dev] Tempest basic

Hi, I'm trying to run a single tempest test on openstack but things aren't working as expected. My pwd is tempest root. This is what I'm trying to do, 'nosetests -v tempest.scenario.test_minimum_basic.py', but it throws error. I tried 'nosetests -v tempest/scenario/test_minimum_basic.py' as well

Re: [openstack-dev] Tempest basic

Hi! Try "nosetests -sv tempest.scenario.test_minimum_basic" Regards, Ann On Wed, Nov 19, 2014 at 12:16 PM, Vineet Menon wrote: > Hi, > > I'm trying to run a single tempest test on openstack but things aren't > working as expected. > > My pwd is tempest root. > > This is what I'm trying to do,

Re: [openstack-dev] Dynamic VM Consolidation Agent as part of Nova

If we define a parameter like 'consolidation degree' and consolidate based on this factor, we can achieve both objectives with an implementation. There is an attempt by OpenStack neat project, but it is not integrated into OS. On Wed, Nov 19, 2014 at 10:03 AM, Stuart Fox wrote: > I'd be interest

Re: [openstack-dev] [Neutron][L2 Agent][Debt] Bootstrapping an L2 agent debt repayment task force

My name is also on the etherpad, I'd like to work on improving RPC and ovslib. I am willing to take care of the BP, if somebody else is interested we can do it together. cheers, Rossella On 11/19/2014 12:01 AM, Kevin Benton wrote: > My name is already on the etherpad in the RPC section, but I'l

[openstack-dev] Who maintains the iCal meeting data?

Hi All, I was going to make an iCal feed for all the openstack meetings. I discovered I was waaay behind the times and one exists and is linked from https://wiki.openstack.org/wiki/Meetings With some of the post Paris changes it's a little out of date. I'm really happy to help maintain it i

Re: [openstack-dev] [Fuel] Waiting for Haproxy backends

Hi everyone Actually, we changed a lot in 5.1 HA and there are some changes in 6.0 also. Right now we are using assymetric cluster and use location constraints to control resources. We started using xml diffs as the most reliable and supported approach as it does not depend on pcs/crmsh implementa

Re: [openstack-dev] [Neutron][L2 Agent][Debt] Bootstrapping an L2 agent debt repayment task force

On 19/11/14 11:34, Rossella Sblendido wrote: > My name is also on the etherpad, I'd like to work on improving RPC and > ovslib. I am willing to take care of the BP, if somebody else is > interested we can do it together. sure I can help - (let's sync up on irc to split out the sections and get an

Re: [openstack-dev] [all] Scale out bug-triage by making it easier for people to contribute

On 18 Nov 2014 18:59, "Clint Byrum" wrote: > I think the best approach to this, like reviews, is to have a place > where users can go to drive the triage workload to 0. For instance, the > ubuntu server team had this report for triage: > >http://reqorts.qa.ubuntu.com/reports/ubuntu-server/triage-

Re: [openstack-dev] [nova] Do we need to add xml support for new API extensions on v2 API ?

On Wed, 19 Nov 2014 13:11:40 +0800 Chen CH Ji wrote: > > Hi > I saw we are removing v2 XML support proposed > several days before > > For new api extensions, do we need to add it now and > remove it later or only support JSON ? Thanks I don't think any api add

Re: [openstack-dev] Tempest basic

Hi Anna, Sorry not to be more verbose. Your suggestion works fine in a non-cell devstack installation. But as soon as I have 'ENABLED_SERVICE+=n-cell' in local.conf of devstack, things start to fail. Where as I'm able to boot a server on my own with nova boot command, tempest fails miserably with

[openstack-dev] [api] API-WG meeting (note time change this week)

Hi, We have moved to alternating times each week for the API WG meeting so people from other timezones can attend. Since this is an odd week the meeting will be Thursday UTC 1600. Details here: https://wiki.openstack.org/wiki/Meetings/API-WG The google ical feed hasn't been updated yet, but tha

[openstack-dev] Installing multinode(control node)

Hi, I want to install multinode in openstack, i need some guidence on what all are the services that i need to enable for installing control node. Attached is the localrc. -- Thanks & Regards Chhavi Kant =-=-= Notice: The information contained in this e-mail message and/o

Re: [openstack-dev] [Ironic] Cleaning up spec review queue.

On 11/18/2014 06:13 PM, Chris K wrote: Hi all, In an effort to keep the Ironic specs review queue as up to date as possible, I have identified several specs that were proposed in the Juno cycle and have not been updated to reflect the changes to the current Kilo cycle. I would like to set a dea

Re: [openstack-dev] [Ironic] Cleaning up spec review queue.

On 11/19/2014 12:07 PM, Dmitry Tantsur wrote: On 11/18/2014 06:13 PM, Chris K wrote: Hi all, In an effort to keep the Ironic specs review queue as up to date as possible, I have identified several specs that were proposed in the Juno cycle and have not been updated to reflect the changes to the

Re: [openstack-dev] [barbican] Secret store API validation

On 18/11/2014 21:07, "Nathan Reller" wrote: >> It seems we need to add some validation to the process > >Yes, we are planning to add some validation checks in Kilo. I would >submit a bug report for this. > >The big part of the issue is that we need to be clearer about the >expected input types

Re: [openstack-dev] [tc][neutron] Proposal to split Neutron into separate repositories

I like the definition. PCM (Paul Michali) MAIL …..…. p...@cisco.com IRC ……..… pc_m (irc.freenode.com) TW ………... @pmichali GPG Key … 4525ECC253E31A83 Fingerprint .. 307A 96BB 1A4C D2C7 931D 8D2D 4525 ECC2 53E3 1A83 On Nov 18, 2014, at 10:10 PM, Sumit Naiksatam wrote: > On Tue, Nov 18, 2014

[openstack-dev] [tempest] request to review bug 1321617

Hi All, Could someone please, review the bug https://bugs.launchpad.net/tempest/+bug/1321617 Test case related to quota usage (test_show_quota_usage, test_cinder_quota_defaults and test_cinder_quota_show) uses tenant name, ideally it should use tenant id as quota requires UUID of tenant and not

Re: [openstack-dev] Who maintains the iCal meeting data?

Tony Breeds wrote: > I was going to make an iCal feed for all the openstack meetings. > > I discovered I was waaay behind the times and one exists and is linked from > > https://wiki.openstack.org/wiki/Meetings > > With some of the post Paris changes it's a little out of date. I'm really >

Re: [openstack-dev] Dynamic Policy

Hi Adam, So a comprehensive write-up...although I'm not sure we have made the case for why we need a complete rewrite of how policy is managed. We seemed to have lept into a solution without looking at other possible solutions to the problems we are trying to solve. Here's a start at an alter

[openstack-dev] [glance] Parallels loopback disk format support

Greetings, In scope of these changes [1], I would like to add a new image format into glance. For this purpose there was created a blueprint [2] and would really appreciate if someone from glance team could review this proposal. [1] https://review.openstack.org/#/c/111335/ [2] https://bluepr

Re: [openstack-dev] Quota management and enforcement across projects

Le 18/11/2014 20:05, Doug Hellmann a écrit : On Nov 17, 2014, at 7:18 PM, Kevin L. Mitchell wrote: On Mon, 2014-11-17 at 18:48 -0500, Doug Hellmann wrote: I’ve spent a bit of time thinking about the resource ownership issue. The challenge there is we don’t currently have any libraries that

[openstack-dev] [all][oslo.messaging] Multi-versioning RPC Service API support

Hello Stackers. When i was browsing through bugs of oslo.messaging [1] i found one [2] pretty interesting (it’s old as universe), but it doesn’t seem like a bug, mostly like a blueprint. Digging into code of oslo.messaging i’ve found that, at least, for now, there’s no way launch singl

Re: [openstack-dev] [oslo] kilo graduation plans

On Nov 18, 2014, at 6:11 PM, Sachi King wrote: > On Wednesday, November 12, 2014 02:06:02 PM Doug Hellmann wrote: >> During our “Graduation Schedule” summit session we worked through the list >> of modules remaining the in the incubator. Our notes are in the etherpad >> [1], but as part of the

Re: [openstack-dev] Quota management and enforcement across projects

All I can say at the moment is that Usage and Quota management is a crappy thing to do in OpenStack. Every service has it's own way of doing it both in clients and api's. +n+ for making a effort in standardizing this thing in a way that could be alike across projects.. 2014-11-19 14:33 GMT+01:00 S

Re: [openstack-dev] Quota management and enforcement across projects

On Nov 19, 2014, at 8:33 AM, Sylvain Bauza wrote: > > Le 18/11/2014 20:05, Doug Hellmann a écrit : >> On Nov 17, 2014, at 7:18 PM, Kevin L. Mitchell >> wrote: >> >>> On Mon, 2014-11-17 at 18:48 -0500, Doug Hellmann wrote: I’ve spent a bit of time thinking about the resource ownership is

Re: [openstack-dev] [all][oslo.messaging] Multi-versioning RPC Service API support

On Nov 19, 2014, at 8:49 AM, Denis Makogon wrote: > Hello Stackers. > > > > When i was browsing through bugs of oslo.messaging [1] i found one > [2] pretty interesting (it’s old as universe), but it doesn’t seem like a > bug, mostly like a blueprint. > Digging into code of oslo

Re: [openstack-dev] [all][oslo.messaging] Multi-versioning RPC Service API support

On 11/19/2014 09:18 AM, Doug Hellmann wrote: > > On Nov 19, 2014, at 8:49 AM, Denis Makogon > wrote: > >> Hello Stackers. >> >> >> >> When i was browsing through bugs of oslo.messaging [1] i found >> one [2] pretty interesting (it’s old as universe), but

Re: [openstack-dev] Quota management and enforcement across projects

Le 19/11/2014 15:06, Doug Hellmann a écrit : On Nov 19, 2014, at 8:33 AM, Sylvain Bauza wrote: Le 18/11/2014 20:05, Doug Hellmann a écrit : On Nov 17, 2014, at 7:18 PM, Kevin L. Mitchell wrote: On Mon, 2014-11-17 at 18:48 -0500, Doug Hellmann wrote: I’ve spent a bit of time thinking abo

Re: [openstack-dev] [Fuel] Power management in Cobbler

I am absolutely -1 for using Cobbler for that. Lastly, Ironic guys became much more open for adopting new features (at least if they are implemented in terms of Ironic drivers). Currently, it looks like we are probably able to deliver zero step Fuel Ironic driver by 6.1. Ironic already has working

Re: [openstack-dev] [glance] Parallels loopback disk format support

Hi Maxim, Thanks for showing interest in this aspect. Like nova-specs, Glance also needs a spec to be create for discussion related to the blueprint. Please try to create one here [1]. Additionally you may join us at the meeting [2] if you feel stuck or need clarifications. [1] https://github

Re: [openstack-dev] [Glance][stable] Review request

This patch is a bit different as it is not a straightforward cherry-pick from the commit in master (that fixes the bug). So, it seemed like a good idea to start the discussion. Nonetheless, it's my bad turning into a miscommunication where the email just became a review request; while the inten

[openstack-dev] [NFV][Telco] Telco Working Group meeting minutes (2014-11-19)

Hi all, Please find minutes nd logs for the Telco Working Group meeting held at 1400 UTC on Wednesday the 19th of November at the following locations: * Meeting ended Wed Nov 19 15:02:01 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) * Minutes: http:/

Re: [openstack-dev] [Fuel] Power management in Cobbler

> On 19 Nov 2014, at 16:10, Vladimir Kozhukalov > wrote: > > I am absolutely -1 for using Cobbler for that. Lastly, Ironic guys became > much more open for adopting new features (at least if they are implemented in > terms of Ironic drivers). Currently, it looks like we are probably able to

Re: [openstack-dev] [nova] v3 integrated tests taking a lot longer?

On 11/18/2014 06:48 PM, Matt Riedemann wrote: I just started noticing today that the v3 integrated api samples tests seem to be taking a lot longer than the other non-v3 integrated api samples tests. On my 4 VCPU, 4 GB RAM VM some of those tests are taking anywhere from 15-50+ seconds, while the

Re: [openstack-dev] [Nova][Neutron] Error message when Neutron network is running out of IP addresses

On 11/18/2014 5:27 PM, Vishvananda Ishaya wrote: It looks like this has not been reported so a bug would be great. It looks like it might be as easy as adding the NoMoreFixedIps exception to the list where FixedIpLimitExceeded is caught in nova/network/manager.py Vish On Nov 18, 2014, at 8:13

Re: [openstack-dev] [Nova][Neutron] Error message when Neutron network is running out of IP addresses

Ok, I will open a bug and commit a patch! :-) Edgar From: Vishvananda Ishaya mailto:vishvana...@gmail.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Tuesday, November 18, 2014 at 3:27 PM To: "OpenStack Development

[openstack-dev] [Fuel] We lost some commits during upstream puppet manifests merge

Fuelers I am writing that we had a really sad incident - we noticed that after we merged upstream keystone module we lost modifications (Change-Id: Idfe4b54caa0d96a93e93bfff12d8b6216f83e2f1 ) for memcached dogpile driv

Re: [openstack-dev] [Fuel] Power management in Cobbler

Tomasz, Vladimir, others, The way I see it is we need a way to discover the corresponding IPMI address for a given node for out-of-band power management. The ultimate ipmitool command is going to be exactly the same whether it comes from Cobbler or Ironic, and all we need to do is feed information

Re: [openstack-dev] Quota management and enforcement across projects

On Nov 19, 2014, at 9:51 AM, Sylvain Bauza wrote: > > Le 19/11/2014 15:06, Doug Hellmann a écrit : >> On Nov 19, 2014, at 8:33 AM, Sylvain Bauza wrote: >> >>> Le 18/11/2014 20:05, Doug Hellmann a écrit : On Nov 17, 2014, at 7:18 PM, Kevin L. Mitchell wrote: > On Mon, 201

Re: [openstack-dev] WSME 0.6.2 released

Version 0.6.2 was incorrectly configured to build universal wheels, leading to installation errors under Python 3 because of a dependency on ipaddr that only works on Python 2 (there is a version of the module already in the standard library for Python 3). To fix this, fungi removed the bad whe

Re: [openstack-dev] [Nova][Neutron] Error message when Neutron network is running out of IP addresses

Nova People, In Havana the behavior of this issue was different, basically the VM was successfully created and after trying multiple times to get an IP the state was changed to ERROR. This behavior is different in Juno (currently testing Icehouse) but I am not able to find the bug fix. As an op

[openstack-dev] [rally]Rally created tenant and users

Hi Is there a way to specify that the Rally created tenants and users and created with admin privileges Currently its created using member role and hence some admin operations are not allowed I want to specify that the account created has admin access Ajay ___

[openstack-dev] [oslo.db][nova] NovaObject.save() needs its own DB transaction

We currently have a pattern in Nova where all database code lives in db/sqla/api.py[1]. Database transactions are only ever created or used in this module. This was an explicit design decision: https://blueprints.launchpad.net/nova/+spec/db-session-cleanup . However, it presents a problem when we

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

Perhaps they are there to support older browsers? Thanks, Kevin From: Matthias Runge [mru...@redhat.com] Sent: Wednesday, November 19, 2014 12:27 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Horizon] the future of angularjs develop

Re: [openstack-dev] [Fuel] Power management in Cobbler

Would net booting a minimal discovery image work? You usually can dump ipmi network information from the host. Thanks, Kevin From: Matthew Mosesohn [mmoses...@mirantis.com] Sent: Wednesday, November 19, 2014 7:46 AM To: OpenStack Development Mailing List (

Re: [openstack-dev] [tc][neutron] Proposal to split Neutron into separate repositories

On Tue, Nov 18, 2014 at 5:36 PM, Armando M. wrote: > Mark, Kyle, > > What is the strategy for tracking the progress and all the details about > this initiative? Blueprint spec, wiki page, or something else? > We're in the process of writing a spec for this now, but we first wanted community feedba

Re: [openstack-dev] [tc][neutron] Proposal to split Neutron into separate repositories

On Tue, Nov 18, 2014 at 5:32 PM, Doug Wiegley wrote: > Hi, > >> so the specs repository would continue to be shared during the Kilo cycle. > > One of the reasons to split is that these two teams have different > priorities and velocities. Wouldn’t that be easier to track/manage as > separate laun

Re: [openstack-dev] [tc][neutron] Proposal to split Neutron into separate repositories

While I agree that a unified endpoint could be a good solution for now, I think that the easiest way of doing this would be by implementing it as an external Neutron service. Using python entry_points, the advanced service extensions can be loaded in Neutron just like we do today (using neutron.co

Re: [openstack-dev] [Fuel] Power management in Cobbler

> On 19 Nov 2014, at 17:56, Fox, Kevin M wrote: > > Would net booting a minimal discovery image work? You usually can dump ipmi > network information from the host. > To boot from minimal iso (which is waht we do now) you still need to tell the host to do it. This is where IPMI discovery is

Re: [openstack-dev] [oslo.db][nova] NovaObject.save() needs its own DB transaction

Matthew, LOL ORM on top of another ORM https://img.neoseeker.com/screenshots/TW92aWVzL0RyYW1h/inception_image33.png Best regards, Boris Pavlovic On Wed, Nov 19, 2014 at 8:46 PM, Matthew Booth wrote: > We currently have a pattern in Nova where all database code lives in > db/sqla/api.p

Re: [openstack-dev] [Neutron] DB: transaction isolation and related questions

> On Nov 18, 2014, at 1:38 PM, Eugene Nikanorov wrote: > > Hi neutron folks, > > There is an ongoing effort to refactor some neutron DB logic to be compatible > with galera/mysql which doesn't support locking (with_lockmode('update')). > > Some code paths that used locking in the past were re

Re: [openstack-dev] [Fuel] Power management in Cobbler

I meant, either go into the bios and set the node to netboot, or hit f12(or whatever) and netboot. the netbooted discovery image should be able to gather all the rest of the bits? Minimal ISO could also be just gpxe or something like that and would do the same as above. Then you don't have to up

Re: [openstack-dev] [oslo.db][nova] NovaObject.save() needs its own DB transaction

> On Nov 19, 2014, at 11:46 AM, Matthew Booth wrote: > > We currently have a pattern in Nova where all database code lives in > db/sqla/api.py[1]. Database transactions are only ever created or used > in this module. This was an explicit design decision: > https://blueprints.launchpad.net/nova/+

Re: [openstack-dev] [oslo.db][nova] NovaObject.save() needs its own DB transaction

> On Nov 19, 2014, at 12:59 PM, Boris Pavlovic wrote: > > Matthew, > > > LOL ORM on top of another ORM > > https://img.neoseeker.com/screenshots/TW92aWVzL0RyYW1h/inception_image33.png > I know where you sta

[openstack-dev] [QA] Meeting Thursday November 20th at 17:00 UTC

Hi everyone, Just a quick reminder that the weekly OpenStack QA team IRC meeting will be tomorrow Thursday, November 20th 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 t

Re: [openstack-dev] [oslo.db][nova] NovaObject.save() needs its own DB transaction

> However, it presents a problem when we consider NovaObjects, and > dependencies between them. I disagree with this assertion, because: > For example, take Instance.save(). An > Instance has relationships with several other object types, one of which > is InstanceInfoCache. Consider the followin

Re: [openstack-dev] [Neutron] DB: transaction isolation and related questions

I was waiting for this because I think I may have a slightly different (and outside of the box) view on how to approach a solution to this. Conceptually (at least in my mind) there isn't a whole lot of difference between how the example below (i.e. updates from two concurrent threads) is handled a

Re: [openstack-dev] [glance] Parallels loopback disk format support

Hi Nikhil, Thank you for your response and advice. I'm currently creating the spec and will publish a review for it shortly. Best, Maxim 19.11.2014 18:15, Nikhil Komawar пишет: Hi Maxim, Thanks for showing interest in this aspect. Like nova-specs, Glance also needs a spec to be create for

Re: [openstack-dev] [policy] [congress] Protocol for Congress --> Enactor

anyone read this? comments? On Sat, Nov 1, 2014 at 11:13 AM, Gregory Lebovitz wrote: > Summary from IRC chat 10/14/2014 on weekly meeting [1] [2] > > Topic: Declarative Language for Congress —> Enactor/Enforcer > > Question: Shall we specify a declarative language for communicating policy > con

Re: [openstack-dev] [api] API-WG meeting (note time change this week)

On Nov 19, 2014, at 4:56 AM, Christopher Yeoh wrote: > Hi, > > We have moved to alternating times each week for the API WG meeting so > people from other timezones can attend. Since this is an odd week > the meeting will be Thursday UTC 1600. Details here: > > https://wiki.openstack.org/wiki/M

Re: [openstack-dev] [api] Cross-Project Liaison for the API Working Group

On Nov 16, 2014, at 4:59 PM, Christopher Yeoh wrote: > My 2c is we should say "The liason should be the PTL or whomever they > delegate to be their representative" and not mention anything about the > person needing to be a core developer. It removes any ambiguity about who > ultimately decid

Re: [openstack-dev] [api] Summit summary

Does anybody know what happened to the Etherpad? It’s completely blank now!!! If you check the Timeslider, it appears that it only ever existed on Nov. 15. Bizarre. Everett On Nov 14, 2014, at 5:05 PM, Everett Toews wrote: > Hi All, > > Here’s a summary of what happened at the Summit from t

Re: [openstack-dev] [api] Summit summary

On Nov 19, 2014, at 11:38, Everett Toews wrote: > Does anybody know what happened to the Etherpad? It’s completely blank now!!! > > If you check the Timeslider, it appears that it only ever existed on Nov. 15. > Bizarre. I see it as blank now too, however I can see all of the previous revision

Re: [openstack-dev] [api] API-WG meeting (note time change this week)

On Wed, Nov 19, 2014 at 1:34 PM, Everett Toews wrote: > On Nov 19, 2014, at 4:56 AM, Christopher Yeoh wrote: > > > Hi, > > > > We have moved to alternating times each week for the API WG meeting so > > people from other timezones can attend. Since this is an odd week > > the meeting will be Thur

Re: [openstack-dev] [Fuel] Waiting for Haproxy backends

Hi crew, Please see my inline comments. Hi Everyone, > > I was reading the blueprints mentioned here and thought I'd take the > opportunity to introduce myself and ask a few questions. > For those that don't recognise my name, Pacemaker is my baby - so I take a > keen interest helping people have

Re: [openstack-dev] [Neutron] DB: transaction isolation and related questions

Hi Eugene, please see comments inline. But, bottom line, is that setting the transaction isolation level to READ_COMMITTED should be avoided. On 11/18/2014 01:38 PM, Eugene Nikanorov wrote: Hi neutron folks, There is an ongoing effort to refactor some neutron DB logic to be compatible with gal

Re: [openstack-dev] [OpenStack-dev][Nova] Migration stuck - resize/migrating

Indeed. Ensure you have SSH access between compute nodes (I'm working on some code to remove this requirement, but it may be a while before it gets merged). Also, if you can, could you post logs somewhere with the 'debug' config option enabled? I might be able to spot something quickly, since

Re: [openstack-dev] [Neutron] DB: transaction isolation and related questions

> On Nov 19, 2014, at 1:49 PM, Ryan Moats wrote: > > I was waiting for this because I think I may have a slightly different (and > outside of the box) view on how to approach a solution to this. > > Conceptually (at least in my mind) there isn't a whole lot of difference > between how the exa

Re: [openstack-dev] [Neutron] DB: transaction isolation and related questions

> On Nov 19, 2014, at 2:58 PM, Jay Pipes wrote: > > >> In other words, the retry logic like the following will not work: >> >> def allocate_obj(): >> with session.begin(subtrans=True): >> for i in xrange(n_retries): >> obj = session.query(Model).filter_by(filters) >>

Re: [openstack-dev] [Neutron] DB: transaction isolation and related questions

On 19 November 2014 11:58, Jay Pipes wrote: > Some code paths that used locking in the past were rewritten to retry > >> the operation if they detect that an object was modified concurrently. >> The problem here is that all DB operations (CRUD) are performed in the >> scope of some transaction th

Re: [openstack-dev] [Neutron] DB: transaction isolation and related questions

Ian Wells wrote on 11/19/2014 02:33:40 PM: [snip] > When you have a plugin that's decided to be synchronous, then there > are cases where the DB lock is held for a technically indefinite > period of time.  This is basically broken. A big +1 to this statement Ryan Moats__

Re: [openstack-dev] [Neutron] DB: transaction isolation and related questions

> > > Mike Bayer wrote on 11/19/2014 02:10:18 PM: > > > From: Mike Bayer > > To: "OpenStack Development Mailing List (not for usage questions)" > > > > Date: 11/19/2014 02:11 PM > > Subject: Re: [openstack-dev] [Neutron] DB: transaction isolation and > > related questions > > > > On Nov 19, 2014

Re: [openstack-dev] [nova] v3 integrated tests taking a lot longer?

On 11/19/2014 9:40 AM, Jay Pipes wrote: On 11/18/2014 06:48 PM, Matt Riedemann wrote: I just started noticing today that the v3 integrated api samples tests seem to be taking a lot longer than the other non-v3 integrated api samples tests. On my 4 VCPU, 4 GB RAM VM some of those tests are taki

Re: [openstack-dev] [Glance] Recall for previous iscsi backend BP

Hey Henry/Folks, I think it could make sense for Glance to store the volume UUID, the idea is that no matter where an image is stored it should be *owned* by Glance and not deleted out from under it. But that is more of a single tenant vs multi tenant cinder store. It makes sense for Cinder to at

Re: [openstack-dev] [Fuel] Waiting for Haproxy backends

On 11/18/2014 07:25 PM, Andrew Woodward wrote: On Tue, Nov 18, 2014 at 3:18 PM, Andrew Beekhof wrote: * Openstack services are not managed by Pacemaker Oh? fuel doesn't (currently) set up API services in pacemaker Nor should it, IMO. Other than the Neutron dhcp-agent, all OpenStack serv

Re: [openstack-dev] [Neutron] DB: transaction isolation and related questions

Excerpts from Mike Bayer's message of 2014-11-19 10:05:35 -0800: > > > On Nov 18, 2014, at 1:38 PM, Eugene Nikanorov > > wrote: > > > > Hi neutron folks, > > > > There is an ongoing effort to refactor some neutron DB logic to be > > compatible with galera/mysql which doesn't support locking

Re: [openstack-dev] [nova] v3 integrated tests taking a lot longer?

On 11/19/2014 04:00 PM, Matt Riedemann wrote: On 11/19/2014 9:40 AM, Jay Pipes wrote: On 11/18/2014 06:48 PM, Matt Riedemann wrote: I just started noticing today that the v3 integrated api samples tests seem to be taking a lot longer than the other non-v3 integrated api samples tests. On my 4 V

Re: [openstack-dev] [Neutron] DB: transaction isolation and related questions

> On Nov 19, 2014, at 3:47 PM, Ryan Moats wrote: > > > > BTW, I view your examples from oslo as helping make my argument for > me (and I don't think that was your intent :) ) > I disagree with that as IMHO the differences in producing MM in the app layer against arbitrary backends (Postgresq

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

The Neutron L3 team will meet [1] tomorrow at the regular time. I'd like to discuss the progress of the functional tests for the L3 agent to see how we can get that on track. I don't think we need to wait for the BP to merge before get something going. We will likely not have a meeting next week

Re: [openstack-dev] [Fuel] Waiting for Haproxy backends

> On 20 Nov 2014, at 6:55 am, Sergii Golovatiuk > wrote: > > Hi crew, > > Please see my inline comments. > > Hi Everyone, > > I was reading the blueprints mentioned here and thought I'd take the > opportunity to introduce myself and ask a few questions. > For those that don't recognise my n

Re: [openstack-dev] [Neutron] DB: transaction isolation and related questions

Wow, lots of feedback in a matter of hours. First of all, reading postgres docs I see that READ COMMITTED is the same as for mysql, so it should address the issue we're discussing: "*Read Committed* is the default isolation level in PostgreSQL. When a transaction uses this isolation level, a SELE

Re: [openstack-dev] [nova] v3 integrated tests taking a lot longer?

On 11/19/2014 04:16 PM, Jay Pipes wrote: On 11/19/2014 04:00 PM, Matt Riedemann wrote: On 11/19/2014 9:40 AM, Jay Pipes wrote: On 11/18/2014 06:48 PM, Matt Riedemann wrote: I just started noticing today that the v3 integrated api samples tests seem to be taking a lot longer than the other non

Re: [openstack-dev] [glance] Parallels loopback disk format support

IIUC, the blueprint just want to add a new image format, and no code change in Glance, is it? If that's the case, I'm wondering if we really need a blueprint/spec. Because the image format could be configured in glance-api.conf. Please correct me if I missed anything. Cheers. On 20/11/14 02:27, M

Re: [openstack-dev] Who maintains the iCal meeting data?

On Wed, Nov 19, 2014 at 01:24:03PM +0100, Thierry Carrez wrote: > The iCal is currently maintained by Anne (annegentle) and myself. In > parallel, a small group is building a gerrit-powered agenda so that we > can describe meetings in YAML and check for conflicts automatically, and > build the ics

Re: [openstack-dev] [Neutron] DB: transaction isolation and related questions

> On Nov 19, 2014, at 4:14 PM, Clint Byrum wrote: > > > One simply cannot rely on multi-statement transactions to always succeed. agree, but the thing you want is that the transaction either succeeds or explicitly fails, the latter hopefully in such a way that a retry can be added which has

Re: [openstack-dev] [Neutron] DB: transaction isolation and related questions

> But the isolation mode change won’t really help here as pointed out by Jay; discrete transactions have to be used instead. I still think it will, per postgres documentation (which might look confusing, but still...) It actually helps for mysql, that was confirmed. For postgres it appears to be th

[openstack-dev] [Cinder] mid-cycle meet-up planning ...

All, For those of you that weren't able to make the Kilo meet-up in Paris I wanted to send out a note regarding Cinder's Kilo mid-cycle meet-up. IBM has offered to host it in, warm, sunny, Austin, Texas. The planned dates are January 27, 28 and 29, 2015. I have put together an etherpad wit

[openstack-dev] [neutron][lbaas] Abandon Old LBaaS V2 Review

Evgeny, Since change sets got moved to the feature branch, this review has remained on master. It needs to be abandoned: https://review.openstack.org/#/c/109849/ Thanks, Brandon On Mon, 2014-11-17 at 12:31 -0800, Stephen Balukoff wrote: > Awesome! > > On Mon, Nov 10, 2014 at 9:10 AM, Susanne B

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

On 11/19/2014 04:27 PM, Matthias Runge wrote: > On 18/11/14 14:48, Thomas Goirand wrote: > >> >> And then, does selenium continues to work for testing Horizon? If so, >> then the solution could be to send the .dll and .xpi files in non-free, >> and remove them from Selenium in main. >> > Yes, it s

Re: [openstack-dev] [nova] v3 integrated tests taking a lot longer?

On 11/19/2014 3:34 PM, Andrew Laski wrote: On 11/19/2014 04:16 PM, Jay Pipes wrote: On 11/19/2014 04:00 PM, Matt Riedemann wrote: On 11/19/2014 9:40 AM, Jay Pipes wrote: On 11/18/2014 06:48 PM, Matt Riedemann wrote: I just started noticing today that the v3 integrated api samples tests see

Re: [openstack-dev] Quota management and enforcement across projects

On 20 November 2014 05:25, wrote: > -- > > Message: 24 > Date: Wed, 19 Nov 2014 10:57:17 -0500 > From: Doug Hellmann > To: "OpenStack Development Mailing List (not for usage questions)" > > Subject: Re: [openstack-dev] Quota management and enforcement across

  1   2   >