Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

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.

Select Badges

Select Supported Platforms

Select Status

RSS

bigdata (5) Versions 0.1.5

Installs/Configures Systap Bigdata High Availability

Policyfile
Berkshelf
Knife
cookbook 'bigdata', '~> 0.1.5', :supermarket
cookbook 'bigdata', '~> 0.1.5'
knife supermarket install bigdata
knife supermarket download bigdata
README
Dependencies
Quality 17%

Bigdata Cookbook

The Bigdata cookbook provides the bigdata v1.3.1 opensource triplestore/graph database. The cookbook provides recipes to install the Bigdata server as a web application under Tomcat, with its own embedded Jetty server (NSS - the NanoSparqlServer). The recipes will install pre-configured packages by node and optionally may build and install the server directly from source archive.

For more info on Bigdata please visit:

Requirements

Chef 11 or higher<br/>
Ruby 1.9 (preferably from the Chef full-stack installer)

Attributes

General Attributes

node['bigdata'][:home] - The root directory for bigdata contents (Default: /var/lib/bigdata)

node['bigdata'][:url] - Where to download the bigdata package file from. (Defaults: Tomcat: http://softlayer-dal.dl.sourceforge.net/project/bigdata/bigdata/1.3.1/bigdata.war / NSS: http://bigdata.com/deploy/bigdata-1.3.1.tgz)

node['bigdata'][:data_dir]
- Where the bigdata.jnl resides. Discussed in <a href="http://sourceforge.net/apps/mediawiki/bigdata/index.php?title=NanoSparqlServer#Common_Startup_Problems">Common Startup Problmems</a>
(Defaults: Tomcat: node['bigdata'][:home]/data / NSS: node['bigdata'][:home]/var/data)

node['bigdata'][:log_dir] - Where bigdata log files should reside (i.e. queryLog.csv, rules.log, queryRunStateLog.csv). (Default: Tomcat: node['bigdata'][:home]/var/log / NSS: node['bigdata'][:home]/var/log)

node['bigdata'][:properties] - File path to the Bigdata properties file. (Default: node['bigdata'][:home]/RWStore.properties)

node['bigdata'][:svn_branch] - The Subversion branch to retrieve source files from. Defaults:

node['bigdata'][:source] - The directory to retrieve Subversion contents into. (Default: bigdata-code)

node['bigdata']['journal.AbstractJournal.bufferMode'] - Journal Buffer Mode (Default: DiskRW)

node['bigdata']['service.AbstractTransactionService.minReleaseAge'] - Minimum Release Age (Default: 1)

node['bigdata']['btree.writeRetentionQueue.capacity'] - Writing retention queue length. (Default: 4000)

node['bigdata']['btree.BTree.branchingFactor'] - Branching factor for the journal's B-Tree. (Default: 128)

node['bigdata']['journal.AbstractJournal.initialExtent'] - Journal's initial extent (Default: 209715200)

node['bigdata']['journal.AbstractJournal.maximumExtent'] - Journal's maximum extent (Default: 209715200)

node['bigdata']['rdf.sail.truthMaintenance'] - Switch Truth Maintenance on/off. (Default: false)

node['bigdata']['rdf.store.AbstractTripleStore.quads'] - Switch Quads Mode on/off. (Default: false)

node['bigdata']['rdf.store.AbstractTripleStore.statementIdentifiers'] - Switch statement identifiers on/off. (Default: false)

node['bigdata']['rdf.store.AbstractTripleStore.textIndex'] - Switch text indexing on/off. (Default: false)

node['bigdata']['rdf.store.AbstractTripleStore.axiomsClass'] - The class to handle RDF axioms. (Default: com.bigdata.rdf.axioms.NoAxioms)

node['bigdata']['namespace.kb.lex.com.bigdata.btree.BTree.branchingFactor'] - Branching factor for the journal's Lexical B-Tree. (Default:- 400)

node['bigdata']['namespace.kb.spo.com.bigdata.btree.BTree.branchingFactor'] - Branching factor for the journal's SPO B-Tree. (Default: 1024)

node['bigdata']['rdf.sail.bufferCapacity'] - The number of statements to buffer before committing triples to the persistence layer. (Default: 100000)

Attributes for Tomcat Based Install

node['bigdata'][:web_home] - The web application root directory for bigdata. (Default node['tomcat'][:webapp_dir]/bigdata)

node['bigdata'][:log4j_properties] - File path to the log4j properties file. (Default node['bigdata'][:web_home]/WEB-INF/classes/log4j.properties)

Attributes for NanoSparqlServer (NSS) Based Install

node['bigdata'][:user] - The user to install and run bigdata under. (Default: bigdata)

node['bigdata'][:group] - The group to install and run bigdata under. (Default: bigdata)

node['bigdata'][:jetty_dir] - The Jetty root directory. (Default: node['bigdata'][:home]/var/jetty)

Attributes for MapGraph

node['mapgraph'][:svn_branch] - The Subversion branch to retrieve source files from. (Default: https://svn.code.sf.net/p/mpgraph/code/trunk)

node['mapgraph'][:source] - The directory to retrieve Subversion contents into. (Default: mapgraph-code )

Recipes

A node recipe is not provided by the Bigdata cookbook. The user is given the option to install the Bigdata server under Tomcat or as a Jetty application. Under both options, Bigdata may optinally be built directly from the a Subversion source code branch.

tomcat

Installs the Tomcat server and then bigdata as a web application. Bigdata will be configured according to the attributes. If no attributes are given, Bigdata will be installed with the systems nodes.

If the build_from_svn attribute is set to true Bigdata will be build from the Subversion repository given in the svn_branch attribute.

nss

Installs the Bigdata server to run in the NanoSparqlServer (Jetty) mode.

If the build_from_svn attribute is set to true Bigdata will be build from the Subversion repository given in the svn_branch attribute.

mapgraph

Retrieves the MapGraph project from its Subversion archive at SourceForget and builds it.
This recipe can only be used with GPU architecture and has only been validated against Amazon's "NVIDIA GRID GPU Driver" AMI.

Usage

Vagrant Context

Sample Vagrant configurations are available in the Bigdata Subversion source tree under bigdata/src/resources/deployment/vagrant.

Tomcat Example

chef.json = {
    :bigdata => {
            :install_flavor => "tomcat",
            :build_from_svn => true,
            :svn_branch => "https://svn.code.sf.net/p/bigdata/code/branches/BTREE_BUFFER_BRANCH/"
    },
    :java => {
            :install_flavor => "oracle",
            :jdk_version => "7",
            :oracle => { 'accept_oracle_download_terms' => true }
    },
    :tomcat => {
            :base_version => "7"
    }
}

chef.run_list = [
    ...
    "recipe[bigdata::tomcat]"
    ...
]

NSS Example

chef.json = {
    :bigdata => {
            :install_flavor => "nss"
    },
    :java => {
            :install_flavor => "oracle",
            :jdk_version => "7",
            :oracle => { 'accept_oracle_download_terms' => true }
    }
}

chef.run_list = [
    ...
    "recipe[bigdata::nss]"
    ...
]

Trouble Shooting

The Bigdta cookbook recipes have been tested thoroughly in the Vagrant context with VirtualBox and AWS providers using Ubuntu 12.04 and Oracle's JDK 7.

When errors occur in the Vagrant context, it is most typically during the installation process where a network timeout has occurred during the retrieval of a dependent resource. simply continue with:

% vagrant provision

Which should get past any intermit ant network issues. For assistance with installation and other issues, please visit the Bigdata Support Forum.

License and Authors

Author:: Daniel Mekonnen [daniel<no-spam-at>systap.com]

GNU GPLv2 - This pakcage may be resiributed under the same terms and conditions as the Bigdata project that it is a part of.

http://www.gnu.org/licenses/gpl-2.0.html

Dependent cookbooks

apt >= 0.0.0
java >= 1.22.0
ant >= 0.0.0
tomcat >= 0.0.0
subversion >= 0.0.0
lvm >= 0.0.0
hadoop >= 0.0.0
emacs >= 0.0.0
sysstat >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Collaborator Number Metric
            

0.1.5 failed this metric

Failure: Cookbook has 0 collaborators. A cookbook must have at least 2 collaborators to pass this metric.

Contributing File Metric
            

0.1.5 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a CONTRIBUTING.md file

Foodcritic Metric
            

0.1.5 failed this metric

FC009: Resource attribute not recognised: bigdata/recipes/high_availability.rb:28
FC009: Resource attribute not recognised: bigdata/recipes/nss.rb:26
FC064: Ensure issues_url is set in metadata: bigdata/metadata.rb:1
FC065: Ensure source_url is set in metadata: bigdata/metadata.rb:1
FC066: Ensure chef_version is set in metadata: bigdata/metadata.rb:1
FC069: Ensure standardized license defined in metadata: bigdata/metadata.rb:1
Run with Foodcritic Version 16.3.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

No Binaries Metric
            

0.1.5 passed this metric

Testing File Metric
            

0.1.5 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a TESTING.md file

Version Tag Metric
            

0.1.5 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must include a tag that matches this cookbook version number