=
=YavB
-END PGP SIGNATURE-
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Duncan Thomas
___
OpenStack-dev
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
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
@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Duncan Thomas
On 13 August 2014 13:57, Matthew Treinish mtrein...@kortar.org wrote:
On Tue, Aug 12, 2014 at 01:45:17AM +0400, Boris Pavlovic wrote:
Keystone, Glance, Cinder, Neutron and Heat are running rally performance
jobs, that can be used for performance testing, benchmarking, regression
testing
On 11 August 2014 21:03, Dean Troyer dtro...@gmail.com wrote:
On Mon, Aug 11, 2014 at 5:34 PM, Duncan Thomas duncan.tho...@gmail.com
wrote:
Making an previously mandatory parameter optional, at least on the
command line, does break backward compatibility though, does it?
Everything
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
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
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
(failures=10)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev
late.
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
That is indeed my aim, and thanks for following up
On 25 July 2014 15:29, Yacine Kheddache yac...@alyseo.com wrote:
Le 23/07/2014 22:31, Duncan Thomas a écrit :
Hi
I'm looking for a maintainer email address for the cinder coraid
driver.
http://stackalytics.com/report/driverlog?project_id
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
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
/cgi-bin/mailman/listinfo/openstack-dev
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
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
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
,
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org
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 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
information.
Regards,
Johnson
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Duncan Thomas
___
OpenStack-dev
the lightweight process and skip
the spec if they don't expect to need one.
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/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 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
PGP SIGNATURE-
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Duncan Thomas
___
OpenStack-dev mailing list
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
this code cleanup be done separate from the update
volume-Image-metadata update bp or should be a work item of it?
-Original Message-
From: Duncan Thomas [mailto:duncan.tho...@gmail.com]
Sent: Thursday, June 26, 2014 7:29 PM
To: OpenStack Development Mailing List (not for usage questions
Regards,
Yogesh Prasad.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Duncan Thomas
___
OpenStack-dev mailing list
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
driver.
Thanks Regards,
Yogesh Prasad.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Duncan Thomas
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
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
.
--
Thanks Regards,
Yogesh Prasad.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Duncan Thomas
___
OpenStack-dev
-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev
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'
/mailman/listinfo/openstack-dev
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Duncan Thomas
___
OpenStack-dev mailing list
/listinfo/openstack-dev
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
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
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,
EA19 D33C 3490
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack
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
. If I've got the wrong expectations, I'd at least like
to have the correction on record.
Regards
--
Duncan Thomas
On 16 June 2014 17:58, Clint Byrum cl...@fewbar.com wrote:
Excerpts from Duncan Thomas's message of 2014-06-16 09:41:49 -0700:
On 16 June 2014 17:30, Jason Rist jr...@redhat.com wrote
On 10 June 2014 17:53, Mark McLoughlin mar...@redhat.com wrote:
On Tue, 2014-06-10 at 16:09 +0100, Duncan Thomas wrote:
On 10 June 2014 15:07, Mark McLoughlin mar...@redhat.com wrote:
Exposing which configurations are actively tested is a perfectly sane
thing to do. I don't see why you
/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Duncan Thomas
On 10 June 2014 09:23, Flavio Percoco fla...@redhat.com wrote:
On 09/06/14 19:31 +, Kurt Griffiths wrote:
Against:
• Makes it hard for users to create applications that work across
multiple
clouds, since critical functionality may or may not be available in a
given
deployment.
will it or not, so a far more sensible
stance is to play it out in advance.
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-certified product, go talk to your
vendor' when dealing with the cases we have no control over. Vendors
that don't follow the CI cert requirements eventually get their
driver removed, that simple.
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev
have
done.
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On 6 June 2014 18:29, Anita Kuno ante...@anteaya.info wrote:
So there are certain words that mean certain things, most don't, some do.
If words that mean certain things are used then some folks start using
the word and have expectations around the word and the OpenStack
Technical Committee
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi
On 18 May 2014 12:32, Murali Balcha murali.bal...@triliodata.com wrote:
Hi,
I did a design session on Friday though my proposal was to capture the
delta as qcow2. Here is the link to ether pad notes.
https://etherpad.openstack.org/p/juno-cinder-changed-block-list
Do you see synergies
On 7 May 2014 13:04, Mike Kolesnik mkole...@redhat.com wrote:
- Original Message -
Yeah, we've already got plans in place to get Cinder to use the
interface to provide us more detailed information and eliminate some
polling. We also have a very purpose-built notification scheme
On 7 May 2014 09:36, Trump.Zhang zhangleiqi...@gmail.com wrote:
@Tripp, Thanks for your reply and info.
I am also thinking if it is proper to add support for updating the volume's
glance_image_metadta to reflect the newest status of volume.
However, there may be alternative ways to achieve
' and the reason turned out to be because their instance never
came up properly, or snapshot delete failed because the create failed
but wasn't logged. Anything that causes the test to automatically
report the narrowest definition of the fault is definitely a good
thing.
--
Duncan Thomas
://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
:
On Mon, 2014-04-28 at 12:15 +0100, Duncan Thomas wrote:
Two separate patches, or even two chains of separate patches, will
make reviewing and more importantly (hopefully temporary) backouts
easier. It will also reduce the number of merge conflicts, which are
still likely to be substantial.
True
is currently being looked at - nova
is not the only project that could benefit from better status updates
than polling. Dashboards and even the CLI could also potentially
benefit
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev
(Trump)
Best Regards
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Duncan Thomas
___
OpenStack-dev mailing list
on freenode)
[1] https://bugs.launchpad.net/cinder/+bug/1306275
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Duncan Thomas
On 17 April 2014 18:01, Deepak Shetty dpkshe...@gmail.com wrote:
On Fri, Apr 11, 2014 at 7:29 PM, Duncan Thomas duncan.tho...@gmail.com
wrote:
The scenario I *don't want to see is:
1) Admin import a few hundred volumes into the cloud
2) Some significant time goes by
3) Cloud is being
, and all services and drivers should correctly handle
recovery from an unclean shutdown.
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman
On 11 April 2014 16:24, Eric Harney ehar...@redhat.com wrote:
I suppose I should also note that if the plans in this blueprint are
implemented the way I've had in mind, the main issue here about only
loading shares at startup time would be in place, so we may want to
consider these questions
On 14 April 2014 19:51, James Penick pen...@yahoo-inc.com wrote:
We drive the ³VM=Cattle² message pretty hard. Part of onboarding a
property to our cloud, and allowing them to serve traffic from VMs is
explaining the transient nature of VMs. I broadcast the message that all
compute resources
On 11 April 2014 14:21, Deepak Shetty dpkshe...@gmail.com wrote:
My argument was mostly from the perspective that unmanage shud do its best
to revert back the volume to its original state (mainly the name).
Like you said, once its given to cinder, its not a external volume anymore
similary,
is
Incorrect and should be removed
Thoughts ?
thanx,
deepak
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
--
Duncan Thomas
On 10 April 2014 09:02, Deepak Shetty dpkshe...@gmail.com wrote:
Ok, agreed. But then when admin unmanages it, we shud rename it back to the
name
that it originally had before it was managed by cinder. At least thats what
admin can hope
to expect, since he is un-doing the managed_existing
On 9 April 2014 08:35, Deepak Shetty dpkshe...@gmail.com wrote:
Alternatively, does this mean we need to make name_id a generic field (not a
ID) and then use somethign like uuidutils.is_uuid_like() to determine if its
UUID or non-UUID and then backend will accordinly map it ?
Definitely not,
On 8 April 2014 18:25, Clint Byrum cl...@fewbar.com wrote:
Excerpts from Jay Dobies's message of 2014-04-08 06:40:07 -0700:
I've always assumed TripleO is very low-level. Put another way,
non-prescriptive. It's not going to push an agenda that says you should
be doing things a certain way,
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev
On 6 August 2013 21:18, Christopher Armstrong
chris.armstr...@rackspace.com wrote:
I think it's really unfortunate that people will block patches based on
stylistic concerns. The answer, IMO, is to codify in policy that stylistic
issues *cannot* block a patch from landing.
It think the
that the obj is not completely gone/deleted, so its
vars must still be in scope and valid.. but debug prints suggests the
otherwise :(
On Sun, Apr 6, 2014 at 12:07 PM, Duncan Thomas duncan.tho...@gmail.com
wrote:
I'm not yet sure of the right way to do cleanup on shutdown, but any
driver
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
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
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
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.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev
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 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
@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
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
/mailman/listinfo/openstack-dev
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
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 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 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 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
@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Duncan Thomas
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
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
-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Duncan Thomas
301 - 400 of 413 matches
Mail list logo
