kitchen-gogetit

Kitchen::Gogetit

A test kitchen driver for Gogetit.

Requirements

TODO: document any software or library prerequisites that are required to use this driver. Implement the #verify_dependencies method in your Driver class to enforce these requirements in code, if possible.

What are needed when using Gogetit library are needed as well Since this is devised to use Gogetit as a kitchen driver. Please refer following link before begin. https://github.com/itisnotdone/gogetit

Installation and Setup

Please read the Driver usage page for more details.

$ export PKG_CONFIG_PATH=/usr/lib/x86_64-linux-gnu/pkgconfig

$ kitchen init -D kitchen-gogetit -P chef_zero

Configuration

---
driver:
  name: gogetit

provisioner:
  name: chef_zero

transport:
  ssh_key: <%= Dir.home + '/.ssh/id_rsa' %>

platforms:
  - name: lxc01
    driver:
      provider: lxd
      template: default
  - name: kvm01
    driver:
      provider: libvirt
      template: default

suites:
  - name: default
    run_list:
      - recipe[all_nodes::default]
    attributes:

Uninstall

Please read the Driver usage page for more details.

gem uninstall kitchen-gogetit gogetit maas-client

require_chef_omnibus

Determines whether or not a Chef Omnibus package will be installed. There are several different behaviors available:

• true - the latest release will be installed. Subsequent converges will skip re-installing if chef is present.
• latest - the latest release will be installed. Subsequent converges will always re-install even if chef is present.
• <VERSION_STRING> (ex: 10.24.0) - the desired version string will be passed the the install.sh script. Subsequent converges will skip if the installed version and the desired version match.
• false or nil - no chef is installed.

The default value is unset, or nil.

Development

• Source hosted at GitHub
• Report issues/questions/feature requests on GitHub Issues

Pull requests are very welcome! Make sure your patches are well tested. Ideally create a topic branch for every separate change you make. For example:

1. Fork the repo
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

Authors

Created and maintained by Don Draper ([e-mail])

License

Apache 2.0 (see LICENSE)