Pool capacity is not stored in Cinder db. This is from capabilities reporting
from the driver which manages the backend.
Thanks,
Xing
On May 16, 2016, at 7:10 PM, Adam Lawson
mailto:alaw...@aqorn.com>> wrote:
When I request cinder pool capacity and usage via cinder's API v2, is my client
ta
When I request cinder pool capacity and usage via cinder's API v2, is my
client talking to the backend storage directly or cached information stored
in the DB?
//adam
*Adam Lawson*
AQORN, Inc.
427 North Tatnall Street
Ste. 58461
Wilmington, Delaware 19801-2230
Toll-free: (844) 4-AQORN-NOW ext. 1
Everyone,
Our next OSops group meeting will be help this coming Wednesday at 1900 UTC
in the #openstack-meeting-4 IRC room.
I've posted our agenda for this week:
https://etherpad.openstack.org/p/osops-irc-meeting-20160518
Thanks
Joe
___
OpenStack-op
As a user of logstash myself, thanks for the contribution. I'm currently using
the configuration at [0] with some minor modification to collect from more log
files. These two configurations for logstash seem similar, are they both going
to be kept in sync?
[0]:
https://github.com/openstack/o
Hi all -
The OpenStack Scientific WG has its first IRC meeting tomorrow (Tuesday) at
2100 UTC on #openstack-meeting. A calendar entry for the meetings is attached.
We will be alternating time zones of following WG meetings to broaden
participation.
Full meeting details can be found here [1]
On 13/05/16 17:10 -0400, Nikhil Komawar wrote:
On 5/13/16 4:29 PM, Flavio Percoco wrote:
On 13/05/16 15:52 -0400, Nikhil Komawar wrote:
On 5/13/16 3:36 PM, Flavio Percoco wrote:
On 12/05/16 21:41 -0400, Nikhil Komawar wrote:
I have been of the same opinion as far as upgrades go.
I think
HTML render:
http://www.openstack.org/blog/2016/05/openstack-developer-mailing-list-digest-20160513/
SuccessBot Says
===
* Pabelanger: bare-precise has been replaced by ubuntu-precise. Long live DIB
* bknudson: The Keystone CLI is finally gone. Long live openstack CLI.
* Jrichli: swi
Hello,
I'm trying to achieve something like
https://bugs.launchpad.net/nova/+bug/1350857
The problem described there is: after successful live migration of an instance
on non-shared storage, backing file + overlay (increment) is copied to
destination compute node instead of only increment fil
