<html><head></head><body>I&apos;m very happy to announce the latest release of our Elasticsearch Puppet module, version 0.9.0Since its creation two years ago, the Elasticsearch Puppet module has grown to be one of the most widely used modules and was included in the inaugural class of <a href="http://www.elasticsearch.org/blog/celebrating-success-news-puppetconf-2014/">Puppet Approved</a> modules.<h2>New Features</h2>As with every release, we have a lot of new and exciting things in the module. One of these is support for <a href="https://docs.puppetlabs.com/hiera/1/index.html">hiera</a> out of the box for defining instances and plugins.We also added different custom facts to expose interesting information about the running Elasticsearch instances. These custom facts can be used together with other applications like Mcollective.An example output of these custom facts:<code>elasticsearch_9200_cluster_name =&gt; logging

elasticsearch_9200_mlockall =&gt; false

elasticsearch_9200_name =&gt; es01

elasticsearch_9200_node_id =&gt; WSWFaIzaTLGUqxTKu4LO2A

elasticsearch_9200_plugin_kopf_description =&gt; kopf - simple web administration tool for ElasticSearch

elasticsearch_9200_plugin_kopf_jvm =&gt; false

elasticsearch_9200_plugin_kopf_site =&gt; true

elasticsearch_9200_plugin_kopf_url =&gt; /_plugin/kopf/

elasticsearch_9200_plugin_kopf_version =&gt; 1.3.0-SNAPSHOT

elasticsearch_9200_plugin_marvel_description =&gt; Elasticsearch Management &amp; Monitoring

elasticsearch_9200_plugin_marvel_jvm =&gt; true

elasticsearch_9200_plugin_marvel_site =&gt; true

elasticsearch_9200_plugin_marvel_url =&gt; /_plugin/marvel/

elasticsearch_9200_plugin_marvel_version =&gt; 1.2.1

elasticsearch_9200_plugins =&gt; marvel,kopf

elasticsearch_9200_version =&gt; 1.3.2

elasticsearch_ports =&gt; 9200

</code><h2>Changes</h2>We added support for OpenSuse 13.x and enabled Puppet 3.7 testing.&#xA0;Along the way, we added several internal changes which will help improve the stability of the project.&#xA0;One of these changes is using the official <a href="https://forge.puppetlabs.com/puppetlabs/java">puppetlabs-java</a> module to manage the java installation. This replaces our custom class with a wonderfully, well-tested module from Puppet Labs.<h2>Fixes</h2>Thanks to the feedback from both the community and customers, we fixed several bugs. It is worth mentioning few important fixes here:<ul>
<li>Fix for ensuring that all files are owned by the right user. This bug caused issues when installing the recently released <a href="http://www.elasticsearch.org/overview/shield/">Shield</a> plugin for Elasticsearch.</li>
<li>Fix for avoiding duplicate service resource names in puppet which could cause conflicts.</li>
</ul><h2>Roadmap</h2>The Elasticsearch puppet module will continue to evolve in the future, with different needs and requirements. With this release, we are paving the road for future changes without breaking expectations for your environments.In the next major release, we are planning on using <a href="http://puppetlabs.com/presentations/future-goals-puppet-4-andrew-parker-puppet-labs-kylo-ginsberg">Puppet 4</a>. We are also working to extend support for different Operating systems such as SLES, Windows and many more.As always, if you find any bugs or have questions, enhancements, please reach out to us on the Github <a href="https://github.com/elasticsearch/puppet-elasticsearch/issues">Issues</a> page, or on our <a href="https://groups.google.com/forum/#!forum/elasticsearch">Google Groups</a> page.</body></html>

Elasticsearch Puppet Module 0.9.0 Released

<html><head></head><body><img src="https://api.contentstack.io/v2/assets/575e4c9243e9adc538713bf0/download?uid=blt5bb28f60614dffea?uid=blt5bb28f60614dffea" data-sys-asset-uid="blt6428a6c8bf4b426b" style="width:600px; max-width:100%;">

I first began developing the Elasticsearch Puppet module at a previous employer, where I was already a huge fan of both technologies. I loved working with Puppet because it was so easy to use; its configuration language is very descriptive, making it simple to understand what you&#x2019;re doing under the hood. I&#x2019;d really enjoyed my experiments with Logstash and Elasticsearch, and started whipping up Puppet modules for both of them in my spare time, hoping to see both deployed at my workplace. These efforts led to me joining Elasticsearch to work on the Puppet modules full-time, and the rest, as they say, is history.

