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

hops (2) Versions 0.1.1

Installs/Configures HOPS distribution

Policyfile
Berkshelf
Knife
cookbook 'hops', '~> 0.1.1', :supermarket
cookbook 'hops', '~> 0.1.1'
knife supermarket install hops
knife supermarket download hops
README
Dependencies
Quality 33%

Hops installer

recipes:

  • install.rb
  • namenode.rb
  • datanode.rb

AWS VPC Instructions for Karamel

  1. Try and use a default VPC - it's much easier :)

If you have to create a VPC, then you need to make sure that:
1. Tenancy should be dedicated (for better performance)
2. DNS Resolution must be activated (yes)
3. DNS Hostnames must be activated (yes)
4. Your attached subnets must have auto-assigned public IP enabled
5. Your attached Internet Gateways should have global (public) access for all IPs enabled
You can set the VPC properties when you both create the VPC and using the 'action' button in the VPC menu page.

Roadmap

Roadmap

This is still very much a work-in-progress, but stay tuned for updates as we continue development. If you have ideas or patches, feel free to contribute!

  • [x] Launching Hops using Karamel/Vagrant
    1. Implement Karamel Scheduler and DAG API
    2. Launch it!
  • [x] Chef orchestration
  • [x] AngularJs NgSortable
  • [ ] Integration in Hops Dashboard
  • [ ] Middleware for performance

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Added some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request

Collaborator Number Metric
            

0.1.1 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.1 passed this metric

Foodcritic Metric
            

0.1.1 failed this metric

FC034: Unused template variables: hops/templates/default/core-site.xml.erb:1
FC034: Unused template variables: hops/templates/default/hdfs-site.xml.erb:1
FC034: Unused template variables: hops/templates/default/yarn-site.xml.erb:1
FC064: Ensure issues_url is set in metadata: hops/metadata.rb:1
FC066: Ensure chef_version is set in metadata: hops/metadata.rb:1
FC069: Ensure standardized license defined in metadata: hops/metadata.rb:1
FC070: Ensure supports metadata defines valid platforms: hops/metadata.rb:1
FC072: Metadata should not contain "attribute" keyword: hops/metadata.rb:1
FC085: Resource using new_resource.updated_by_last_action to converge resource: hops/providers/ndb.rb:3
FC085: Resource using new_resource.updated_by_last_action to converge resource: hops/providers/ndb.rb:21
Run with Foodcritic Version 16.3.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

No Binaries Metric
            

0.1.1 passed this metric

Testing File Metric
            

0.1.1 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.1 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