An open API service indexing awesome lists of open source software.

https://github.com/moznion/chef-jubatus

Chef cookbook for Jubatus
https://github.com/moznion/chef-jubatus

Last synced: about 1 year ago
JSON representation

Chef cookbook for Jubatus

Awesome Lists containing this project

README

          

jubatus Cookbook [![Build Status](https://travis-ci.org/moznion/chef-jubatus.png?branch=master)](https://travis-ci.org/moznion/chef-jubatus)
================
This is a chef cookbook for [Jubatus](http://jubat.us/)

Requirements
------------

#### platforms
- CentOS, RedHat, Fedora
- Ubuntu, Debian

#### Chef
Version 11.40 or later

#### cookbooks
- [apt](https://github.com/opscode-cookbooks/apt) (if you are using debian family OS.)

Attributes
----------

#### jubatus::default


Key
Type
OS
Description
Default


['jubatus']['packages']
Array(String)
Common
List of install packages
['jubatus'](Debian), ['jubatus', 'jubatus-client'](RHEL)


['jubatus']['repository']['url']
String
Debian
URL of jubatus apt repository
http://download.jubat.us/apt


['jubatus']['repository']['components']
Array(String)
Debian
Contents of repository
['binary/']


['jubatus']['environment_file']
String
Debian
Jubatus environment file. If you’re using csh or tcsh
use this instead:profile.csh:
profile


['jubatus']['profile']
String
Debian
Profile file to execute 'source jubatus_environment_file'
/etc/profile


['jubatus']['pkg_manager_src']
String
RHEL
URL to rpm file of jubatus
http://download.jubat.us/yum/rhel/6/stable/x86_64/jubatus-release-6-1.el6.x86_64.rpm


['jubatus']['pkg_manager']
String
RHEL
Temporary directory path to put rpm file
#{Chef::Config[:file_cache_path]}/jubatus.rpm

Usage
-----

#### jubatus::default
Just include `jubatus` in your node's `run_list`:

```json
{
"name":"my_node",
"run_list": [
"recipe[jubatus]"
]
}
```

If you are using debian family OS, please include `apt` too:
```json
{
"name":"my_node",
"run_list": [
"recipe[apt]"
"recipe[jubatus]"
]
}
```

Contributing
------------
1. Fork the repository on Github
2. Create a named feature branch (like `add_component_x`)
3. Write you change
4. Write tests for your change (if applicable)
5. Run the tests, ensuring they all pass
6. Submit a Pull Request using Github

Author
------
moznion (moznion@gmail.com)

License
-------
MIT