Re: [openstack-dev] [Openstack-operators] [Openstack-sigs] Dropping lazy translation support

I seem to recall list discussion on this quite a ways back. I think most of it happened on the Docs ml, though. Maybe Juno/Kilo timeframe? If possible, it would be good to search over the code bases for places it was called to see its current footprint. I'm pretty sure it was the docs folks

Re: [openstack-dev] [Openstack-sigs] [goals][tc][ptl][uc] starting goal selection for T series

Oh, very definitely +1000 -- Rochelle Grober Rochelle Grober M: +1-6508889722(preferred) E: rochelle.gro...@huawei.com<mailto:rochelle.gro...@huawei.com> 2012实验室-硅谷研究所技术规划及合作部 2012 Laboratories-Silicon Valley Technology Planning & C

Re: [openstack-dev] [nova][placement][upgrade][qa] Some upgrade-specific news on extraction

Sounds like an important discussion to have with the operators in Denver. Should put this on the schedule for the Ops meetup. --Rocky > -Original Message- > From: Matt Riedemann [mailto:mriede...@gmail.com] > Sent: Thursday, September 06, 2018 1:59 PM > To: OpenStack Development Mailing

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

Zane Bitter wrote: > On 31/05/18 14:35, Julia Kreger wrote: > > Back to the topic of nitpicking! > > > > I virtually sat down with Doug today and we hammered out the positive > > aspects that we feel like are the things that we as a community want > > to see as part of reviews coming out of this

Re: [openstack-dev] [User-committee] [Forum] [all] [Stable] OpenStack is "mature" -- time to get serious on Maintainers -- Session etherpad and food for thought for discussion

minds for the discussion. And yes, this is a discussion to see if we are interested, and only if there is interest, how to move forward. --Rocky From: Lance Bragstad [mailto:lbrags...@gmail.com] Sent: Friday, May 18, 2018 2:03 PM To: Rochelle Grober <rochelle.gro...@huawei.com>; opensta

Re: [openstack-dev] [tc] [all] TC Report 18-20

Thierry Carrez [mailto:thie...@openstack.org] > > Graham Hayes wrote: > > Any additional background on why we allowed LCOO to operate like this > > would help a lot. > The group was started back when OPNFV was first getting involved with OpenStack. Many of the members came from that

[openstack-dev] [Forum] [all] [Stable] OpenStack is "mature" -- time to get serious on Maintainers -- Session etherpad and food for thought for discussion

collection of those who are already doing the job without title. Thanks and see you next week. --rocky 华为技术有限公司 Huawei Technologies Co., Ltd. [Company_logo] Rochelle Grober Sr. Staff Architect, Open Source Office Phone:408-330-5472 Email:rochelle.gro...@

Re: [openstack-dev] [tc] campaign question: How can we make contributing to OpenStack easier?

Doug Hellmann wrote: > I would like for us to collect some more data about what efforts teams are > making with encouraging new contributors, and what seems to be working or > not. In the past we've done pretty well at finding new techniques by > experimenting within one team and then adapting the

Re: [openstack-dev] Adding "not docs" banner to specs website?

It could be *really* useful if you could include the date (month/year would be good enough)of the last significant patch (not including the reformat to Openstackdocstheme). That could give folks a great stick in the mud for what "past" is for the spec. It might even incent some to see if

Re: [openstack-dev] [refstack] Full list of API Tests versus 'OpenStack Powered' Tests

Submission is no longer anonymous, but the results are not public, still. The submitter decides whether the guideline results are public, but if they do, only the guideline tests are made public. If the submitter does not actively select public availability for the test results, all results

Re: [openstack-dev] [DriverLog] DriverLog future

> -Original Message- > From: Matt Riedemann [mailto:mriede...@gmail.com] > Sent: Thursday, March 01, 2018 4:19 AM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [DriverLog] DriverLog future > > On 3/1/2018 10:44 AM, Ilya Shakhat wrote: > > > > For those who do

Re: [openstack-dev] [neutron] Stepping down from core

Armando, You’ve been great for Neutron. It’s sad to see you have to cut back, but it’s great to hear you aren’t totally leaving. Thank you for all of your hard work. You’ve brought Neutron along quite nicely. I’d also like to thank you for all of your help with the stadium projects. Your

Re: [openstack-dev] Help needed with Fusion SPhere

