Contribute to the elasticsearch cookbook?


#1

Hello Opscode folks,

I’ve made a good update for the elasticsearch cookbook. And now I try to
fecth it from the opscode-cookbooks repository with no success:) Yeah,
it’s absent there.
But I’m really eager to merge my changes… So what steps should I
produce than?

Regards,
Denis


#2

Hi Denis,

On Thu, Apr 12, 2012 at 3:38 PM, Denis Barishev
denis.barishev@gmail.com wrote:

I’ve made a good update for the elasticsearch cookbook. And now I try to
fecth it from the opscode-cookbooks repository with no success:) Yeah, it’s
absent there.
But I’m really eager to merge my changes… So what steps should I produce
than?

Which elasticsearch cookbook? This one?

http://community.opscode.com/cookbooks/elasticsearch

That one is maintained by Grant Rodgers, not Opscode. Unless you mean
a different elasticsearch cookbook - I see three on GitHub after a
Google search.

The “ospcode-cookbooks” organization on GitHub contains only cookbooks
that we directly publish, maintain and support, all under the
"opscode" user on the community site. Everyone is free to share their
own cookbooks on the community site (and host the code repository
wherever they like).

http://community.opscode.com/users/opscode


Opscode, Inc
Joshua Timberman, Technical Program Manager
IRC, Skype, Twitter, Github: jtimberman


#3

On 04/13/2012 07:48 AM, Joshua Timberman wrote:

Hi Denis,

On Thu, Apr 12, 2012 at 3:38 PM, Denis Barishev
denis.barishev@gmail.com wrote:

I’ve made a good update for the elasticsearch cookbook. And now I try to
fecth it from the opscode-cookbooks repository with no success:) Yeah, it’s
absent there.
But I’m really eager to merge my changes… So what steps should I produce
than?
Which elasticsearch cookbook? This one?

http://community.opscode.com/cookbooks/elasticsearch

That one is maintained by Grant Rodgers, not Opscode. Unless you mean
a different elasticsearch cookbook - I see three on GitHub after a
Google search.

Yes this one.

The “ospcode-cookbooks” organization on GitHub contains only cookbooks
that we directly publish, maintain and support, all under the
"opscode" user on the community site. Everyone is free to share their
own cookbooks on the community site (and host the code repository
wherever they like).

http://community.opscode.com/users/opscode

Hey Joshua,

Thanks that exactly what I thought. This cookbook is heavily outdated.
Could we publish the new cookbook in the opscode repository? I think it
would be problematic to contact the author, the cookbook is dated to
2010 and it’s too old. Though I haven’t try to contact the author… I
mean the author doesn’t support the cookbook, so this may just turn into
a waste of time.
It also concerns all other cookbooks that are forgot by their authors.
They don’t have any life in their repositories. Actually I have also
created the new graylog2 cookbook which uses elasticsearch.
If both of them were in the opscode repository they would probably get
more progress.

So is it possible to publish the named cookbooks into the opsocde
repository?

Regards,
Denis


#4

Hi Denis,

I’am really glad you made a update on this both cookbooks, you can ask the
author to be a contributor on the community Opscode site. This way you
should be able to update the cookbooks."I am not sure about that I have
never try it"
On Apr 13, 2012 11:15 AM, “Denis Barishev” denis.barishev@gmail.com wrote:

On 04/13/2012 07:48 AM, Joshua Timberman wrote:

Hi Denis,

On Thu, Apr 12, 2012 at 3:38 PM, Denis Barishev
denis.barishev@gmail.com wrote:

I’ve made a good update for the elasticsearch cookbook. And now I try to
fecth it from the opscode-cookbooks repository with no success:) Yeah,
it’s
absent there.
But I’m really eager to merge my changes… So what steps should I
produce
than?

Which elasticsearch cookbook? This one?

http://community.opscode.com/**cookbooks/elasticsearchhttp://community.opscode.com/cookbooks/elasticsearch

That one is maintained by Grant Rodgers, not Opscode. Unless you mean
a different elasticsearch cookbook - I see three on GitHub after a
Google search.

Yes this one.

The “ospcode-cookbooks” organization on GitHub contains only cookbooks

that we directly publish, maintain and support, all under the
"opscode" user on the community site. Everyone is free to share their
own cookbooks on the community site (and host the code repository
wherever they like).

http://community.opscode.com/**users/opscodehttp://community.opscode.com/users/opscode

Hey Joshua,