Today, I have a great news to add to that story. If you&#x2019;re attending PuppetConf 2014, you&#x2019;ve probably heard about the brand new <a href="https://forge.puppetlabs.com/approved">Puppet Approved program</a>. I&#x2019;m really extremely honored and excited to share that the Elasticsearch Puppet module was selected as one of the very first modules to be Puppet Approved!

The team at Puppet Labs has created the Puppet Approved program to make it easier for customers to choose modules for specific automation tasks and quickly deploy them to production. Puppet Approved modules are recommended by Puppet Labs, and meet its standards for quality composition, reliable operation, and active development.

In true open source fashion, the Elasticsearch Puppet module was a personal side project turned dream job. I&#x2019;m thrilled to see that so many members of the Puppet community find the Elasticsearch Puppet module useful.

Happy Puppetizing!
</body></html>

Celebrating Our Success: News from PuppetConf 2014

<html><head></head><body>
	Since the beginning, we&apos;ve tried to support all current and historic releases of Puppet. We&apos;re big fans of Puppet - just like many of our users - so we went broad in our version support. We wanted to ensure the best possible experience for as many folks as possible.


	At the time of writing this post, we&apos;re testing against 9 different versions of Puppet, both vanilla and Puppet Enterprise. We have a great testing infrastructure to do this work for us. However, long term maintenance to support all these versions, with even more great bits to come, is proving to be more challenging.

<h3>Moving forward</h3>

	After pondering the challenges and tradeoffs, we&apos;ve decided to shrink the versions we test against and officially support. Puppet is developed and released at quite a fast pace - one of the reasons we love it - so we&apos;ll make sure our modules always keep up with Puppet&apos;s latest releases. Specifically, we&apos;ll support the latest version of vanilla Puppet, plus the prior four releases. For Puppet Enterprise, we will support the latest two releases.

<h3>What this means for you</h3>

	Moving forward, we will support the following:


	Puppet Open Source: 3.2.x to 3.6.x 
Puppet Enterprise: 3.1.x and 3.2.x


	If you&apos;re running an older version, our Puppet modules should still keep right on working for you. However, with this change we cannot guarantee that will always be the case. We&apos;d recommend <a href="http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html">upgrading to one of the officially supported versions</a> to ensure compatibility, and because why not get the latest bits?
</body></html>

Streamlining Maintenance of Our Puppet Modules

<html><head></head><body><article>
			We&#x2019;re very happy to announce our latest release of our Elasticsearch Puppet module, version 0.4.0. With this release, we&#x2019;ve implemented one of the most widely requested features: supporting multiple instances of Elasticsearch running on a single machine. This new functionality required a substantial rewrite of our Elasticsearch Puppet module, so this release breaks backwards compatibility with our previous releases. You can get full details in the <a href="https://github.com/elasticsearch/puppet-elasticsearch/blob/0.4.0/README.md">README file</a>. 
Now, when creating a single instance of Elasticsearch, you would simply: 
<pre class="prettyprint noescape"># Setup main class class { &apos;elasticsearch&apos;: } # Setup instance 1 elasticsearch::instance { &apos;es-01&apos;: }</pre>
This sets up a single instance called &#x2018;es-01&#x2032;. The data directory is automatically set to &#x201C;/usr/share/elasticsearch/data/es-01&#x2033;. Since no node name is given in the configuration, we automatically set that to &#x201C;$hostname-es-01&#x2033;
When you want to have 2 instances, you just need to add another instance call:
<pre class="prettyprint noescape"># Setup main class class { &apos;elasticsearch&apos;: } # Setup instance 1 elasticsearch::instance { &apos;es-01&apos;: } # Setup instance 2 elasticsearch::instance { &apos;es-02&apos;: }</pre>
Along with this new functionality, we have also added support for another Linux distro, Ubuntu 14.04. Lastly, we&#x2019;ve spiffed up our documentation to make it easier for you to get started.
For more detailed information about configuring instances, set up and usage, <a href="https://github.com/elasticsearch/puppet-elasticsearch/blob/0.4.0/README.md">see the README</a>. We&#x2019;ll keep adding new functionality to our Puppet modules, so make sure to check them out and <a href="https://github.com/elasticsearch/puppet-elasticsearch/issues">give us your feedback</a>.
Happy Puppetizing!
			<aside id="post_tags">
							</aside>
		</article></body></html>

