easier
> > and straightforward.
I'm fine with that plan, speaking as the original developer; as I say,
I don't think Rackspace ever utilized the functionality anyway, and if
no one else pipes up saying that they're using it, I'd be all over
deprecating the quota class
can imagine stopping these errors in the future would be
to double-up on the pep8 check: have the gate run pep8 under both
Python 2 and Python 3.
--
Kevin L. Mitchell <klmi...@mit.edu>
signature.asc
Description: This is a digitally signed message part
_
contributors to Nova get involved which helps grow our
> contributor base.
+1 from me
--
Kevin L. Mitchell <klmi...@mit.edu>
signature.asc
Description: This is a digitally signed message part
__
OpenStack Dev
ouldn't require a version bump in
this case: it _is_ a breakage that's being fixed.
--
Kevin L. Mitchell <klmi...@mit.edu>
signature.asc
Description: This is a digitally signed message part
__
OpenStack Development Maili
ve a
deployer would view as a bug, if they encountered it, and because it
was introduced prior to a named final release.
--
Kevin L. Mitchell <klmi...@mit.edu>
signature.asc
Description: This is a digitally signed message part
_
On Fri, 2017-08-04 at 12:26 -0700, Boris Pavlovic wrote:
> By the way stevedore is really providing very bad plugin experience
> and should not be used definitely.
Perhaps entrypointer[1]? ;)
[1] https://pypi.python.org/pypi/entrypointer
--
Kevin L. Mitchell <klmi...@mit.edu>
s
at'd be even better.
--
Kevin L. Mitchell <klmi...@mit.edu>
signature.asc
Description: This is a digitally signed message part
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
that's hit by "register"; it
returns a response telling you to just upload your project. I hit that
about a month or so ago…
--
Kevin L. Mitchell <klmi...@mit.edu>
signature.asc
Description: This is a digitally signed message part
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
If that's the case, that may help provide a solution to
translate user-visible messages while leaving logs untranslated.
--
Kevin L. Mitchell <klmi...@mit.edu>
signature.asc
Description: This is a digitally signed message part
__
hat are your thoughts?
When the translators go to translate, they generally only get to see
what's inside _(), so #2 is a no-go for translations, and #3 also is a
no-go.
--
Kevin L. Mitchell <klmi...@mit.edu>
signature.asc
Description: This is a digitally signed message part
__
ppened to
be the #3 largest IRC network at the time. Fixing *that* was fun :)
--
Kevin L. Mitchell <klmi...@mit.edu>
signature.asc
Description: This is a digitally signed message part
__
OpenStack Development Mailing List (n
2nd, rather than
February: US date conventions.
--
Kevin L. Mitchell <klmi...@mit.edu>
signature.asc
Description: This is a digitally signed message part
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.op
On Fri, 2016-12-02 at 09:22 -0600, Matt Riedemann wrote:
> I'm proposing that we add Stephen Finucane to the nova-core team.
+1 from me.
--
Kevin L. Mitchell <klmi...@mit.edu>
signature.asc
Description: This is a digitally signed mes
ee that that is non-ideal. How about a syntax
something like:
?finished_at=between:ISO_DATE_A@ISO_DATE_B_at=between:ISO_DATE_C@ISO_DATE_D
--
Kevin L. Mitchell <klmi...@mit.edu>
signature.asc
Description: This is a digitally signed message part
eutil than to
> put the function in a library not meant for anyone else outside of
> OpenStack to use.
You might also want to look at the timestring library…
--
Kevin L. Mitchell <klmi...@mit.edu>
signature
I'm going to start a pet project of rooting this stuff out
> again, starting with nova.context.RequestContext.quota_class, unless
> anyone has a good reason we should keep this in tree.
>
> I think we should also add a microversion to the API in Ocata to disable
> the abi
, and since I'm not notified, I have to notice that the
review hasn't merged yet and check up on it.
Is there some setting I need to click to get Gerrit to send me
notifications about rebases, or is this something systemic that needs to
be reported upstream as a bug?
--
Kevin L. Mitchell <k
ny sense at all to add
additional keys? We could add a 'warnings' key in that top-level
dictionary that could document deprecations, among other things.
(That said, /capabilities or equivalent would probably be superior for
this particular case…)
--
Kevin L. Mitchell <klmi...@mit.edu>
sign
several backoff
strategies. Of course, it's a decorator-based backoff implementation,
whereas I tend to implement iterator-based solutions, but there may
already be a solution in that space as well…
--
Kevin L. Mitchell <klmi...@mit.edu>
signature.asc
Description: This is a digital
nfortunately, we weren't able to get priority for the project,
and I'm afraid it's probably not going to go anywhere now :/
--
Kevin L. Mitchell <kevin.mitch...@rackspace.com>
Rackspace
__
OpenStack Development Mailing L
other distracting
elements, such as schwag and giveaways…
--
Kevin L. Mitchell <kevin.mitch...@rackspace.com>
Rackspace
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openst
th a name
or ID of 'admin' exists." Anyone have any insights into why "admin"
would be missing from novaclient's functional test suite?
--
Kevin L. Mitchell <kevin.mitch...@rackspace.com>
Rackspace
__
Ope
to. I think the
first phase is essentially complete at this point, but I think Chris is
right that it's high time to decide whether the guidelines are normative
or informative…and my vote would be for normative, and with a focus on
the API consumer. After all, an API is useless if it's a pain to use :)
ions of Python, we're going to
have to warn the operator community about the consequences well in
advance, so that all the issues can be worked out…
--
Kevin L. Mitchell <kevin.mitch...@rackspace.com>
Rackspace
__
OpenStack
there's no specific quota for that
tenant in its database. That's why you're getting a reasonable-looking
set of quota information.
--
Kevin L. Mitchell <kevin.mitch...@rackspace.com>
Rackspace
__
OpenStack
added unless the corresponding
nova change has been merged…
--
Kevin L. Mitchell <kevin.mitch...@rackspace.com>
Rackspace
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@l
race conditions that are not a problem
for other quota types.
(For reference, the AbsoluteResource quotas are metadata_items,
injected_files, injected_file_content_bytes, and
injected_file_path_bytes; everything else is a ReservableResource.)
--
Kevin L. Mitchell <kevin.mitch...@racksp
at you could think of as an audience *class*—this
notification is intended for metrics consumers, this one is intended for
log monitors, etc. That kind of data could be included in the actual
notification, so you still have a single notification stream. (I could
envision later refinemen
ng. However, I'd like to start off by asking
if "quota" is the correct concept? It might be worthwhile to make a
detour and consider what the problem is we're actually trying to solve.
I think in the end it'll still end up being recognizably "quota", but I
think it would be a worthwhil
o.i18n, oslo.serialization, and oslo.utils. If we drop
Python 2.6 compatibility on any of those three, we would also have to
drop it from novaclient (and potentially other clients). Perhaps we
need to have a discussion about whether the clients still need to
support Python 2.6?
--
Kevin L. Mi
to address the problem?
--
Kevin L. Mitchell <kevin.mitch...@rackspace.com>
Rackspace
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
On Mon, 2015-10-12 at 12:16 -0400, Sean Dague wrote:
> On 10/12/2015 11:54 AM, Kevin L. Mitchell wrote:
> > Functional tests on novaclient (gate-novaclient-dsvm-functional) have
> > started failing consistently. The test failures all seem to be for an
> > HTTP 300, whic
own away the scalability
that deploying multiple schedulers was supposed to buy you.
[1] https://en.wikipedia.org/wiki/CAP_theorem
--
Kevin L. Mitchell <kevin.mitch...@rackspace.com>
Rackspace
__
OpenStack Development Mailing
On Fri, 2015-10-02 at 11:00 -0400, Sean Dague wrote:
> On 10/02/2015 10:53 AM, Kevin L. Mitchell wrote:
> > The Pillow-breaking-gate issue was related to having doc dependencies
> > listed in the test-requirements.txt; however, those dependencies are not
> > needed for te
ntain only the doc dependencies? The appropriate doc environments in
tox.ini would then need to be extended to pull in that file, and of
course the global requirements tooling would have to be enhanced to
recognize the new file as well.
--
Kevin L. Mitchell <kevin.mitch...@rackspace.c
It looks like Pillow (pulled in by blockdiag, pulled in by
sphinxcontrib-seqdiag, in test-requirements.txt of nova and probably
others) had a 3.0.0 release today, and now the gate is breaking because
libjpeg isn't available in the image…thoughts on how best to address
this problem?
--
Kevin L
On Thu, 2015-10-01 at 15:53 -0700, Clark Boylan wrote:
> On Thu, Oct 1, 2015, at 03:48 PM, Kevin L. Mitchell wrote:
> > It looks like Pillow (pulled in by blockdiag, pulled in by
> > sphinxcontrib-seqdiag, in test-requirements.txt of nova and probably
> > others) had a 3.0.0 r
eads like an API change, requiring a
microversion bump. That said, I approve of increased consistency across
the API, and perhaps the behavior on limit=0 is something the API group
needs to discuss a guideline for?
--
Kevin L. Mitchell <kevin.mitch...@rackspace.com>
Rackspace
_
thing per line given the
rule to only import modules, not objects. While that is not currently
enforced by hacking, it is a strong style guideline. (Exceptions for
things like sqlalchemy do exist, of course.)
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
in Python 2.6, and has been deprecated as of
Python 2.7 because it's no longer necessary.
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
On Thu, 2015-07-30 at 15:27 -0700, Adam Lawson wrote:
How many up votes are needed for code to be accepted into the trunk
(assuming it passes testing etc)?
Which project? Different projects may have different criteria.
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
were a smaller code base, I think it would make
sense to reorganize in this fashion, but given how large nova actually
is…
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
__
OpenStack Development Mailing List
based on subsection scheme; that seems perfect to
me.
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
signature.asc
Description: This is a digitally signed message part
__
OpenStack Development Mailing List
to create a new top-level package and split the
config options up into a small number of individual files there? Would
that be a reasonable compromise between Roman's suggestion and the
one-file-of-config route?
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
On Mon, 2015-06-22 at 18:10 +0100, Daniel P. Berrange wrote:
On Mon, Jun 22, 2015 at 11:10:40AM -0500, Kevin L. Mitchell wrote:
On Sat, 2015-06-20 at 21:35 +0100, Daniel P. Berrange wrote:
In general I would say that is an unsupported deployment scenario to
have other random virt guests
on the hypervisor node…
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
as a possible solution? That at least would be a standard
HTTP convention for this sort of thing, and tends to match up with the
semantics of a changes-since query parameter.
[1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.25
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
?
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi
to a plain HTTP proxy would probably result in that error.
(Also noticed that your proxy URL is specified as http://;; if you know
that proxy works for SSL, try https://…)
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
the git review -s to get that
all fixed up. (Could also use git remote set-url, FYI, but I figured
starting from scratch may be easier for you…)
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
__
OpenStack
file in the interim (as is done for
configuration now), which may improve the situation from Horizon's
standpoint, until the discoverability piece is in place.
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
discourage service developers from requiring bodies on HTTP
methods that a client framework may prohibit sending bodies with.
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
__
OpenStack Development Mailing List
behavior
applies to all nova reviews I've tried to load. Restarting by browser
did not have any effect.
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
__
OpenStack Development Mailing List (not for usage questions
to encompass the over-quota
condition; and of those, 403 makes the most sense. (Note that I believe
we use 413 for rate limiting, because of the Retry-After header…)
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
within one week.
Definitely a +1 from me…
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
. We're
talking about automated tests here, by the way.
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
purposes, I don't care where it is, as
long as it's somewhere; so we could also move it to, say, tools. I
don't even care what it outputs, as long as it gives a reasonable return
value; so we could have it print out a scary-looking warning about it
being legacy… :)
--
Kevin L. Mitchell kevin.mitch
find a different way to encode the path
name to deal with that problem :)
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev
at present, so
we have to run tests using run_tests.sh instead of tox :( I have an
issue open on tox to address this need, but haven't seen any movement on
that; so until then, I have to oppose the removal of run_tests.sh…
despite how much *I'd* like to see it bite the dust!
--
Kevin L. Mitchell
detect the mixing :)
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
the GPL right now, but if anyone wants to use
it, I'd be happy to relicense under Apache…)
[1] https://pypi.python.org/pypi/policies
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
__
OpenStack Development
entries are in whatever array from which
the script selects randomly? That's the best part of the release
script, IMO :)
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
__
OpenStack Development Mailing List
and it would simplify adding new
attributes on the server side. You'd still need versioning to handle
deleting
attributes or changing their meaning, of course.
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
or
-'s. I even subscribe to a couple of projects and check out new reviews
submitted there. This is actually partly to blame for me being such a
prolific reviewer in nova and novaclient :)
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
several from the
novaclient review queue (or commented on them to see if they were still
alive). I also know of a few novaclient changes that are waiting for
corresponding nova changes before they can be merged. Could these be
introducing a skew factor?
--
Kevin L. Mitchell kevin.mitch
, and
once that happens, then I can foresee it becoming a formal standard
recommended by the API WG…
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
__
OpenStack Development Mailing List (not for usage questions
an error vs. The server messed
up.) Is it intended to convey a retryable condition? (If you retry
this, it may succeed.) If it's intended to convey that the server
messed up spectacularly and that everything's broken now, well… :)
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
any of our *-specs repos; to me, a spec provides documentation of a
change, and is thus independent of the guidelines.
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
__
OpenStack Development Mailing List
On Tue, 2015-01-27 at 14:41 -0800, Michael Still wrote:
I would like to nominate Melanie Witt for the python-novaclient-core
team.
I +1 this…
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
__
OpenStack
:
'session'
)
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
if their value is null.
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
://logs.openstack.org/26/145626/2/check/gate-nova-python27/b350bbc/console.html
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev
in the novaclient
implementation as a reviewer. I also had suggestions about how it
should be transmitted in the REST API, but that had already been settled
at the blueprint phase; that may be something the API WG will want to
take up and review and provide guidance on now, though…
--
Kevin L. Mitchell
'no-' to options, but
that is my current backup.
My mental model insists that --no-share would remove all shares, so
perhaps that's not the correct antonym. How about --grant and
--revoke?
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
___
Mailing
for all virt drivers. For example,
the host for Xen-based installations is often a separate VM on the same
hypervisor, which would have its own distinct IP address.
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
___
OpenStack-dev mailing
runs in a VM on the hypervisor. There has
also been discussion of allowing one host to be responsible for multiple
hypervisors, which would be useful for providers with large numbers of
hypervisors.
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
one day, then
be automatically rolled back by the scheduler.
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
be that difficult to
implement or maintain.
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
the rest of the code is related to
the checks which I just agreed should be dropped :) Am I missing
anything?
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
to be done to the
simpler H306 test (probably involving changes to the core import
normalization)…
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi
On Mon, 2014-12-08 at 14:07 +0800, Eli Qiao wrote:
I wonder if we can use body in delete, currently , there isn't any
case used in v2/v3 api.
No, many frameworks raise an error if you try to include a body with a
DELETE request.
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
as allowing a null value.
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
can see whether it makes sense to roll it into
Keystone or maintain it as a separate thing.
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin
in the nomination period, then the election coordinator
would send out the appropriate reminder email. I think this would have
the same effect as the one week re-open period without delaying the
election process.
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
; anytime nova refers to a flavor, it returns the flavor
UUID.
I would, by the way, suggest using UUIDs rather than plain IDs, for
consistency with the rest of the APIs…
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
___
OpenStack-dev mailing
/wiki/Boson
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
until_refresh or max_age, in
the [DEFAULT] section. You could try setting until_refresh to a
suitable value, say, 50, then restarting nova. The value 14 may still
show until the next time you request an instance, at which time it
*should* refresh.
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
:)
As for the clients, we could probably drop that segment now; it's not
like we *test* against 2.4, right? :)
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin
the [oslo] tag in the subject line and was thinking generally;
so no, none of the Xen plugins use anything from oslo, because of the
need to support 2.4.
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
___
OpenStack-dev mailing list
OpenStack
On Tue, 2014-09-23 at 18:18 -0400, Jay Pipes wrote:
Yes, I'd be willing to head up the working group... or at least
participate in it.
I'll raise my hand to participate…
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
___
OpenStack-dev
a
unified ReST API service to replace the service from all of the
individual projects. Then, users can just hit that one service to
handle all their different interactions.
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
___
OpenStack-dev
is a client, and we're talking about a server. A
server, in this instance, has some advantages over a client, including
making it easier to create that client in the first place :)
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
___
OpenStack-dev
[1] to replace it with a simple dict.
[1] https://review.openstack.org/#/c/123189/
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman
no reason that _get_collection_kwargs() needs to use an
OrderedDict: it's initialized in an arbitrary order (generator
comprehension over a set), then later passed to functions with **, which
converts it to a plain old dict.
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
by indenting the following lines by 4 spaces.
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
for Timeout indicate that it's an
Exception subclass, and passing it no args doesn't seem to start the
timer running. I think you have to explicitly pass a duration value for
Timeout to enable its timeout behavior, but that's just a guess on my
part at this point…
--
Kevin L. Mitchell kevin.mitch
? That way, their reviews can be counted
by the core reviewers. With this change in policy, you still need two
+2s, but you have more people that can +2, and you only need one of our
limited number of cores to review.
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
when packages get
too big, so why not split repos when they get too big?
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo
…
That ensures that arg will be the configured value, and should also
solve the import conflict.
--
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman
On Thu, 2014-08-07 at 10:55 -0500, Matt Riedemann wrote:
On 8/7/2014 10:27 AM, Kevin L. Mitchell wrote:
On Thu, 2014-08-07 at 12:15 +0100, Matthew Booth wrote:
A (the?) solution is to register_opts() in foo before importing any
modules which might also use oslo.config.
Actually, I
1 - 100 of 141 matches
Mail list logo