Thanks that exactly what I thought. This cookbook is heavily outdated.
Could we publish the new cookbook in the opscode repository? I think it
would be problematic to contact the author, the cookbook is dated to 2010
and it’s too old. Though I haven’t try to contact the author… I mean the
author doesn’t support the cookbook, so this may just turn into a waste of
time.
It also concerns all other cookbooks that are forgot by their authors.
They don’t have any life in their repositories. Actually I have also
created the new graylog2 cookbook which uses elasticsearch.
If both of them were in the opscode repository they would probably get
more progress.

So is it possible to publish the named cookbooks into the opsocde
repository?

Regards,
Denis


#5

Hi,

On Fri, Apr 13, 2012 at 7:15 PM, Denis Barishev
denis.barishev@gmail.com wrote:

The “ospcode-cookbooks” organization on GitHub contains only cookbooks
that we directly publish, maintain and support, all under the
"opscode" user on the community site. Everyone is free to share their
own cookbooks on the community site (and host the code repository
wherever they like).

http://community.opscode.com/users/opscode

Thanks that exactly what I thought. This cookbook is heavily outdated. Could
we publish the new cookbook in the opscode repository? I think it would be
problematic to contact the author, the cookbook is dated to 2010 and it’s
too old. Though I haven’t try to contact the author… I mean the author
doesn’t support the cookbook, so this may just turn into a waste of time.
It also concerns all other cookbooks that are forgot by their authors. They
don’t have any life in their repositories.

This is a concern I also have. I have several cookbooks that have the
same name as those on the community site so I never bothered to look
into what would be required to release them there. If we could somehow
add a “name” field to the metadata that the download tool could use to
name the directory downloaded into (or perhaps rework the way recipes
are named to be based on names rather than directory names) that would
solve a lot of these issues.

Actually I have also created the
new graylog2 cookbook which uses elasticsearch.

I would be very interested in these - we already have custom
mongo/graylog cookbooks that were derived from somewhere in the wild
at one stage. I am a week or two away from upgrading from 0.9.5p1 to
the latest and would like to share the effort if possible. Are these
stored in a github repository anywhere?


Cheers,

Peter Donald


#6

Hello,

http://community.opscode.com/cookbooks/elasticsearch

That one is maintained by Grant Rodgers, not Opscode.

Thanks that exactly what I thought. This cookbook is heavily outdated. Could we publish the new cookbook in the opscode repository? I think it would be problematic to contact the author, the cookbook is dated to 2010 and it’s too old. Though I haven’t try to contact the author… I mean the author doesn’t support the cookbook, so this may just turn into a waste of time.