MISTAKE!!! Ooops. I’m sorry. Please ignore. --Rocky From: Rochelle Grober Sent: Monday, November 20, 2017 5:23 PM To: Farhad Sunavala <farhad.sunav...@huawei.com>; Zhiqiang Yang <zhiqiang.y...@huawei.com> Cc: OpenStack Development Mailing List (not for usage questions) &l

Re: [openstack-dev] Help needed with Fusion SPhere

. Thanks, --Rocky From: Farhad Sunavala Sent: Monday, November 20, 2017 4:54 PM To: Zhiqiang Yang <zhiqiang.y...@huawei.com> Cc: Rochelle Grober <rochelle.gro...@huawei.com> Subject: Help needed with Fusion SPhere Hi Rocky, Henry from SW lab wanted to know who has worked with Fusion Sp

Re: [openstack-dev] [Openstack-sigs] [Openstack-operators] [QA] Proposal for a QA SIG

First off, let me say I think this is a tremendous idea. And, it's perfect for the SIG concept. Next, see inline: Thierry Carrez wrote: > Andrea Frittoli wrote: > > [...] > > during the last summit in Sydney we discussed the possibility of > > creating an OpenStack quality assurance special

Re: [openstack-dev] [Openstack-operators] [LTS] Upstream LTS Releases

> -Original Message- > From: Erik McCormick [mailto:emccorm...@cirrusseven.com] > Sent: Tuesday, November 14, 2017 4:25 PM > To: Rochelle Grober <rochelle.gro...@huawei.com> > Cc: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@list

Re: [openstack-dev] Upstream LTS Releases

Folks, This discussion and the people interested in it seem like a perfect application of the SIG process. By turning LTS into a SIG, everyone can discuss the issues on the SIG mailing list and the discussion shouldn't end up split. If it turns into a project, great. If a solution is found

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

Clint Byrum wrote: > Excerpts from Jonathan Proulx's message of 2017-09-26 16:01:26 -0400: > > On Tue, Sep 26, 2017 at 12:16:30PM -0700, Clint Byrum wrote: > > > > :OpenStack is big. Big enough that a user will likely be fine with > > learning :a new set of tools to manage it. > > > > New users in

Re: [openstack-dev] [docs] [ptls] Install guide testing

Might I suggest a PTG activity such as an evening docathon? Drinks and Docs Everyone welcome to locate in some convenient location to review/test docs, converse and plan for the next dev cycle with Docs folks. It might not be doable at this late date for Pike, but I suspect there may be some

Re: [openstack-dev] [all][tc] Wiki

And I'd just like to point out, when was the last time you tried to find info contained in some etherpad on our etherpad server without having the etherpad's exact name? Either searched for a specific etherpad or for info you knew was somewhere on an etherpad somewhere on the

Re: [openstack-dev] [nova][placement] Add API Sample tests for Placement APIs

Thanks for the clarification. Yeah. No interop interaction to see here. These are not the api's you are looking for;-) I think Chris Dent's response about extending the gabbi based tests is great. I'm a firm believer in never discouraging anyone from writing more tests, especially when

Re: [openstack-dev] [nova][placement] Add API Sample tests for Placement APIs

> From: Matt > On 6/21/2017 7:04 AM, Shewale, Bhagyashri wrote: > > I would like to write functional tests to check the exact req/resp > > for each placement API for all supported versions similar > > > > to what is already done for other APIs under > >

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

OK. So, our naming is like branding. We are techies -- not good at marketing. But, gee, the foundation has a marketing team. And they end up fielding a lot of the confusing questions from companies not deeply entrenched in the OpenStack Dev culture. Perhaps it would be worth explaining

Re: [openstack-dev] [Product] PTG attendance