Elasticsearch Puppet module 0.4.0 released

<html><head></head><body>Today, we are happy to announce the release of our Logstash Puppet module version 0.5.0. You can download it and read the full changes list here:
<ul>
<li><a class="ulink" href="https://github.com/elasticsearch/puppet-logstash/tree/0.5.0" target="_top">Logstash Puppet module v0.5.0 on GitHub</a></li>
<li><a class="ulink" href="http://forge.puppetlabs.com/elasticsearch/logstash/0.5.0" target="_top">Logstash Puppet module v0.5.0 on Puppet Forge</a></li>
</ul>
<h2>What&apos;s New</h2>
Like we did in the <a class="ulink" href="http://www.elasticsearch.org/blog/elasticsearch-puppet-module-0-3-0-released/">Elasticsearch Puppet module</a>, we&apos;ve made a number of improvements, including a better test suite, and switching to <a class="ulink" href="http://projects.puppetlabs.com/projects/1/wiki/puppet_augeas" target="_top">Augeas</a> for easier configuration.
We have worked hard to incorporate the package changes that were made in logstash 1.4.x, and now you can install the contrib package directly from the repository or other remote source. We have also made some minor improvements like fixing inline documentation and, with the help of the community, found and squashed some minor bugs.
We&apos;re always working to improve the quality and support of our Puppet offerings, and we hope you enjoy these latest enhancements. As always, you can give us your feedback or report problems on our <a class="ulink" href="https://github.com/elasticsearch/puppet-logstash/issues" target="_top">GitHub issues</a> page.
</body></html>

Logstash Puppet module 0.5.0 released

<html><head></head><body>
	Today we are happy to announce the release of our Elasticsearch Puppet modules version 0.3.0. You can download them and read the full changes list here:
<ul>
	<li><a class="ulink" href="https://github.com/elasticsearch/puppet-elasticsearch/tree/0.3.0" target="_top">on GitHub</a></li>
	<li><a class="ulink" href="http://forge.puppetlabs.com/elasticsearch/elasticsearch/0.3.0" target="_top">on the Puppet Forge</a></li>
</ul><h3>What&apos;s New</h3>
	We&apos;ve improved support for different Linux distributions and added OpenSuse to our list of supported distros. Debian 6 support has also been improved. To improve the support for the defaults files we&apos;ve implemented <a class="ulink" href="http://projects.puppetlabs.com/projects/1/wiki/puppet_augeas" target="_top">Augeas support</a>.
<h3>Improved testing</h3>
	For the past few weeks, we&apos;ve worked hard on improving the quality of these modules. With the implementation of System Tests, we now have several layers of testing:
<blockquote>
	<h3>Puppet Lint</h3>
Puppet lint allows us to validate the code against the recommended Puppet style guidelines from the 
	<a class="ulink" href="http://docs.puppetlabs.com/guides/style_guide.html" target="_top">Puppet Labs style guide</a>. This makes sharing code easier as everyone holds to the same guidelines as much as possible. 
	
		 
	 
	<h3>Syntax Validation</h3>
The syntax validation step validates the code against the 
	<a class="ulink" href="http://docs.puppetlabs.com/puppet/latest/reference/lang_summary.html" target="_top">Puppet DSL syntax</a> without having to run the actual code. 
	
		 
	 
	<h3>Rspec Tests</h3>
Rspec tests are the first step in actual validation of the module. This step runs the code and validates different test scenarios and is the first step in catching errors.
	 
	
		 
	 
	<h3>System Tests</h3>
System testing is the final step in the testing process. These tests run the actual code on real systems to validate it all actually works.
</blockquote><h3>Conclusion</h3>
	We will continue to improve the quality and support of our Puppet modules. You can report any problems on our <a class="ulink" href="https://github.com/elasticsearch/puppet-elasticsearch/issues" target="_top">GitHub issues</a> page.
</body></html>

Elasticsearch Puppet Modules 0.3.0 Released

<html><head></head><body><section id="post_content">
		<article>
			We are happy to announce that the frequently requested DEB and RPM repositories are now available.
