Re: [openstack-dev] [tc][nova][mogan] How to show respect to the original authors?

Thanks dims, that's cool :D I'll make sure there's no new patches landed to master before replacing the repo. On Fri, Sep 22, 2017 at 9:53 AM, Davanum Srinivas wrote: > Zhenguo, > > I did some fancy surgery with both cinder and nova repos to add the > history, please check

Re: [openstack-dev] Garbage patches for simple typo fixes

On Fri, 22 Sep 2017, at 12:21, Matt Riedemann wrote: > I just wanted to highlight to people that there seems to be a series of > garbage patches in various projects [1] which are basically doing things > like fixing a single typo in a code comment, or very narrowly changing > http to https in

Re: [openstack-dev] Garbage patches for simple typo fixes

Thanks for being brave enough to say it publicly. Not sure how many more times I can stomach reading such classic patches as "Optimize the link address" or "Replace six.iteritems() with .items()". Yes, it is still possible for us to be an open community while also minimizing the amount of useless

Re: [openstack-dev] Garbage patches for simple typo fixes

Wow, Matt, that's excellent timing. Day for day, an exact year after the last thread of this kind [1]. Thanks for speaking up, I didn't want to it'd seem like encouraging a stereotype or prejudice towards certain kind of contributions (or contributors) but I've also been rolling my eyes a lot

Re: [openstack-dev] Garbage patches for simple typo fixes

+1000 Thanks for bringing this up, I fully agree that we need to do something about it. Some time ago I even had an idea of creating a case when we intentionally exclude a person from a team for constantly doing things like this and ignoring our comments. Although I understand it slightly

Re: [openstack-dev] [all][api] POST /api-sig/news

> Microversions also reared their head in the form of a long discussion > about how SDK developers and users are consuming microversions at a very > granular level. This discussion opened many surprised eyes as we learned > how different SDK platforms deal with microversions, and what exactly are

Re: [openstack-dev] Garbage patches for simple typo fixes

Let's not forget the epic fail earlier on the "contribution.rst fix" that almost melt down the community CI system. For any companies that are doing what Matt mentioned, please be aware that the dev community of the country you belong to is getting hurt by your stupid activity. Stop patch

[openstack-dev] Garbage patches for simple typo fixes

I just wanted to highlight to people that there seems to be a series of garbage patches in various projects [1] which are basically doing things like fixing a single typo in a code comment, or very narrowly changing http to https in links within docs. Also +1ing ones own changes. I've been

Re: [openstack-dev] [oslo][oslo.service] looping.RetryDecorator behavior

Thanks Josh, I’m not sure I fully understand your point though. You mean it’s a legacy (deprecated?) code that we should never use in our code? Should it be considered a private class of oslo_service? In our global requirements tenacity is configured as "tenacity>=3.2.1”, should we bump it to

Re: [openstack-dev] [tc][nova][mogan] How to show respect to the original authors?

Zhenguo, I did some fancy surgery with both cinder and nova repos to add the history, please check my repo here: https://github.com/dims/mogan/commits/master (Needed quota.py from cinder and rest of the files from Nova) If that repo looks good, then we can request infra folks to replace the

Re: [openstack-dev] [tc][nova][mogan] How to show respect to the original authors?

On Thu, Sep 21, 2017 at 1:33 PM, Clint Byrum wrote: > Excerpts from Michael Still's message of 2017-09-20 10:25:17 -0600: > > Dims, I'm not sure that's actually possible though. Many of these files > > have been through rewrites and developed over a large number of years. > >

[openstack-dev] [nova] Your semi-monthly file injection and shelve mailer

Just thought everyone might like to know about this. I realized tonight that if you shelve an instance and it's offloaded, which is the default behavior, any injected files you had in the original instance are gone, and you can't specify them again on unshelve. We're awesome. The More You

Re: [openstack-dev] [tc][nova][mogan] How to show respect to the original authors?

On Wed, Sep 20, 2017 at 7:51 PM, Davanum Srinivas wrote: > Zhenguo, > > Thanks for bringing this up. > > For #1, yes please indicate which file from Nova, so if anyone wanted > to cross check for fixes etc can go look in Nova > For #2, When you pick up a commit from Nova,