In many ways, having the PWG at the PTG is a great idea. The only problem with that is that the PWG and the InteropWG would overlap in the current way the PTG is arranged. Having both at the same place is great for synergy, but having them at the same times is not :( We actually have a

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

From: Ildiko > On 2017. May 23., at 15:43, Sean McGinnis > wrote: > > > > On Mon, May 22, 2017 at 05:50:50PM -0500, Anne Gentle wrote: > >> On Mon, May 22, 2017 at 5:41 PM, Sean McGinnis > >> > >> wrote: > >> > >>> > >>> [snip] > >>> > >> > >> Hey

[openstack-dev] Summary of BOS Summit session: User API Improvements

and multi cloud 华为技术有限公司 Huawei Technologies Co., Ltd. [Company_logo] Rochelle Grober Sr. Staff Architect, Open Source Office Phone:408-330-5472 Email:rochelle.gro...@huawei.com  本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁 止任何其他人以任何形式使用

Re: [openstack-dev] [nova] [cinder] Follow up on Nova/Cinder summit sessions from an ops perspective

From: Duncan Thomas > On 18 May 2017 at 22:26, Rochelle Grober <rochelle.gro...@huawei.com> > wrote: > > If you're going to use --distance, then you should have specific values > (standard definitions) rather than operator defined: > > And for that matter, is there som

Re: [openstack-dev] [nova] [cinder] Follow up on Nova/Cinder summit sessions from an ops perspective

From: Matt Riedemann > On 5/15/2017 2:28 PM, Edmund Rhudy (BLOOMBERG/ 120 PARK) wrote: > > Hi all, > > > > I'd like to follow up on a few discussions that took place last week > > in Boston, specifically in the Compute Instance/Volume Affinity for > > HPC session > >

Re: [openstack-dev] All Hail our Newest Release Name - OpenStack Rocky

I arrive Sunday afternoon and leave Friday morning, so you can bracket and schedule your drink buying ;-) My view of Rocky is that of a *solid* base to build on. One that withstands the ravages of storms and squalls. So, I look forward to helping to reinforce and expand the stability of

[openstack-dev] Boston Summit Forum and working session Log messages (please comment and participate)

华为技术有限公司 Huawei Technologies Co., Ltd. [Company_logo] Rochelle Grober Sr. Staff Architect, Open Source Office Phone:408-330-5472 Email:rochelle.gro...@huawei.com  本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁 止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散

Re: [openstack-dev] [scientific][nova][cyborg] Special Hardware Forum session

I know that some cyborg folks and nova folks are planning to be there. Now we need to drive some ops folks. Sent from HUAWEI AnyOffice From:Blair Bethwaite To:openstack-dev@lists.openstack.org,openstack-oper. Date:2017-04-25 08:24:34 Subject:[openstack-dev] [scientific][nova][cyborg] Special

Re: [openstack-dev] [tc] [elections] Available time and top priority

Matt Riedemann, Monday, April 10, 2017 1:41 PM On 4/10/2017 2:55 PM, Dean Troyer wrote: > > The TC meetings are held in IRC and that may somewhat mitigate the > issue for non-native English speakers, but I've had problems myself > keeping up at times with the flurry of comments. In any case,

Re: [openstack-dev] [shade] help wanted - tons to do, not enough people

On April 14, 2017 1:23 PM Jay Pipes wrote: On 04/12/2017 02:15 PM, Sean Dague wrote: > On 04/12/2017 01:38 PM, Monty Taylor wrote: >> On 04/12/2017 11:21 AM, Joshua Harlow wrote: >>> Just a question, not meant as anything bad against shade, >>> >>> But would effort be better spent on

Re: [openstack-dev] [ironic] New contributor

Welcome! And, of course, writing tests that demonstrate some of those more difficult open bugs would help make sure they don't resurface once fixed ;-) so, if you can't get a handle yet on the intricacies of the the code that contains the issue, you still might be able to demonstrate the

Re: [openstack-dev] [i18n] [nova] understanding log domain change - https://review.openstack.org/#/c/439500

Sorry for top posting, but this is likely the best place... I wanted to provide an update from the Ops midcycle about related topics around this. The operators here are in general agreement that translation is not needed, but they are also very interested in the possibility of getting some of

Re: [openstack-dev] Refstack - final mascot

Looks great to me. --Rocky From: Catherine Cuong Diep [mailto:cd...@us.ibm.com] Sent: Monday, February 06, 2017 4:25 PM To: OpenStack Dev Mailer Subject: [openstack-dev] Refstack - final mascot Hello RefStack team, Please see RefStack mascot in Heidi's note

Re: [openstack-dev] [ironic] New mascot design

Well, uh, how about Jazz hands? Open, waving hands are pretty universally friendly and it would look more like a dancing bear which brings the music aspect bac a bit. Sorry for butting in, but I couldn resist... --Rocky -Original Message- From: Miles Gould [mailto:mgo...@redhat.com]

