So given the increased complexity of a spec, why not make it 2 specs per week?
Matt
> -Original Message-
> From: Ben Nemec [mailto:openst...@nemebean.com]
> Sent: 23 July 2014 14:21
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [TripleO]
Any chance for getting it streamed or at least IRC'd for those of us who have
an interest in this but can't attend?
From: Robert Collins [robe...@robertcollins.net]
Sent: 20 July 2014 20:30
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [Triple
+1 from me.
Matt
> -Original Message-
> From: Clint Byrum [mailto:cl...@fewbar.com]
> Sent: 09 July 2014 16:52
> To: openstack-dev@lists.openstack.org
> Subject: [openstack-dev] [TripleO] Proposal to add Jon Paul Sullivan and
> Alexis
> Lee to core review team
>
> Hello!
>
> I've been
And the spec is now up at https://review.openstack.org/104524 for everyone to
pull apart... ;)
Matt
> -Original Message-
> From: Macdonald-Wallace, Matthew
> Sent: 03 July 2014 11:18
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re:
FWIW, I've just registered
https://blueprints.launchpad.net/tripleo/+spec/re-assert-system-state and I'm
about to start work on the spec.
Matt
> -Original Message-
> From: Clint Byrum [mailto:cl...@fewbar.com]
> Sent: 27 June 2014 17:01
> To: openstack-dev
> Subject: Re: [openstack-dev]
> -Original Message-
> From: Chris Jones [mailto:c...@tenshu.net]
> Sent: 26 June 2014 20:58
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [TripleO] os-refresh-config run frequency
>
> Hi
>
> On 26 Jun 2014, at 20:55, Clint Byrum wrote:
Hi Chris,
> -Original Message-
> From: Chris Jones [mailto:c...@tenshu.net]
> Sent: 26 June 2014 20:38
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [TripleO] os-refresh-config run frequency
>
> Hi
>
> Given...
>
> On 26 Jun 2014, at 2
Hi Clint,
> -Original Message-
> From: Clint Byrum [mailto:cl...@fewbar.com]
> Sent: 26 June 2014 20:21
> To: openstack-dev
> Subject: Re: [openstack-dev] [TripleO] os-refresh-config run frequency
>
> So I see two problems highlighted above.
>
> 1) We don't re-assert ephemeral state set
Hi all,
I've been working more and more with TripleO recently and whilst it does seem
to solve a number of problems well, I have found a couple of idiosyncrasies
that I feel would be easy to address.
My primary concern lies in the fact that os-refresh-config does not run on
every boot/reboot o
9:03
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [TripleO] Reviews - we need your help!
>
> On 12/06/14 16:02, Macdonald-Wallace, Matthew wrote:
> > FWIW, I've tried to make a useful dashboard for this using Sean
> > Dague's gerrit-das
FWIW, I’ve tried to make a useful dashboard for this using Sean Dague’s
gerrit-dash-creator [0].
Short URL is http://bit.ly/1l4DLFS long url is:
https://review.openstack.org/#/dashboard/?foreach=%28project%3Aopenstack%2Ftripleo-incubator+OR+project%3Aopenstack%2Ftripleo-image-elements+OR+project
Thanks all for the comments and I’m glad you agree with one of the proposed
approaches! ☺
I’ll take a look at using an env var first and then look at a check_mk.d style
directory if I get a chance later on.
Thanks again,
Matt
From: Robert Collins [mailto:robe...@robertcollins.net]
Sent: 29 Ap
Hi all,
I have a patch in flight at the moment [0] to install check_mk server and
compliment the already merged installation of check_mk agent [1] so my thoughts
are now turning to how we would recommend adding new service checks.
The concept behind check_mk makes this really simple to do. You
anks.
>
> -Ben
>
> On 04/20/2014 02:44 PM, Macdonald-Wallace, Matthew wrote:
> > Hi all,
> >
> > Can I please ask for some reviews on the following:
> >
> > https://review.openstack.org/#/c/87226/ - Install checkmk_agent
> > https://review.openstack.org/#
Hi all,
Can I please ask for some reviews on the following:
https://review.openstack.org/#/c/87226/ - Install checkmk_agent
https://review.openstack.org/#/c/87223/ - Install icinga cgi interface
I already have a souple of +1s and jenkins is happy, all I need is +2 and +A! :)
Thanks,
Matt
> -Original Message-
> From: Ben Nemec [mailto:openst...@nemebean.com]
> Sent: 31 January 2014 16:01
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] Proposed Logging Standards
> > I'd just love to see the ability in the python logger to include the
> > application nam
> -Original Message-
> From: Sean Dague [mailto:s...@dague.net]
> Sent: 31 January 2014 12:29
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] Proposed Logging Standards
>
> On 01/30/2014 07:15 PM, John Dickinson wrote:
> > 1) Every log mess
Re: [openstack-dev] Proposed Logging Standards
>
> Hi Matt,
> What about the rest of the components? Do they also have this capability?
> Thanks
>
> Cristian
>
> On 30/01/14 04:59, "Macdonald-Wallace, Matthew"
> wrote:
>
> >Hi Cristian,
> >
&
or this?
> Cheers,
>
> Cristian
>
> On 27/01/14 11:07, "Macdonald-Wallace, Matthew"
> wrote:
>
> >Hi Sean,
> >
> >I'm currently working on moving away from the "built-in" logging to use
> >log_config= and the python logging framewor
> > I've also noticed just now that we appear to be "re-inventing" some parts of
> the logging framework (openstack.common.log.WriteableLogger for example
> appears to be a "catchall" when we should just be handing off to the default
> logger and letting the python logging framework decide what to
> -Original Message-
> From: Sean Dague [mailto:s...@dague.net]
> Sent: 27 January 2014 14:26
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] Proposed Logging Standards
>
> On 01/27/2014 09:07 AM, Macdonald-Wallace,
> -Original Message-
> From: Sean Dague [mailto:s...@dague.net]
> Sent: 27 January 2014 14:26
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] Proposed Logging Standards
>
> On 01/27/2014 09:07 AM, Macdonald-Wallace,
Hi Sean,
I'm currently working on moving away from the "built-in" logging to use
log_config= and the python logging framework so that we can start
shipping to logstash/sentry/.
I'd be very interested in getting involved in this, especially from a "why do
we have log messages that are split acr
Hi all,
Please can one of the core reviewers take a look at
https://review.openstack.org/#/c/33296/ and either approve or reject it?
It has had two "+1's" from other developers and has also been passing Jenkins
and Smokestack since June 28th whilst undergoing numerous rebases.
I realise that t
Thanks, that's good news... :)
Matt
From: Doug Hellmann [mailto:doug.hellm...@dreamhost.com]
Sent: 26 June 2013 15:20
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [nova] Making logging more modular
On Wed, Jun 26, 2013 at 9:18 AM, Macdonald-Wallace, Ma
lopment Mailing List
Subject: Re: [openstack-dev] [nova] Making logging more modular
On Wed, Jun 26, 2013 at 6:31 AM, Macdonald-Wallace, Matthew
mailto:matthew.macdonald-wall...@hp.com>>
wrote:
Hi all,
One of the things we'd like to start thinking about is having the ability to
lo
Hi all,
One of the things we'd like to start thinking about is having the ability to
log to multiple destinations at the same time.
This would include a move towards making the logging section of Nova more like
the API and Network sections in that the end user would be able to include
multiple
27 matches
Mail list logo
