[openstack-dev] [kuryr] Kuryr-Kubernetes gates broken

Hi, Kuryr-Kubernetes LBaaSv2 gates are currently broken due to bug [1] in python-neutronclient. Until commit [2] is merged and a new version of the client is released I'm proposing to make those gates non-voting [3]. [1] https://bugs.launchpad.net/python-neutronclient/+bug/1801360 [2] https://rev

Re: [openstack-dev] [all] Naming the T release of OpenStack

On Thu, 2018-10-18 at 17:35 +1100, Tony Breeds wrote: > Hello all, > As per [1] the nomination period for names for the T release have > now closed (actually 3 days ago sorry). The nominated names and any > qualifying remarks can be seen at2]. > > Proposed Names > * Tarryall > * Teakettle >

Re: [openstack-dev] Nominating Luis Tomás Bolívar for kuryr-kubernetes core

On Thu, 2018-09-20 at 18:33 +0200, Daniel Mellado wrote: > Hi All, > > Id like to nominate Luis Tomás for Kuryr-Kubernetes core. > > He has been contributing to the project development with both features > and quality reviews at core reviewer level, as well as being the stable > branch liaison ke

[openstack-dev] [kuryr] [os-vif] kuryr-kubernetes gates unblocked

Hi, kuryr-kubernetes gates were broken by recent try to switch from neutron-legacy DevStack to plain neutron [1]. Meanwhile it modified DevStack jobs we were relying on and introduced us another failure. Now neutron-legacy change was reverted [2] and fix for the second issue [3] is getting merged

Re: [openstack-dev] [all] review.openstack.org downtime and Gerrit upgrade TODAY 15:00 UTC - 23:59 UTC

On wto, 2017-09-19 at 09:19 +0200, Andreas Jaeger wrote: > Two things currently: > > * no post jobs are run, I suggest to not tag anything > > * I don't get emails from gerrit anymore > Same here, since the outage I've stopped receiving Gerrit notifications to my email. Thanks, Michal ___

Re: [openstack-dev] [heat] Rolling Upgrades

On 10/21/2016 11:57 PM, Zane Bitter wrote: > On 21/10/16 08:37, Michał Dulko wrote: >>> > Finally, a note about Oslo versioned objects: they don't really help >>> > us. They work great for nova where there is just nova-conductor >>> > reading and

Re: [openstack-dev] [heat] Rolling Upgrades

On 10/21/2016 02:02 AM, Crag Wolfe wrote: > At Summit, folks will be discussing the rolling upgrade issue across a > couple of sessions. I personally won't be able to attend, but thought > I would share my thoughts on the subject. > > To handle rolling upgrades, there are two general cases to consi

Re: [openstack-dev] [keystone][nova][neutron][all] Rolling upgrades: database triggers and oslo.versionedobjects

On 10/16/2016 11:52 AM, Duncan Thomas wrote: > On 14 October 2016 at 23:55, Jay Pipes > wrote: > > The primary thing that, to me at least, differentiates rolling > upgrades of distributed software is that different nodes can > contain multiple versions of the

Re: [openstack-dev] [nova] Getting DetachedInstanceError from sqlalchemy on instance.get_by_uuid()

On 10/07/2016 11:04 PM, Beliveau, Ludovic wrote: > > Hi all, > > > > In kilo (yeah I know it’s an old release, but still :)), I was getting > a nova errors for DetachedInstanceError on instance.get_by_uuid(). > > > > > > Has anybody seen this issue before or something similar ? > > > > T

Re: [openstack-dev] [neutron] clean up your git checkout!

On 09/30/2016 04:06 PM, Ihar Hrachyshka wrote: > Ihar Hrachyshka wrote: > >> Hi all, >> >> today we landed https://review.openstack.org/#/c/269658/ (huge!) that >> removed neutron/objects/network/ directory and replaced it with >> neutron/objects/network.py file. Though it makes python that sees o

Re: [openstack-dev] [cinder] [qa] Proposal to make multinode grenade job voting

On 09/29/2016 12:10 PM, Michał Dulko wrote: > Hello everyone, > > We have a non-voting multinode grenade job in check queue for around a > month now. > > https://goo.gl/Kr10s6 Whoops, I've sent this by mistake. Here's the actual email: Hello everyone, We have a non-