Re: [openstack-dev] [infra][qa][glance] gate-tempest-dsvm-full-ceph-plugin-src-glance_store-ubuntu-xenial failures

There was a driver thread about snapshot management test failures. It appears there is a config option that changed for devstack from false to true, causing the cinder drivers all sorts of issues. Here is the email that discusses the change and its effects on cinder drivers:

Re: [openstack-dev] PTG? / Was (Consistent Versioned Endpoints)

YEES! -Original Message- From: Tom Fifield [mailto:t...@openstack.org] Sent: Monday, January 16, 2017 3:48 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] PTG? / Was (Consistent Versioned Endpoints) On 14/01/17 04:07, Joshua Harlow wrote: > > Sometimes I almost

Re: [openstack-dev] [release] change in plan for releases repo data model updates

Sorry for top posting, but exchange Automation is our friend. Define the structure/naming of the release repo patches such that when they merge, they auto generate the governance patch and submit it. It gives you time to run a cycle and see how things work and what a more elegant

Re: [openstack-dev] [keystone][tripleo][ansible][puppet][all] changing default token format

a blog post on the OpenStack sore might be good. superuser? there are folks reading this who can help Sent from HUAWEI AnyOffice From:Lance Bragstad To:OpenStack Development Mailing List (not for usage questions),openstack-operat...@lists.openstack.org, Date:2016-11-03 08:11:20 Subject:Re:

Re: [openstack-dev] [release] proposing adding Tony Breeds to "Release Managers" team

I have no vote, but my nonvote is a hearty +1 Tony is amazing. --Rocky -Original Message- From: Amrith Kumar [mailto:amr...@tesora.com] Sent: Tuesday, September 06, 2016 10:56 AM To: d...@doughellmann.com Cc: OpenStack Development Mailing List (not for usage questions) Subject: Re:

Re: [openstack-dev] [nova] Next steps for proxy API deprecation

Thank you, Doug. Yes, if the DefCore guidelines have any of these tests, the tests used by DefCore will need to be run beyond EOL of Newton as the DefCore tests last longer than the EOL timeframe. But, first we should check which tests need to be capped and whether they are part of a/some

Re: [openstack-dev] [gnocchi] typical length of timeseries data

Just an FYI that might be the reason for the 14400: 1440 is the number of minutes in a day. 14400 would be tenths of minutes in a day of number of 6second chunks (huh???) So, the number was picked to divide files in human logical, not computer logical chunks. --Rocky -Original

Re: [openstack-dev] [Openstack-operators] [nova] Rabbit-mq 3.4 crashing (anyone else seen this?)

repository is: http://git.openstack.org/cgit/openstack/osops-tools-contrib/ FYI, there are also: osops-tools-generic, osops-tools-logging, osops-tools-monitoring, osops-example-configs and osops-coda Wish I could help more, --Rocky -Original Message- From: Joshua Harlow

Re: [openstack-dev] [release] Invitation to join Hangzhou Bug Smash

Perhaps the right way to schedule these bug smashes is to do it at the same time as the release scheduling is determined. Decide on a fixed time within the release cycle (it's been just after M3/feature freeze a few times) and when the schedule is put together, the bugsmash is part of the

Re: [openstack-dev] [higgins] Should we rename "Higgins"?

Well, you could stick with the wine bottle analogy and go with a bigger size: Jeroboam Methuselah Salmanazar Balthazar Nabuchadnezzar --Rocky -Original Message- From: Kumari, Madhuri [mailto:madhuri.kum...@intel.com] Sent: Wednesday, June 01,

Re: [openstack-dev] Timeframe for naming the P release?

But, the original spelling of the landing site is Plimoth Rock. There were still highway signs up in the 70's directing folks to "Plimoth Rock" --Rocky Who should know about rocks ;-) -Original Message- From: Brian Haley [mailto:brian.ha...@hpe.com] Sent: Monday, May 02, 2016 3:12 PM

Re: [openstack-dev] [Congress] Issues with Tox testing

Bryan, Check out refstack.openstack.org and https://github.com/openstack/refstack The refstack project provides a client which enables anyone to run tempest tests on their own clouds. It is flexible, with options for selecting all or specific test sets, or specific tests and also has an

Re: [openstack-dev] [OpenStack-DefCore] [defcore][glance] Glare not defcore ready

Hi folks. I'm chiming in here from a systems engineering perspective. I recently discovered that OpenStack-client is trying to build cross-project consistency into its design. As such, it is opinionated, but this is good. The glance team might consider also consulting the OSC team to ensure

Re: [openstack-dev] Floating IPs and Public IPs are not equivalent

Cross posting to the Ops ML as one/some of them might have a test cloud like this. Operators: If you respond to this thread, please only respond to the openstack-dev list? They could use your input;-) --Rocky -Original Message- From: Sean Dague [mailto:s...@dague.net] Sent:

Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint?