have you tried to contact Grant Rodgers [https://github.com/grantr] to discuss the matters with him? If not, I strongly suggest to do so. We have have frequently discussed out different approaches to Chef-related ElasticSearch stuff.

Karel


#7

Howdy!

On 04/16/2012 05:16 AM, Peter Donald wrote:

Hi,

On Fri, Apr 13, 2012 at 7:15 PM, Denis Barishev
denis.barishev@gmail.com wrote:

The “ospcode-cookbooks” organization on GitHub contains only cookbooks
that we directly publish, maintain and support, all under the
"opscode" user on the community site. Everyone is free to share their
own cookbooks on the community site (and host the code repository
wherever they like).

http://community.opscode.com/users/opscode
Thanks that exactly what I thought. This cookbook is heavily outdated. Could
we publish the new cookbook in the opscode repository? I think it would be
problematic to contact the author, the cookbook is dated to 2010 and it’s
too old. Though I haven’t try to contact the author… I mean the author
doesn’t support the cookbook, so this may just turn into a waste of time.
It also concerns all other cookbooks that are forgot by their authors. They
don’t have any life in their repositories.
This is a concern I also have. I have several cookbooks that have the
same name as those on the community site so I never bothered to look
into what would be required to release them there. If we could somehow
add a “name” field to the metadata that the download tool could use to
name the directory downloaded into (or perhaps rework the way recipes
are named to be based on names rather than directory names) that would
solve a lot of these issues.

Actually I have also created the
new graylog2 cookbook which uses elasticsearch.
I would be very interested in these - we already have custom
mongo/graylog cookbooks that were derived from somewhere in the wild
at one stage. I am a week or two away from upgrading from 0.9.5p1 to
the latest and would like to share the effort if possible. Are these
stored in a github repository anywhere?

Yes, I pushed them into my repo you may have a look:
https://github.com/dennybaa/cookbooks


#8

Hello,

On 04/16/2012 11:04 AM, Karel Minařík wrote:

Hello,

http://community.opscode.com/cookbooks/elasticsearch

That one is maintained by Grant Rodgers, not Opscode.
Thanks that exactly what I thought. This cookbook is heavily outdated. Could we publish the new cookbook in the opscode repository? I think it would be problematic to contact the author, the cookbook is dated to 2010 and it’s too old. Though I haven’t try to contact the author… I mean the author doesn’t support the cookbook, so this may just turn into a waste of time.
have you tried to contact Grant Rodgers [https://github.com/grantr] to discuss the matters with him? If not, I strongly suggest to do so. We have have frequently discussed out different approaches to Chef-related ElasticSearch stuff.

Karel

not yet Karel but I will try to do so. thanks for suggestion.

Denis


#9

if I can chime in, downloading and unpacking using the ark resource
would be as simple as

ark “elasticsearch” do
url https://github.com/downloads/elasticsearch/elasticsearch/elasticsearch-0.19.2.tar.gz
prefix_root "/usr/local"
checksum adac92d66ce91f42d9e67bd60e6b1335995f5dfdd153165fdcf1fe24b63ac59e
has_binaries [ “bin/elasticsearch” ]
end

just an idea :wink:

On Tue, Apr 17, 2012 at 11:21 AM, Denis Barishev
denis.barishev@gmail.com wrote:

Hello,

On 04/16/2012 11:04 AM, Karel Minařík wrote:

Hello,

http://community.opscode.com/cookbooks/elasticsearch

That one is maintained by Grant Rodgers, not Opscode.

Thanks that exactly what I thought. This cookbook is heavily outdated.
Could we publish the new cookbook in the opscode repository? I think it
would be problematic to contact the author, the cookbook is dated to 2010
and it’s too old. Though I haven’t try to contact the author… I mean the
author doesn’t support the cookbook, so this may just turn into a waste of
time.

have you tried to contact Grant Rodgers [https://github.com/grantr] to
discuss the matters with him? If not, I strongly suggest to do so. We have
have frequently discussed out different approaches to Chef-related
ElasticSearch stuff.

Karel

not yet Karel but I will try to do so. thanks for suggestion.

Denis


#10

On 04/17/2012 01:29 PM, Bryan Berry wrote:

if I can chime in, downloading and unpacking using the ark resource
would be as simple as

ark “elasticsearch” do
url https://github.com/downloads/elasticsearch/elasticsearch/elasticsearch-0.19.2.tar.gz
prefix_root "/usr/local"
checksum adac92d66ce91f42d9e67bd60e6b1335995f5dfdd153165fdcf1fe24b63ac59e
has_binaries [ “bin/elasticsearch” ]
end

https://github.com/bryanwb/chef-ark

just an idea :wink:

Yeah, I couldn’t agree more it is awesome. But I’ve got only one
question regarding ark. How does it track whether the app is installed?
Does it keep downloaded source tarball or what?
Actually I’m interested in the ark and I will probably use it later)
Bryan note that elasticsearch is now debianized (>- 0.19) so there’s no
need to use source installation method if you’ve got your apt repository
or some kind of third-party repository like PPA. In debian/ubuntu with
versions later 0.19 packages can be easily used.

Denis


#11

it checks to see whether elasticsearch is unpacked

I forgot an important attribute in my example

ark “elasticsearch” do
url https://github.com/downloads/elasticsearch/elasticsearch/elasticsearch-0.19.2.tar.gz
version "0.19.2"
prefix_root "/usr/local"
checksum adac92d66ce91f42d9e67bd60e6b1335995f5dfdd153165fdcf1fe24b63ac59e
has_binaries [ “bin/elasticsearch” ]
end

ark does keep the downloaded tarball in the chef cache path

ark checks whether or not the directory
/usr/local/elasticsearch-0.19.2/ exists and is empty
If it is not empty, ark unpacks the downloaded tarball

that’s awesome that it is debianized, sadly it has not been
centos-ized ;( as well
On Tue, Apr 17, 2012 at 11:53 AM, Denis Barishev
denis.barishev@gmail.com wrote:

On 04/17/2012 01:29 PM, Bryan Berry wrote:

if I can chime in, downloading and unpacking using the ark resource
would be as simple as

ark “elasticsearch” do
url
https://github.com/downloads/elasticsearch/elasticsearch/elasticsearch-0.19.2.tar.gz
prefix_root "/usr/local"
checksum
adac92d66ce91f42d9e67bd60e6b1335995f5dfdd153165fdcf1fe24b63ac59e
has_binaries [ “bin/elasticsearch” ]
end

https://github.com/bryanwb/chef-ark

just an idea :wink:

Yeah, I couldn’t agree more it is awesome. But I’ve got only one question
regarding ark. How does it track whether the app is installed? Does it keep
downloaded source tarball or what?
Actually I’m interested in the ark and I will probably use it later)
Bryan note that elasticsearch is now debianized (>- 0.19) so there’s no need
to use source installation method if you’ve got your apt repository or some
kind of third-party repository like PPA. In debian/ubuntu with versions
later 0.19 packages can be easily used.

Denis