I don't think --marker does at all what I want. The --limit -1 does doe
multiple successive queries (with a marker) automagically returning a
single list as CLI output to nova list. That really IS what I want (and
what some of our automation is written around.)
Thanks!
On Wed, May 18, 2016 at
On Wed, May 18, 2016 at 04:37:42PM -0600, David Medberry wrote:
> It seems to bypass it... or I'm running into a LOWER limit (undocumented).
> So help on limit -1 says it is still limited by osapi_max_limit
You're looking for:
--marker The last server UUID of the previous page;
We just hit this and replaced a call to nova with a direct database query -
literally yesterday!
Chris Morgan
Sent from my iPhone
> On May 18, 2016, at 6:13 PM, David Medberry wrote:
>
> So, we just ran into an "at-sale" issue that shouldn't have been an issue.
>
>
It seems to bypass it... or I'm running into a LOWER limit (undocumented).
So help on limit -1 says it is still limited by osapi_max_limit
I'll check my config for that value (likely the default) when I get home.
On Wed, May 18, 2016 at 4:18 PM, Kris G. Lindgren
wrote:
Nova has a config setting for the maximum number of results to be returned by a
single call. You can bump that up so that you can do a nova list —all-tenants
and still see everything. However if I am reading the below correctly, then I
didn't realize that the —limit –1 apparently by-passes
So, we just ran into an "at-sale" issue that shouldn't have been an issue.
Many of the OpenStack CLI tools accept a limit parameter (to limit how much
data you get back from a single query). However, much less well documented
is that there is an inherent limit that you will run into at a 1000 VMs
I forgot how to reply-all here :)
// jim
On Wed, May 18, 2016 at 05:35:55PM -0400, Jim Rollenhagen wrote:
> On Tue, May 17, 2016 at 11:32:25PM +0100, Stig Telfer wrote:
> > Is there anywhere that these experiences can be captured in a way that
> > might help?
> >
> > For example, I have a few
On Wed, May 18, 2016 at 9:20 AM, Sean Dague wrote:
> nova-net is now deprecated - https://review.openstack.org/#/c/310539/
>
> And we're in the process in Nova of doing some spring cleaning and
> deprecating the proxies to other services -
>
nova-net is now deprecated - https://review.openstack.org/#/c/310539/
And we're in the process in Nova of doing some spring cleaning and
deprecating the proxies to other services -
https://review.openstack.org/#/c/312209/
At some point in the future after deprecation the proxy code is going to
Hello all,
Thank you very much to the 25(!) of you who participated in our first
meeting. We had some fantastic discussion, which has been helpfully
summarised by Chris Morgan at[1].
==Proposal: Regular Meeting Time==
Those at the first meeting concluded that generally, the Ops Meetups
Team
About docker:
testing this docker setup is in my TODO list from a long time:
https://github.com/dguerri/dockerstack
Looks very well done but I think is not very well known.
Saverio
___
OpenStack-operators mailing list
> Hi there all-ye-operators,
> I am investigating how to help move godaddy from rpms to a
> container-like solution (virtualenvs, lxc, or docker...) and a set of
> questions that comes up is the following (and I would think that some
> folks on this mailing list may have some useful insight into
12 matches
Mail list logo