On Feb 21, 2015, at 9:49 PM, Joshua Harlow harlo...@outlook.com wrote:
Some comments/questions inline...
Mike Bayer wrote:
Yuriy Taradayyorik@gmail.com wrote:
On Fri Feb 20 2015 at 9:14:30 PM Joshua Harlowharlo...@outlook.com
wrote:
This feels like something we could do in
Yuriy Taraday yorik@gmail.com wrote:
On Fri Feb 20 2015 at 9:14:30 PM Joshua Harlow harlo...@outlook.com wrote:
This feels like something we could do in the service manager base class,
maybe by adding a post fork hook or something.
+1 to that.
I think it'd be nice to have the
Some comments/questions inline...
Mike Bayer wrote:
Yuriy Taradayyorik@gmail.com wrote:
On Fri Feb 20 2015 at 9:14:30 PM Joshua Harlowharlo...@outlook.com wrote:
This feels like something we could do in the service manager base class,
maybe by adding a post fork hook or something.
+1
Hi all,
I tried to go through the new redis example at the quickstart guide [1],
but was not able to go through. I was blocked by connecting to the redis
slave container:
*$ docker exec -i -t $REDIS_ID redis-cli*
*Could not connect to Redis at 127.0.0.1:6379 http://127.0.0.1:6379:
Connection
Hello,
Thanks a lot for explanation. Now is is more clear for me :)
--
Pozrawiam / Best regards
Sławek Kapłoński
sla...@kaplonski.pl
W dniu 2015-02-21 o 01:20, Sumit Naiksatam pisze:
Inline...
On Fri, Feb 20, 2015 at 3:38 PM, Sławek Kapłoński sla...@kaplonski.pl wrote:
Hello,
Thx guys. Now
On Fri Feb 20 2015 at 9:14:30 PM Joshua Harlow harlo...@outlook.com wrote:
This feels like something we could do in the service manager base class,
maybe by adding a post fork hook or something.
+1 to that.
I think it'd be nice to have the service __init__() maybe be something
like:
Hi Rattenpal,
Could you elaborate on this more. I haven't seen any issues with the API being
able to parse type. it's using the json standard library. Is this in regard
to another json parser?
thanks,
brandon
On Feb 19, 2015 11:24 PM, Rattenpal Amandeep rattenpal.amand...@tcs.com wrote:
Hi
A few inline comments and a general point
How do we handle scenarios like volumes when we have a per-component janitor
rather than a single co-ordinator ?
To be clean,
1. nova should shutdown the instance
2. nova should then ask the volume to be detached
3. cinder could then perform the
Let's put off this cleanup to L release. There is a problem with mounting loop
device with enabled user namespaces. so we can't commit the change and broke
containers with user namespaces.
I going on vacation until 6th march, when I'll return I'm going to learn LXC
code and figure out, what
