emoves all unintentional blockquotes in the tripleo docs:
https://review.openstack.org/#/c/504518/
You can find them by yourself with:
$ tox -e docs
$ grep -rn blockquote doc/build/html/ --include *.html
I often use http://rst.aaroniles.net/ for a quick check.
--
Regards, Markus Zoeller
er is appreciated.
--
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/cg
possible to add that to those Ansible roles?
https://github.com/openstack/ansible-role-nodepool
https://github.com/openstack/ansible-role-zuul
--
Regards, Markus Zoeller (markus_z)
__
OpenStack Development Mailin
om/openstack/openstack-ansible-os_nova/blob/
> 4b9100a612ba0e9449d792b2783b9ec50a8fb28e/tasks/nova_post_install.yml#L40
> [2]: https://docs.openstack.org/project-deploy-guide/
> openstack-ansible/ocata/app-advanced-config-override.html
>
> Best regards,
> JP
That helps resolving my issues. Thanks a l
in a mixed arch environment (x86 + s390x) based on image properties.
I still don't fully get it. In which use-case is `architecture` the
correct property to set?
--
Regards, Markus Zoeller (markus_z)
> On Wed, Aug 23, 2017 at 5:45 AM, Markus Zoeller
> wrote:
>> On 22.08.2017 17:
On 22.08.2017 17:10, Markus Zoeller wrote:
> I'm wondering if there is an issue in the docs which describe the
> possible image metadata properties:
> https://docs.openstack.org/python-glanceclient/latest/cli/property-keys.html#
>
> This document says to use `architecture` (
keys?
--
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-bin/mailman/lis
; I'm allowed
to touch or is it considered an "internal/private" part of
OpenStack-Ansible (and/or its roles)?
--
Regards, Markus Zoeller (markus_z)
> On Mon, Aug 21, 2017 at 6:09 PM Markus Zoeller
> wrote:
>
>> On 21.08.2017 16:40, Andy McCrae wrote:
>>&g
ova/nova.conf
root@compute1:~# grep reserved_host_memory_mb /etc/nova/nova.conf
reserved_host_memory_mb = 512
### compute2: /etc/nova/nova.conf
root@compute2:~# grep reserved_host_memory_mb /etc/nova/nova.conf
reserved_host_memory_mb = 512
I'd like to avoid to introduce some "
vironments
(dev, test, prod) with a different amount of nodes.
Any tips how to do this properly?
References:
[1]
https://docs.openstack.org/project-deploy-guide/openstack-ansible/draft/app-advanced-config-override.html
--
Regards, Markus Zoeller (markus_z)
_
On 16.08.2017 18:40, Alex Schultz wrote:
> On Wed, Aug 16, 2017 at 8:24 AM, Markus Zoeller
> wrote:
>> On 16.08.2017 02:59, Emilien Macchi wrote:
>>> On Tue, Aug 15, 2017 at 5:46 PM, Alex Schultz wrote:
>>>> Hey folks,
>>>>
>>>> I'm p
nder" with the same commit which introduced the technical debt
in the code. Similar to what OpenStack already does with the
release-notes. The list of technical debt items is then always visible
in the docs and not a query in the bug-tracker with tags (or something
like that).
Just an idea, may
enstack-dev/2015-November/079835.html
[3] https://phabricator.wikimedia.org/T37534
--
Regards, Markus Zoeller (markus_z)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@list
On 25.07.2017 16:20, Major Hayden wrote:
> On 07/25/2017 08:36 AM, Markus Zoeller wrote:
>> A short grep in 'openstack-ansible' shows that the file permissions are
>> often not set. I used these commands:
>>
>> $ grep -n -R "template:" --include \*.ym
On 17.07.2017 23:13, Major Hayden wrote:
> On 07/04/2017 03:54 AM, Markus Zoeller wrote:
>> How do you deal with hosts which have a restrictive umask of 077
>> *before* openstack-ansible starts the setup? Do you start with the
>> default umask of 022 and opt-in later to that
fe3ae20f74a912925d5c78040984957a6d55f9de/tasks/repo_post_build.yml#L43-L46
[3]
https://stackoverflow.com/questions/42286765/using-repo-other-then-pypi-with-pip
--
Regards, Markus Zoeller (markus_z)
__
OpenStack Developme
in the current model it's far more frequent for bugs to be blocked away
> as "assigned" when no one is working on them.
>
> A future version might be smarter and give folks a 7 day window or
> something, but
.55:8082/bugs-dashboard.html
Most of the time in the past, I asked for logs, versions and
configuration. Tooling for that could save some back-and-forth.
>>
>> This is going to be kind of an ongoing experiment, bu
there is a concern that it's changing the API. Though from an
> end user perspective that's not happening, it's just changing which
> field things get logged into. We'll see if we can work throug
On 11.05.2017 15:56, Markus Zoeller wrote:
> I'm working on a nova live-migration hook which configures and starts
> the nova-serialproxy service, runs a subset of tempest tests, and tears
> down the previously started service.
>
>https://review.openstack.org/#/c/3474
her services too) with less change in the set of default enabled
services in the gate.
Is this the right direction? Any other thoughts?
--
Regards, Markus Zoeller (markus_z)
__
OpenStack Development Mailing List
a
>
> __________
> 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/openstack-
onsole-action-deprecated-detail,create-remote-console-detail
--
Regards, Markus Zoeller (markus_z)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
_bug_reports.py
I did that back in July 2016 (be aware that some people may not like that):
http://openstack.markmail.org/thread/i4drtyqddluwnp2m
--
Regards, Markus Zoeller (markus_z)
__
OpenStack Development Mai
-options
>
> Cheers,
> macsz
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.op
]
https://www.ibm.com/support/knowledgecenter/zosbasics/com.ibm.zos.zmainframe/zconc_mfhwterms.htm
[4]
https://github.com/openstack/nova/blob/bcbfee183e74f696085fcd5c18aff333fc5f1403/nova/tests/unit/conductor/test_conductor.py#L1468-L1469
[
nv for that is at:
http://markuszoeller.github.io/posts/2016/03/06/grafana-graphite-statsd/
Would love to have that for Openstack (at least the core projects). It
would give that area more visibility which could incentivize people to
work there.
--
Regards, M
On 11.10.2016 16:09, Kashyap Chamarthy wrote:
> On Tue, Oct 11, 2016 at 02:09:33PM +0200, Markus Zoeller wrote:
>
> [Snip well-written backrgound detail]
>
>> Request
>> ---
>> My question is, if you have interest in this plugin and its
>> capabilities, ar
On 12.10.2016 10:52, Kashyap Chamarthy wrote:
> On Tue, Oct 11, 2016 at 05:53:24PM +0200, Thomas Goirand wrote:
>> On 10/11/2016 02:09 PM, Markus Zoeller wrote:
>>> * How to create a "*.deb" package out of the source code of
>>> libvirt/qemu? (surprisingly e
ges and increase the version in the gate?
* Actually hack some code and push it
--
Regards, Markus Zoeller (markus_z)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@list
nd date. I'm in
the UTC+1 timezone.
>
> On Mon, Sep 5, 2016 at 7:20 PM, Sylvain Bauza wrote:
>
>>
>>
>> Le 05/09/2016 13:19, Markus Zoeller a écrit :
>>
>>> TL;DR: bug czar role for Nova is vacant from now on
>>>
>>>
>>&g
t's Python based.
* I'll still hang out in the IRC channels, but don't expect much from me.
Thanks a lot to the people who helped making Nova a better project by
doing bug triage! Special thanks to auggy who put a lot(!)
Yeah, no meeting again, same reason :/
--
Regards, Markus Zoeller (markus_z)
On 23.08.2016 14:21, Markus Zoeller wrote:
> I get dragged into some internal stuff recently and didn't have time to
> prepare anything or host the meeting.
>
> One noteworthy thing though, please t
+bugs?field.tag=newton-rc-potential
There's less than 3 weeks left until RC1 target week starts.
--
Regards, Markus Zoeller (markus_z)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
On 11.08.2016 16:46, Markus Zoeller wrote:
> On 11.08.2016 13:31, Daniel P. Berrange wrote:
>> On Thu, Aug 11, 2016 at 07:19:42AM -0400, Sean Dague wrote:
>>> On 08/11/2016 05:45 AM, Markus Zoeller wrote:
>>>> On 26.07.2016 12:16, Jordan Pittier wrote:
>>>>
On 11.08.2016 13:31, Daniel P. Berrange wrote:
> On Thu, Aug 11, 2016 at 07:19:42AM -0400, Sean Dague wrote:
>> On 08/11/2016 05:45 AM, Markus Zoeller wrote:
>>> On 26.07.2016 12:16, Jordan Pittier wrote:
>>>> Hi Markus
>>>> You don"t really need a
hat slowdown comes from ?
>
> On Tue, Jul 26, 2016 at 11:50 AM, Markus Zoeller <
> mzoel...@linux.vnet.ibm.com> wrote:
>
Hi Jordan,
after thinking again about this I think you're right. The mutual
exclusive relationship between "serial console" and "console
echeck leave a comment with 'intel-nfv-ci recheck'.
2) The link to the wiki seems to be wrong (hyphen vs. underscore):
https://wiki.openstack.org/wiki/ThirdPartySystems/Intel_NFV_CI
--
Regards, Markus Zoeller (markus_z)
> >-Original Message-
> >From:
uot;supernova":
https://de.wikipedia.org/wiki/Supernova#/media/File:SN1994D.jpg
https://en.wikipedia.org/wiki/Nova#/media/File:GKPersei-MiniSuperNova-20150316.jpg
--
Regards, Markus Zoeller (markus_z)
__
OpenStack
rg/developer/oslo.config/mutable.html
[3]
https://github.com/openstack/nova/blob/master/nova/tests/live_migration/hooks/run_tests.sh
--
Regards, Markus Zoeller (markus_z)
__
OpenStack Development Mailing List (not for usage qu
al to bring the discussion to a conclusion.
--
Regards, Markus Zoeller (markus_z)
On 12.07.2016 09:59, Markus Zoeller wrote:
> After closing the old (>18months) bug reports nobody is working on a few
> days ago [1], it became clear that the "in progress" reports are the
>
which fits better for
more people. What would fit best for you (1000, 1100, $any_other_time)?
References:
[1] https://review.openstack.org/#/c/320337/
--
Regards, Markus Zoeller (markus_z)
__
OpenStack Development Mailing Lis
mixed use of (non-)admin
context even an issue?
--
Regards, Markus Zoeller (markus_z)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubs
ple) to get things up and running. Combining forces
and stuff: https://www.youtube.com/watch?v=ZGegECwSiGY
References:
[1] https://github.com/openstack/devstack-plugin-additional-pkg-repos/
--
Regards, Markus Zoeller (markus_z)
> On 07/26/2016 05:23 PM, Mooney, Sean K wrote:
>> Hi I w
is the host for a Devstack environment.
--
Regards, Markus Zoeller (markus_z)
> On Tue, Jul 26, 2016 at 11:50 AM, Markus Zoeller <
> mzoel...@linux.vnet.ibm.com> wrote:
>
>> I'd like to discuss a testing strategy which ensures that the "serial
>> console"
until the
instance is booted completely and accepts console input, which makes the
test run for [3] a very long one.
References:
[1] https://bugs.launchpad.net/nova/+bug/1455252
[2] https://review.openstack.org/#/c/346815/1
[3] https://review.openstack.org/#/c/346911/
nces:
[1] https://github.com/openstack/devstack-plugin-additional-pkg-repos/
[2]
https://github.com/openstack-infra/project-config/blob/master/jenkins/jobs/devstack-gate.yaml#L565-L595
--
Regards, Markus Zoeller (markus_z)
t me skim through our modules first and filter out those which aren't
yet ready for your rewording. I'll post a list of modules in this thread
in the next days.
In case you don't already know, we have all config options at:
https://github.com/openstack/nova/tree/master/nova/conf
--
can have a look at it and merge it, that would be great.
References:
[1]
https://github.com/openstack/requirements/commit/238389c4ee1bd3cc9be4931dd2639aea2dae70f1
[2] https://review.openstack.org/#/c/342604/1
[3] https://bugs.launchpad.net/nova/+bug/1603979
[4] logstash: http://goo.gl/79yFb9
--
ocs team.
Be aware, that this is still an ongoing effort in Nova (see [1],
especially "needs:fix_opt_description").
References:
[1] http://45.55.105.55:8082/config-options.html
--
Regards, Markus Zoeller (markus_z)
_
On 13.07.2016 19:11, Jeremy Stanley wrote:
> On 2016-07-13 13:25:44 +0200 (+0200), Markus Zoeller wrote:
>> For some reason the gate docs job didn't find the issue (wrong json
>> format) which got fixed with change [1]. It doesn't even emit a warning.
>> Locally
On 13.07.2016 21:51, Doug Hellmann wrote:
> Excerpts from Jeremy Stanley's message of 2016-07-13 17:22:32 +:
>> On 2016-07-13 17:10:20 +0200 (+0200), Markus Zoeller wrote:
>>> Whoever chooses the wording in these announcements, you're a genius!
>>
>>
On 13.07.2016 16:01, no-re...@openstack.org wrote:
> We are tickled pink to announce the release of:
>
Whoever chooses the wording in these announcements, you're a genius!
--
Regards, Markus Zoeller (markus_z)
> mox3 0.17.0: Mock object framework for Python
>
> This re
my mind.
Having the api-ref and the config-ref at one place, near the code, seems
logical to me. Nova put a lot of effort into providing valuable help
text for the config options in the last months. We should also make sure
that it will result in a good manual, which could be easier if it's
in-t
On 13.07.2016 09:56, Sahid Orentino Ferdjaoui wrote:
> On Tue, Jul 12, 2016 at 06:45:03PM +0200, Markus Zoeller wrote:
>> On 12.07.2016 17:39, Sahid Orentino Ferdjaoui wrote:
>>> On Tue, Jul 12, 2016 at 09:59:12AM +0200, Markus Zoeller wrote:
>>>> After closing t
though, or can it?
Nevertheless, it's a good alternative which can support the whole idea,
thanks for bringing that up.
--
Regards, Markus Zoeller (markus_z)
__
OpenStack Development Mailing List (not for
On 13.07.2016 10:09, Andreas Jaeger wrote:
> On 2016-07-12 09:59, Markus Zoeller wrote:
>> After closing the old (>18months) bug reports nobody is working on a few
>> days ago [1], it became clear that the "in progress" reports are the
>> majority [2]. After askin
On 23.06.2016 12:21, Andreas Jaeger wrote:
> On 06/23/2016 10:43 AM, Markus Zoeller wrote:
>> On 21.06.2016 15:01, Doug Hellmann wrote:
>>> A while back pbr had a feature that let projects pass "warnerror"
>>> through to Sphinx during documentation builds, caus
enstack/gertty
[2]
http://eavesdrop.openstack.org/meetings/nova_bugs_team/2016/nova_bugs_team.2016-07-12-17.59.log.html
--
Regards, Markus Zoeller (markus_z)
__
OpenStack Development Mailing List (not for usage questio
On 12.07.2016 18:19, Chris Friesen wrote:
> On 07/12/2016 01:59 AM, Markus Zoeller wrote:
>> After closing the old (>18months) bug reports nobody is working on a few
>> days ago [1], it became clear that the "in progress" reports are the
>> majority [2]. After
On 12.07.2016 17:39, Sahid Orentino Ferdjaoui wrote:
> On Tue, Jul 12, 2016 at 09:59:12AM +0200, Markus Zoeller wrote:
>> After closing the old (>18months) bug reports nobody is working on a few
>> days ago [1], it became clear that the "in progress" reports are the
&
k-dev/2016-July/098792.html
[2] http://45.55.105.55:3000/dashboard/db/openstack-bugs
[3]
https://github.com/markuszoeller/openstack/blob/master/scripts/gerrit/bug_fix_histogram.py
--
Regards, Markus Zoeller (markus_z)
_
progress. You can see a graphical impact at
[1]. The list of affected bug reports is at [2] and as an attached file.
References:
[1] http://45.55.105.55:3000/dashboard/db/openstack-bugs
[2] http://paste.openstack.org/show/525937/
--
Regards, Markus Zoeller (markus_z)
On 21.06.2016 14:43, Markus
changes [2] and [3] did already get a lot of attention from danpb.
References:
[1] https://blueprints.launchpad.net/openstack/?searchtext=libvirt-virtlogd
[2] https://review.openstack.org/#/c/334480/
[3] https://review.openstack.org/#/c/323765/
--
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-bin/mailman/listinfo/openstack-dev
>
References:
On 23.06.2016 11:50, Daniel P. Berrange wrote:
> On Mon, Jun 20, 2016 at 05:47:57PM +0200, Markus Zoeller wrote:
>> White working on the change series to implement the virtlogd feature I
>> got feedback [1] to move code which creates parts of the libvirt.xml
>> file from the
On 23.06.2016 12:21, Andreas Jaeger wrote:
> On 06/23/2016 10:43 AM, Markus Zoeller wrote:
>> On 21.06.2016 15:01, Doug Hellmann wrote:
>>> A while back pbr had a feature that let projects pass "warnerror"
>>> through to Sphinx during documentation builds, caus
estions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
Thanks for the heads up. I checked Nova, and every sphinx-build command
we use in ou
On 21.06.2016 18:24, Adam Young wrote:
> On 06/21/2016 08:43 AM, Markus Zoeller wrote:
>> A reminder that this will happen in ~2 weeks.
>>
>> Please note that you can spare bug reports if you leave a comment there
>> which says one of these (case-sensitive flags):
A reminder that this will happen in ~2 weeks.
Please note that you can spare bug reports if you leave a comment there
which says one of these (case-sensitive flags):
* CONFIRMED FOR: NEWTON
* CONFIRMED FOR: MITAKA
* CONFIRMED FOR: LIBERTY
On 23.05.2016 13:02, Markus Zoeller wrote:
> TL
ttps://review.openstack.org/#/c/323761/2/nova/virt/libvirt/driver.py@4190
--
Regards, Markus Zoeller (markus_z)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-re
#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://lists.openstack.org/cgi-bin
> 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/openstack-dev
>
References:
[1] https://review.openstack.org/#/c/322255/1
--
Nova needs one or more volunteers for the bug skimming duty [1] for the
coming week (R-18). Unfortunately no one signed up yet. Let me know if
you wanna help in this area.
References:
[1] https://wiki.openstack.org/wiki/Nova/BugTriage#Weekly_bug_skimming_duty
--
Regards, Markus Zoeller
References:
[1]
https://github.com/markuszoeller/openstack/blob/master/scripts/launchpad/bugs_dashboard.py#L276
--
Regards, Markus Zoeller (markus_z)
__
OpenStack Development Mailing List (not for usage questions)
. Feel free to use the script in your favorite project.
I'll do that in week R-13 for Nova [2].
References:
[1] https://review.openstack.org/#/c/321008/
[2] http://lists.openstack.org/pipermail/openstack-dev/2016-May/095654.html
--
Regards, Markus Zoeller (mar
'm going to
>> finish it this week. If there is a place in an OpenStack repo, just give
>> me a pointer and I'll push a change.
>>
>>> On 23 May 2016 at 14:02, Markus Zoeller wrote:
>>>
>>>> TL;DR: Automatic closing of 185 bug reports w
end.
This takes effect starting from 2016-06-07 [2].
References:
[1] https://wiki.openstack.org/wiki/Meetings/Nova/BugsTeam
[2] https://review.openstack.org/#/c/320337/
--
Regards, Markus Zoeller (markus_z)
__
OpenStack D
ularly for Q/A folks who work between different projects.
A first draft (without the actual expiring) is at [1]. I'm going to
finish it this week. If there is a place in an OpenStack repo, just give
me a pointer and I'll push a change.
> On 23 May 2016 at 14:02, Markus Zoeller wrote:
d example: CONFIRMED FOR: KILO
* AND add the steps to reproduce the issue (if applicable)
Let me know if you think this comment gives enough information how to
handle this situation.
References:
[1] http://45.55.105.55:8082/bugs-dashboard.html#t
On 20.05.2016 16:51, Ben Nemec wrote:
> On 05/20/2016 04:26 AM, Markus Zoeller wrote:
>> On 05/19/2016 09:18 PM, Ben Nemec wrote:
>>> On 05/17/2016 07:27 PM, Matt Fischer wrote:
>>>>
>>>> If config sample files are being used as a living document then
om/openstack/nova/blob/d619ad6ba15df1cf7dc92ddf84d1c65af018682f/nova/cmd/dhcpbridge.py#L92-L92
[2]
https://github.com/openstack/nova/blob/b8aac794d4620aca341b269c6db71ea9e70d2210/nova/cmd/manage.py#L1397-L1397
[3] http://burndown.dague.org/
--
Regards, Markus Zoeller (markus_z)
__
On 05/19/2016 09:18 PM, Ben Nemec wrote:
On 05/17/2016 07:27 PM, Matt Fischer wrote:
If config sample files are being used as a living document then that
would be a reason to leave the deprecated options in there. In my
experience as a cloud deployer I never once used them in tha
> From: Michael Still
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 05/09/2016 11:12 PM
> Subject: Re: [openstack-dev] config options: current state (R-21)
>
> On Tue, May 10, 2016 at 2:12 AM, Markus Zoeller
wrote:
> We
is ready for review.
This is the most important part of this effort.
For questions, ping me in #openstack-nova
References
[1] http://releases.openstack.org/newton/schedule.html
Regards, Markus Zoeller (markus_z)
Appendix:
=
nova [1]https://review.openst
t actually one changes multiple other
> > config options as well. Making it explicit that "pybasedir" gets used
> > multiple times as a base could prevent confusion.
> >
> > References:
> > [1] https://review.openstack.org/#/c/299236/7/nova/conf/paths.py
> >
well. Making it explicit that "pybasedir" gets used
multiple times as a base could prevent confusion.
References:
[1] https://review.openstack.org/#/c/299236/7/nova/conf/paths.py
Regards, Markus Zoeller (markus_z)
In case the dashboard is not loading, you can use
* query_inconsistent.py
* query_stale_incomplete.py
from
https://github.com/markuszoeller/openstack/tree/master/scripts/launchpad
Regards, Markus Zoeller (markus_z)
> From: Matt Riedemann
> To: "OpenStack Developm
A short reminder that this is happening next Monday 04/18
A few stats are at: http://45.55.105.55:8082/bugs-stats.html
Regards, Markus Zoeller (markus_z)
> From: Matt Riedemann
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 04/05/2
> From: Dean Troyer
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 04/14/2016 08:18 PM
> Subject: Re: [openstack-dev] [all] [devstack] Adding example
> "local.conf" files for testing?
>
> On Thu, Apr 14, 2016 at 11:
> From: Matt Riedemann
> To: openstack-dev@lists.openstack.org
> Date: 04/14/2016 04:53 PM
> Subject: Re: [openstack-dev] [all] [devstack] Adding example
> "local.conf" files for testing?
>
>
>
> On 4/14/2016 6:09 AM, Sean Dague wrote:
> > O
> From: Neil Jerram
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 04/14/2016 10:50 AM
> Subject: Re: [openstack-dev] [all] [devstack] Adding example
> "local.conf" files for testing?
>
> On 14/04/16 08:35, Markus Zoe
ixes pre summit, and do a virtual doc
> sprint post summit to push through to completion.
>
>-Sean
>
> --
> Sean Dague
> http://dague.net
The rendered output looks pretty neat. I like that all is on one page:
http://docs-draft.opens
l.conf.compute1
--- --- --- --- local.conf.compute2
--- mitaka
--- --- # same structure as master branch. omitted for brevity
--- liberty
--- --- # same structure as master branch. omitted for brevity
Thoughts?
Regards, Markus Zo
and suggestions are [...]."
+1 | "I understand the code and your change. It improves the
project and I'd maintain it."
0 | "I don't get the code or your change. My questions are [...]."
If it already has at least one +2, I (usually) ignore i
g.
References:
[1]
https://github.com/openstack/python-novaclient/commit/7304ed80df265b3b11a0018a826ce2e38c052572#diff-56f10b3a40a197d5691da75c2b847d31R33
Regards, Markus Zoeller (markus_z)
> [image removed] Matt Riedemann ---2016/04/05 03:49:05 PM---As we
> discuss the glance v2 spec for nova, questions are com
https://etherpad.openstack.org/p/nova-bugs-team
[2] http://45.55.105.55:8082/bugs-dashboard.html#tabInProgressStale
>
> Adam Lawson
>
> AQORN, Inc.
> 427 North Tatnall Street
> Ste. 58461
> Wilmington, Delaware 19801-2230
> Toll-free: (844) 4-AQORN-NOW ext. 101
> In
bugs == (trivial) blueprint?":
http://lists.openstack.org/pipermail/openstack-dev/2016-March/089365.html
[7] https://wiki.openstack.org/wiki/Meetings/Nova/BugsTeam
[8] https://etherpad.openstack.org/p/nova-bugs-team
[9] https://launchpad.net/~nova-bugs
[10] http://markuszoe
ML post, which makes me believe the bug is still a valid
issue.
References:
[1] https://review.openstack.org/#/c/298023/
Regards, Markus Zoeller (markus_z)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstac
the missing decision. Would be great if we could come to a conclusion.
References:
[1] https://bugs.launchpad.net/nova/+bug/1550250
[2] https://review.openstack.org/#/c/288433/
Regards, Markus Zoeller (markus_z)
__
OpenStack
1 - 100 of 263 matches
Mail list logo