Due to big differences between major versions, we have decided to setup different repository URLs for each major version.&#xA0;We wanted to make this process simple and make sure you don&#x2019;t accidentally upgrade between major versions and break stuff.&#xA0;But don&#x2019;t forget to check the changelog of new versions before installing them.
<h4>Public key</h4>
Our public key can be found <a href="http://packages.elasticsearch.org/GPG-KEY-elasticsearch">here</a>.
For Debian/Ubuntu systems you can do the following:
<pre class="prettyprint lang=js">wget -O - http://packages.elasticsearch.org/GPG-KEY-elasticsearch | apt-key add -</pre>
For CentOS/Red Hat systems:
<pre class="prettyprint lang=js">rpm --import http://packages.elasticsearch.org/GPG-KEY-elasticsearch</pre>
<h4>Repositories</h4>
On APT based systems add the following to your sources.list for using the repositories:
Elasticsearch 0.90.x:
<pre class="prettyprint lang=js">deb http://packages.elasticsearch.org/elasticsearch/0.90/debian stable main</pre>
Elasticsearch 1.0.x:
<pre class="prettyprint lang=js">deb http://packages.elasticsearch.org/elasticsearch/1.0/debian stable main</pre>
Logstash 1.2.x:
<pre class="prettyprint lang=js">deb http://packages.elasticsearch.org/logstash/1.2/debian stable main</pre>
Logstash 1.3.x:
<pre class="prettyprint lang=js">deb http://packages.elasticsearch.org/logstash/1.3/debian stable main</pre>
Run <code>apt-get update</code> and you will be able to use the repositories
Even though the distribution is specified as stable in the <code>sources.list</code>, you should be able to install the debian packages on any distribution.
On YUM based systems add these to your <code>/etc/yum.repos.d/</code> directory:
Elasticsearch 0.90.x:
<pre class="prettyprint lang=js">[elasticsearch-0.90]
name=Elasticsearch repository for 0.90.x packages
baseurl=http://packages.elasticsearch.org/elasticsearch/0.90/centos
gpgcheck=1
gpgkey=http://packages.elasticsearch.org/GPG-KEY-elasticsearch
enabled=1</pre>
Elasticsearch 1.0.x:
<pre class="prettyprint lang=js">[elasticsearch-1.0]
name=Elasticsearch repository for 1.0.x packages
baseurl=http://packages.elasticsearch.org/elasticsearch/1.0/centos
gpgcheck=1
gpgkey=http://packages.elasticsearch.org/GPG-KEY-elasticsearch
enabled=1</pre>
Logstash 1.2.x:
<pre class="prettyprint lang=js">[logstash-1.2]
name=logstash repository for 1.2.x packages
baseurl=http://packages.elasticsearch.org/logstash/1.2/centos
gpgcheck=1
gpgkey=http://packages.elasticsearch.org/GPG-KEY-elasticsearch
enabled=1</pre>
Logstash 1.3.x:
<pre class="prettyprint lang=js">[logstash-1.3]
name=logstash repository for 1.3.x packages
baseurl=http://packages.elasticsearch.org/logstash/1.3/centos
gpgcheck=1
gpgkey=http://packages.elasticsearch.org/GPG-KEY-elasticsearch
enabled=1</pre>
For more information on setting up Elasticsearch, take a look at our <a href="http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup.html">setup documentation</a>
Got feedback about our repositories? Let us know via <a href="http://twitter.com/elasticsearch">Twitter</a>, <a href="https://groups.google.com/forum/#!forum/elasticsearch">Google Groups</a> or <a href="https://github.com/elasticsearch/elasticsearch/issues">Github</a>
			<aside id="post_tags">
							</aside>
		</article>
			</section></body></html>

AUTHOR

Articles by Richard Pijnenburg

Elasticsearch Puppet Module 0.9.0 Released

Celebrating Our Success: News from PuppetConf 2014

Streamlining Maintenance of Our Puppet Modules

Elasticsearch Puppet module 0.4.0 released

Logstash Puppet module 0.5.0 released

Elasticsearch Puppet Modules 0.3.0 Released

Announcing DEB and RPM Repositories

Sign up for Elastic Cloud free trial

Products & Solutions

Company

We're hiring

Resources

Solutions

Elastic (ELK) Stack

New

Featured topics

News

AUTHOR

Articles by Richard Pijnenburg

Elasticsearch Puppet Module 0.9.0 Released

Celebrating Our Success: News from PuppetConf 2014

Streamlining Maintenance of Our Puppet Modules

Elasticsearch Puppet module 0.4.0 released

Logstash Puppet module 0.5.0 released

Elasticsearch Puppet Modules 0.3.0 Released

Announcing DEB and RPM Repositories

Sign up for Elastic Cloud free trial

Company

We're hiring

Resources