Michael Still wrote:
On 21/07/12 00:08, Jay Pipes wrote:
Not that I've seen, but I think it would be good to standardize on one.
How about just ops?
Works for me.
Added to http://wiki.openstack.org/BugTags and as official tag for all
core projects.
Cheers,
--
Thierry Carrez (ttx)
On 23/07/12 19:54, Thierry Carrez wrote:
Michael Still wrote:
On 21/07/12 00:08, Jay Pipes wrote:
Not that I've seen, but I think it would be good to standardize on one.
How about just ops?
Works for me.
Added to http://wiki.openstack.org/BugTags and as official tag for all
core
On 21/07/12 00:08, Jay Pipes wrote:
Not that I've seen, but I think it would be good to standardize on one.
How about just ops?
Works for me.
Mikal
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
On 19/07/12 23:16, Gabe Westmaas wrote:
There is definitely support for logging only patches that help us
find problems easier. I just added openstack operators, because I
think it would be good to get as much input as possible over what
problems are difficult to track down.
Some thoughts
On 07/18/2012 04:32 PM, Eugene Kirpichov wrote:
Hi,
I noticed that there are quite a few cases when I found my OpenStack
installation is broken and logging was not verbose enough for me to
understand what exactly was broken, so I had to add more logging
statements to the code and relaunch.
+malini.k.bhandaru=intel@lists.launchpad.net
[mailto:openstack-bounces+malini.k.bhandaru=intel@lists.launchpad.net] On
Behalf Of Eugene Kirpichov
Sent: Wednesday, July 18, 2012 4:32 PM
To: openstack@lists.launchpad.net
Subject: [Openstack] Improving logging
Hi,
I noticed
On 19/07/12 09:32, Eugene Kirpichov wrote:
Hi,
I noticed that there are quite a few cases when I found my OpenStack
installation is broken and logging was not verbose enough for me to
understand what exactly was broken, so I had to add more logging
statements to the code and relaunch.
Most
7 matches
Mail list logo