[openstack-dev] [cinder] [qa] Proposal to make multinode grenade job voting

Hello everyone, We have a non-voting multinode grenade job in check queue for around a month now. https://goo.gl/Kr10s6 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists

[openstack-dev] [cinder][db] lazy loading of an attribute impossible

Hi, I've just noticed another Cinder bug [1], similar to past bugs [2], [3]. All of them have a common exception causing them: sqlalchemy.orm.exc.DetachedInstanceError: Parent instance <{$SQLAlchemyObject} at {$MemoryLocation}> is not bound to a Session; lazy load operation of attribute '{$Column

Re: [openstack-dev] [cinder] running afoul of Service.__repr__() during client.serivces.list()

On 09/21/2016 03:32 PM, Konstanski, Carlos P wrote: > Am Mittwoch, den 21.09.2016, 15:07 +0200 schrieb Michał Dulko: >> On 09/21/2016 02:32 AM, Konstanski, Carlos P wrote: >>> Am Dienstag, den 20.09.2016, 15:31 -0600 schrieb Konstanski, Carlos P: >>>> I am curre

Re: [openstack-dev] [cinder] running afoul of Service.__repr__() during client.serivces.list()

On 09/21/2016 02:32 AM, Konstanski, Carlos P wrote: > Am Dienstag, den 20.09.2016, 15:31 -0600 schrieb Konstanski, Carlos P: >> I am currently using python-cinderclient version 1.5.0, though the code in >> question is still in master. >> >> When calling client.services.list() I get this result: "At

Re: [openstack-dev] [cinder][sahara] LVM vs BDD drivers performance tests results

On 09/20/2016 05:48 PM, John Griffith wrote: > On Tue, Sep 20, 2016 at 9:06 AM, Duncan Thomas > mailto:duncan.tho...@gmail.com>> wrote: > > On 20 September 2016 at 16:24, Nikita Konovalov > mailto:nkonova...@mirantis.com>> wrote: > > Hi, > > From Sahara (and Hadoop workload

Re: [openstack-dev] [Cinder] FFE request for RBD replication

+1, thanks for taking care of that! On 09/12/2016 03:35 AM, Huang Zhiteng wrote: > +1 for this long-waited feature to land in Newton. > > On Sun, Sep 11, 2016 at 1:09 AM, Jay S. Bryant > mailto:jsbry...@electronicjungle.net>> > wrote: > > +1 from me. It is making good progress and is low risk

Re: [openstack-dev] [cinder] moving driver to open source

On 09/06/2016 05:27 PM, Alon Marx wrote: > I want to share our plans to open the IBM Storage driver source code. > Historically we started our way in cinder way back (in Essex if I'm > not mistaken) with just a small piece of code in the community while > keeping most of the driver code closed. S

Re: [openstack-dev] [Nova][API] Need naming suggestions for "capabilities"

On 08/25/2016 07:52 PM, Andrew Laski wrote: > On Thu, Aug 25, 2016, at 12:22 PM, Everett Toews wrote: >> Top posting with general comment... >> >> It sounds like there's some consensus in Nova-land around these >> traits (née "capabilities"). The API Working Group [4] is >> also aware of similar e

Re: [openstack-dev] Announcing Gertty 1.4.0

On 07/27/2016 12:39 AM, James E. Blair wrote: > Announcing Gertty 1.4.0 > === > > Gertty is a console-based interface to the Gerrit Code Review system. > > Gertty is designed to support a workflow similar to reading network > news or mail. It syncs information from Gerrit to lo

Re: [openstack-dev] [Cinder] Nominating Scott D'Angelo to Cinder core

+2 I was wondering when this will happen. Congratulations Scott! :) On 06/27/2016 07:27 PM, Sean McGinnis wrote: > I would like to nominate Scott D'Angelo to core. Scott has been very > involved in the project for a long time now and is always ready to help > folks out on IRC. His contributions [

Re: [openstack-dev] [openstack-operators][cinder] max_concurrent_builds in Cinder

On 05/24/2016 04:38 PM, Gorka Eguileor wrote: > On 23/05, Ivan Kolodyazhny wrote: >> Hi developers and operators, >> I would like to get any feedback from you about my idea before I'll start >> work on spec. >> >> In Nova, we've got max_concurrent_builds option [1] to set 'Maximum number >> of in

Re: [openstack-dev] [Heat] Versioned objects upgrade patterns

On 05/18/2016 10:39 PM, Zane Bitter wrote: > On 17/05/16 20:27, Crag Wolfe wrote: >> Now getting very Heat-specific. W.r.t. to >> https://review.openstack.org/#/c/303692/ , the goal is to de-duplicate >> raw_template.files (this is a dict of template filename to contents), >> both in the DB and in

Re: [openstack-dev] [Heat] Versioned objects upgrade patterns

On 05/17/2016 09:40 PM, Crag Wolfe wrote: > That helps a lot, thanks! You are right, it would have to be a 3-step > upgrade to avoid the issue you mentioned in 6. > > Another thing I am wondering about: if my particular object is not > exposed by RPC, is it worth making it a full blown o.vo or

Re: [openstack-dev] [Heat] Versioned objects upgrade patterns

On 05/17/2016 06:30 PM, Crag Wolfe wrote: > Hi all, > > I've read that versioned objects are favored for supporting different > versions between RPC services and to support rolling upgrades. I'm > looking to follow the pattern for Heat. Basically, it is the classic > problem where we want to migrat

Re: [openstack-dev] [neutron][ovo] NeutronDbObject concurrency issues

On 05/16/2016 05:49 PM, Ilya Chukhnakov wrote: > On 16 May 2016, at 18:18, Michał Dulko <mailto:michal.du...@intel.com>> wrote: >> In Cinder we're handling similar problems related to race conditions >> between status check and status change with conditional upda

Re: [openstack-dev] [neutron][ovo] NeutronDbObject concurrency issues

On 05/12/2016 08:26 PM, Ilya Chukhnakov wrote: > Hi everyone. > > I’ve recently found that straightforward use of NeutronDbObject is prone to > concurrency-related problems. > > I’ve submitted a patch set [3] with some tests to show that without special > treatment using NeutronDbObject could lead

Re: [openstack-dev] [Cinder] Nominating Micha?? Dulko to Cinder Core

my best to fulfill the expectations. …but I'll start making it happen in the next week, when I'll return from post-summit vacations. :) > On Tue, May 03, 2016 at 01:16:59PM -0500, Sean McGinnis wrote: >> Hey everyone, >> >> I would like to nominate Michał Dulko to the

Re: [openstack-dev] [Cinder] API features discoverability

t may or may not be available in different installations. This certainly isn't addressed by microversions efforts, which may seem related. My feeling is that this goes beyond Cinder and hits a more general topic of API discoverability. I think that we should seek the API WG advice in that m

Re: [openstack-dev] [all] -The lifecycle of deploying openstack on production environment

You should probably try openstack-operators mailing list next time, as openstack-dev is more developer oriented. But anyway: On 04/15/2016 08:53 AM, Kenny Ji-work wrote: > Hi all, > > We wanner to deploy openstack to the production environment, so what's > the recommended way to complete it? By us

[openstack-dev] [Cinder] API features discoverability

Hi, When looking at bug [1] I've thought that we could simply use /v2//extensions to signal features available in the deployment - in this case backups, as these are implemented as API extension too. Cloud admin can disable an extension if his cloud doesn't support a particular feature and this is

Re: [openstack-dev] [OpenStack Foundation] [board][tc][all] One Platform – Containers/Bare Metal? (Re: Board of Directors Meeting)

On 04/13/2016 11:16 AM, Thierry Carrez wrote: > Fox, Kevin M wrote: >> I think my head just exploded. :) >> >> That idea's similar to neutron sfc stuff, where you just say what >> needs to connect to what, and it figures out the plumbing. >> >> Ideally, it would map somehow to heat & docker COE & n

