Jeremy Bingham | 1 Oct 01:24 2014
Picon

goiardi 0.8.0 & shovey

Just in time for Chef Summit, I'd like to announce the release of goiardi 0.8.0 "Hojotoho! Hojotoho!". This release brings "shovey", a goiardi facility for running jobs on nodes without a chef-client run. It's similar to Chef Push, although the implementation is rather different - shovey is built into goiardi, rather than running in a separate push-server, and it uses serf to send its commands out rather than polling zeromq.

Shovey with goiardi isn't very useful without a way to execute or manage the jobs, which is why there is also schob 0.1.0 "Heiaha! Heiaha!", the shovey client, and knife-shove 0.6.0 "Helmwige! Hier!", a knife plugin forked from knife-push to manage shovey jobs.

There are releases:


And there is documentation:


Blog post is at https://github.com/ctdk/knife-shove/blob/master/README.rdoc. A better cookbook for the shovey client, and a cookbook for goiardi itself, are coming soon.

Thanks, and if you're coming to the Summit I'll see you there.

-j
Douglas Thrift | 1 Oct 00:55 2014
Picon

Updates and new cookbooks from RightScale

Ohai chefs,

RightScale has just published new versions of two cookbooks and one new cookbook today:

rightscale_volume (v1.2.3)

  • Support volume types on all clouds instead of just those that require it (#16).

rightscale_backup (v1.1.5)

  • Remove unused code that previously dealt with volume types (#13).

rhsm (v1.0.0)

Cookbook to handle RedHat Subscription Management.

-- Douglas William Thrift <http://douglasthrift.net/>
pratik_gadiya | 30 Sep 21:08 2014
Picon

How to pass hash password from ruby-block to user resource


Hi All,

I am trying to implement a cookbook which would create users by reading
passwords from attributes file ( non hash password ex: root <at> 123)

And for this, my cookbook is as follows :

1. Contains of attributes file ( attributes/attr.rb )

default['my']['instance']['users']=[{uid:
1004,user_name:'m1',homedir:'/home/m1',password:'root <at> 111'},{uid:
1003,user_name:'m2',homedir:'/home/m2',password:'root <at> 222'},{uid: 1002,
user_name:'m3',homedir:'/home/m3',password:'root <at> 333'}]

2. Recipe : 

password_hash=''
node['my']['instance']['users'].each do |each_user|
    ruby_block "Generating hash password" do
	block do
	    require 'digest/sha2'
	    password=each_user['password']
	    salt=rand(36**8).to_s(36)
	    shadow_hash=password.crypt("$6$" + salt)
	    password_hash=shadow_hash
	end
    end

    user each_user['user_name'] do
	password "#{password_hash}"
	home each_user['homedir']
	system true
	action :create
	manage_home true
	uid each_user['uid']
    end
end

After execution of the cookbook, respective users are created appropriately but
passwords are set blank.

Looks like the variable which I am trying to access in the password attribute
of user resource is not correct.

Please let me how can I resolve this.

Note : In my case, I dont want to use databags

Thanks,
Pratik

Tom Duffield | 30 Sep 20:22 2014

Knife Container Redesign Discussion - Feedback Requested

Ohai Chefs,

The Chef Community Summit is coming up and I am very excited to see everyone and have a chance to talk about Chef Container. There has been a lot of work being on both chef-init and knife-container including the initial stages of a huge redesign that will address many of the pain points that have been mentioned by everyone as well as ensure that the container workflow fits with the chef workflow that is being established.

You can find the discussion happening in Issue #22 of the chef-init repo: https://github.com/opscode/chef-init/issues/22

I want to thank everyone who has tried out Knife Container so far and I want to especially thank everyone who has filed issues or spoken to me about their experiences on IRC. I look forward to hearing your feedback on the design changes I've proposed either on the mailing list, in the issue, or this week at the Chef Summit.

Thanks,


Tom Duffield — Software Development Engineer

651.769.7497 – tom <at> getchef.com – my: Linkedin  Twitter

CHEF

GETCHEF.COM

TM

getchef.com   Blog   Facebook   Twitter   Youtube





Morgan Blackthorne | 30 Sep 17:11 2014
Picon

Re: Re: Re: Re: Re: Re: Shellshock patching with Chef

Thanks, that looks great!

--
~*~ StormeRider ~*~

"Every world needs its heroes [...] They inspire us to be better than we are. And they protect from the darkness that's just around the corner."

(from Smallville Season 6x1: "Zod")

On why I hate the phrase "that's so lame"... http://bit.ly/Ps3uSS

On Tue, Sep 30, 2014 at 8:05 AM, David Giesberg <david <at> davidgiesberg.net> wrote:
Morgan,

I can't speak to RH distros, but we (Union Metrics) are an Ubuntu shop. I put together some logic that *only* updates the bash package if the package version for that OS release is lower than the version detailed in the USN. This gist shows the whole rundown - hopefully it's useful to you and anyone else trying to figure out how to deal with updating these packages gracefully: https://gist.github.com/davidgiesberg/aa7116611737edee31e0

-David Giesberg

On Mon, Sep 29, 2014 at 5:48 PM, Morgan Blackthorne <stormerider <at> gmail.com> wrote:
I'd rather have a bit more control, and that doesn't help for our RH family boxen.

--
~*~ StormeRider ~*~

"Every world needs its heroes [...] They inspire us to be better than we are. And they protect from the darkness that's just around the corner."

(from Smallville Season 6x1: "Zod")

On why I hate the phrase "that's so lame"... http://bit.ly/Ps3uSS

On Mon, Sep 29, 2014 at 3:39 PM, Brian Pitts <brian.pitts <at> lonelyplanet.com> wrote:
Depending on your tolerance for automatic security upgrades, on ubuntu
and debian you could use
https://supermarket.getchef.com/cookbooks/unattended-upgrades

On Mon, Sep 29, 2014 at 5:32 PM, Morgan Blackthorne
<stormerider <at> gmail.com> wrote:
> We have our own mirror for ubuntu, but we don't force the latest version. I
> don't think we have RHEL or OL or Debian mirrors at the moment, though.
>
> Forcing the latest version might just be the simplest way to resolve it.
>
> --
> ~*~ StormeRider ~*~
>
> "Every world needs its heroes [...] They inspire us to be better than we
> are. And they protect from the darkness that's just around the corner."
>
> (from Smallville Season 6x1: "Zod")
>
> On why I hate the phrase "that's so lame"... http://bit.ly/Ps3uSS
>
> On Mon, Sep 29, 2014 at 3:26 PM, AJ Christensen
> <aj <at> junglistheavy.industries> wrote:
>>
>> yo,
>>
>> On Tue, Sep 30, 2014 at 11:23 AM, Morgan Blackthorne
>> <stormerider <at> gmail.com> wrote:
>> > I'm looking to see if there's a good way to help manage patching of
>> > vulnerabilities with Chef. This Shellshock one seems to be a great
>> > example
>> > of why Chef would be a helpful tool for the job, since it's just a
>> > package
>> > in need of upgrading (bash).
>> >
>> > My question is, what's the best way in Chef to say "for this
>> > distribution
>> > and release, ensure that this package is at least at version X" without
>> > potentially downgrading the package down the road? I want to set a
>> > minimum
>> > bar, but I don't wan't to permanently pin the version.
>>
>> I like pushing sec packages into a signed internal repository. Always
>> roll to latest. Makes the chef code simple(r), especially for managing
>> multiple edges.
>>
>> Some providers support pessimistic version specifications (~>). They
>> may be of use.
>>
>> --aj
>>
>> >
>> > Thoughts? Thanks!
>> >
>> > --
>> > ~*~ StormeRider ~*~
>> >
>> > "Every world needs its heroes [...] They inspire us to be better than we
>> > are. And they protect from the darkness that's just around the corner."
>> >
>> > (from Smallville Season 6x1: "Zod")
>> >
>> > On why I hate the phrase "that's so lame"... http://bit.ly/Ps3uSS
>
>



--
Brian Pitts
Web Operations Engineer



Vangelis Katsikaros | 30 Sep 10:46 2014
Picon

knife show organization

Hi

I would like to ask if there is a way with knife to list the 
organization it is configured to work with.

So if in a dir the .chef/knife.rb has:
chef_server_url      "https://api.opscode.com/organizations/my_org_name"

I would like to do something like:
$ knife organization
my_org_name

Regards
Vangelis

Jesse Adams | 30 Sep 03:04 2014

knife-linode 0.3.1 released!

This small release just includes one change:

jblancett - Add option for setting display group in linode web portal

Thanks!

Jesse

Morgan Blackthorne | 30 Sep 01:22 2014
Picon

omnibus_updater equivalent for Windows?

Does anyone know of something like this? Thanks!

--
~*~ StormeRider ~*~

"Every world needs its heroes [...] They inspire us to be better than we are. And they protect from the darkness that's just around the corner."

(from Smallville Season 6x1: "Zod")

On why I hate the phrase "that's so lame"... http://bit.ly/Ps3uSS
Morgan Blackthorne | 30 Sep 00:23 2014
Picon

Shellshock patching with Chef

I'm looking to see if there's a good way to help manage patching of vulnerabilities with Chef. This Shellshock one seems to be a great example of why Chef would be a helpful tool for the job, since it's just a package in need of upgrading (bash).

My question is, what's the best way in Chef to say "for this distribution and release, ensure that this package is at least at version X" without potentially downgrading the package down the road? I want to set a minimum bar, but I don't wan't to permanently pin the version.

Thoughts? Thanks!
 
--
~*~ StormeRider ~*~

"Every world needs its heroes [...] They inspire us to be better than we are. And they protect from the darkness that's just around the corner."

(from Smallville Season 6x1: "Zod")

On why I hate the phrase "that's so lame"... http://bit.ly/Ps3uSS
Indra k | 29 Sep 15:05 2014

sugarcrm-ce --no method error

Hi,

When installing sugarcrm-ce cookbook, it shows   no method error.I ve added their dependencies cookbook and am testing that in a linux platform of ubuntu,

[2014-09-29T14:30:25+02:00] INFO: *** Chef 11.4.4 ***
[2014-09-29T14:30:26+02:00] INFO: Setting the run_list to ["recipe[chef_handler]", "recipe[notification_handler]", "recipe[sugarcrm-ce]"] from JSON
[2014-09-29T14:30:26+02:00] INFO: Run List is [recipe[chef_handler], recipe[notification_handler], recipe[sugarcrm-ce]]
[2014-09-29T14:30:26+02:00] INFO: Run List expands to [chef_handler, notification_handler, sugarcrm-ce]
[2014-09-29T14:30:26+02:00] INFO: Starting Chef Run for e41bd7ad-f9fc-4a41-b7a7-419443b4575c
[2014-09-29T14:30:26+02:00] INFO: Running start handlers
[2014-09-29T14:30:26+02:00] INFO: Start handlers complete.
[2014-09-29T14:30:26+02:00] ERROR: Running exception handlers
[2014-09-29T14:30:27+02:00] ERROR: Exception handlers complete
[2014-09-29T14:30:27+02:00] FATAL: Stacktrace dumped to /var/chef-solo/cache/chef-stacktrace.out
[2014-09-29T14:30:27+02:00] FATAL: NoMethodError: undefined method `[]' for nil:NilClass
~                                                            
Thanks & regards,
indra K

Mathias Lafeldt | 29 Sep 11:18 2014
Picon

Re: Article: Infrastructure automation by example (practicingruby.com)

All of Practicing Ruby’s articles, including "Infrastructure
automation by example", have been released behind the paywall and are
now freely available.

If you haven’t already read our piece on infrastructure automation
(with Chef), now is the perfect time to do so:

https://practicingruby.com/articles/infrastructure-automation

Since the project was great in so many ways, I also shared some
additional content on my personal blog:

http://mlafeldt.github.io/blog/infrastructure-automation-by-example/

-Mathias

On Tue, Nov 19, 2013 at 12:12 PM, Mathias Lafeldt
<mathias.lafeldt <at> gmail.com> wrote:
> Hi,
>
> We spent the last couple of weeks automating the infrastructure of
> practicingruby.com with Chef and writing an article about it. Each
> month Practicing Ruby publishes a Ruby-related article and I thought
> it would be cool to contribute something about treating
> "infrastructure as code".
>
> As a result, I've developed a Chef cookbook [1] that fully automates
> the process of setting up an environment that can run the Practicing
> Ruby Rails app. The final article [2] was a collaboration between me
> and Gregory Brown, who is the owner of Practicing Ruby and author of
> the O'Reilly book "Ruby Best Practices".
>
> This project was exhausting but also very rewarding. I hope you like
> the article.
>
> Nathen: Drop me a line if you think this article could be used for
> #learnchef or similar efforts. Gregory is fine with sharing the direct
> link.
>
> -Mathias
>
> [1] https://github.com/elm-city-craftworks/practicing-ruby-cookbook
> [2] https://practicingruby.com/articles/infrastructure-automation?u=c94a53804e
> (short link: http://tinyurl.com/pr-chef)


Gmane