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

RSS

abiquo (21) Versions 0.10.1

Installs and configures an Abiquo platform

Berkshelf/Librarian
Policyfile
Knife
cookbook 'abiquo', '= 0.10.1'
cookbook 'abiquo', '= 0.10.1', :supermarket
knife cookbook site install abiquo
knife cookbook site download abiquo
README
Dependencies
Changelog
Quality

Abiquo Cookbook

Build Status Abiquo Cookbook Chef Version

This cookbook provides several recipes to install and upgrade an Abiquo platform. It allows you to provision an Abiquo Server, the Remote Services server, standalone V2V server, monitoring server, frontend components and a KVM hypervisor from scratch, as long as upgrading an existing Abiquo installation.

Usage

The cookbook is pretty straightforwatd to use. Just set the node['abiquo']['profile'] attribute according to the profile you want to install or upgrade and and include one of the following recipes in the run list:

  • recipe[abiquo] - To perform an installation from scratch
  • recipe[abiquo::upgrade] - To upgrade an existing installation

The available profiles are:

  • monolithic sets up all Abiquo components in one host.
  • remoteservices sets up the Abiquo remote services (except V2V).
  • server sets up the Abiquo management components (API, M) plus the frontend components (UI, websockify).
  • ui sets up the Abiquo UI.
  • websockify sets up the Websockify proxy for noVNC connections.
  • frontend sets up the frontend components, UI and Websockify.
  • v2v sets up the Abiquo V2V conversion manager.
  • kvm sets up an Abiquo KVM cloud node.
  • monitoring sets up the monitoring components of the Abiquo platform
  • ext_services sets up the management components' supporting databases (MariaDB, Redis) and the RabbitMQ message bus.

When installing the Abiquo Monolithic profile, you may also want to set the node['abiquo']['certificate'] properties so the right certificate is used or a self-signed one is generated. You can also use it together with the hostname cookbook to make sure the node will have it properly configured.

Testing

In order to test the cookbook you will need to install Vagrant and VirtualBox. Once installed you can run the unit and integration tests as follows:

bundle install
bundle exec berks         # Install the cookbook dependencies
bundle exec rake          # Run the unit and style tests
bundle exec rake kitchen  # Run the integration tests

The tests and Gemfile have been developed using Ruby 2.1.5, and that is the recommended Ruby version to use to run the tests. Other versions may cause conflicts with the versions of the gems Bundler will install.

RHEL testing

Integration tests for RHEL are specified in a separate .kitchen.rhel.yml file. They use a vagrant box named rhel-6.8 which you will need to build and add to the host running the tests as described in bento project repository.

Once the box is available in the host, you can run the tests by specifying the kitchen config file to use and the user and password so the VM can register to RedHat and get a subscription.

$ KITCHEN_LOCAL_YAML=.kitchen.rhel.yml RHN_USERNAME=some_user RHN_PASSWORD=some_pass bundle exec rake kitchen-basic

License and Authors

Copyright:: 2014, Abiquo

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

abiquo CHANGELOG

0.10.0

  • Added support for OpenStack Neutron in KVM hosts.
  • Add support for CentOS 7.
  • Allow to configure MariaDB as master so new slaves can replicate from it.
  • Use a custom plugin for webSockify instead of the token scripts.

0.9.1

  • The update recipe includes the default one.
  • Enforce a Ruby friendly style.

0.9.0

  • Enforce a proper Ruby style with Rubocop.
  • Use HAproxy as SSL termination for Websockify.
  • Use official cookbooks to install MariaDB, RabbitMQ and Redis.

0.8.0

  • Added suppoert for RHEL >= 6.7.
  • Simplified the ui configuration by leveraging only the 'ui_config' attribute.
  • Added ext_services profile.
  • Added front-end profile.
  • Configured the monitoring resources to be idempotent.
  • Fix watchtower schema creation during install and upgrade.
  • Upgrade tests to Centos 6.8.
  • Added ui and websockify profiles.
  • Removed the Abiquo nightly repository.

0.7.3

  • Properly restart tomcat after configuring users in RabbitMQ

0.7.2

  • Create the monitoring schema when installing the monitoring nodes

0.7.1

  • Cookbook metadata fixes

0.7.0

  • Install the websockify package for VM remote access.
  • Configure an Abiquo user in RabbitMQ
  • Added the EPEL repository.
  • Configured resources to be idempotent and avoid unwanted restarts.
  • Configure a generic recipe to manage teh Abiquo Tomcat service.
  • Better management for SSL certificates.
  • Remove the need for the ark cookbook.
  • Monitoring nodes can be upgraded
  • Install Watchtower services in the monitoring node

0.6.0

  • Added custom firewall templates for each profile.
  • General recipe refactor to include the 'server' and 'v2v' profiles.
  • Created a Kitchen suite to use nightly build branches.

0.5.0

  • Configured the firewall in the kvm profile.
  • Upgrade the database using the abiquo-liquibase script.
  • Added integration tests with ServerSpec.
  • Added a recipe to install a monitoring node.
  • Upgraded base repositories to 3.6.

0.4.0

  • Use the rpm signing keys from the abiquo-release-ee package.

0.3.3

  • Removed the start, stop and update recipes.
  • Changed the upgrade recipe to also upgrade the database.
  • Added database configuration attributes.

0.3.2

  • Added the abiquo-updates yum repository.
  • Configured the rpm GPG sign keys that are not present in the abiquo-release-ee package.
  • Fixed encofing in the UI configuration file.

0.3.1

  • Fixed the NFS resource.

0.3.0

  • Added support for Abiquo 3.3.

0.2.1

  • Install Java and RabbitMQ from the Abiquo repositories.
  • Added all missing signatures to the repository configuration.
  • Configured the cookbook to install Abiquo 3.3.

0.2.0

  • Support Java 8.
  • Support using JCE unlimited strength encryption policies.
  • Allow customization of the RabbitMQ and Redis properties.
  • Dropped support to configure the Abiquo Tomcat in jpda mode.
  • Redis is installed from the Abiquo packages.

0.1.0

  • Initial release. Support for Monolithic installations from scratch and platform upgrades using nightly builds.

Collaborator Number Metric
            

0.10.1 passed this metric

Contributing File Metric
            

0.10.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 http://github.com/user/repo, and your repo must contain a CONTRIBUTING.md file

Foodcritic Metric
            

0.10.1 failed this metric

FC066: Ensure chef_version is set in metadata: abiquo/metadata.rb:1
FC069: Ensure standardized license defined in metadata: abiquo/metadata.rb:1
Run with Foodcritic Version 10.3.1 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

License Metric
            

0.10.1 passed this metric

No Binaries Metric
            

0.10.1 passed this metric

Publish Metric
            

0.10.1 passed this metric

Supported Platforms Metric
            

0.10.1 passed this metric

Testing File Metric
            

0.10.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 http://github.com/user/repo, and your repo must contain a TESTING.md file

Version Tag Metric
            

0.10.1 passed this metric