On 8 August 2014 07:55, Dean Troyer dtro...@gmail.com wrote:
In cinderclient I think you're stuck with size as a mandatory argument to
the 'cinder create' command, as you must be backward-compatible for at least
a deprecation period.[0]
Making an previously mandatory parameter optional, at

I've literally just finished the Cinder mid-cycle meetup (I'm still in
my hotel room), and the value was huge and undeniable.
Reading through this thread, I've just realised one massive advantage
of the mid-cycle meetup that improved our productivity massively: it
is in the middle of a cycle. We

On 21 August 2014 19:39, gordon chung g...@live.ca wrote:
from the pov of a project that seems to be brought up constantly and maybe
it's my naivety, i don't really understand the fascination with branding and
the stigma people have placed on non-'openstack'/stackforge projects. it
can't be a

On 2 September 2014 04:56, Emma Lin l...@vmware.com wrote:
Hi Gurus,
I saw the wiki page for Cinder Brick proposal for Havana, but I didn’t see
any follow up on that idea. Is there any real progress on that idea?
As this proposal is to address the local storage issue, I’d like to know the

On 11 August 2014 19:26, Jay Pipes jaypi...@gmail.com wrote:
The above does not really make sense for MySQL Galera/PXC clusters *if only
Galera nodes are used in the cluster*. Since Galera is synchronously
replicated, there's no real point in segregating writers from readers, IMO.
Better to

On 3 September 2014 01:20, Emma Lin l...@vmware.com wrote:
Thank you all for the prompt response. And I’m glad to see the progress on
this topic.
Basically, what I’m thinking is the local storage support for big data and
large scale computing is specially useful.
I’ll monitor the meeting

On 4 September 2014 16:00, Solly Ross sr...@redhat.com wrote:
My only question is about the need to separate out each virt driver into a
separate project, wouldn't you
accomplish a lot of the benefit by creating a single virt project that
includes all of the drivers?
I don't think there's

On 11 September 2014 12:36, Sean Dague s...@dague.net wrote:
I continue to not understand how N non overlapping teams makes this any
better. You have to pay the integration cost somewhere. Right now we're
trying to pay it 1 patch at a time. This model means the integration
units get much

On 11 September 2014 03:17, Angus Lees g...@inodes.org wrote:
(As inspired by eg kerberos)
2. Ensure at some environmental/top layer that the advertised token lifetime
exceeds the timeout set on the request, before making the request. This
implies (since there's no special handling in place)

On 11 September 2014 15:35, James Bottomley
james.bottom...@hansenpartnership.com wrote:
OK, so look at a concrete example: in 2002, the Linux kernel went with
bitkeeper precisely because we'd reached the scaling limit of a single
integration point, so we took the kernel from a single

On 12 September 2014 09:54, Thierry Carrez thie...@openstack.org wrote:
At this point, unless it's critical to the success of the release (like,
it completes a feature that is 99% there, or it increases consistency by
plugging a feature gap, or it fixes a potential security vulnerability),
I

On 16 September 2014 01:28, Nathan Kinder nkin...@redhat.com wrote:
The idea would be to leave normal tokens with a smaller validity period
(like the current default of an hour), but also allow one-time use
tokens to be requested.
Cinder backup makes many requests to swift during a backup, one

of work once the end of the blockage is removed, neither of
which is desirable.
I'd rather not have convenience labels on the backend array than
increase the risks of this sort of failure mode.
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev

significant dividends in that area - state machine, cinder
agent, decoupling of drivers and connector types.
I have always encouraged anybody to reach out to me with questions and
concerns, and continue to do so. I look forward to continuing the
great work we've been doing.
Regards
--
Duncan Thomas

On 22 September 2014 23:14, Robert Collins robe...@robertcollins.net wrote:
I am not at all sure we've prevented other flowers blooming -
and I hate the idea that we have done that.
I've certainly sat around at discussions which shut down hard with
somebody making the statement that 'that is

