Kitchen::Wpar

A Test Kitchen Driver for Wpar.

You need a AIX partition with chef client and sudo installed.

Please read the Driver usage page for more details.

TODO: Write descriptions of all configuration options

• wpar_name wpar name on AIX global system. Default to kitchenwpar.
• aix_host aix global partition name. Default to localhost.
• aix_user aix global partition username. Default to root.
• aix_key Specify a path to the ssh key to create a connection.
• wpar_address wpar IP address to use. Not needed if an entry already exists in /etc/hosts on Global partition.
• wpar_vg Volume group to use to store shared wpar filesystems. Default to rootvg.
• wpar_rootvg Specify the hdisk to use to create a rootvg system wpar.
• wpar_mksysb uses a wpar backup. Specify a path to a backup to save time.
• wpar_copy_rootvg adds the option ' -t' to copy rootvg file systems.
• isVersioned create a versioned wpar. Used only with wpar_mksysb.
• isWritable adds the option ' -l' to have a non-shared, writable /usr file system and /opt file system.
• share_network_resolution adds the option ' -r' to share name resolution services (i.e. /etc/resolv.conf) with the wpar.
• sudo path to sudo command in case we need it.
• ssh_port Lets you specify the ssh port to use. Default to 22.

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 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. Should be false if your AIX system has no internet access.

• 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

Created and maintained by Alain Dejoux (adejoux@djouxtech.net)

Apache 2.0 (see LICENSE)