Re: [openstack-dev] [tc][nova][mogan] How to show respect to the original authors?

Thanks John Dickinson, we can follow Swift's way but as Michael Still mentioned seems listing all authors isn't practical. On Thu, Sep 21, 2017 at 5:43 AM, John Dickinson wrote: > > > On 20 Sep 2017, at 9:25, Michael Still wrote: > > > Dims, I'm not sure that's actually possible

Re: [openstack-dev] [tc][nova][mogan] How to show respect to the original authors?

On Fri, Sep 22, 2017 at 5:48 AM, Matt Riedemann wrote: > On 9/21/2017 11:55 AM, Mike Perez wrote: > >> On 15:56 Sep 20, Flavio Percoco wrote: >> >>> On 20/09/17 12:21 +, Jeremy Stanley wrote: >>> On 2017-09-20 07:51:29 -0400 (-0400), Davanum Srinivas wrote:

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

On Thu, Sep 21, 2017 at 12:13:23PM -0400, Doug Hellmann wrote: > Excerpts from Tony Breeds's message of 2017-09-21 08:36:39 -0400: > > On Wed, Sep 20, 2017 at 06:08:22PM -0400, Doug Hellmann wrote: > > > > > I like the idea. I'm not sure why, if the constraints file is only used > > > for the

Re: [openstack-dev] [infra] Unable to add member to Zun core team

Hi Jeremy, No problem at all. I just checked it and everything seems work well now. I will tell Hongbin Lu to try again. Huge thanks, Kien Nguyen 2017-09-22 3:59 GMT+07:00 Jeremy Stanley : > On 2017-09-22 00:16:13 +0700 (+0700), Kiên Nguyễn Tuấn wrote: > > I'm Kien Nguyen

Re: [openstack-dev] [neutron][fwaas] Proposal to change the time for Firewall-as-a-Service Team Meeting

Hi, I’m sorry I’m late. I just voted it. Thanks, Yushiro Furukawa From: reedip banerjee [mailto:reedi...@gmail.com] Sent: Tuesday, September 19, 2017 11:54 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev]

[openstack-dev] PDFs for project-specific docs with unified doc builds

Hello, "Build PDF docs from rst-based guide documents" [1] was implemented in Ocata cycle, and I have heard that there were a small conversation at the Denver PTG regarding getting PDFs for project-specific docs setup to help translations. In my opinion, it would be a nice idea to extend [1]

Re: [openstack-dev] [nova] About live-resize spec

On 9/21/2017 3:13 AM, Claudiu Belu wrote: I don't know how soon the capabilities thing can become a real thing, but IMO, we can go with Matt's suggestion of disabling the feature by default through policy. I wouldn't hold my breath on a capabilities API, so I think a policy rule is what

Re: [openstack-dev] [Openstack-operators] [nova] Is there any reason to exclude originally failed build hosts during live migration?

On 9/21/2017 6:17 AM, Saverio Proto wrote: Why the change is called: Ignore original retried hosts when live migrating ? Isn't it implementing the opposite ? Dont Ignore ? Heh, you're right. I'll fix. Beyond that, any feedback on the actual intent here? -- Thanks, Matt

Re: [openstack-dev] [tc][nova][mogan] How to show respect to the original authors?

On 9/21/2017 11:55 AM, Mike Perez wrote: On 15:56 Sep 20, Flavio Percoco wrote: On 20/09/17 12:21 +, Jeremy Stanley wrote: On 2017-09-20 07:51:29 -0400 (-0400), Davanum Srinivas wrote: [...] please indicate which file from Nova, so if anyone wanted to cross check for fixes etc can go look

[openstack-dev] [nova] Forum topics brainstorming