(Inline because the mail formatted friendly this time) From: Tim Bell March 17, 2016 11:26 AM: On 17/03/16 18:29, "Sean Dague" wrote: >On 03/17/2016 11:57 AM, Markus Zoeller wrote: > >> Suggested action items: >> >> 1. I close the open wish list items older than 6 months (=138

Re: [openstack-dev] [stable] Proposing Tony Breeds for stable-maint-core

+1 Here's another not counting vote and cheer! --Rocky +1 for Tony! (my vote does not count, but still wanted to cheer!) -- Dims On Fri, Mar 18, 2016 at 4:38 PM, Anita Kuno wrote: > On 03/18/2016 04:11 PM, Matt Riedemann wrote: >> I'd like to propose tonyb for

Re: [openstack-dev] [QA][all] Propose to remove negative tests from Tempest

(Sorry for the top post. It was this or bottom post because of company choice of email systems) Integration tests, corner cases, negative tests. Lots of names that don't have clear definitions in this discussion. But, it seems like the collection of "negative tests" include both functional

Re: [openstack-dev] [nova] config options help text improvement: current status

Don't quote me on this, but the tool that generates the dev docs is the one the docs team for the config ref use to generate that document. And they have been looped in on the upcoming improvements. --Rocky -Original Message- From: Matthew Treinish [mailto:mtrein...@kortar.org] Sent:

Re: [openstack-dev] [oslo] nominating Ronald Bradford for oslo-core

I'm not a voting member of the Oslo team, but a BIG +1 >From me. --Rocky -Original Message- From: Joshua Harlow [mailto:harlo...@fastmail.com] Sent: Thursday, January 28, 2016 11:38 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [oslo]

Re: [openstack-dev] [nova][glance][cinder][neutron]How to make use of x-openstack-request-id

At the Tokyo summit, there was a working session that addressed how to log the request-id chain. The etherpad for that is [0] A spec needs to be written and implementation details need some hashing out, but the approach should provide a way to track the originating request through each logged

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

Devananda van der Veen, on January 21, 2016 5:14 PM wrote: On Wed, Jan 20, 2016 at 9:53 AM, Flavio Percoco > wrote: Greetings, At the Tokyo summit, we discussed OpenStack's development themes in a cross-project session. In this session a group of

Re: [openstack-dev] [stable] meeting time proposal

Any chance you could make the Monday meeting a few hours later? Japan and China are still mostly in bed then, but two hours would allow both to participate. --Rocky > -Original Message- > From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] > Sent: Wednesday, December 16, 2015

Re: [openstack-dev] [stable] Stable team PTL nominations are open

Congratulations, Matt! Condolences to Erno, but he's already said he's still part of the team. I'm looking forward to the IRC meetings and and also what the team becomes. --Rocky > -Original Message- > From: Anita Kuno [mailto:ante...@anteaya.info] > Sent: Wednesday, December 09, 2015

Re: [openstack-dev] [openstack][openstack-operators] IRC meeting(s)

++ > -Original Message- > From: Thierry Carrez [mailto:thie...@openstack.org] > Sent: Thursday, November 19, 2015 1:52 AM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [openstack][openstack-operators] IRC > meeting(s) > > JJ Asghar wrote: > > I've been seeing

Re: [openstack-dev] [all]Can we get some sanity in the Neutron logs please?

Thanks both Armando and Matt! I am cross posting this to the operators' list (as the main post -- operators, simple reply and no spam to dev). The logging tag should be a tag in all projects. I'm glad it's already there in Neutron. And, this sort of feedback is exactly what we need operators

[openstack-dev] [release][stable] OpenStack 2014.2.4 (juno)

Again, my plea to leave the Juno repository on git.openstack.org, but locked down to enable at least grenade testing for Juno->Kilo upgrades. For upgrade testing purposes, python2.6 is not needed as any cloud would have to upgrade python before upgrading to kilo. The testing could/should be

