Skip to content
This repository was archived by the owner on Dec 31, 2021. It is now read-only.

Add support for Chef Solo/RightScale, fill out metadata, more directive support in template#4

Open
flaccid wants to merge 15 commits into
coderanger:masterfrom
flaccid:master
Open

Add support for Chef Solo/RightScale, fill out metadata, more directive support in template#4
flaccid wants to merge 15 commits into
coderanger:masterfrom
flaccid:master

Conversation

@flaccid

@flaccid flaccid commented Aug 27, 2012

Copy link
Copy Markdown

The client recipe has been improved to support chef-solo where collectd servers can be specified via a node attribute.

Metadata has been completed (recipes and attribute definitions) as well as adding metadata.json back as this is required for usage on RightScale.

The Hostname and FQDNLookup directives have been added to the template for user specifiable configuration to be more flexible on arbitrary node requirements.

@zach-rightscale

Copy link
Copy Markdown

Nice work Chris!

Comment thread attributes/default.rb Outdated

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a particular reason to use a string instead of a real Ruby boolean? Usually nice to use native types when possible.

@simonoff

Copy link
Copy Markdown

Any update?

Comment thread metadata.rb Outdated

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It only depends on apache2 if collectd_web is used. We don't use it for example

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kpumuk Chef doesn't support optional dependencies (in metadata) so technically its a dependency. What the best practice is, I'm not sure but personally I think its better to do this as recipes don't have a mechanism to even check nicely on the cookbook needed (which would also create a lot of extra redundant code in every cookbook that has optional deps).

@flaccid

flaccid commented Oct 21, 2013

Copy link
Copy Markdown
Author

@coderanger I have finally updated this pr! Please let me know if it needs more work before it can be merged. Thanks for your year-long patience :)

@coderanger

Copy link
Copy Markdown
Owner

Just as a heads up I'm about to get really busy for a week or two, and this no longer cleanly merges, so it may take a while to get it sorted.

@flaccid

flaccid commented Oct 22, 2013

Copy link
Copy Markdown
Author

No problem coderanger. I'll go on standby and look at for any action items I should do. Worse case, I don't mind re-doing the whole thing with a fresh fork, but it would be cool to avoid that if possible.

@jhmartin

Copy link
Copy Markdown
Contributor

Perhaps you could rebase on top of master so this becomes a clean merge?

@flaccid

flaccid commented Apr 21, 2015

Copy link
Copy Markdown
Author

@coderanger hmm what should we do now? Please let me know :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants