Re: [openstack-dev] [infra][neutron][nova] publish and update Gerrit dashboard link automatically

? References: [1] http://git.openstack.org/cgit/openstack-infra/system-config/tree/modules/openstack_project/manifests/static.pp Regards, Markus Zoeller (markus_z) __ OpenStack Development Mailing List (not for usage questio

[openstack-dev] [all] FYI: how-to subscribe to specific bug tags

://wiki.openstack.org/wiki/Nova/BugTriage#How_to_Subscribe_to_Tags Regards, Markus Zoeller (markus_z) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org

Re: [openstack-dev] [oslo][all] What would you like changed/fixed/new in oslo??

master/doc/source/generator.rst [2] https://github.com/openstack/oslo.config/blob/master/oslo_config/generator.py [3] https://bugs.launchpad.net/nova/+bug/1553231 Regards, Markus Zoeller (markus_z) __ OpenStack Development Mai

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

openstack.org/wiki/BugTriage#Task_9:_Deprecate_old_wishlist_bugs_.28bug_supervisors.29 [4] http://45.55.105.55:8082/bugs-dashboard.html#tabWishlist Regards, Markus Zoeller (markus_z) Rochelle Grober <rochelle.gro...@huawei.com> wrote on 03/18/2016 12:45:38 AM: > From: Rochelle Gro

Re: [openstack-dev] [new-project][gate]devstack-plugin-additional-pkg-repos

[2] http://lists.openstack.org/pipermail/openstack-dev/2015-November/079679.html > [3] https://review.openstack.org/#/c/289255/ > [4] http://lists.openstack.org/pipermail/openstack-dev/2016-January/083947.html > [attachment "signature.asc" deleted by Markus Zoeller/Germany/IBM] >

Re: [openstack-dev] [all][infra][ptls] tagging reviews, making tags searchable

eviews and search > them. The availability of the Gerrit "hashtags" (blog entries call them often "labels" or "tags"; not to confuse with git tags) got discussed in [1]. I still have the hope that they will come as I see great potential and flexibility in their usage

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

The correct tldr: TL;DR: Use the openstack-*ops* ML and discuss the most wanted RFEs at the summit? Markus Zoeller/Germany/IBM wrote on 03/17/2016 04:57:27 PM: > From: Markus Zoeller/Germany/IBM > To: "OpenStack Development Mailing List \(not for usage questions\)"

Re: [openstack-dev] [nova] working on bug reports; what blocks you?

AM > Subject: Re: [openstack-dev] [nova] working on bug reports; what blocks you? > > On Thu, Mar 17, 2016 at 03:28:48PM -0500, Matt Riedemann wrote: > > On 3/17/2016 11:41 AM, Markus Zoeller wrote: > > >What are the various reasons which block you to work on bug reports? >

Re: [openstack-dev] [nova] Reminder to move implemented nova specs from mitaka

effort during Newton to finish it. References: [1] https://blueprints.launchpad.net/nova/+spec/centralize-config-options Regards, Markus Zoeller (markus_z) __ OpenStack Development Mailing List (not for usage questions) Un

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

a stable and reliable product and preparation for the summit, so I have less time to review these changes. But you can always contact me in IRC. References: [1] https://blueprints.launchpad.net/nova/+spec/centralize-config-options-newton Regards, Markus Zoeller (markus_z) Markus Zoeller/Germany/IBM

[openstack-dev] [nova] working on bug reports; what blocks you?

