Re: [openstack-dev] [swift] Optimizing storage for small objects in Swift

This is great work. I'm sure you've already thought of this, but could you explain why you've chosen not to put the small objects in the k/v store as part of the value rather than in secondary large files? Excerpts from Alexandre Lécuyer's message of 2017-06-16 15:54:08 +0200: > Swift stores

Re: [openstack-dev] [deployment][kolla][openstack-ansible][openstack-helm][tripleo] ansible role to produce oslo.config files for openstack services

On Fri, Jun 16, 2017 at 11:09 AM, Jiří Stránský wrote: > On 15.6.2017 19:06, Emilien Macchi wrote: >> >> I missed [tripleo] tag. >> >> On Thu, Jun 15, 2017 at 12:09 PM, Emilien Macchi >> wrote: >>> >>> If you haven't followed the "Configuration management

Re: [openstack-dev] [neutron] security group OVO change

To close the loop here, - this also broke heat py3 job (https://launchpad.net/bugs/1698355) - we polished https://review.openstack.org/474575 to fix both vmware-nsx and heat issues - I also posted a patch for oslo.serialization for the bug that triggered MemoryError in heat gate:

Re: [openstack-dev] [tc][fuel] Making Fuel a hosted project

> On Jun 16, 2017, at 07:28, Jay Pipes wrote: > > On 06/16/2017 09:57 AM, Emilien Macchi wrote: >> On Thu, Jun 15, 2017 at 4:50 PM, Dean Troyer wrote: >>> On Thu, Jun 15, 2017 at 10:33 AM, Jay Pipes wrote: I'd fully support the

Re: [openstack-dev] [tc] Status update, Jun 16

> > == Need for a TC meeting next Tuesday == > > In order to make progress on the Pike goal selection, I think a > dedicated IRC meeting will be necessary. We have a set of valid goals > proposed already: we need to decide how many we should have, and which > ones. Gerrit is not great to have

Re: [openstack-dev] [tc] Status update, Jun 16

On 11:17 Jun 16, Thierry Carrez wrote: > == Need for a TC meeting next Tuesday == > > In order to make progress on the Pike goal selection, I think a > dedicated IRC meeting will be necessary. We have a set of valid goals > proposed already: we need to decide how many we should have, and

Re: [openstack-dev] [all][qa][glance] some recent tempest problems

> > So, before we go further, ceph seems to be -nv on all projects right > now, right? So I get there is some debate on that patch, but is it > blocking anything? > Ceph is voting on os-brick patches. So it does block some things when we run into this situation. But again, we should avoid

Re: [openstack-dev] [devstack] etcd v3.2.0?

On Fri, Jun 16, 2017 at 6:01 AM, Sean Dague wrote: > On 06/15/2017 10:06 PM, Tony Breeds wrote: >> Hi All, >> I just push a review [1] to bump the minimum etcd version to >> 3.2.0 which works on intel and ppc64le. I know we're pretty late in the >> cycle to be making

Re: [openstack-dev] [devstack] etcd v3.2.0?

Mikhail, I have a TODO on my list - " adding a job that looks for new releases and uploads them to tarballs periodically " Thanks, -- Dims On Fri, Jun 16, 2017 at 3:32 PM, Mikhail Medvedev wrote: > On Fri, Jun 16, 2017 at 6:01 AM, Sean Dague wrote: >> On

[openstack-dev] [neutron] no CI and upgrades meetings in next two weeks

Hi all, subject says it all. Also note that upgrades meeting moved to Thursday: https://review.openstack.org/474347 Ihar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [swift] Optimizing storage for small objects in Swift

Excerpts from John Dickinson's message of 2017-06-16 11:35:39 -0700: > > On 16 Jun 2017, at 10:51, Clint Byrum wrote: > > > This is great work. > > > > I'm sure you've already thought of this, but could you explain why > > you've chosen not to put the small objects in the k/v store as part of >

Re: [openstack-dev] [all][qa][glance] some recent tempest problems

On 6/16/2017 8:13 PM, Matt Riedemann wrote: Yeah there is a distinction between the ceph nv job that runs on nova/cinder/glance changes and the ceph job that runs on os-brick and glance_store changes. When we made the tempest dsvm ceph job non-voting we failed to mirror that in the

Re: [openstack-dev] [deployment][kolla][openstack-ansible][openstack-helm][tripleo] ansible role to produce oslo.config files for openstack services

So I'm trying to figure out how to actually use it. We (and any other container based deploy..) will run into some chicken/egg problem - you need to deploy container to generate big yaml with defaults, then you need to overload it with your configurations, validate if they're not deprecated, run

Re: [openstack-dev] [neutron] security group OVO change

It also broke networking-odl. The patch[1] is needed to unbreak. [1] https://review.openstack.org/#/c/448420/ necessary db info is taken from context.session.new. But with OVO, those expunge themselves with create method. Those info needs to be passed as callback argument. Thanks, On Fri, Jun

Re: [openstack-dev] [all][qa][glance] some recent tempest problems

On 6/16/2017 3:32 PM, Sean McGinnis wrote: So, before we go further, ceph seems to be -nv on all projects right now, right? So I get there is some debate on that patch, but is it blocking anything? Ceph is voting on os-brick patches. So it does block some things when we run into this

Re: [openstack-dev] [all][qa][glance] some recent tempest problems

On 6/16/2017 9:46 AM, Eric Harney wrote: On 06/16/2017 10:21 AM, Sean McGinnis wrote: I don't think merging tests that are showing failures, then blacklisting them, is the right approach. And as Eric points out, this isn't necessarily just a failure with Ceph. There is a legitimate logical

Re: [openstack-dev] [swift] Optimizing storage for small objects in Swift

On 16 Jun 2017, at 10:51, Clint Byrum wrote: > This is great work. > > I'm sure you've already thought of this, but could you explain why > you've chosen not to put the small objects in the k/v store as part of > the value rather than in secondary large files? I don't want to co-opt an answer

Re: [openstack-dev] [all][tc] Moving away from "big tent" terminology

On Fri, Jun 16 2017, gordon chung wrote: > *sigh* so this is why we can't have nice things :p > > as an aside, in telemetry project, we did something somewhat similar > when we renamed/rebranded to telemetry from ceilometer. we wrote several > notes to the ML, had a few blog posts, fixed the

Re: [openstack-dev] [all][tc] Moving away from "big tent" terminology

On Thu, Jun 15 2017, Doug Hellmann wrote: > One of the *most* common complaints the TC gets from outside the > contributor community is that people do not understand what projects > are part of OpenStack and what parts are not. We have a clear > definition of that in our minds (the projects that

Re: [openstack-dev] [ironic] the driver composition and breaking changes to the supported interfaces

Thanks! I think this is what we seem to agree so far: keep the old interface and deprecate it usage. On 06/13/2017 01:39 PM, tie...@vn.fujitsu.com wrote: Hi, Dmitry: Thanks for bringing this issue into discussion. For the iRMC patch, I would vote for the first option as it is commonly

[openstack-dev] [release] Release countdown for week R-10 and R-9, June 16-30

Welcome to our regular release countdown email! Development Focus - Teams should be reconsidering how much they can deliver in the Pike release, prioritizing critical items and wrapping up what was started. Actions --- We are getting closer to the final Pike release. A

Re: [openstack-dev] [heat] Deprecate/Remove deferred_auth_method=password config option

Hi Rabi, I still takes `deferred _auth_method=password` behalf of trusts because we don't enable trusts in the Keystone side due to some internal reason. The issues what you pointed are correct(e.g. user_domain_id), we don't use the domain well and also added some patches to skip those issues.

[openstack-dev] [tc] Status update, Jun 16

Hi! Back on regular schedule, here is an update on the status of a number of TC-proposed governance changes, in an attempt to rely less on a weekly meeting to convey that information. You can find the full status list of open topics at: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee

Re: [openstack-dev] [all][tc] Moving away from "big tent" terminology

On 15/06/17 22:35, Ed Leafe wrote: > On Jun 15, 2017, at 3:35 PM, Jeremy Stanley wrote: > >> For me it's one of the most annoying yet challenging/interesting >> aspects: free software development is as much about community and >> politics as it is actual software development

Re: [openstack-dev] [all][tc] Moving away from "big tent" terminology

On Fri, Jun 16 2017, Thierry Carrez wrote: > I should have made it clearer in my original post that this discussion > actually originated at the Board+TC+UC workshop in Boston, as part of > the "better communicating what is openstack" subgroup. This is still such a vague problem statement that

Re: [openstack-dev] [devstack] etcd v3.2.0?

On 06/15/2017 10:06 PM, Tony Breeds wrote: > Hi All, > I just push a review [1] to bump the minimum etcd version to > 3.2.0 which works on intel and ppc64le. I know we're pretty late in the > cycle to be making changes like this but releasing pike with a dependacy > on 3.1.x make it harder

[openstack-dev] [tripleo] CI Squad Meeting Summary (week 24) - devmode issues, promotion progress

If the topics below interest you and you want to contribute to the discussion, feel free to join the next meeting: Time: Thursdays, 14:30-15:30 UTC Place: https://bluejeans.com/4113567798/ Full minutes: https://etherpad.openstack.org/p/tripleo-ci-squad-meeting = Devmode OVB issues = Devmode

Re: [openstack-dev] [vitrage-dashboard] Alarm Header Blueprint

Actually just saw the horizon extensible header blueprint go approved. see https://blueprints.launchpad.net/horizon/+spec/extensible-header let me know what your thoughts are on the Vitrage-dashboard blueprint Greg. From: Greg Waines Date: Thursday, June 15, 2017 at

Re: [openstack-dev] [tc][fuel] Making Fuel a hosted project

Shake Chen wrote: > HI Vikash > > I think Kolla is suitable for official project for deployment Deployment tooling is, by nature, opinionated. You just can't enable everything and keep it manageable. As long as people will have differing opinions on how OpenStack pieces should be deployed,

Re: [openstack-dev] [all][tc] Moving away from "big tent" terminology

Matt Riedemann wrote: > On 6/15/2017 9:57 AM, Thierry Carrez wrote: >> Obviously we are not the target audience for that term. I think we are >> deep enough in OpenStack and technically-focused enough to see through >> that. But reality is, the majority of the rest of the world is confused, >> and

Re: [openstack-dev] [tc][fuel] Making Fuel a hosted project

On Fri, Jun 16, 2017 at 3:39 PM, Thierry Carrez wrote: > Shake Chen wrote: > > HI Vikash > > > > I think Kolla is suitable for official project for deployment > > Deployment tooling is, by nature, opinionated. You just can't enable > everything and keep it manageable. As

Re: [openstack-dev] [nova][api] Strict validation in query parameters

On 06/15/2017 10:01 PM, Matt Riedemann wrote: > On 6/15/2017 8:43 PM, Alex Xu wrote: >> We added new decorator 'query_schema' to support validate the query >> parameters by JSON-Schema. >> >> It provides more strict valiadation as below: >> * set the 'additionalProperties=False' in the schema, it

Re: [openstack-dev] [tc] Status update, Jun 16

On 2017-06-16 11:17:30 +0200 (+0200), Thierry Carrez wrote: [...] > In order to make progress on the Pike goal selection, I think a > dedicated IRC meeting will be necessary. We have a set of valid goals > proposed already: we need to decide how many we should have, and which > ones. Gerrit is not

Re: [openstack-dev] [tc] Status update, Jun 16

On Fri, Jun 16, 2017 at 7:19 AM, Doug Hellmann wrote: > Excerpts from Thierry Carrez's message of 2017-06-16 11:17:30 +0200: > > > == Need for a TC meeting next Tuesday == > > > > In order to make progress on the Pike goal selection, I think a > > dedicated IRC meeting

Re: [openstack-dev] [tc][fuel] Making Fuel a hosted project

On Thu, Jun 15, 2017 at 4:50 PM, Dean Troyer wrote: > On Thu, Jun 15, 2017 at 10:33 AM, Jay Pipes wrote: >> I'd fully support the removal of all deployment projects from the "official >> OpenStack projects list". > > Nice to hear Jay! :) > > It was

Re: [openstack-dev] [all][qa][glance] some recent tempest problems

On 06/16/2017 10:21 AM, Sean McGinnis wrote: > > I don't think merging tests that are showing failures, then blacklisting > them, is the right approach. And as Eric points out, this isn't > necessarily just a failure with Ceph. There is a legitimate logical > issue with what this particular test

Re: [openstack-dev] [all][qa][glance] some recent tempest problems

On 06/16/2017 10:46 AM, Eric Harney wrote: > On 06/16/2017 10:21 AM, Sean McGinnis wrote: >> >> I don't think merging tests that are showing failures, then blacklisting >> them, is the right approach. And as Eric points out, this isn't >> necessarily just a failure with Ceph. There is a legitimate

Re: [openstack-dev] [deployment][kolla][openstack-ansible][openstack-helm][tripleo] ansible role to produce oslo.config files for openstack services

On 15.6.2017 19:06, Emilien Macchi wrote: I missed [tripleo] tag. On Thu, Jun 15, 2017 at 12:09 PM, Emilien Macchi wrote: If you haven't followed the "Configuration management with etcd / confd" thread [1], Doug found out that using confd to generate configuration files

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

On Sat, Jun 17, 2017 at 12:14 AM, Jeremy Stanley wrote: > On 2017-06-16 15:12:36 +1000 (+1000), Tony Breeds wrote: > [...] > > It seeems a little odd to be following up so long after I first started > > this thread but can someone on infra please process the EOLs as > >

Re: [openstack-dev] [heat] Deprecate/Remove deferred_auth_method=password config option

HI all, On Fri, Jun 16, 2017 at 4:33 PM, Zane Bitter wrote: > On 16/06/17 05:09, Kaz Shinohara wrote: > >> I still takes `deferred _auth_method=password` behalf of trusts because >> we don't enable trusts in the Keystone side due to some internal reason. >> > > Free advice:

[openstack-dev] [swift] Optimizing storage for small objects in Swift

Swift stores objects on a regular filesystem (XFS is recommended), one file per object. While it works fine for medium or big objects, when you have lots of small objects you can run into issues: because of the high count of inodes on the object servers, they can’t stay in cache, implying lot

Re: [openstack-dev] [all][qa][glance] some recent tempest problems

On 06/15/2017 10:51 PM, Ghanshyam Mann wrote: > On Fri, Jun 16, 2017 at 9:43 AM, wrote: >> https://review.openstack.org/#/c/471352/ may be an example > > If this is case which is ceph related, i think we already discussed > these kind of cases, where functionality

Re: [openstack-dev] [all][qa][glance] some recent tempest problems

> > It would be useful to provide detailed examples. Everything is trade > offs, and having the conversation in the abstract is very difficult to > understand those trade offs. > > -Sean > We've had this issue in Cinder and os-brick. Usually around Ceph, but if you follow the user

Re: [openstack-dev] [all][qa][glance] some recent tempest problems

On Fri, Jun 16, 2017 at 10:57 PM, Sean Dague wrote: > On 06/16/2017 09:51 AM, Sean McGinnis wrote: >>> >>> It would be useful to provide detailed examples. Everything is trade >>> offs, and having the conversation in the abstract is very difficult to >>> understand those trade

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

On 2017-06-16 15:12:36 +1000 (+1000), Tony Breeds wrote: [...] > It seeems a little odd to be following up so long after I first started > this thread but can someone on infra please process the EOLs as > described in [1]. [...] I thought in prior discussions it had been determined that the

Re: [openstack-dev] [all][qa][glance] some recent tempest problems

Excerpts from Ghanshyam Mann's message of 2017-06-16 23:05:08 +0900: > On Fri, Jun 16, 2017 at 10:57 PM, Sean Dague wrote: > > On 06/16/2017 09:51 AM, Sean McGinnis wrote: > >>> > >>> It would be useful to provide detailed examples. Everything is trade > >>> offs, and having the

Re: [openstack-dev] [all][qa][glance] some recent tempest problems

> > yea, we had such cases and decided to have blacklist of tests not > suitable for ceph. ceph job will exclude the tests failing on ceph. > Jon is working on this - https://review.openstack.org/#/c/459774/ > I don't think merging tests that are showing failures, then blacklisting them, is the

Re: [openstack-dev] [heat] Deprecate/Remove deferred_auth_method=password config option

On 16/06/17 05:09, Kaz Shinohara wrote: I still takes `deferred _auth_method=password` behalf of trusts because we don't enable trusts in the Keystone side due to some internal reason. Free advice: whatever reason you have for not enabling trusts, storing user passwords in the Heat database

Re: [openstack-dev] [all][qa][glance] some recent tempest problems

On 06/16/2017 09:51 AM, Sean McGinnis wrote: >> >> It would be useful to provide detailed examples. Everything is trade >> offs, and having the conversation in the abstract is very difficult to >> understand those trade offs. >> >> -Sean >> > > We've had this issue in Cinder and os-brick.

Re: [openstack-dev] [tc] Status update, Jun 16

Excerpts from Thierry Carrez's message of 2017-06-16 11:17:30 +0200: > == Need for a TC meeting next Tuesday == > > In order to make progress on the Pike goal selection, I think a > dedicated IRC meeting will be necessary. We have a set of valid goals > proposed already: we need to decide how

Re: [openstack-dev] [tc][fuel] Making Fuel a hosted project

On 06/16/2017 09:57 AM, Emilien Macchi wrote: On Thu, Jun 15, 2017 at 4:50 PM, Dean Troyer wrote: On Thu, Jun 15, 2017 at 10:33 AM, Jay Pipes wrote: I'd fully support the removal of all deployment projects from the "official OpenStack projects list".

[openstack-dev] [glance] nominating Abhishek Kekane for glance core

I'm nominating Abhishek Kekane (abhishekk on IRC) to be a Glance core for the Pike cycle. Abhishek has been around the Glance community for a long time and is familiar with the architecture and design patterns used in Glance and its related projects. He's contributed code, triaged bugs, provided

Re: [openstack-dev] [tc][fuel] Making Fuel a hosted project

On Fri, Jun 16, 2017 at 8:57 AM, Emilien Macchi wrote: > Regarding all the company efforts to invest in one deployment tool, > it's going to be super hard to find The OneTrue and convince everyone > else to work on it. The idea is not that everyone works on it, it is simply

Re: [openstack-dev] [all][qa][glance] some recent tempest problems

On 06/16/2017 09:51 AM, Sean McGinnis wrote: >> >> It would be useful to provide detailed examples. Everything is trade >> offs, and having the conversation in the abstract is very difficult to >> understand those trade offs. >> >> -Sean >> > > We've had this issue in Cinder and os-brick.

Re: [openstack-dev] [Keystone][Mistral][Devstack] Confusion between auth_url and auth_uri in keystone middleware

On Thu, Jun 15, 2017 at 1:12 PM, Harry Rybacki wrote: > On Thu, Jun 15, 2017 at 1:57 PM, Brant Knudson wrote: > > > > > > On Thu, Jun 15, 2017 at 5:14 AM, Mikhail Fedosin > wrote: > >> > >> Recently I decided to remove deprecated

Re: [openstack-dev] [tc] Status update, Jun 16

Clay Gerrard wrote: > I'm loving this new ML thing the TC is doing! Like... I'm not going to > come to the meeting. I'm not a helpful person in general and probably > wouldn't have anything productive to say. > > But I love the *idea* that I know *when and where* this is being decided > so that

Re: [openstack-dev] [tc] Status update, Jun 16

Since there are 2 topics that are very very important to me: 1. binary resolution waiting for votes 2. kolla stable:follows-policy tag Is there anything I can to do help with either? On 16 June 2017 at 09:23, Thierry Carrez wrote: > Clay Gerrard wrote: >> I'm loving this

Re: [openstack-dev] [swift] Optimizing storage for small objects in Swift

Alex, this is fantastic work and great info. Thanks for sharing it. Additional comments inline. On 16 Jun 2017, at 6:54, Alexandre Lécuyer wrote: > Swift stores objects on a regular filesystem (XFS is recommended), one file > per object. While it works fine for medium or big objects, when you