8/25 Opscode Ticket Triage


#1

Ohai!

Here are the results from our weekly ticket merge:

To merge:
CHEF-2346 - beware of solr maxFieldLength option ! It will stop indexing nodes with a lot of attributes
CHEF-2548 - Options list in knife manpages are out of date
CHEF-2549 - Add start handlers to a chef-client run
CHEF-2553 - chef-solr configs are packed within tar.gz
CHEF-2559 - --with-uri option broken for multiple commands
CHEF-2563 - Missing specs for some of the knife cookbook commands
OHAI-157 - Ohai doesn’t get ip address when multiple attached to one interface

COOK-681 - create a SQL Server cookbook
COOK-721 - ssh_known_hosts creates the known_hosts file with incorrect permissions

To fix:
OHAI-291 - StringIO needs to be required in ruby 1.8.7

Other:
OHAI-152 - Reports Fedora systems as redhat.

This raises a larger question about the possibility for a new ohai attribute; platform_family maybe? more discussion to come on that.

Seth


Opscode, Inc.
Seth Chisamore, Software Design Engineer
IRC, Skype, Twitter, Github: schisamo


#2

Seth Chisamore schisamo@opscode.com writes:

Bonjour,

To merge:
CHEF-2346 - beware of solr maxFieldLength option ! It will stop
indexing nodes with a lot of attributes

is 100k enough ?
what about issuing a warning when the limit has been reached ?


Laurent


#3

I agree (and I’ve commented in the ticket), Silent drop / failure
shouldn’t be the norm.
-C

On Fri, Aug 26, 2011 at 3:27 AM, laurent+opscode@u-picardie.fr wrote:

Seth Chisamore schisamo@opscode.com writes:

Bonjour,

To merge:
CHEF-2346 - beware of solr maxFieldLength option ! It will stop
indexing nodes with a lot of attributes

is 100k enough ?
what about issuing a warning when the limit has been reached ?


Laurent


Christopher Brown, Chief Technical Officer, Opscode, Inc.
T: (425) 502-5522, E: cb@opscode.com
IRC, Github: skeptomai
Twitter: @skeptomai