pleasure and honor
for me.
It's been a pleasure to work with you this far, and I hope to continue
doing so. You've seen Cinder through its birthing pains and into a
mature project, and done a great job doing so.
Cheers for all the hard work.
--
Duncan Thomas

On 28 November 2013 10:14, Daniel P. Berrange berra...@redhat.com wrote:
For this specific block zero'ing case it occurred to me that it might
be sufficient to just invoke 'ionice dd' instead of 'dd' and give it
a lower I/O priority class than normal.
Excuse the thread necromancy, I've just

On 15 January 2014 18:53, Brant Knudson b...@acm.org wrote:
At no point do I care what are the different commits that are being brought
in from oslo-incubator. If the commits are listed in the commit message then
I feel an obligation to verify that they got the right commits in the
message

On 11 March 2014 09:09, Zhangleiqiang zhangleiqi...@huawei.com wrote:
For example, one tenant's volume quota is five, and has 5 volumes and 1
snapshot already. If the data in base volume of the snapshot is corrupted,
the user will need to create a new volume from the snapshot, but this

On 12 March 2014 17:35, Tim Bell tim.b...@cern.ch wrote:
And if the same mistake is done for a cinder volume or a trove database ?
Deferred deletion for cinder has been proposed, and there have been
few objections to it... nobody has put forward code yet, but anybody
is welcome to do so.

On 14 March 2014 16:10, Jay S Bryant jsbry...@us.ibm.com wrote:
-- Duncan, It is important to know what commits are being brought over to
help provide a pointer to
-- the possible cause of subsequent bugs that arise. I.E. if we sync up
the DB, there is a commit for fixing
-- db connection

On 13 March 2014 21:13, Roman Podoliaka rpodoly...@mirantis.com wrote:
Hi Steven,
Code from openstack/common/ dir is 'synced' from oslo-incubator. The
'sync' is effectively a copy of oslo-incubator subtree into a project
source tree. As syncs are not done at the same time, the code of
synced

ideas?
This has been discussed in various cinder meetings and summits
multiple times. The end answer is 'no, we don't support that. If you
want to keep the snapshot, you need to keep the volume too'.
--
Duncan Thomas
___
OpenStack-dev mailing list

On 7 March 2014 08:17, Yuzhou (C) vitas.yuz...@huawei.com wrote:
First, generally, in public or private cloud, the end users of VMs
have no right to create new VMs directly.
If someone want to create new VMs, he or she need to wait for approval
process.
Then, the administrator Of

On 17 March 2014 11:34, Yuzhou (C) vitas.yuz...@huawei.com wrote:
Hi Duncan Thomas,
Maybe the statement about approval process is not very exact. In fact
in my mail, I mean:
In the enterprise private cloud, if beyond the quota, you want to create a
new VM ,that needs to wait

On Mar 26, 2014 6:46 PM, Jay Pipes jaypi...@gmail.com wrote:
Personally, I feel it is a mistake to continue to use the Amazon concept
of an availability zone in OpenStack, as it brings with it the
connotation from AWS EC2 that each zone is an independent failure
domain. This characteristic of

On 28 March 2014 14:38, Joshua Harlow harlo...@yahoo-inc.com wrote:
An idea that might be good to do is to start off using SQLite as the
taskflow persistence backend.
Get that working using SQLite files (which should be fine as a persistence
method for most usages) and then after this works

On 29 March 2014 02:49, Zhangleiqiang (Trump) zhangleiqi...@huawei.com wrote:
Hi, Duncan:
Thanks for your advice.
About the summit session you mentioned, what things can I do for it
?
If you (or a colleague who can speak on your behalf) is going to the
summit, then go to