Re: [openstack-dev] [cinder] Let's do presentations/sessions on Mitaka's new complex features in Design Summit

On 03/14/2016 09:52 PM, Gorka Eguileor wrote: > Hi, > > As you all probably know, during this cycle we have introduced quite a > big number of changes in cinder that will have a great impact in the > development of the new functionality as well as changes to existing ones > moving forward from an i

Re: [openstack-dev] [cinder] Proposal: changes to our current testing process

On 03/02/2016 04:11 PM, Gorka Eguileor wrote: > On 02/03, Ivan Kolodyazhny wrote: >> Eric, >> >> There are Gorka's patches [10] to remove API Races >> >> >> [10] >> https://review.openstack.org/#/q/project:openstack/cinder+branch:master+topic:fix/api-races-simplified >> > I looked at Rally a long t

Re: [openstack-dev] Openstack Cinder - Wishlist

On 03/01/2016 11:31 AM, mohammed.asha...@wipro.com wrote: > > Hi, > > > > Would like to know if there’s feature wish list/enhancement request > for Open stack Cinder I.e. a list of features that we would like to > add to Cinder Block Storage ; but hasn’t been taken up for development > yet. > >

Re: [openstack-dev] [nova] solving API case sensitivity issues

On 02/24/2016 01:48 PM, Sean Dague wrote: > We have a specific bug around aggregrate metadata setting in Nova which > exposes a larger issue with our mysql schema. > https://bugs.launchpad.net/nova/+bug/1538011 > > On mysql the following will explode with a 500: > >> nova aggregate-create agg1 >> n

