Project

kitchen-vz

0.0
No commit activity in last 3 years
No release in over 3 years
kitchen-vzkasen/kitchen-vzHomepageDocumentationSource CodeBug TrackerWiki
A Virtuozzo driver for Test Kitchen
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Popularity
Downloads
10,280
Stars
4
Forks
2
Watchers
2
 Releases
Current version
0.1.4
Total releases
4
First release
2016-03-15
Latest release
2018-06-21
 Issues
Open Issues
2
Closed Issues
2
Total Issues
4
Issue Closure Rate
50%
 Pull Requests
Open Pull Requests
1
Closed Pull Requests
0
Merged Pull Requests
2
Pull Request Acceptance Rate
66%
 Development
Primary Language
Ruby
Licenses
Apache 2.0
Average date of last 50 commits
2016-11-09
Reverse Dependencies
0

 Dependencies

Development

bundler
~> 1.3
rake
>= 0
rubocop
>= 0

Runtime

net-ssh
~> 3.0
test-kitchen
~> 1.5
 Project Readme

Kitchen::Vz

A Virtuozzo driver for Test Kitchen

Requirements

This driver works via ssh or directly executes command. So you need to have ssh access via keys on the server, where container will be started. Also you need to have sudo permissions for your user to run prlctl and vzctl commands.

This driver tested only on Virtuozzo 7.

Installation and Setup

Please read the Test Kitchen docs for more details.

Example .kitchen.local.yml:

---
  driver:
    name: vz

  platforms:
    - name: centos-7
    driver:
      socket: ssh://user@virtuozzo.domain.loc
  suites:
    - name: default

Configuration

Attribute Description Default value
:socket Connection string to virtuozzo server. Supports ssh uri or local. local means what prlctl and vzctl will be started locally. 'local'
:username User with this name will be created in virtuozzo container. Test kitchen uses this user to connect to the container. 'kitchen'
:arch Container architecture. This attribute shows how architecture container will be created. 'x86_64'
:network Hash with network configuration. See section Network configuration. 'Bridged' => {dhcp: true}
:customize Hash with container settings. It may contain :memory, :disk and :cpus options. memory: '512M', disk: '10G', cpus: 2
:private_key Path to private key. This key pair used by the kitchen to login into container. .kitchen/kitchen_id_rsa
:public_key Path to public key. This key pair used by the kitchen to login into container. .kitchen/kitchen_id_rsa.pub
:use_agent_forwarding Set agent forwarding option into container. 'False'
:ostemplate Virtuozzo template which will be used for container creating.
:use_sudo It shows will sudo be used or not. true
:additional_options Array with prlctl set options, which will be pass as is. Example: ["--features nfs:on"] []
:ct_hostname Container hostname. It is formed from platform name and suite name.

Network configuration

Example of network settings:

{
  'Bridged' => {
    dhcp: true
  },
  'Host-Only' => {
    ip: '192.168.75.1/24'
  },
  'PUB' => {
    ip: '10.10.10.20/24'
    gw: '10.10.10.1'
  }
}

The key of hash is a name of Virtuozzo network. Container interface will be bridged with this network. Value is a hash, which may contains next keys:

  • dhcp - If this parameter is true, then network settings will be get from dhcp server.
  • ip - IP-address which will be set to container. The address must be specified with the mask. Ex: 192.168.5.3/24
  • gw - Gateway which will be set to container.

Development

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 Pavel Yudin (pyudin@parallels.com)

License

Apache 2.0 (see LICENSE)