On 3 April 2014 08:28, 王宏 w.wangho...@gmail.com wrote:
I agree. Actually, I already have a BP on it:
https://blueprints.launchpad.net/cinder/+spec/restore-image.
I am happy for any suggestion.
Needs a little thought since container_format and some other fields
will need to be regenerated (e.g.

is useful, especially from one of the
Horizon sessions I heard in Hong Kong for filtering/sorting.
--
Mike Perez
On 11:18 Thu 03 Apr , Duncan Thomas wrote:
Some of the cinder APIs do weird database joins and double lookups and
things, making every field sortable might have some serious

to do next? Waiting for approving for this blueprint? Or see
others' opinions on this before we putting more efforts in achieving
this? I just want to make sure that we could handle other people's use
cases and not just our own.
2014-04-03 18:12 GMT+08:00 Duncan Thomas duncan.tho

, and often far more limited, than the concerns of somebody
who reviews many drivers and core code changes.
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

On 11 October 2013 20:51, Rochelle.Grober rochelle.gro...@huawei.com wrote:
Proposed solution:
There have been a couple of solutions proposed. I’m presenting a
merged/hybrid solution that may work
· Create a new repository for the extra drivers:
o Keep kvm and Xenapi in the Nova

. The more people do that, the
faster things go for everybody. The higher rate tax is being a core
reviewer, but that comes with certain advantages too.
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http

On 22 November 2013 12:27, Elena Ezhova eezh...@mirantis.com wrote:
But what if I want to update some module that consists of ten or even more
files (like rpc or db) and each of these files has quite a long change log?
In that case the commit message may turn out to be really long even if only

module at a time, because it makes it far harder to review
and spot problems, so some from of automation of this would be great.
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman

On 16 June 2014 17:30, Jason Rist jr...@redhat.com wrote:
I'm going to have to agree with Tomas here. There doesn't seem to be
any reasonable expectation of backwards compatibility for the reasons
he outlined, despite some downstream releases that may be impacted.
Backward compatibility is a

then it is only going to take moments for the second core to review
it, so the saving really is negligible compared to the risk.
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo

On 18 June 2014 15:28, Matthew Booth mbo...@redhat.com wrote:
On 18/06/14 13:31, Sean Dague wrote:
Even with 2 +2s you do the wrong thing. Yesterday we landed
baremetal tests that broke ironic. It has a ton of +1s from people
that have been working on those tests.
This is slightly off topic,

On 19 June 2014 10:01, Giulio Fidente gfide...@redhat.com wrote:
From a the 10.000 feet view, I can imagine people relying on a stable API
for services like Cinder but I don't see how that applies to TripleO
Why should one try to install an older version of OpenStack using some
'recent'

On 19 June 2014 19:21, Travis McPeak travis_mcp...@symantec.com wrote:
Hi all,
In the OpenStack Security Group (OSSG) we¹ve been kicking around the idea
of getting some simple non-blocking security-related gate tests going.
These tests would be designed to be simple and automated checks for

On 24 June 2014 16:42, Avishay Traeger avis...@stratoscale.com wrote:
One more reason why block storage management doesn't really work on file
systems. I'm OK with storing the format, but that just means you fail
migration/backup operations with different formats, right?
Actually I think

On 26 June 2014 05:46, Amit Das amit@cloudbyte.com wrote:
This seems cool.
Does it mean the storage vendors write their new drivers just map it from
cinder.conf ?
Correct. You can cause devstack to set up cinder.conf for you by
setting CINDER_DRIVER=cinder.volume.drivers.foo.bar in

for each type of logs.
like cinder-api, cinder-scheduler and cinder-volume logs.
On Thu, Jun 26, 2014 at 5:49 PM, Duncan Thomas duncan.tho...@gmail.com
wrote:
I'm afraid that isn't the log we need to diagnose your problem. Can
you put cinder-api, cinder-scheduler and cinder-volume logs up

of success in our
3rd party guidelines: Passes every test in tempest-dsm-full. If that
needs documenting somewhere else, please let me know. It may of course
change as we learn more about how 3rd party CI works out, so the fewer
places it is duplicated the better, maybe?
--
Duncan Thomas

On 1 July 2014 14:44, Anita Kuno ante...@anteaya.info wrote:
On 07/01/2014 05:56 AM, Duncan Thomas wrote:
For the record, cinder gave a very clear definition of success in our
3rd party guidelines: Passes every test in tempest-dsm-full. If that
needs documenting somewhere else, please let me

On 30 June 2014 07:47, Steve Kowalik ste...@wedontsleep.org wrote:
Personally, I think generating and comparing a sample config every build
is daft, and a sample configuration should be generated during sdist or
something.
This argument has gone back and forth several times.
There is definite

of the word 'tested' - how long until edits can be
made to the cinder wiki to comply with that agreement?
It's a wiki - anybody who cares enough can go and re-word it...
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev

for a few taskflow integration bits - we'd do better froma
stability point of view to ignore OSLO all together and do our own
thing.
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin

On 15 July 2014 08:24, Johnson Cheng johnson.ch...@qsantechnology.com
wrote:
I have two questions here,
1. It still has “Error encountered during initialization of driver:
LVMISCSIDriver” error message in cinder-volume.log, how to fix this issue?
2. From cinder-scheduler.log, it

On 15 July 2014 11:59, Johnson Cheng johnson.ch...@qsantechnology.com wrote:
May I ask you another question that how cinder choose volume node to create
volume if I have multi volume nodes?
For example,
when controller node and compute node are alive, the volume will be created
at compute

on the whiteboard of the vluprint/bug. Then
a quick discussion there could be used to define if a SPEC would be needed.
Launchpad has proven terrible for this, which is a strong driver for
the spec process in the first place
--
Duncan Thomas
___
OpenStack-dev

On 16 July 2014 03:57, Jay S. Bryant jsbry...@electronicjungle.net wrote:
John,
So you have said a few times that the specs are a learning process.
What do you feel with have learned thus far using specs?
I'm not John, but I'm going to answer as if you'd addressed the question wider:
- Specs

On 17 July 2014 08:36, Abbass MAROUNI abbass.maro...@virtualscale.fr wrote:
Thanks Thomas,
What I'm trying to achieve is the following :
To be able to create a VM on a host (that's a compute and volume host at the
same time) then call cinder and let it find the host and create and attach

On 21 July 2014 21:38, Boris Pavlovic bpavlo...@mirantis.com wrote:
Hi,
I would like to propose my candidacy for Rally PTL.
I've been working with Boris on both Rally and the associated
OSProfiler code, and I can confirm he is dedicated, very open to ideas
and contributions, and I heartily

No. There a blueprint in to do the integration, but no code merged yet let
alone documentation.
Duncan Thomas
On Jul 22, 2014 4:42 PM, Giuseppe Galeota giuseppegale...@gmail.com
wrote:
Dear all,
is Cinder capable today to use Barbican for encryption? If yes, can you
link to me some useful doc

Hi
I'm looking for a maintainer email address for the cinder coraid
driver. http://stackalytics.com/report/driverlog?project_id=openstack%2Fcinder
just lists it as Alyseo team with no contact details.
Thanks
--
Duncan Thomas
___
OpenStack-dev

Duncan Thomas
On Aug 1, 2014 9:44 PM, Jay Pipes jaypi...@gmail.com wrote:
Yup. Though I'd love for this code to live in olso, not glance...
Why Oslo? There seems to be a general obsession with getting things into
Oslo, but our (cinder team) general experiences with the end result have
been

On 7 August 2014 16:39, John Griffith john.griff...@solidfire.com wrote:
On Thu, Aug 7, 2014 at 9:28 AM, Eric Harney ehar...@redhat.com wrote:
On 08/07/2014 09:55 AM, John Griffith wrote:
There are three things that have just crushed productivity and
motivation
in Cinder this release