On 16/12/13 03:47, Thomas Goirand wrote:
Hi,
I've been working over the last 2 months to get Ironic, TripleO and
Tuskar ready for an upload in Debian. However, for tuskar-ui, I'm facing
the fact that there's a lack of documentation.
It was easy to get Tuskar packaged. If I understand well, it o
Ok, I though we can make make cinder-volume aware of SIGTERM call and make
sure it terminates with cleaning all the existing operations. If its not
possible then probably SIGHUB is the only solution. :(
On Mon, Dec 16, 2013 at 10:25 AM, Joshua Harlow wrote:
> It depends on the "corruption" that
On 13/12/13 19:13, Thierry Carrez wrote:
> Robert Collins wrote:
>> "
>> Confirmed The bug was reproduced or confirmed as a genuine bug
>> Triaged The bug comments contain a full analysis on how to properly
>> fix the issue
>> "
>>
>> From wiki.openstack.org/wiki/Bugs
>>
>> Putting aside the diffic
Hi Stephan
Comments inline for redirect action. Perhaps we may want to discuss each
section in different email threads.
On Sun, Dec 15, 2013 at 8:49 AM, Stephen Wong wrote:
> Hi,
>
> During Thursday's group-policy meeting[1], there are several
> policy-rules related issues which we agreed
It depends on the "corruption" that u are willing to tolerate. Sigterm means
the process just terminates, what if said process was 3/4 through some
operation (create_volume for example)??
Personally I am willing to tolerate zero corruption, reliability and
consistency are foundational things fo
How about sending SIGTERM to child processes and then starting them? I know
this is the hard way of achieving the objective and SIGHUP approach will
handle it more gracefully. As you mentioned it is a major change,
tentatively can we use SIGTERM to achieve the objective?
On Mon, Dec 16, 2013 at 9
The basic upgrade process for all versions of Swift follow the same basic
pattern:
First for storage nodes:
On a single "canary" node:
1) stop background processes
2) upgrade packages
3) restart/reload main processes
4) start background processes
And if everything goes well there, perform the sa
In your proposal does it means that the child process will be restarted (that
means kill -9 or sigint??). If so, without taskflow to help (or other solution)
that means operations in progress will be corrupted/lost. That seems bad...
A SIGHUP approach could be handled more gracefully (but it doe
What's the easiest way to upgrade Swift from a Folsom(ish) release to Havana?
Any shortcuts or is it best to follow the multinode installation instructions?
Apologizes for the dumb question.
Thanks,
Tim
___
OpenStack-dev mailing list
OpenStack-dev@lists
Hi,
I've been working over the last 2 months to get Ironic, TripleO and
Tuskar ready for an upload in Debian. However, for tuskar-ui, I'm facing
the fact that there's a lack of documentation.
It was easy to get Tuskar packaged. If I understand well, it only needs
2 daemons: tuskar-api, and tuskar
On 15 December 2013 21:17, Clint Byrum wrote:
> Excerpts from Steven Dake's message of 2013-12-14 09:00:53 -0800:
>> On 12/13/2013 01:13 PM, Clint Byrum wrote:
>> > Excerpts from Dmitry Mescheryakov's message of 2013-12-13 12:01:01 -0800:
>> >> Still, what about one more server process users will
+1 in support.
-Lianhao
Nicolas Barcet wrote on 2013-12-13:
> +1 in support of Sandy. He is a proven contributor and reviewer and he
> brings a great business vision and experience to the team.
>
> Cheers,
> Nick
>
>
> On Wed, Dec 11, 2013 at 8:18 PM, Gordon Chung wrote:
>
>
> > To
On 16 December 2013 03:36, Matt Riedemann wrote:
> I was looking at this review [1] and grepping through the code on that
> method and found a lot of old code [2][3] that needs to be removed but can't
> until we bump the network API version to 2.0.
>
> I know Russell has started bumping the comput
On Sat, Dec 14, 2013 at 10:30 PM, Subramanian <
subramanian.neelakan...@gmail.com> wrote:
> Is there a bug/bp tracking the overall cinder unit tests move from mox to
> mock? Is this targeted to complete in IceHouse?
>
> Thanks,
> Subbu
>
There is no bp tracking who is switching over what. The ge
On Sun, Dec 15, 2013 at 3:08 AM, iKhan wrote:
> I don't know if this is being planned in Icehouse, if not probably
> proposing an approach will help. We have seen cinder-volume service
> initialization part. Similarly if we can get our hands on child process
> that are running under cinder-volume
On 12/15/2013 09:59 AM, Ajay Phogat wrote:
> Extremely sorry I could reply back, I had my vacations and was away on
> leave.
>
> Sure, I'll do try to come in contact with the current developers as to know
> how I can contribute. Thanks a lot for your help and time. Have a great
> time!
>
>
> On
Hi Mohammad,
Good writeup, one minor comment at the end below (look for [s3wong]).
On Thu, Dec 12, 2013 at 3:42 PM, Mohammad Banikazemi wrote:
> Continuing the discussion we had earlier today during the Neutron Group
> Policy weekly meeting [0], I would like to initiate a couple of email
> t
Hi,
During Thursday's group-policy meeting[1], there are several
policy-rules related issues which we agreed should be posted on the
mailing list to gather community comments / consensus. They are:
(1) Conflict resolution between policy-rules
--- a priority field was added to the policy-
On 12/10/2013 10:33 AM, Ben Nemec wrote:
> On 2013-12-09 21:37, Adam Young wrote:
>> While Python 3 has enumerated types, Python 2 does not, and the
>> standard package to provide id, Flufl.enum, is not yet part of our
>> code base. Is there any strong objection to including Flufl.enum?
>>
>> ht
Extremely sorry I could reply back, I had my vacations and was away on
leave.
Sure, I'll do try to come in contact with the current developers as to know
how I can contribute. Thanks a lot for your help and time. Have a great
time!
On Tue, Nov 12, 2013 at 4:38 PM, Julie Pichon wrote:
> Hi Ajay
I was looking at this review [1] and grepping through the code on that
method and found a lot of old code [2][3] that needs to be removed but
can't until we bump the network API version to 2.0.
I know Russell has started bumping the compute RPC API version so would
something like this for the
I don't know if this is being planned in Icehouse, if not probably
proposing an approach will help. We have seen cinder-volume service
initialization part. Similarly if we can get our hands on child process
that are running under cinder-volume service, if we terminate those process
and restart them
Excerpts from Steven Dake's message of 2013-12-14 09:00:53 -0800:
> On 12/13/2013 01:13 PM, Clint Byrum wrote:
> > Excerpts from Dmitry Mescheryakov's message of 2013-12-13 12:01:01 -0800:
> >> Still, what about one more server process users will have to run? I see
> >> unified agent as library whi
23 matches
Mail list logo