Re: [openstack-dev] [all] A proposal to separate the design summit

On 02/25/2016 09:13 AM, Qiming Teng wrote: > Hi, All, > > After reading through all the +1's and -1's, we realized how difficult > it is to come up with a proposal that makes everyone happy. When we are > discussing this proposal with some other contributors, we came up with a > proposal which is a

Re: [openstack-dev] [os-brick][nova][cinder] os-brick/privsep change is done and awaiting your review

On 02/24/2016 04:51 AM, Angus Lees wrote: > Re: https://review.openstack.org/#/c/277224 > > Most of the various required changes have flushed out by now, and this > change now passes the dsvm-full integration tests(*). > > (*) well, the experimental job anyway. It still relies on a > merged-but-no

Re: [openstack-dev] [all] A proposal to separate the design summit

On 02/22/2016 04:49 PM, Daniel P. Berrange wrote: > On Mon, Feb 22, 2016 at 04:14:06PM +0100, Thierry Carrez wrote: >> The idea would be to split the events. The first event would be for upstream >> technical contributors to OpenStack. It would be held in a simpler, >> scaled-back setting that woul

Re: [openstack-dev] [cinder] v2 image upload from url

The second command isn't really related to images, but to Glance Metadata Definitions Catalog. Some docs on these concepts can be found in [1]. [1] http://docs.openstack.org/developer/glance/metadefs-concepts.html On 02/08/2016 02:24 PM, Pankaj Mishra wrote: > Hi Kevin, > > I am executing command

Re: [openstack-dev] [Cinder] the spec of Add-ServiceGroup-using-Tooz

On 01/31/2016 10:43 PM, dong.wenj...@zte.com.cn wrote: > > Hi all, > > I proposed the spec of Add-ServiceGroup-using-Tooz in Ciner[1]. > > Project doctor[2] in OPNFV community is its upstream. > The goal of this project is to build fault management and > maintenance framework for high a

Re: [openstack-dev] [keystone][nova][cinder][horizon] Projects acting as a domain at the top of the project hierarchy

On 01/30/2016 07:02 PM, Henry Nash wrote: > Hi > > One of the things the keystone team was planning to merge ahead of > milestone-3 of Mitaka, was “projects acting as a domain”. Up until now, > domains in keystone have been stored totally separately from projects, even > though all projects must

Re: [openstack-dev] [cinder] Testing Cinder upgrades - c-bak upgrade

On 01/20/2016 09:11 PM, Li, Xiaoyan wrote: > @ DuncanT and @dule: > > I noticed from IRC log that you are discussing about c-bak upgrade, and I am > working on this, please see following message. Hope I don't miss anything. > > As you know, currently c-bak and c-vol are in same nodes. c-bak depen

Re: [openstack-dev] [TaskFlow] TaskFlow persistence

On 01/26/2016 10:23 AM, pn kk wrote: > Hi, > > I use taskflow for job management and now trying to persist the state > of flows/tasks in mysql to recover incase of process crashes. > > I could see the state and the task results stored in the database. > > Now I am looking for some way to store the

Re: [openstack-dev] [kolla] 40 hour time commitment requested from core reviewers before Feb 9th/10th midcycle

