Hiera helps to seperate data from Puppet manifests. It let's us write and use reusable manifests and modules. Puppet classes can request the data they need from the hiera data store. Hiera reads environment specific key / value pairs (including passwords) from its own YAML files and parses them to Puppet. Puppet then populates templated configuration files and delivers them to the specified directories. However, Hiera still needs access to the passwords in order to pass them along to Puppet.
Icinga 2 is an open source network and computer system monitoring application, which checks the availability of your network resources, notifies users of outages, and generates performance data for reporting.
Over the past few months we have been getting more and more information about Puppet 4, as well as the vast improvements to Puppet Enterprise. The array of new features and major changes is gigantic. A lot of these changes are very welcome and I'm excited to see what they will bring to the Puppet world. On the other hand, I'm also a bit afraid. Here's a non-exhaustive list of changes.
Whenever we talk about IaaS (Infrastructure as a Service) or cloud management platform or cloud provisioners, we often think about VMWare vSphere, AWS EC2, Openstack, and co. Not known to many people, there is another project on the rise and this is OpenNebula. So what is OpenNebula? As quoted from the OpenNebula website:
One of my favorite conferences in 2014 was the first edition of Config Management Camp, back in February. A very rare occasion where we had major contributors and users from each of the current FOSS Configuration Management tools in a single building.
Two months back OlinData announced OpsTheatre, a pluggable
operations dashboard that runs on Node.js. Our in-house dev team believes this tool will be key in eliminating a growing
issue in the DevOps community - the duplication of Operations Management tools. On top of that, we open sourced the project
as we believe community support and involvement will be integral in the realization, manifestation and shaping of this vision.
It has been a while since the PuppetConf 2014 ended in San Francisco and there are lot of news that came out of it as usual. But, the biggest news is during the keynote that Luke Kanies, CEO of PuppetLabs announced there will be a new Puppet Server. A new Puppet Server? Yup. A Puppet Server and its not the same as our current Puppet Master. Curious on what this means I decided to check out the preview. All my opinions stated below are my own and does not reflect any of OlinData or PuppetLabs.
Puppet includes a basic puppet master web server based on Ruby’s WEBrick library. This default server cannot be used for real-life loads, as it can’t handle concurrent connections; it is only suitable for small tests with ten nodes or fewer. You must configure a production quality web server before you start managing your nodes with Puppet i.e. more robust – namely Apache and Passenger.
Having just come back from PuppetConf 2014 in the San Francisco last week, there have been a lot of new developments. Some of the most significant changes since Puppet was started all the way 10 years back have been announced.