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

ovirt (2) Versions 0.1.0

Installs/Configures ovirt

Berkshelf/Librarian
Policyfile
Knife
cookbook 'ovirt', '= 0.1.0'
cookbook 'ovirt', '= 0.1.0', :supermarket
knife cookbook site install ovirt
knife cookbook site download ovirt
README
Dependencies
Quality

ovirt Cookbook

The oVirt cookbook allows you to easily install oVirt engine and oVirt node with Chef.

oVirt is a virtualization management application. That means that you can use the oVirt management interface (the oVirt engine) to manage hardware nodes, storage and network resources, and to deploy and monitor virtual machines running in your data center. The ovirt module allows you to install the oVirt Engine (management host) and oVirt Node (hyperviser host) software on RedHat-based distros.

Requirements

RHEL and CentOS hosts need to have EPEL configured in order to fulfill oVirt rpm dependencies.

Supported Operating Systems

  • CentOS
  • RHEL
  • Fedora

Attributes

default

  • node['ovirt']['ovirt_release_base_url'] - This setting can be used to override the default url of http://ovirt.org/releases.

  • node['ovirt']['application_mode'] - This setting can be used to override the default ovirt application mode of both. Valid options are both, virt, gluster.

  • node['ovirt']['storage_type'] - This setting can be used to override the default ovirt storage type of nfs. Valid options are nfs, fc, iscsi, and posixfs.

  • node['ovirt']['organization'] - This setting can be used to override the default ovirt PKI organization of localdomain.

  • node['ovirt']['nfs_config_enabled'] - This setting can be used to override the default ovirt nfs configuration of true. Valid options are true and false.

  • node['ovirt']['iso_domain_name'] - This setting can be used to override the default ISO Domain Name of ISO_DOMAIN.

  • node['ovirt']['iso_domain_mount_point'] - This setting can be used to override the default ISO Domain Mount Point of /var/lib/exports/iso.

  • node['ovirt']['admin_password'] - This setting can be used to override the default ovirt admin password of admin.

  • node['ovirt']['db_user'] - This setting can be used to override the default database user of engine.

  • node['ovirt']['db_password'] - This setting can be used to override the default database password of dbpassword.

  • node['ovirt']['db_host'] - This setting can be used to override the default database host of localhost.

  • node['ovirt']['db_port'] - This setting can be used to override the default database port of 5432.

  • node['ovirt']['firewall_manager'] - This setting can be used to override the default firewall manager. The module uses iptables for RHEL and CentOS and firewalld for Fedora by default. Valid options are iptables and firewalld.

Usage

Creating an oVirt Engine

To create an oVirt Engine include ovirt::engine in your node's run_list:

{
  "name":"my_node",
  "run_list": [
    "recipe[ovirt::engine]"
  ]
}

The oVirt Engine is now up and running. You can log in to the oVirt Engine's web administration portal with the username admin in the internal domain.

Creating an oVirt Node

To create an oVirt Node include ovirt::node in your node's run_list:

{
  "name":"my_node",
  "run_list": [
    "recipe[ovirt::node]"
  ]
}

At this point, you are able to add the node to a host cluster using an oVirt Engine.

Contributing

  1. Fork the repository on Github.

    $ git clone git@github.com:jasonc/chef-ovirt.git

  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

License and Authors

Author:: Jason Cannon

Dependent cookbooks

This cookbook has no specified dependencies.

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

No quality metric results found