On 01/26/2016 10:11 AM, Michał Jastrzębski wrote: > Well we still can perform upgrades with some API downtime, so it's not > like we're bound to rolling upgrades on architectural level. I'll talk > to you after midcycle and we'll find a good way to tackle it. Sure, this will work. projects.yaml sa

Re: [openstack-dev] [kolla] 40 hour time commitment requested from core reviewers before Feb 9th/10th midcycle

On 01/23/2016 02:32 AM, Steven Dake (stdake) wrote: > Hello, > > In our weekly IRC meeting, all developers and others in attendance > were in unanimous agreement that upgrades are the #1 priority for > Kolla to solve [1]. inc0 has developed both a simple database > migration implementation around

Re: [openstack-dev] [cinder] Core/minimum features requirements for Cinder Driver

On 01/22/2016 01:17 PM, vishal yadav wrote: > Hey Guys, > > I would like to know the requirement for core/minimum features that > any new Cinder driver should implement. Provided lot many features > have been added in Cinder since Icehouse release, Is the core feature > requirements mentioned in [1

[openstack-dev] [grenade] [upgrades] [cinder] Testing Cinder upgrades

Hi, In Mitaka Cinder team is implementing rolling upgrades capabilities. I want to get some feedback on possibilities of implementing some partial or multinode grenade check for our purposes. Basically Cinder consists of 4 services calling each other over RPC the in following fashion: +---

Re: [openstack-dev] [cinder] Object backporting and the associated service

On 01/18/2016 03:31 PM, Duncan Thomas wrote: > On 5 January 2016 at 18:55, Ryan Rossiter > wrote: > > This is definitely good to know. Are you planning on setting up > something off to the side of o.vo within that holds a dictionary > of all values f

Re: [openstack-dev] [cinder] Should we fix XML request issues?

On 01/15/2016 07:14 AM, Jethani, Ravishekar wrote: > Hi Devs, > > I have come across a few 500 response issues while sending request > body as XML to cinder service. For example: > > > > I can see that XML support has been marked as depricated and will be > removed in 'N' release. So is it still w

Re: [openstack-dev] [trove][neutron][cinder][swift][ceilometer][nova][keystone][sahara][glance][neutron-lbaas][imm] stylistic changes to code, how do we handle them?

On 01/12/2016 03:02 PM, Chris Dent wrote: > On Tue, 12 Jan 2016, Amrith Kumar wrote: > >> if var > 0: >> ... something ... >> >> To >> >> if var: >> ... something ... > > I may be missing something but the above is not a stylistic change > if var can ever be negative. In one of the ceilomet

Re: [openstack-dev] [cinder] Object backporting and the associated service

On 01/04/2016 11:41 PM, Ryan Rossiter wrote: > My first question is: what will be handling the object backports that the > different cinder services need? In Nova, we have the conductor service, which > handles all of the messy RPC and DB work. When anyone needs something > backported, they ask

Re: [openstack-dev] [cinder] oslo_config.PortOp is undefined

PortOpt definitely exists in oslo.config [1]. Try executing "pip install -U -r /opt/stack/cinder/requirements.txt". [1] https://github.com/openstack/oslo.config/blob/f5e2fab3ae5af5bd47fe3526a73f13fbaa27c1f0/oslo_config/cfg.py#L1180-L1216 On 01/05/2016 12:33 PM, Pradip Mukhopadhyay wrote: > I did

Re: [openstack-dev] [Horizon][stable] Horizon kilo gate fails due to testrepository dependency

On 01/04/2016 03:41 PM, Ihar Hrachyshka wrote: > UPD: Turns out it breaks Liberty gate too, f.e. for Neutron. It’s > interesting that it did not break the thing for e.g. Neutron master. > > Matthias Runge wrote: We observe this on Cinder's stable/liberty in Grenade tests (e.g. [1]) and on stable/

Re: [openstack-dev] Gerrit performance

On 12/29/2015 10:44 AM, Gary Kotton wrote: > Hi, > I know it is holidays but gerrit response is so slow. If anyone from > Infra is online please can you help. > Thanks > Gary > Actually it's not only slow, but occasionally drops/timeouts requests. As the UI is making multiple HTTP calls to display

Re: [openstack-dev] [cinder] [nova] whether the ServiceGroup in Cinder is necessary

On 12/28/2015 05:03 AM, hao wang wrote: > hi, Janice > > This idea seems to me that is useful to detect the state of > cinder-volume process more quickly, but I feel there is another issue > that if the back-end device go to fail you still > can't keep cloud in ha or create volume successfully sinc

Re: [openstack-dev] [cinder] [nova] whether the ServiceGroup in Cinder is necessary

On 12/22/2015 09:01 PM, Erlon Cruz wrote: > Hmm, I see. There's this spec[1] that was discussed in the past with a > similar proposal. There's a SPEC with some other points on the > discussion, I think Janice forgot to mention. > > Erlon > > [1] https://review.openstack.org/#/c/176233/ > [2] https:

Re: [openstack-dev] [OpenStack-Infra] Gerrit Upgrade to ver 2.11, completed.

On 12/22/2015 10:52 PM, Carl Baldwin wrote: > On Mon, Dec 21, 2015 at 6:21 PM, Zaro wrote: >> Hit '?' and it says '/' is find, give that a try. > '/' isn't really much better. It seems to highlight all of the > occurrences but I can't find a way to navigate to the next/previous > occurence with t

Re: [openstack-dev] [cinder] [nova] whether the ServiceGroup in Cinder is necessary

On 12/22/2015 01:29 PM, Erlon Cruz wrote: > Hi Li, > > Can you give a quick background on servicegroups (or links to. The > spec you linked only describe the process on Nova to change from what > they are using to tooz)? Also, what are the use cases and benefits of > using this? > > Erlon > This i

Re: [openstack-dev] [cinder] [nova] whether the ServiceGroup in Cinder is necessary

On 12/17/2015 04:49 AM, li.yuanz...@zte.com.cn wrote: > Hi all, > > I'd like to start discussion on whether the servicegroup in Cinder > is necessary. > > Recently, cinder can only support db driver, and doesn't have > servicegroup concept. > our team wants to implement the servicegroup fea

Re: [openstack-dev] [OpenStack-Infra] Gerrit Upgrade to ver 2.11 completed.

On 12/16/2015 11:40 PM, Zaro wrote: > We have identified this and will look into it soon. Thanks for > reporting the issue. > > On Wed, Dec 16, 2015 at 2:02 PM, Michał Dulko wrote: >> On 12/16/2015 10:22 PM, Zaro wrote: >>> Thanks to everyone for their patience

Re: [openstack-dev] Announcing Gertty 1.3.0

On 12/17/2015 11:59 PM, James E. Blair wrote: > Announcing Gertty 1.3.0 > === > > Gertty is a console-based interface to the Gerrit Code Review system. > > Gertty is designed to support a workflow similar to reading network > news or mail. It syncs information from Gerrit to lo

Re: [openstack-dev] [OpenStack-Infra] Gerrit Upgrade to ver 2.11 completed.

On 12/16/2015 10:22 PM, Zaro wrote: > Thanks to everyone for their patience while we upgraded to Gerrit > 2.11. I'm happy to announce that we were able to successfully > completed this task at around 21:00 UTC. You may hack away once more. > > If you encounter any problems, please let us know her

Re: [openstack-dev] [cinder] Custom fields for versioned objects

On 12/15/2015 04:08 PM, Ryan Rossiter wrote: > Thanks for the review Michal! As for the bp/bug report, there’s four options: > > 1. Tack the work on as part of bp cinder-objects > 2. Make a new blueprint (bp cinder—object-fields) > 3. Open a bug to handle all changes for enums/fields > 4. Open a bu

[openstack-dev] [Cinder] Rolling upgrades

Hi, At the meeting recently it was mentioned that our rolling upgrades efforts are pursuing an "elusive unicorn" that makes development a lot more complicated and restricted. I want to try to clarify this a bit, explain the strategy more and give an update on the status of the whole affair. So fi

Re: [openstack-dev] [cinder] Custom fields for versioned objects

On 12/14/2015 03:59 PM, Ryan Rossiter wrote: > Hi everyone, > > I have a change submitted that lays the groundwork for using custom enums and > fields that are used by versioned objects [1]. These custom fields allow for > verification on a set of valid values, which prevents the field from being