Re: [openstack-dev] [stable] Preparing 2014.2.4 (Juno) WAS Re: [Openstack-operators] [stable][all] Keeping Juno "alive" for longer.

I would like to make a plea that while Juno is locked down so as no changes can be made against it, the branch remains on the git.openstack.org site. Please? One area that could be better investigated with the branch in place is upgrade. Kilo will continue to get patches, as will Liberty, so

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

+1 I think that as OpenStack's customer base grows, this is going to become more and more important, and will get the pain of users not getting updates will increase enough that there *will* be a group of engineers willing to do not only backports and releases, but bugfixes in trunk and gate

[openstack-dev] Logging sessions at the Tokyo summit -- Let's get serious!

Hey operators and other users (and devs), We've got a number of logging sessions scheduled for the Summit. I'm collecting up information on the summit logging etherpad: https://etherpad.openstack.org/p/TYO-ops-logging and it will get fleshed out a lot more during the flight;-) Two goals of

Re: [openstack-dev] [all] FYI - Depends-On vs. backports

Could you put this in the devref? Or getting started or something so this info isn't lost and new devs will be educated? Thanks! --Rocky > -Original Message- > From: Sean Dague [mailto:s...@dague.net] > Sent: Tuesday, October 13, 2015 2:44 AM > To: openstack-dev@lists.openstack.org >

Re: [openstack-dev] [tc] naming N and O releases nowish

> -Original Message- > From: Anita Kuno [mailto:ante...@anteaya.info] > Sent: Wednesday, October 07, 2015 3:48 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [tc] naming N and O releases nowish > > On 10/07/2015 06:22 PM, Monty Taylor wrote: > > On 10/07/2015

[openstack-dev] [election][TC] Candidacy

Hello People! I am tossing one of my hats into the ring to run for TC. Yes, I believe you could call me a "diversity candidate" as I'm not much of a developer any more, but I think my skills would be a great addition to the excellent people who are on the TC (past and present). My background:

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

Doug Hellmann wrote: Excerpts from Mark Voelker's message of 2015-09-25 17:42:24 +: > On Sep 25, 2015, at 1:24 PM, Brian Rosmaita > wrote: > > > > I'd like to clarify something. > > > > On 9/25/15, 12:16 PM, "Mark Voelker" wrote: > >

Re: [openstack-dev] [searchlight] Liberty release planning video conference

Just wanted to point out that if you dig a little in Postman's website, it looks like all the base code is on github, and appears to be under the Apache license. I didn't check the jetpacks, but I suspect those might be proprietary bits. Tripp, Travis S wrote on Monday, August 10, 2015

Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

In line (at the bottom) From: Devananda van der Veen [mailto:devananda@gmail.com] Sent: Friday, June 19, 2015 12:40 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header On Wed, Jun 17, 2015 at 7:31 AM

Re: [openstack-dev] [devstack] apache wsgi application support

Adam pointed to this url as a proposal for the namespaces: https://wiki.openstack.org/wiki/URLs How about this gets turned into a cross project spec or part of a larger one with the stuff in this ML thread? Then we can get the projects aware and buying into this little slice of sanity. --Rocky

Re: [openstack-dev] stackforge projects are not second class citizens

I'd also like to point out that if the state of the projects has encouraged *new* contributors to OpenStack, then their contributions will likely take a couple to a few months to become visible in a significant way in the statistics. Two to three months to get your first merge is extremely

Re: [openstack-dev] [api] [Nova] [Ironic] [Magnum] Microversion guideline in API-WG

Just want to add that for logging purposes, consistency, as Devananda explains and Adrian and Sean agree, is really important. The number of fields in a header response should be consistent. If the field is not always used, a placeholder should be put in (usually a “-“ in logs). Makes parsing

Re: [openstack-dev] [all] error codes design conclusion?

Spec is in the works but needs to be reworked a bit more. It’s under Openstack-specs. I’m revamping it, but I’m taking vacation until Monday, so you won’t see the new patch until at least next week. You are welcome to comment on the current version, though:

Re: [openstack-dev] [Neutron][LBaaS] Jenkins CI failure for patch: https://review.openstack.org/180019

Madhu, There have been problems with Gerrit all day. And, trying the link to you review, the service is now down. Consider letting the infra folks work the problem some more, look for a posting from them, or watch the topic messages on IRC and hold off on resubmitting until you see an all