to dig into the code. I'm asking this because I'm not sure what the main reasons are that our bug list is this huge (~1000 open bug reports). Maybe you have reasons which can be resolved or mitigated by me in my bug czar role. Let me know. Regards, Markus Zoeller (markus_z

Re: [openstack-dev] [nova] Identifying Mitaka release blockers

PM > Subject: Re: [openstack-dev] [nova] Identifying Mitaka release blockers > > On 3 March 2016 at 13:10, Markus Zoeller <mzoel...@de.ibm.com> wrote: > > We have now 11-15 days left [1] until it is planned to release the first > > release candidate. To provide a stable release,

Re: [openstack-dev] [nova] Reminder to move implemented nova specs from mitaka

Markus Zoeller/Germany/IBM wrote on 03/18/2016 11:46:01 AM: > From: Markus Zoeller/Germany/IBM > To: "OpenStack Development Mailing List \(not for usage questions\)" > <openstack-dev@lists.openstack.org> > Date: 03/18/2016 11:46 AM > Subject: Re: [opensta

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

kimming_duty [2] https://wiki.openstack.org/wiki/Nova/BugTriage#Tags [3] http://lists.openstack.org/pipermail/openstack-dev/2016-February/087161.html Regards, Markus Zoeller (markus_z) Thierry Carrez <thie...@openstack.org> wrote on 03/16/2016 11:26:14 AM: > From: Thierry Carrez <t

Re: [openstack-dev] [nova] Reminder to move implemented nova specs from mitaka

ova > specs from mitaka > > > > On 3/18/2016 5:46 AM, Markus Zoeller wrote: > > Matt Riedemann <mrie...@linux.vnet.ibm.com> wrote on 03/16/2016 09:49:06 > > PM: > > > >> From: Matt Riedemann <mrie...@linux.vnet.ibm.com> > >>

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

k Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev Regards, Markus Zoeller (markus_z) ___

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

016 09:37 AM, Chris Dent wrote: > > On Tue, 15 Mar 2016, Markus Zoeller wrote: > > > >> Long story short, I'm in favor of abandoning the use of "wishlist" > >> as an importance in bug reports to track requests for enhancements. > > > > While I'm

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

ubject: Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint? > > On Tue, 15 Mar 2016, Markus Zoeller wrote: > > > Long story short, I'm in favor of abandoning the use of "wishlist" > > as an importance in bug reports to track requests for enhancement

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

pinion" (a closed state) in [2], which does also make sense to me, as it is easy to query. Not sure who would do that though. References: [1] https://bugs.launchpad.net/nova/+bug/1556756 [2] https://bugs.launchpad.net/nova/+bug/1552786 Regards, Markus Zoeller (markus_z) __

Re: [openstack-dev] [all][oslo] config generator default overrides and namespaces

r+topic:bug/1551836 > [3] https://review.openstack.org/#/c/291904/ Thanks Doug and Robert for catching this and providing the fixes! Regarding potential backports: Do you have information if this is something which came up in a specific version in "oslo.config"? Regards, Markus Zoeller (ma

Re: [openstack-dev] [nova] bug status "incomplete" is *not* a closedstate.

Markus Zoeller/Germany/IBM@IBMDE wrote on 03/10/2016 11:06:24 AM: > From: Markus Zoeller/Germany/IBM@IBMDE > To: "OpenStack Development Mailing List" <openstack-dev@lists.openstack.org> > Date: 03/10/2016 11:07 AM > Subject: [openstack-dev] [nova] bug status "inc

Re: [openstack-dev] [nova] stuck review, mtu incorrectly set on vhost-user port prevents vm booting.

"mitaka-rc-potential" last Friday. The report is also on the priorities etherpad [1] and I informed our PTL John Garbutt to consider this before creating the stable branch. Hopefully some of the core reviewers will check your patch(es) today. References: [1] https://etherpad.opensta

[openstack-dev] [nova] bug status "incomplete" is *not* a closed state.

in a comment *what* is missing. Without this, a reassessment gets unneccessary hard [1]. Closed states are: "Invalid", "Opinion", "Won't Fix" and "Fix Released". References: [1] https://wiki.openstack.org/wiki/BugTriag

Re: [openstack-dev] [nova] patches that improve code quality

ing patches more visible and queryable could be to use a topic "refactoring" for them. Reviewers can then search for them if they decide to switch their focus to resolving technical debt. Regards, Markus Zoeller (markus_z) __

Re: [openstack-dev] [nova] bug reports and stable branches: tags or series?

nches: > tags or series? > > > > On 3/4/2016 6:27 AM, Markus Zoeller wrote: > > What's the story behind having the tags "in-stable-liberty" and > > "liberty-backport-potential" and also having the series target "liberty"? > > > > I didn

[openstack-dev] [nova] bugs team meeting: March 8th 2016 1800 UTC

/BugTriage#Weekly_bug_skimming_duty Regards, Markus Zoeller (markus_z) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http

Re: [openstack-dev] [bug-smash] Global OpenStack Bug Smash Mitaka

re you have to change that in case for Cinder, Neutron and so on. Thanks dims for your effort! References: [1] https://github.com/markuszoeller/openstack/tree/master/scripts/launchpad Regards, Markus Zoeller (markus_z) > -Original Message- > From: Markus Zoeller [mailto:mzoe

[openstack-dev] [nova] "DocImpact" => bug report

on't* need an update, "DocImpact" is not necessary. IOW, saying "DocImpact" is shorthand for "the manuals need to be updated". @(core-)reviewers: Please consider this also in the reviews of patches. References: [1] https://bugs.launchpad.net/no

Re: [openstack-dev] [nova][bugs] Weekly Status Report

, Markus Zoeller (markus_z) Markus Zoeller/Germany/IBM@IBMDE wrote on 11/06/2015 05:54:59 PM: > From: Markus Zoeller/Germany/IBM@IBMDE > To: "OpenStack Development Mailing List" <openstack-dev@lists.openstack.org> > Date: 11/06/2015 05:56 PM > Subject: [openstack-dev

[openstack-dev] [nova] bug reports and stable branches: tags or series?

he history behind it. Regards, Markus Zoeller (markus_z) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-

Re: [openstack-dev] [oslo][all] Documenting configuration optionslifespan

o_config/cfg.py#n636 Right now I have trouble to paint a picture in my head how this will look like in the end. Could you provide a mockup of the resulting artifact? I also don't fully understand how the ops would work with that artifact. Could you describe an example workflow?

[openstack-dev] [docs] Can we get the "configuration reference" of master more often?

enstack-nova.2016-03-03.log.html#t2016-03-03T13:40:15 [3] http://eavesdrop.openstack.org/irclogs/%23openstack-doc/%23openstack-doc.2016-03-03.log.html#t2016-03-03T13:51:15 [4] https://github.com/openstack/openstack-doc-tools/tree/master/autogenerate_config_docs Regards, Mark

[openstack-dev] [nova] Identifying Mitaka release blockers

g/mitaka/schedule.html#m-rc1 [2] https://bugs.launchpad.net/nova/+bugs?field.tag=mitaka-rc-potential [3] https://launchpad.net/nova/+milestone/mitaka-rc1 [4] https://github.com/markuszoeller/openstack/tree/master/scripts/launchpad [5] https://bugs.launchp

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

Markus Zoeller/Germany/IBM@IBMDE wrote on 03/03/2016 11:45:52 AM: > From: Markus Zoeller/Germany/IBM@IBMDE > To: "OpenStack Development Mailing List \(not for usage questions\)" > <openstack-dev@lists.openstack.org> > Date: 03/03/2016 11:47 AM > Subject: Re: [opens

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

y > (not just within the comment text for the options). > > Doug I assume you mean the information about the services which use the config option. We have indeed the concern that this is prone to be outdated easily. I was thinking if it would make sense to do an analysis

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

improvement: current status > > > > On 3/2/2016 11:45 AM, Markus Zoeller wrote: > > TL;DR: From ~600 nova specific config options are: > > ~140 at a central location with an improved help text > > ~220 options in open revie

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

; [1]. References: [1] https://github.com/openstack/nova/blob/307b74977456735d4dcebc2988421b5980a2a71e/nova/conf/serial_console.py#L73 Regards, Markus Zoeller (markus_z) __ OpenStack Development Mailing List (not for usage questions) Uns

Re: [openstack-dev] [bug-smash] Global OpenStack Bug Smash Mitaka

a cleanup of inconsistencies in bug reports in Launchpad * triaging new bugs in Launchpad * reviews of pushed bug fixes in Gerrit Basically the steps from [1]. As we're heading to the rc phase in a few weeks it would be benefitial to have a lot of eyes on that. Re

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

i [36] - client [2] - image [8] --- vnc [0] --- volume [8] -- encryptors [0] --- wsgi [0] ------------ Number of total options: 610 Regards, Markus Zoeller (markus_z)

[openstack-dev] [all][infra] eventlet 0.18.1 not on PyPi anymore

is merged, there is a change that our CI (and your third-party CI) will break after the locally cached version in the CI vanishes. References: [1] https://review.openstack.org/#/c/277912/ Regards, Markus Zoeller (markus_z) __

Re: [openstack-dev] [nova][bugs] nova-bugs-team IRC meeting

ject: Re: [openstack-dev] [nova][bugs] nova-bugs-team IRC meeting > > On 22 January 2016 at 10:08, Markus Zoeller <mzoel...@de.ibm.com> wrote: > > The dates and times are final now [1]. They differ from the previously > > dates in this thread! The first and next meetings

Re: [openstack-dev] [all] Getting error after doing unstack.sh onstable/liberty

e with "px aux | grep python" which one of the services is still running, despite of the "unstack.sh" call, and have to kill that processes manually with "kill -9 ". After that, a new "stack.sh" does usually work for me. Regards, Markus Zoeller (markus_z) __

Re: [openstack-dev] [devstack] Failure on installing openstack with latest devstack.

Vikram Choudhary wrote on 01/22/2016 08:11:52 AM: > From: Vikram Choudhary > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 01/22/2016 08:12 AM > Subject: [openstack-dev] [devstack] Failure

Re: [openstack-dev] [nova][bugs] nova-bugs-team IRC meeting

in "early" and "late" time of day. The agenda can be found in the wiki [2]. See you there! References: [1] http://eavesdrop.openstack.org/#Nova_Bugs_Team_Meeting [2] https://wiki.openstack.org/wiki/Meetings/Nova/BugsTeam Regard, Markus Zoeller (markus_z) Markus Zoeller/Germany/I

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

the bug reporter necessary to get enough data. This makes me believe that stabilization should be a continuous effort. wrt cycle length: To get things merged in a specific cycle is indeed a big thing for my employer (at least the parts I directly interact with). A lot of effort g

Re: [openstack-dev] [nova][bugs] nova-bugs-team IRC meeting

an agenda ready until then [2]. Feel free to ping me in IRC or here on the ML when you have questions. References: [1] https://review.openstack.org/#/c/270281/ [2] https://wiki.openstack.org/wiki/Meetings/Nova/BugsTeam Regards, Markus Zoeller (markus_z) Markus Zoeller/Germany/IBM@IBMDE wrote on 01/13

Re: [openstack-dev] [nova][bugs] help needed: volunteers for bug skimming (1 week)

rpodolyaka for their work in the last 2 weeks! References: [1] https://wiki.openstack.org/wiki/Nova/BugTriage#Weekly_bug_skimming_duty Regards, Markus Zoeller (markus_z) Markus Zoeller/Germany/IBM@IBMDE wrote on 01/07/2016 12:06:31 PM: > From: Markus Zoeller/Germany/IBM@IBMDE > To: "OpenStac

Re: [openstack-dev] [Oslo] Improving deprecated options identification and documentation

"; "Deprecation Notes": http://docs.openstack.org/releasenotes/nova/unreleased.html#deprecation-notes [2] OpenStack governance docs; tag "assert_follows_standard_deprecation": https://governance.openstack.org/reference/tags/assert_follows-standard-deprecation.html R

Re: [openstack-dev] [infra][all] "openstack-meeting-cp" == "openstack-meeting-5"?

[1] "[openstack-dev] [nova][bugs] nova-bugs-team IRC meeting"; 2016-01-13: http://lists.openstack.org/pipermail/openstack-dev/2016-January/083966.html Regards, Markus Zoeller (markus_z) __ OpenStack Development

Re: [openstack-dev] [nova] config options: IRC meeting at Jan. 11th

Esra Celik <celik.e...@tubitak.gov.tr> wrote on 01/12/2016 12:55:25 PM: > From: Esra Celik <celik.e...@tubitak.gov.tr> > To: "OpenStack Development Mailing List (not for usage questions)" > <openstack-dev@lists.openstack.org>, Markus Zoeller/Germany/

[openstack-dev] [nova] nova unit tests failing with os-win 0.1.0

This post is just to make you aware that there was an issue in the last 24 hours which might have hit your patches: https://bugs.launchpad.net/nova/+bug/1533290 Regards, Markus Zoeller (markus_z) __ OpenStack Development

[openstack-dev] [infra][all] "openstack-meeting-cp" == "openstack-meeting-5"?

can I use it too? Regards, Markus Zoeller (markus_z) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-b

Re: [openstack-dev] [infra][all] "openstack-meeting-cp" == "openstack-meeting-5"?

ting scheduling and 2/ there is only one cross-project > discussion at a time). So it should not be used for more vertical team > meetings. > > -- > Thierry Carrez (ttx) Understood. Would it then be possible to create a new channel "openstack-meeting-5"? The sho

[openstack-dev] [nova][bugs] nova-bugs-team IRC meeting

that proposal. References: [1] Nova docs: "Bug Process": https://review.openstack.org/#/c/266453 Regards, Markus Zoeller (markus_z) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: o

Re: [openstack-dev] [nova][bugs] help needed: volunteers for bug skimming (1 week)

AM > Subject: Re: [openstack-dev] [nova][bugs] help needed: volunteers for > bug skimming (1 week) > > On Mon, Jan 11, 2016 at 11:21:29AM +0100, Markus Zoeller wrote: > > Augustina Ragwitz <aragw...@pobox.com> wrote on 01/08/2016 07:50:23 PM: > > > > >

Re: [openstack-dev] [nova][bugs] help needed: volunteers for bug skimming (1 week)

d at before. I see the whole process in 3 levels: * level 1: bug skimming duty => keep the input sane, prepares the report for level 2 * level 2: subteam digs deeper, finds the issue, proposes solution ideas for level 3 * level 3: contributor provides a change in

Re: [openstack-dev] [oslo][cfg] Benefit of MultiStrOpt over ListOpt

t numbers here please? I work for Nova on the config options and like to be aware of those bug reports. Regards, Markus Zoeller (markus_z) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ

Re: [openstack-dev] [doc] DocImpact vs. reno

n necessary https://review.openstack.org/#/c/237643/ Removes a deprecated config option => should have reno file https://review.openstack.org/#/c/180202/ Enhances flavor extra specs => to this day I don't know how they get documented and I'm clueless about a further action https://review.

Re: [openstack-dev] [nova] config options: IRC meeting at Jan. 11th

Markus Zoeller/Germany/IBM@IBMDE wrote on 01/08/2016 03:21:28 PM: > From: Markus Zoeller/Germany/IBM@IBMDE > To: "OpenStack Development Mailing List (not for usage questions)" > <openstack-dev@lists.openstack.org> > Date: 01/08/2016 03:22 PM > Subject: [openstack-

Re: [openstack-dev] [nova][bugs] help needed: volunteers for bug skimming (1 week)

ycles). [1] http://markuszoeller.github.io/posts/openstack-bugs/ Regards, Markus Zoeller (markus_z) > > On Thu, Jan 7, 2016 at 3:06 AM, Markus Zoeller <mzoel...@de.ibm.com> wrote: > The bug triage is an important first step to improve the quality > of Nova. Every code contributor

[openstack-dev] [nova] config options: IRC meeting at Jan. 11th

. Let's use the channel #openstack-meeting-3 at coming Monday, January the 11th, at 15:00 UTC for that. References: [1] "single point of entry for sample config generation" https://review.openstack.org/#/c/260015 Regards, Markus Zoeller

Re: [openstack-dev] [nova][bugs] Weekly Status Report

k.org/wiki/BugTriage * https://wiki.openstack.org/wiki/Nova/BugTriage * http://lists.openstack.org/pipermail/openstack-dev/2015-November/078252.html Regards, Markus Zoeller (markus_z) Markus Zoeller/Germany/IBM@IBMDE wrote on 12/04/2015 03:33:24 PM: > From: Markus Zoeller/Germany/IBM@IBMDE >

[openstack-dev] [nova][bugs] help needed: volunteers for bug skimming (1 week)

name in the wiki [2]. At best we will have at least 1 person until today's Nova meeting at 21:00 UTC [3]. When you volunteer, I will be available in IRC for requests, too. Regards, Markus Zoeller (markus_z) References: [1] https://wiki.openstack.org/wikiBugTriage#Task_1:_Confirm_new_bugs_

Re: [openstack-dev] [nova] proposed new compute review dashboard

r bug fixes. > > Hopefully many of these move up into slot 1. > > > > The rest is basically the way the old dashboard was. > > > > If you find this dashboard useful, enjoy. If not, hopefully you take > > some ideas out of it for your own review p

Re: [openstack-dev] [gate] job failure rate at ~ 12% (check queue) <= issue?

> > > [1] http://grafana.openstack.org/dashboard/db/tempest-failure-rate > > [2] logstash query: http://bit.ly/1O8qjtn > > > > Regards, Markus Zoeller (markus_z) > > That graph is a pretty narrow time slice. What's the rolling

[openstack-dev] [gate] job failure rate at ~ 12% (check queue) <= issue?

, Markus Zoeller (markus_z) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo

Re: [openstack-dev] [nova][serial-console-proxy]

well, try: $ make unstack $ make clean $ make stack * Enable the "nova-serialproxy" service in devstack: # local.conf enable_service n-sproxy * You can check if the connection with telnet is possible: $ telnet 127.0.0.1 10005 * You could give larsks's "novaconsole

Re: [openstack-dev] [nova] Contribution to improve Nova's config option space

ll working on that patch and aim for the next few days. Ping me in IRC if you have questions (I'm not around at Dec. 11th(FRI) + 15th (TUE)). Regards and thanks for your efforts, Markus Zoeller (markus_z) Markus Zoeller/Germany/IBM@IBMDE wrote on 12/03/2015 05:10:48 PM: > From: Markus Zoeller/Germ

Re: [openstack-dev] [nova] Contribution to improve Nova's config option space

er to execute than to start a whole system and debug it remotely. The Nova docs explain how to do it with the tool *tox* [1]. [1] http://docs.openstack.org/developer/nova/unit_tests.html Regards, Markus Zoeller (markus_z) > Kimden: "Markus Zoeller" <mzoel...@de.ib

Re: [openstack-dev] [nova] Contribution to improve Nova's config option space

t) you can use your browser: http://webchat.freenode.net/?channels=openstack-nova My nick is "markus_z". More info about IRC at: * https://wiki.openstack.org/wiki/UsingIRC * https://wiki.openstack.org/wiki/IRC > Kimden: "Markus Zoeller" <mzoel...@de.ibm.com> >

Re: [openstack-dev] [nova][bugs] Weekly Status Report

nstack.org/pipermail/openstack-dev/2015-November/078252.html Regards, Markus Zoeller (markus_z) Markus Zoeller/Germany/IBM@IBMDE wrote on 11/20/2015 05:36:48 PM: > From: Markus Zoeller/Germany/IBM@IBMDE > To: "OpenStack Development Mailing List \(not for usage questions\)" > <

Re: [openstack-dev] Looking to contribute

options. Here is the call for that: http://lists.openstack.org/pipermail/openstack-dev/2015-December/081271.html Regards, Markus Zoeller (markus_z) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [nova] Contribution to improve Nova's config option space

] and give it a try. References == [1] blueprint "centralize config options": http://specs.openstack.org/openstack/nova-specs/specs/mitaka/approved/centralize-config-options.html [2] https://etherpad.openstack.org/p/config-options Regards, Markus Zoeller

Re: [openstack-dev] [nova] Contribution to improve Nova's config option space

ts in the mentioned etherpad. Just pick one of those. Maybe the 'filesystems' option. Thanks for your help! Regards, Markus Zoeller > Kimden: "Markus Zoeller" <mzoel...@de.ibm.com> > Kime: "OpenStack Development Mailing List (not for usage questions)" > <

Re: [openstack-dev] [nova][infra][bugs] Grafana Dashboard for Bugs

; Subject: Re: [openstack-dev] [nova][infra][bugs] Grafana Dashboard for Bugs > > On Tue, Nov 24, 2015 at 04:20:26PM +0100, Markus Zoeller wrote: > > Background > > == > > We have "grafana" for data visualization [1] and I'd like to introduce > > a da

Re: [openstack-dev] [nova]New Quota Subteam on Nova

hat some of them are not valid anymore or are already solved. That would be really helpful from a bug management perspective. [1] Launchpad nova bugs; tag "quotas"; status is not in progress: http://bit.ly/1Pbr8YL Regards, Markus Zoeller (markus_z)

Re: [openstack-dev] [nova] Nova meeting this Thursday

think we should still have the meeting. Even if it > ends up being fairly short. > > I hope that works out OK for everyone? > > Thanks, > johnthetubaguy +1 Regards, Markus Zoeller (markus_z) __ OpenSta

[openstack-dev] [nova][infra][bugs] Grafana Dashboard for Bugs

(expires on 2015-12-20): http://www.tiikoni.com/tis/view/?id=7f3f191 [5] https://gist.github.com/anonymous/4368eb69059f11286fe9 [6] http://docs.openstack.org/infra/grafyaml/ Footnotes = * you can set ``target="syso"`` to print the data to the stdout without the n

Re: [openstack-dev] [nova][bugs] Weekly Status Report

nstack.org/pipermail/openstack-dev/2015-November/078252.html Markus Zoeller/Germany/IBM@IBMDE wrote on 11/13/2015 04:07:24 PM: > From: Markus Zoeller/Germany/IBM@IBMDE > To: "OpenStack Development Mailing List \(not for usage questions\)" > <openstack-dev@lists.openstack.org&

Re: [openstack-dev] [nova] release notes with reno and which patches need that?

t: Re: [openstack-dev] [nova] release notes with reno and which > patches need that? > > > > Le 19/11/2015 18:37, Markus Zoeller a écrit : > > If you ever had a patch which contained "UpgradeImpact" or "DocImpact", > > this mail is for you. You may

Re: [openstack-dev] [OpenStack-Infra] Report from Gerrit User Summit

David Pursehouse wrote on 11/12/2015 09:22:50 PM: > From: David Pursehouse > To: OpenStack Development Mailing List > Cc: openstack-in...@lists.openstack.org > Date: 11/12/2015 09:27 PM > Subject: Re:

Re: [openstack-dev] [nova][infra] Getting a bleeding edge libvirt gate job running

eds wrote: > > > On Tue, Nov 17, 2015 at 03:32:45PM -0800, Jay Pipes wrote: > > > > On 11/17/2015 11:10 AM, Markus Zoeller wrote: > > > > >Background > > > > >== > > > > >The blueprint [1] wants to utilize the *virtlogd*

[openstack-dev] [nova] release notes with reno and which patches need that?

http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-11-18-16.00.log.html Regards, Markus Zoeller (markus_z) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@list

Re: [openstack-dev] [oslo][All] Make CONF.set_override with paramter enforce_type=True by default

ments in https:// > etherpad.openstack.org/p/enforce_type_true_by_default > > -- > ChangBo Guo(gcb) Does it make sense to introduce a hacking check when your changes are merged? To prevent that new things slip in in Nova during the time period until "oslo.config" changes t

[openstack-dev] [nova][infra] Getting a bleeding edge libvirt gate job running

gs/%23openstack-nova/%23openstack-nova.2015-11-17.log.html#t2015-11-17T08:44:57 Regards, Markus Zoeller (markus_z) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org

[openstack-dev] [nova] config options: location and help text

g-options [2] Gerrit, "config options: centralize section "serial_console"; https://review.openstack.org/#/c/244177/ [3] https://etherpad.openstack.org/p/config-options Regards, Markus Zoeller (markus_z) __

Re: [openstack-dev] [nova] config options: location and help text

Markus Zoeller/Germany/IBM@IBMDE wrote on 11/16/2015 02:37:14 PM: > From: Markus Zoeller/Germany/IBM@IBMDE > To: "OpenStack Development Mailing List (not for usage questions)" > <openstack-dev@lists.openstack.org> > Date: 11/16/2015 02:38 PM > Subject: [opens

Re: [openstack-dev] [nova][bugs] Weekly Status Report

count: 0 (0) query: http://bit.ly/1kfntfk Readings * https://wiki.openstack.org/wiki/BugTriage * https://wiki.openstack.org/wiki/Nova/BugTriage * http://lists.openstack.org/pipermail/openstack-dev/2015-November/078252.html Markus Zoeller/Germany/IBM@IBMDE wrote on 11/06/2015

Re: [openstack-dev] [OpenStack-Infra] Report from Gerrit User Summit

it's basically Gerrits term for a folksonomy which usually uses the term "labels" or "tags" (not git tags). This was previously discussed on the ML with [1]. [1] [openstack-dev] [infra][all] Reviews with a prio label?: http://lists.openstack.org/pipermail/openstac

Re: [openstack-dev] [nova][bugs] Weekly Status Report

PM > Subject: Re: [openstack-dev] [nova][bugs] Weekly Status Report > > On Fri, Nov 06, 2015 at 05:54:59PM +0100, Markus Zoeller wrote: > > Hey folks, > > > > below is the first report of bug stats I intend to post weekly. > > We discussed it shortly during the

Re: [openstack-dev] [nova][bugs] Weekly Status Report

5 09:54 PM > Subject: Re: [openstack-dev] [nova][bugs] Weekly Status Report > > On Fri, Nov 6, 2015 at 11:54 AM, Markus Zoeller <mzoel...@de.ibm.com> wrote: > > below is the first report of bug stats I intend to post weekly. > > We discussed it shortly during the Mitak

Re: [openstack-dev] [nova][bugs] Weekly Status Report

nging-fruit bugs. I think the launchpad query for the tag is the way to track this, right? https://bugs.launchpad.net/nova/+bugs?field.tag=low-hanging-fruit > Off topic slightly, but we have an etherpad with some ideas, see here: > https://wiki.openstack.org/wiki/N

Re: [openstack-dev] [nova][bugs] Weekly Status Report

eport a bug by yourself :) > Would bug triaging be a meta low-hanging-fruit item? ;) To be honest, I don't think it's easy. You need to know a lot of the code to understand the bug but you need to fix some bugs to deeply understand the code base.

Re: [openstack-dev] [all][bugs] Developers Guide: Who's mergingthat?

gt; Subject: Re: [openstack-dev] [all][bugs] Developers Guide: Who's merging that? > > On 2015-11-05 16:23:56 +0100 (+0100), Markus Zoeller wrote: > > some months ago I wrote down all the things a developer should know > > about the bug handling process in general [1]. It is written

[openstack-dev] [nova][bugs] Weekly Status Report

Hey folks, below is the first report of bug stats I intend to post weekly. We discussed it shortly during the Mitaka summit that this report could be useful to keep the attention of the open bugs at a certain level. Let me know if you think it's missing something. Stats = New bugs which are

[openstack-dev] [all][bugs] Developers Guide: Who's merging that?

as I'm under the impression that the mental image differs a lot among the contributors. So, my questions are: 1) Who's in charge of merging such non-project-specific things? 2) Did I miss some important things in the commit? [1] https://review.openstack.org/#/c/192232/ Regards, Markus Zoeller

[openstack-dev] [nova][bugs] weekly bug status + bug tag contacts

missed a subteam. Just to be clear, this is *not* intended to be finger-pointing in any way. It's an attempt to organize the effort of bug solving to get a more stable product. Regards, Markus Zoeller (markus_z) References: [1] https://wiki.

Re: [openstack-dev] How we can find list of medium/low bugs for nova

ed) "bug handling description" of the developer's guide: https://review.openstack.org/#/c/192232/4/doc/source/developers.rst,cm Regards, Markus Zoeller (markus_z) __ OpenStack Development Mailing List (not

Re: [openstack-dev] [nova-compute][nova][libvirt] Extending Nova-Compute for image prefetching

be the need to distribute new images such often. Regards, Markus Zoeller (markus_z) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubs

Re: [openstack-dev] [Nova] Migration state machine proposal.

what the new state machine will be. > > http://paste.openstack.org/show/476954/ > > Thanks. I'd like to make you aware of bp "split-different-live-migration-types": https://review.openstack.org/#/c/225910/ It intends to split those 3 types you are tal

<    1   2   3   >