Adoptable Cookbooks List

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Chef bareos-cookbook

Deployment Strategy

This cookbook is intended to provide a Chef custom resource library for deploying and managing Bareos in a standard linux environment. There are a few recipes provided but are optional in that the resources should operate independently given a Bareos installation already exists or is installed alongside (i.e. packages, repos, directory structure). This strategy might change to some degree in the future but for now seemed to be the simplest way to separate the server setup tasks from the deployment of specific resources.

Use of these custom resources can be instantiated by way of features such as chef-vault for secret management, chef attributes, chef databags, etc. They are heavily reliant on hash and/or arrays to drop configurations into place and should provide a lot of flexibility but also provide the structure needed to manage Bareos resources as described per Bareos documentation. Templates can be replaced in wrapper cookbooks by way of the template_cookbook and template_name functionality of each custom resource. Issues or pull requests for official changes are also welcome.

Deployment Considerations

This cookbook does not and will not manage ancillary services for you such as PostgreSQL, MySQL, Python, Apache, Yum EPEL Repositories, etc. In the test fixture cookbook, there are some simple examples to get you going in the right direction. They are minimally configured for testing purposes only. You will need to make a plan to support a database type, Python, Apache/Nginx (optionally), and Yum EPEL repositories in RedHat based systems.

Client Custom Resources

bareos_client_client

Default action is :create which generates a client client resource.

As a matter of getting out a first release cut, we do not currently support pointing to multiple Director Connections via the FD Addresses directive but it can be added later if enough need is required. PRs are welcome to add this later.

Console Custom Resources

To help address some inconsistency with the Bareos config layout regarding console configuration(s) (i.e. no bareos-console.d/ directory or similar), I am having to combine both the bareos_console_console and bareos_console_director resources into a single resources which configures bconsole.conf. If they change/fix their strategy on this in the future, the necessary changes will be made.

bareos_console

Default action is :create which generates a combined console config with either console and/or director resources in bconsole.conf.

Other Cookbook Features/Resources

Graphite Poller (Bareos Contrib Repository)

Description

If you have a graphite node/cluster to monitor systems, we have a custom resource that installs the plugin and configures a cronjob (optionally and configurable) to simply send job statistics to the graphite cluster.

It could fall out of date as we have locked down to a specific commit but we can change that if users start to see issues with the one we are deploying by default.

SPECIAL NOTE: This custom resource does not currently support Ubuntu >= 16. The custom resource will post an error in your chef-client log in those cases.

graphite_poller (Custom Resource)

Default action is :create which generates an instance of the Bareos graphite poller.