[openstack-dev] [magnum] Issue on going through the quickstart guide

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 : Connection re

Re: [openstack-dev] [all][oslo] Dealing with database connection sharing issues

> On Feb 21, 2015, at 9:49 PM, Joshua Harlow wrote: > > Some comments/questions inline... > > Mike Bayer wrote: >> >> Yuriy Taraday wrote: >> On Fri Feb 20 2015 at 9:14:30 PM Joshua Harlow wrote: This feels like something we could do in the service manager base class,

Re: [openstack-dev] [all][oslo] Dealing with database connection sharing issues

Some comments/questions inline... Mike Bayer wrote: Yuriy Taraday wrote: On Fri Feb 20 2015 at 9:14:30 PM Joshua Harlow 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 hav

Re: [openstack-dev] [all][oslo] Dealing with database connection sharing issues

Yuriy Taraday wrote: > On Fri Feb 20 2015 at 9:14:30 PM Joshua Harlow 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 some

Re: [openstack-dev] [neutron] [lbaas] Querries Regarding Health Monitor parameter in loadbalancer

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 wrote: Hi Team As per V2 API speci

Re: [openstack-dev] [all][oslo] Dealing with database connection sharing issues

On Fri Feb 20 2015 at 9:14:30 PM Joshua Harlow 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: > > def __i

Re: [openstack-dev] [Openstack-operators] RFC: Increasing min libvirt to 1.0.6 for LXC driver ?

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 sho

Re: [openstack-dev] [Openstack-operators] Resources owned by a project/tenant are not cleaned up after that project is deleted from keystone

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 'proje

Re: [openstack-dev] [Neutron] FWaaS - question about drivers

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 wrote: Hello, Thx guys. Now it is clear for me