On Sat, Oct 31, 2015 at 09:11:31AM +0900, Davanum Srinivas wrote:
> Matt,
>
> 0.6.0 and 0.7.0 were released for Mitaka! not Liberty. Though yes, because
> of not having pins any library we release for Mitaka will end up being used
> with Liberty as well.
> http://lists.openstack.org/pipermail/open
Matt,
0.6.0 and 0.7.0 were released for Mitaka! not Liberty. Though yes, because
of not having pins any library we release for Mitaka will end up being used
with Liberty as well.
http://lists.openstack.org/pipermail/openstack-announce/2015-October/000701.html
No, we are not reverting. Here's my c
On 10/29/2015 5:22 PM, Sean Dague wrote:
Right, the crux of the problem is the move by the library from SIGUSR1
-> SIGUSR2 with no overlap and deprecation period breaks the ability to
have any tooling use this without atomically updating that tooling, and
this library, in all environments, all
On 10/29/2015 4:46 PM, Davanum Srinivas wrote:
Matt,
Yes, Sean already opened a critical bug -
https://bugs.launchpad.net/oslo.reports/+bug/1510740
Please note that this change was added to oslo.reports *after* the
liberty release in support of Mitaka. So i am not sure why we need to
add it t
Right, the crux of the problem is the move by the library from SIGUSR1
-> SIGUSR2 with no overlap and deprecation period breaks the ability to
have any tooling use this without atomically updating that tooling, and
this library, in all environments, all at the same time.
We need the SIGUSR1 handle
Matt,
Yes, Sean already opened a critical bug -
https://bugs.launchpad.net/oslo.reports/+bug/1510740
Please note that this change was added to oslo.reports *after* the liberty
release in support of Mitaka. So i am not sure why we need to add it to liberty
release notes. Also this is a consequence
On 10/21/2015 7:43 AM, Kashyap Chamarthy wrote:
Background
--
Oslo Guru Meditation (error) Reports (GMR)[*] are a useful debugging
mechanism that allows one to capture the current state of a Nova
process/executable (e.g. `nova-compute`, `nova-api`, etc).
The way to generate the error
On Wed, Oct 21, 2015 at 01:58:46PM -0400, Davanum Srinivas wrote:
> Sean,
>
> If you are using the GMR code from oslo-incubator, please switch over to
> the new oslo.service. I don't see any pending reviews.
>
> Thanks,
> -- Dims
Thanks Dims. I remembered the initial patch from May that added it
Sean,
If you are using the GMR code from oslo-incubator, please switch over to
the new oslo.service. I don't see any pending reviews.
Thanks,
-- Dims
On Wed, Oct 21, 2015 at 1:29 PM, Sean McGinnis
wrote:
> On Wed, Oct 21, 2015 at 02:43:39PM +0200, Kashyap Chamarthy wrote:
> > Background
> > --
On Wed, Oct 21, 2015 at 02:43:39PM +0200, Kashyap Chamarthy wrote:
> Background
> --
>
> Oslo Guru Meditation (error) Reports (GMR)[*] are a useful debugging
> mechanism that allows one to capture the current state of a Nova
> process/executable (e.g. `nova-compute`, `nova-api`, etc).
>
>
Background
--
Oslo Guru Meditation (error) Reports (GMR)[*] are a useful debugging
mechanism that allows one to capture the current state of a Nova
process/executable (e.g. `nova-compute`, `nova-api`, etc).
The way to generate the error report is to supply the 'User-defined
signal', SIGUS
11 matches
Mail list logo