So this shouldn't be news now that I've read back through a few emails in the mailing list (I've been distracted with the Pike release, PTG planning, etc) [1][2][3] but we have until Sept 29 to come up with whatever forum sessions we want to propose. There is already an etherpad for Nova [4].

Re: [openstack-dev] [infra] Unable to add member to Zun core team

On 2017-09-22 00:16:13 +0700 (+0700), Kiên Nguyễn Tuấn wrote: > I'm Kien Nguyen . Actually, the older > account with id 22406 is my current account and the newer is not. > > Therefore, please mark the newer account (26112) as inactive and > re-active the 22406 account.

Re: [openstack-dev] [vitrage] Extending Topology

Hi Usman, Great to hear back from you ☺ You are more than welcome to join our efforts. You can look at the list of blueprints[1], suggest new ones, implement existing, or solve bugs[2]. Whatever you chose, we will be happy to assist. The ways to contact Vitrage developers are here in the

[openstack-dev] Sydney Forum Topic Submission

Hi, We have made it to the next stage of the topic selection process for the Forum in Sydney! At the Forum the entire OpenStack community (users and developers) gathers to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go

Re: [openstack-dev] [skip-level-upgrades][fast-forward-upgrades] PTG summary

On 2017-09-21 13:29:53 -0400 (-0400), Doug Hellmann wrote: [...] > On the other hand, some of those were meant to be aspirational, so > not documenting them may mean no one is thinking about them at > all. Previous tags were added to document existing state/practices and came with projects

Re: [openstack-dev] [TripleO] TripleO/Ansible PTG session

On Thu, Sep 21, 2017 at 11:53 AM, Jiří Stránský wrote: > On 21.9.2017 18:04, Marios Andreou wrote: >> >> On Thu, Sep 21, 2017 at 3:53 PM, Jiří Stránský wrote: >> >>> On 21.9.2017 12:31, Giulio Fidente wrote: >>> On 09/20/2017 07:36 PM, James Slagle wrote:

[openstack-dev] [all][api] POST /api-sig/news

Greetings OpenStack community, This week's meeting was primarily focused on reviewing the discussions and plans that were proposed at the PTG. We also merged one new guideline which was frozen prior to the PTG. For a review of PTG activity, please see the etherpad[4] One of the big

Re: [openstack-dev] [ptg] Simplification in OpenStack

Excerpts from Jeremy Stanley's message of 2017-09-21 16:17:00 +: > On 2017-09-20 17:39:38 -0700 (-0700), Clint Byrum wrote: > [...] > > Something about common use cases and the exact mix of > > projects + configuration to get there, and testing it? Help? > [...] > > Maybe you're thinking of

Re: [openstack-dev] [TripleO] TripleO/Ansible PTG session

On 21.9.2017 18:04, Marios Andreou wrote: On Thu, Sep 21, 2017 at 3:53 PM, Jiří Stránský wrote: On 21.9.2017 12:31, Giulio Fidente wrote: On 09/20/2017 07:36 PM, James Slagle wrote: On Tue, Sep 19, 2017 at 8:37 AM, Giulio Fidente wrote: On

Re: [openstack-dev] [skip-level-upgrades][fast-forward-upgrades] PTG summary

Excerpts from Thierry Carrez's message of 2017-09-21 17:10:52 +0200: > Sean Dague wrote: > > Agreed. We're already at 5 upgrade tags now? > > > > I think honestly we're going to need a picture to explain the > > differences between them. Based on the confusion that kept seeming to > > come during

Re: [openstack-dev] [os-vif] [passthrough] [VifHostDevice]

> -Original Message- > From: pranab boruah [mailto:pranabjyotibor...@gmail.com] > Sent: Thursday, September 21, 2017 5:12 PM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: [openstack-dev] [os-vif] [passthrough]

[openstack-dev] [cinder] Update Ping List for Weekly Meeting ...

All, Just wanted to communicate the fact that I have cleaned out the ping list for our weekly team meeting.  I shared this in yesterday's team meeting but also wanted to communicate it here for those who missed the meeting. The new list is in our new meeting agenda etherpad [1] .  If you

Re: [openstack-dev] [infra] Unable to add member to Zun core team

Hi Infra Team, I'm Kien Nguyen . Actually, the older account with id 22406 is my current account and the newer is not. Therefore, please mark the newer account (26112) as inactive and re-active the 22406 account. Sorry for this inconvenient. Best regards, Kien Nguyen

[openstack-dev] Janney 2.0 "Data Protection in OpenStack" Summary Presentation

Hi everyone, I will be presenting a recap of the "Data Protection in OpenStack" presentation from IEEE CLOUD on Monday, September 25th at 4 PM in Central Spark. The OpenStack team wrote the paper, and the funding came from the Janney 2.0 "Engage" awards.

Re: [openstack-dev] [tc][nova][mogan] How to show respect to the original authors?

On 15:56 Sep 20, Flavio Percoco wrote: > On 20/09/17 12:21 +, Jeremy Stanley wrote: > > On 2017-09-20 07:51:29 -0400 (-0400), Davanum Srinivas wrote: > > [...] > > > please indicate which file from Nova, so if anyone wanted to cross > > > check for fixes etc can go look in Nova > > [...] > >

[openstack-dev] Fwd: [k8s][deployment][kolla-kubernetes][magnum][kuryr][qa][api] Proposal for SIG-K8s

In preparation for the Sydney Forum, I’ve created a brainstorming etherpad for forum topics. Please contribute topics as you see fit, and from there we can start making some submissions. https://etherpad.openstack.org/p/sig-k8s-sydney-forum-topics

Re: [openstack-dev] [infra] Unable to add member to Zun core team

On 2017-09-21 02:55:13 + (+), Hongbin Lu wrote: > I tried to add Kien Nguyen > kie...@vn.fujitsu.com to the Zun's > core team [1], but gerrit prevented me to do that. Attached file > showed the error. Could anyone provide suggestion for this? Kien has

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

On 17-09-21 12:13:23, Doug Hellmann wrote: > Excerpts from Tony Breeds's message of 2017-09-21 08:36:39 -0400: > > On Wed, Sep 20, 2017 at 06:08:22PM -0400, Doug Hellmann wrote: > > > > > I like the idea. I'm not sure why, if the constraints file is only used > > > for the dependency installation

Re: [openstack-dev] [requirements][stable] publish upper-constraints.txt periodic vs post

On 17-09-21 12:09:52, Doug Hellmann wrote: > Excerpts from Matthew Thode's message of 2017-09-21 10:43:50 -0500: > > On 17-09-20 14:09:15, Tony Breeds wrote: > > > On Wed, Sep 20, 2017 at 01:43:51PM -0400, Tony Breeds wrote: > > > > > > > The solution I thought we decide on at the PTG is: > > > >

[openstack-dev] [glance] priorities for the week (09/21-09/27)

Hello Glancers, As discussed at today's Glance weekly meeting, priorities are: 1 patches associated with Q-1 milestone targeted bugs https://launchpad.net/glance/+milestone/queens-1 2 specs https://review.openstack.org/#/q/status:open+project:openstack/glance-specs Have a productive

Re: [openstack-dev] [ptg] Simplification in OpenStack

On 2017-09-20 17:39:38 -0700 (-0700), Clint Byrum wrote: [...] > Something about common use cases and the exact mix of > projects + configuration to get there, and testing it? Help? [...] Maybe you're thinking of the "constellations" suggestion? It found its way into the TC vision statement,

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

Excerpts from Tony Breeds's message of 2017-09-21 08:36:39 -0400: > On Wed, Sep 20, 2017 at 06:08:22PM -0400, Doug Hellmann wrote: > > > I like the idea. I'm not sure why, if the constraints file is only used > > for the dependency installation step, we still need tox_install.sh? > > Right now

[openstack-dev] [os-vif] [passthrough] [VifHostDevice]

Hi, We have a SRIOV capable NIC that supports OVS offload and Switchdev. We are trying to test the VifHostDevice model on a Pike cluster. We are running into issues. Here are the config options that we have used: 1. In Neutron conf file: mechanism driver = ovn 2. In Nova conf file:

Re: [openstack-dev] [requirements][stable] publish upper-constraints.txt periodic vs post

Excerpts from Matthew Thode's message of 2017-09-21 10:43:50 -0500: > On 17-09-20 14:09:15, Tony Breeds wrote: > > On Wed, Sep 20, 2017 at 01:43:51PM -0400, Tony Breeds wrote: > > > > > The solution I thought we decide on at the PTG is: > > > * Add a post job to all branches that publish a

Re: [openstack-dev] [TripleO] TripleO/Ansible PTG session

On Thu, Sep 21, 2017 at 3:53 PM, Jiří Stránský wrote: > On 21.9.2017 12:31, Giulio Fidente wrote: > >> On 09/20/2017 07:36 PM, James Slagle wrote: >> >>> On Tue, Sep 19, 2017 at 8:37 AM, Giulio Fidente >>> wrote: >>> On 09/18/2017 05:37 PM, James

Re: [openstack-dev] [requirements][stable] publish upper-constraints.txt periodic vs post

On 17-09-20 14:09:15, Tony Breeds wrote: > On Wed, Sep 20, 2017 at 01:43:51PM -0400, Tony Breeds wrote: > > > The solution I thought we decide on at the PTG is: > > * Add a post job to all branches that publish a constraints/$series.txt > >to $server (I don't mind if it's releases.o.o or

Re: [openstack-dev] [oslo][oslo.service] looping.RetryDecorator behavior

It does look like is sort of a bug, Though in all honesty I wouldn't be using oslo.service or that looping code in the future for doing retrying... https://pypi.python.org/pypi/tenacity is a much better library with more `natural` syntax and works more as one would expect (even under

Re: [openstack-dev] [skip-level-upgrades][fast-forward-upgrades] PTG summary

Sean Dague wrote: > Agreed. We're already at 5 upgrade tags now? > > I think honestly we're going to need a picture to explain the > differences between them. Based on the confusion that kept seeming to > come during discussions at the PTG, I think we need to circle around and > figure out if

Re: [openstack-dev] [TripleO] TripleO/Ansible PTG session

On 21.9.2017 12:31, Giulio Fidente wrote: On 09/20/2017 07:36 PM, James Slagle wrote: On Tue, Sep 19, 2017 at 8:37 AM, Giulio Fidente wrote: On 09/18/2017 05:37 PM, James Slagle wrote: - The entire sequence and flow is driven via Mistral on the Undercloud by default.

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

On Wed, Sep 20, 2017 at 06:08:22PM -0400, Doug Hellmann wrote: > I like the idea. I'm not sure why, if the constraints file is only used > for the dependency installation step, we still need tox_install.sh? Right now that isn't true, when we get something like my idea implemented we'd still need

Re: [openstack-dev] [docs][ptls][install] Install guide vs. tutorial

> For me, a tutorial is something that teaches. So after I've gone through a > tutorial I would expect to have learned how installs work and would just know > these things (with an occasional need to reference a few points) going forward. > > A guide to me is something that I

[openstack-dev] [oslo][oslo.service] looping.RetryDecorator behavior

Hi Oslo team, Can you please check the bug [1]? There may be a problem with how looping.RetryDecorator works. Just stumbled on it in Mistral. Not sure if it’s really a bug or made by design. If it’s by design then maybe we need to have more accurate documentation for it. FYI: We use this

Re: [openstack-dev] [TripleO] TripleO/Ansible PTG session

On 09/20/2017 07:36 PM, James Slagle wrote: > On Tue, Sep 19, 2017 at 8:37 AM, Giulio Fidente wrote: >> On 09/18/2017 05:37 PM, James Slagle wrote: >>> - The entire sequence and flow is driven via Mistral on the Undercloud >>> by default. This preserves the API layer and

[openstack-dev] [doc][meeting] Doc team meeting cancelled today

Hi everyone, The documentation team meeting is cancelled today as I am unable to host this afternoon due to a conflict, and Petr is travelling home from the PTG. The next documentation team meeting will be scheduled in #openstack-meeting at 16:00 UTC, 5 October 2017. Petr has asked me to

Re: [openstack-dev] [nova] About live-resize spec

Hello, I am willing to restart working on it, if it actually has a chance of getting approved. Last time, the spec got 2 x +2's and ~12 +1's [1]. I don't know how soon the capabilities thing can become a real thing, but IMO, we can go with Matt's suggestion of disabling the feature by default

Re: [openstack-dev] [TripleO] TripleO/Ansible PTG session

st 20. 9. 2017 v 19:37 odesílatel James Slagle napsal: > On Tue, Sep 19, 2017 at 8:37 AM, Giulio Fidente > wrote: > > On 09/18/2017 05:37 PM, James Slagle wrote: > >> - The entire sequence and flow is driven via Mistral on the Undercloud > >> by