- From: Bryan McLellan <
>
- To:
- Subject: [chef-dev] Opscode 2/1 Ticket Triage
- Date: Fri, 3 Feb 2012 10:58:07 -0800
Woops! Running late on this email, bunch of fires this week.
The engineering team at Opscode has been really busy rewriting Omnibus
in Ruby for immediate use for internal projects. Thus the release
dates for Ohai 0.6.12 and Chef 0.10.10 have slipped and I don't know
when we will get to them. Soon.
We've added a new resource to master named 'chef_gem'. We found a
pretty even split between people using gem_package for installing gems
for use in recipes and for use on the system. These really are
different use cases, particularly since the former required some
trickery to get the action to run immediately and then get Gem to
immediately recognise the new library. chef_gem does both of these for
you, simplifying the process. Details can be found in CHEF-2879.
http://tickets.opscode.com/browse/CHEF-2879
We've got a good CI infrastructure built out now on jenkins at Opscode
HQ, testing multiple versions of Ruby as well as Windows. Those of you
contributing tests definitely win cake.
Merge:
CHEF-2566 - knife cookbook site install (and possibly other
commands) does not gracefully handle paths with spaces
CHEF-2881 - Chef-client init scripts should have a target which
triggers a chef run with SIGUSR1
CHEF-2894 - Chef::Cookbook::Metadata initialize method hardcodes
license as Apache v2.0
CHEF-2896 - Shef's become_node fails with " HTTP Request Returned
400 Bad Request: Missing param: run_list"
CHEF-1247 - logrotate scripts attempt to rotate non-existent log files
CHEF-2856 - gpasswd provider does not handle empty groups
COOK-798 - Option to run Chef-client as a cron job
COOK-835 - Add app pool to IIS cookbook
COOK-860 - Nagios Email Notification Does Not Work When Combined
with Postfix Cookbook
COOK-905 - erlang cookbook on RedHat / Centos 6 fails
COOK-921 - apt: use cookbook_file or remote_file for key
COOK-947 - chef-solo support for recipe[apt::cacher-client] in apt cookbook
COOK-949 - NTP cookbook checks for VMware when it should check for
any virtualized system
COOK-955 - Nagios Service Checks Defined by Data Bags
COOK-957 - Nginx Cookbook: Compress application/javascript.
COOK-964 - database: Syntax error in recipe example for connection string
COOK-969 - server_name and server_aliases as configurable attributes
on chef_server::nginx_proxy and chef_server::apache_proxy
COOK-975 - Database resource doesn't honor attributes for template,
encoding, tablespace or connection limit when creating Postgres
databases.
COOK-981 - NGINX service should support reload - config files should
notify reload, not restart
Other:
CHEF-2594 - chef-expander goes into a die/fork/die loop on invalid messages
Reopened - Contributor needs a CLA
CHEF-2882 - Insufficient Rick Astley in 'rake roles' diagnostic message
Use case uncertain, can anyone provide one?
COOK-350 - LWRP to manage sudo files via includedir (/etc/sudoers.d)
Reopened - Backwards compatibility with /etc/sudoers.d?
COOK-985 - If chef-client runs on chef-server it will change
permissions on run and log directory which causes solr to crash.
Reopened - Use node.recipe?
COOK-599 - chef-client::config recipe breaks folder permissions of
chef-server::rubygems-install recipe on same node
Reopened - Use node.recipe?
COOK-778 - chef-server cookbook fails because chef-server can't load
libgecode*.so
Reopened - Use file resource instead of execute resource; what is
the state of gecode on RHEL5?
COOK-858 - Java cookbook doesn't properly handle new jdks from
Oracle, for java 6 and java 7
Reopened - Test on Ubuntu 10.04
COOK-911 - Add auto-clustering and SSL support to the rabbitmq recipe
Reopened - Questions about the patch
COOK-963 - application w/rails recipe fails for older rails 3.0.x
apps. Should use 'bundle exec unicorn' to launch unicorn when app uses
bundler
Reopened - Contributor needs a CLA
COOK-972 - Merge rvm, passenger and bundler cookbooks from
jamesotron/opscode-cookbooks
Closed - Wontfix, not accepting new cookbooks to our own repository.
COOK-981 - NGINX service should support reload - config files should
notify reload, not restart
Reopened - How do we know the nginx pid file will exist? What if it doesn't?
--
Bryan McLellan | opscode | technical program manager
(c) 206.607.7108 | (t) @btmspox | (b)
http://blog.loftninjas.org
- [chef-dev] Opscode 2/1 Ticket Triage, Bryan McLellan, 02/03/2012
Archive powered by MHonArc 2.6.16.