Re: [openstack-dev] [RefStackl] - http://refstack.org/ - does not resolve

The Refstack team is working with Infra to get refstack.org up in a vm under Infra's purview. Right now, the demo is on refstack.net refstack.net will go away once refstack.org is up and managed. --rocky -Original Message- From: Jeremy Stanley [mailto:fu...@yuggoth.org] Sent:

Re: [openstack-dev] [Nova][Neutron] Linuxbridge as the default in DevStack [was: Status of the nova-network to Neutron migration work]

I know the DevStack issue seems to be solved, but I had to respond.inline From: Fox, Kevin M [mailto:kevin@pnnl.gov] Sent: Friday, April 17, 2015 12:28 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Nova][Neutron] Linuxbridge as the default

Re: [openstack-dev] [Nova][Neutron] HELP -- Please review some Kilo bug fixes

Open Reviews from the etherpad: Nova(lots), Neutron(2), Keystone(2), Glance(1), Ironic/DevStack(1) reviews I went through, checked all the reviews listed and put a notation on state of the patches, next steps, etc. Take another look. (my comments are medium blue). Some reviews are ready for

Re: [openstack-dev] [all] [api] [log] Erring is Caring

Hi all, The first draft of the spec for Log Message Error Codes (from the Log Working Group) is out for review: https://review.openstack.org/#/c/172552/ Please comment, and please look for the way forward so that the different places, ways and reasons errors get reported provide consistency

Re: [openstack-dev] [OpenStack-Dev] [third-party-ci] Clarifications on the goal and skipping tests

Top posting… I believe the main issue was a problem with snapshots that caused false negatives for most cinder drivers. But, that got fixed. Unfortunately, we haven’t yet established a good process to notify third parties when skipped tests are fixed and should be “unskipped”. Maybe tagging

Re: [openstack-dev] Beyond IRC (was Re: Cinder Third-Party CI: what next?)

Mike Perez on March 24, 2015 16:39 wrote: On 15:13 Tue 24 Mar , Stefano Maffulli wrote: On Tue, 2015-03-24 at 19:01 +, Rochelle Grober wrote: *Somehow queueing requests in the IRC channel so that offline developers can easily find review requests when looking at channel logs

Re: [openstack-dev] [nova][api] Microversions. And why do we need API extensions for new API functionality?

Jeremy Stanley on March 24, 2015 07:28 wrote: On 2015-03-24 10:10:07 -0400 (-0400), Jay Pipes wrote: [...] I'm really not a fan of the Defcore effort. This should come as no surprise to anyone. I've been quite blunt about my disdain for the focus on identifying which API things are mandatory

Re: [openstack-dev] [OpenStack-DefCore] [nova][api] Microversions. And why do we need API extensions for new API functionality?

Forwarded from Rob Hirschfeld, Co-chair of DefCore committee -Original Message- From: Rob Hirschfeld [mailto:r...@zehicle.com] Sent: Tuesday, March 24, 2015 18:50 To: Rochelle Grober; OpenStack Development Mailing List (not for usage questions) Cc: defcore-commit

Re: [openstack-dev] Cinder Third-Party CI: what next? (was Re: [cinder] Request exemption for removal of NetApp FC drivers (no voting CI))

help not just Third Party developers, but all of OpenStack and make the community more inviting to Asian and Australian (and maybe European and African) developers. --Rocky From: Rochelle Grober [mailto:rochelle.gro...@huawei.com] Sent: Monday, March 23, 2015 14:51 To: OpenStack Development Mailing

Re: [openstack-dev] Cinder Third-Party CI: what next? (was Re: [cinder] Request exemption for removal of NetApp FC drivers (no voting CI))

I’d like to suggest that the myriad wiki pages and spreadsheets for Third Party CI also be consolidated to a more manageable count. Just looking for maintainers contact, you can find information (often conflicting) in Stackalytics, on the ThirdPartyDrivers page, on the Cinder PTL’s google doc

Re: [openstack-dev] [cinder] Request exemption for removal of NetApp FC drivers (no voting CI)

