Re: [openstack-dev] [puppet][Fuel] OpenstackLib Client Provider Better Exception Handling

2015-10-15 Thread Vladimir Kuklin
Gilles, 5xx errors like 503 and 502/504 could always be intermittent operational issues. E.g. when you access your keystone backends through some proxy and there is a connectivity issue between the proxy and backends which disappears in 10 seconds, you do not need to rerun the puppet completely -

Re: [openstack-dev] [puppet][Fuel] OpenstackLib Client Provider Better Exception Handling

2015-10-15 Thread Gilles Dubreuil
On 15/10/15 12:42, Matt Fischer wrote: > > > On Thu, Oct 8, 2015 at 5:38 AM, Vladimir Kuklin > wrote: > > Hi, folks > > * Intro > > Per our discussion at Meeting #54 [0] I would like to propose the > uniform approach of

Re: [openstack-dev] [puppet][Fuel] OpenstackLib Client Provider Better Exception Handling

2015-10-15 Thread Vladimir Kuklin
Matt > You are right, it probably won't. At that point you are using puppet to work around some fundamental issues in your OpenStack deployment. Actually, as you know, with Fuel we are shipping our code to people who have their own infrastructure. We do not have any control over that

Re: [openstack-dev] [puppet][Fuel] OpenstackLib Client Provider Better Exception Handling

2015-10-15 Thread Matt Fischer
On Thu, Oct 15, 2015 at 4:10 AM, Vladimir Kuklin wrote: > Gilles, > > 5xx errors like 503 and 502/504 could always be intermittent operational > issues. E.g. when you access your keystone backends through some proxy and > there is a connectivity issue between the proxy and

Re: [openstack-dev] [puppet][Fuel] OpenstackLib Client Provider Better Exception Handling

2015-10-15 Thread Gilles Dubreuil
On 15/10/15 21:10, Vladimir Kuklin wrote: > Gilles, > > 5xx errors like 503 and 502/504 could always be intermittent operational > issues. E.g. when you access your keystone backends through some proxy > and there is a connectivity issue between the proxy and backends which > disappears in 10

Re: [openstack-dev] [puppet][Fuel] OpenstackLib Client Provider Better Exception Handling

2015-10-14 Thread Matt Fischer
On Thu, Oct 8, 2015 at 5:38 AM, Vladimir Kuklin wrote: > Hi, folks > > * Intro > > Per our discussion at Meeting #54 [0] I would like to propose the uniform > approach of exception handling for all puppet-openstack providers accessing > any types of OpenStack APIs. > > *

Re: [openstack-dev] [puppet][Fuel] OpenstackLib Client Provider Better Exception Handling

2015-10-13 Thread Rich Megginson
On 10/13/2015 12:57 PM, Emilien Macchi wrote: On 10/08/2015 07:38 AM, Vladimir Kuklin wrote: [...] * Proposed solution Introduce a library of exception handling methods which should be the same for all puppet openstack providers as these exceptions seem to be generic. Then, for each of the

Re: [openstack-dev] [puppet][Fuel] OpenstackLib Client Provider Better Exception Handling

2015-10-13 Thread Emilien Macchi
On 10/08/2015 07:38 AM, Vladimir Kuklin wrote: [...] > * Proposed solution > > Introduce a library of exception handling methods which should be the > same for all puppet openstack providers as these exceptions seem to be > generic. Then, for each of the providers we can introduce >

[openstack-dev] [puppet][Fuel] OpenstackLib Client Provider Better Exception Handling

2015-10-08 Thread Vladimir Kuklin
Hi, folks * Intro Per our discussion at Meeting #54 [0] I would like to propose the uniform approach of exception handling for all puppet-openstack providers accessing any types of OpenStack APIs. * Problem Description While working on Fuel during deployment of multi-node HA-aware environments