One more vote from "not a core member" .
I am not a core and I am mainly involved in the Nova project where Scott
presence is always useful
and valuable when we need to sort out some cinder <-> nova issue.
--
Andrea Rosa
On 27/06, Sean McGinnis wrote:
> I would like to nominate Scott
Hi
thanks Sean for bringing this point, I have been working on the change and on
the (abandoned) spec.
I'll try here to summarize all the discussions we had and what we decided.
> From: Sean Dague [mailto:s...@dague.net]
> Sent: 02 December 2015 13:31
> To: OpenStack Development Mailing List
Hi,
> -Original Message-
> From: Wang, Shane [mailto:shane.w...@intel.com]
> Sent: 12 November 2015 16:34
> To: OpenStack Development Mailing List (not for usage questions); Daniel P.
> Berrange; Bhargava, Ruchi
> Subject: Re: [openstack-dev] [nova] hackathon day
>
> Hey, how about
Hi
I knew that people in China had a 3 days hackathon few months ago I was
thinking to have a similar thing in Europe.
My original idea was to propose to add an extra day after the mid-cycle but I
am not sure if that is a good idea anymore:
CONS:
- the next mid-cycle is going to be the first
Hi all
> Not all of these are covered by specs yet and all the existing specs need
> reviews. Please look at the etherpad and see if there is anything you think is
> missing.
What about adding a way to migrate files which are not migrated at the moment,
like console.log?
I think that could be
Hi all,
> Please respond to this post if you have an interest in this and what you
> would like to see done. Include anything you are already getting on with so
> we get a clear picture.
I have put a new spec about "allow more instance actions during the live
migration" [0].
Please note that
Hi all
Thank you very much for your feedback, I found the discussion quick and useful.
I'll abandon my change and for the bug fixing I'll pass a parameter in the
DELETE.
Regards
--
ar
-Original Message-
From: Jay Pipes [mailto:jaypi...@gmail.com]
Sent: 11 May 2015 19:29
To:
Hi all,
I noticed that in the nova API we allow to specify body just for the PUT and
POST requests [0], for all the other methods, if a body is specified, it gets
ignored.
I had a look at the RFC 7231 [1] and I noticed that just the TRACE must not
have a body, for all the other request a body
Why is DELETE /volumes/ID?force=true not an option?
I believe it's valid for DELETE method to take parameters. Just not a body.
I am not 100% sure that it would be considered RESTful as it could violates
some REST principlebut I think we do not want to open this discussion.
So yes it
Hi Vish,
Thank you very much indeed for your reply!
From: Vishvananda Ishaya [mailto:vishvana...@gmail.com]
Sent: 12 November 2013 21:56
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Nova XML serialization bug 1223358 moving
discussion here to get
Hi
Generally mock is supposed to be used over mox now for python 3 support.
That is my understanding too
As for when to use mock vs stubs, I think you'll get different opinions from
different people. Stubs are quick and easy and that's what I used early when I
started contributing to the
in finding a common solution for the
original bug.
As soon as we have a consensus I'll be really happy to submit a new patch.
Regards
--
Andrea Rosa
-Original Message-
From: Rosa, Andrea (HP Cloud Services)
Sent: 01 November 2013 14:35
To: OpenStack Development Mailing List (openstack-dev
-Original Message-
From: Chris Friesen [mailto:chris.frie...@windriver.com]
Sent: 31 October 2013 17:07
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] When is it okay for submitters to say 'I don't
want to add tests' ?
On 10/31/2013 06:04 AM, Rosa, Andrea (HP Cloud
Hi all
Long story short: a long time ago I raised a bug [1] and I started to work on
the fix: GuoHui LIu (the reviewer) and myself had long and useful discussion
about the right solution for that but now we are stuck and we need some more
opinions to find a proper one.
And now the long
Hi all,
This is a bit of a social norms thread
I've been consistently asking for tests in reviews for a while now, and I get
the
occasional push-back. I think this falls into a few broad camps:
A - there is no test suite at all, adding one in unreasonable B - this thing
cannot
be tested
Hi
2. Before submitting the new patch for review it's better to run unit tests
(tox -epy27) and pep8 check (tox -epep8)
Instead of pep8 I think you should run flake8 we moved to that some months
ago[1].
Usually I find always useful to test my changes in devstack.
Regards
--
Andrea Rosa
[1]
Hi
On 23.10.2013 11:29, Rosa, Andrea (HP Cloud Services) wrote:
Usually I find always useful to test my changes in devstack.
How do you do that? I think the devstack does not always contain up to date
codebase does it, so what would be the point in testing changes on the old
code?
With devstack
Hi Clark,
From: Clark Boylan [mailto:clark.boy...@gmail.com]
Sent: 11 September 2013 04:44
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] run_tests in debug mode fails
I did manage to confirm that the attached patch mostly fixes the problem.
with your patch I am able to
Hi all
I need to debug a specific test but when I try to run it in debug mode using
the run_tests -d (I need to attach pdb) that command fails but if I run the
script without the -d option that works.
I created a brand-new env so I don't think it's related to my local env.
Anyone is
HI
AFAIK, amqp only uses the exchange as a dispatcher and all storage is done in
the queue ... but I could be wrong. I vaguely recall there being a durable
exchange setting as well as durable queue.
AFAIK if a message can't be routed there are three options:
- the message is discarded (I think
I'd like to turn it off by default, as already pointed in [1] I think the rate
limiting should be managed by something else (for example load balancers) in
front of the API.
Regards
--
Andrea Rosa
[1] http://www.gossamer-threads.com/lists/openstack/operators/28599
From: Joe Gordon
Hi all,
What happens if a greenthread, after acquiring a lock (not external), it dies?
For example:
A thread is performing the do_terminate_instance, it has the lock and before
terminating the process it dies, what happens at the lock?
Is that released in some way?
If not I think that all
22 matches
Mail list logo