Ditto for Huawei. While we are not *reliably* reporting, we are reporting and the necessary steps have already been taken (and more importantly, approved) to get this reliably working ASAP. We respectfully request the same consideration for our cinder drivers. --Rocky (as proxy for Liu

Re: [openstack-dev] [puppet] Moving under the big tent

Emilien Macchi [mailto:emil...@redhat.com] on Monday, March 16, 2015 09:00 wrote: On 03/16/2015 11:13 AM, Colleen Murphy wrote: This thread is to follow up on our IRC discussion today. In today's meeting we started discussing whether we want to pursue applying to move under the OpenStack

[openstack-dev] [log] Log working group -- Alternate moderator needed for today

Or Cancellation. I'm in the Ops Midcycle meeting and can't guarantee I can join. Meeting meets Wednesdays at 20:00UTC, which is now 11am PDT. --Rocky __ OpenStack Development Mailing List (not for usage questions)

[openstack-dev] [all][log][api] Reminder: Log Working Group meeting 3/4/2015 -- Wednesday 20:00UTC

Log Working Group is a cross project (horizontal) and community group that is working to rationalize log messages and logging practices across the OpenStack ecosystem. This has been identified as a big concern within the user communities. Anyone with an interest in improving logs, logging and

Re: [openstack-dev] [nova] Shared storage support

-Original Message- From: Jay Pipes Sent Monday, March 02, 2015 16:24 On 02/25/2015 06:41 AM, Daniel P. Berrange wrote: On Wed, Feb 25, 2015 at 02:08:32PM +, Gary Kotton wrote: I understand that this is a high or critical bug but I think that we need to discuss more on it and try

[openstack-dev] [all][log][api] Log Working Group meeting days/times -- Wednesdays 20:00UTC

The Log Working Group is a cross project (horizontal) and community group that is working to rationalize log messages and logging practices across the OpenStack ecosystem. This has been identified as a big concern within the user communities. Anyone with an interest in improving logs, logging

Re: [openstack-dev] [api][nova] Openstack HTTP error codes

Duncan Thomas [mailto:duncan.tho...@gmail.com] on Wednesday, February 04, 2015 8:34 AM wrote: The downside of numbers rather than camel-case text is that they are less likely to stick in the memory of regular users. Not a huge think, but a reduction in usability, I think. On the other hand

Re: [openstack-dev] [oslo][nova][cinder] removing request_utils from oslo-incubator

Doug, thanks for responding so quickly to this. I had flagged it and was searching for just this email. Ankit, thanks for raising the issue. It *is* key. I agree with Doug that this should be a cross-project spec. Right now, Glance is moving in this direction, but as many have seen on the

Re: [openstack-dev] [Product] [all][log] Openstack HTTP error codes

What I see in this conversation is that we are talking about multiple different user classes. Infra-operator needs as much info as possible, so if it is a vendor driver that is erring out, the dev-ops can see it in the log. Tenant-operator is a totally different class of user. These guys need

Re: [openstack-dev] [all][log] Openstack HTTP error codes

Hi folks! Changed the tags a bit because this is a discussion for all projects and dovetails with logging rationalization/standards/ At the Paris summit, we had a number of session on logging that kept circling back to Error Codes. But, these codes would not be http codes, rather, as others

Re: [openstack-dev] [api] Next meeting agenda

Ryan Brown [mailto:rybr...@redhat.com], January 29, 2015 7:29 AM wrote: On 01/29/2015 10:20 AM, Sean Dague wrote: On 01/29/2015 07:17 AM, Anne Gentle wrote: On Thu, Jan 29, 2015 at 4:10 AM, Thierry Carrez thie...@openstack.org mailto:thie...@openstack.org wrote: Everett Toews wrote:

[openstack-dev] [Cross Project][Log][Profiler] Specs are in review and need constructive feedback soonest

The Cross Project team meeting discussed the following specs today: * Discuss openstack-spec: log guidelines [1] * Discuss openstack-spec: OSProfiler [2] * Open discussion announcements [1] https://review.openstack.org/#/c/132552/ [2] https://review.openstack.org/#/c/134839/ For

[openstack-dev] [Refstack] Refstack mid cycle meet up in Santa Clara, CA Jan 12-14 2015

Refstack is having its midcycle F2F meetup January 12-14, 2015 in Santa Clara, CA Etherpad is: https://etherpad.openstack.org/p/refstack-january-2015-midcycle Everyone is welcome to join in, but please add your list to the etherpad if you will be attending in person. We are hoping to do a

  1   2   >