kitchen-openstack 6.1.0 → 6.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 16893c5388d5afa323c078534d17c9ad94bb294cb9db3577c67e7620d58cfcd7
-  data.tar.gz: d5ab4ff3115b267a77eb9084bfe354d25eea77bbd9afcabb02b24eec1c3c6190
+  metadata.gz: a54b200667def52dee3afc0ac1be2f58dbe082396fa6ee17833ac5d0a91d6bfd
+  data.tar.gz: 397fbc6af66ed869b827ac30014c42f6c41a90a386a4a77fcd76a660e921e06b
 SHA512:
-  metadata.gz: 2b333a6c382943d6fca7f647a77ff8248e688335fcd6c1719db6cb348d105016ffa63f94f9c21c7e8e37e1a66f6e6bfab5155ad2c86117bc678da0c879eea9d4
-  data.tar.gz: 52e4a20679da413c401b62e2982a48022992964514595bec563902117e737d017699d6a5d94c63afbf5f40c049a9f28fab23ee204d37db184fb70e703d990195
+  metadata.gz: 10b1f6ee9220f1c0724e0182392d00bd28806e80863d939f565921e5646da09ed681cba71a342da22c25f2bec8023699c9dab39c29a22cef8286eceb83bf645a
+  data.tar.gz: e05e7903c57e1c0b776fe4b751fed1bd596335b0ddf4ba0f0cee4f8ee1174a69c3e1b9f9b92ea8cd1f70adb877eee75d5943c39f6f022f1387e2144690705b5f

data/README.md

@@ -43,404 +43,9 @@ Or install it yourself as:
 $ gem install kitchen-openstack
 ```
 
-## Minimum Configuration
-
-```yaml
-driver:
-  name: openstack
-  openstack_username: [YOUR OPENSTACK USERNAME]
-  openstack_api_key: [YOUR OPENSTACK API KEY] # AKA your OpenStack Password
-  openstack_auth_url: [YOUR OPENSTACK AUTH URL] # if you are using v3, API_URL/v3/auth/tokens
-  openstack_domain_id: [default is 'default'; otherwise YOUR OPENSTACK DOMAIN ID]
-  require_chef_omnibus: [e.g. 'true' or a version number if you need Chef]
-  image_ref: [SERVER IMAGE ID]
-  flavor_ref: [SERVER FLAVOR ID]
-transport:
-  username: ubuntu # For a Ubuntu Box
-```
-
-The `image_ref` and `flavor_ref` options can be specified as an exact id,
-an exact name, or as a regular expression matching the name of the image or flavor.
-
-All of Fog's `openstack` options (`openstack_domain_name`, `openstack_project_name`,
-...) are supported. This includes support for the OpenStack Identity v3 API.
-
-## General Configuration
-
-### name
-
-**Required** Tell test-kitchen what driver to use. ;)
-
-### openstack\_username
-
-**Required** Your OpenStack username.
-
-### openstack\_api\_key
-
-**Required** Your OpenStack API Key, aka your OpenStack password.
-
-### openstack\_auth\_url
-
-**Required** Your OpenStack auth url. If you are using ID v3, you'll need to use `API_URL/v3/auth/tokens`.
-
-### require\_chef_omnibus
-
-**Required** Set to `true` otherwise the specific version of Chef omnibus you want installed.
-
-### image\_ref
-
-**image_ref or image_id required** Server Image Name or ID.
-
-### image\_id
-
-**image_ref or image_id required** Server Image ID.  Specifying the ID instead of reference results in a faster create time.
-
-**Note** If the image UUID changes this value will need to be updated.
-
-### flavor\_ref
-
-**flavor_ref or flavor_id required** Server Flavor Name or ID.
-
-### flavor\_ref
-
-**flavor_ref or flavor_id required** Server Flavor ID.  Specifying the ID instead of reference results in a faster create time.
-
-**Note** If the flavor UUID changes this value will need to be updated.
-
-### server\_name
-
-If a `server_name_prefix` is specified then this prefix will be used when
-generating random names of the form `<NAME PREFIX>-<RANDOM STRING>` e.g.
-`myproject-asdfghjk`. If both `server_name_prefix` and `server_name` are
-specified then the `server_name` takes precedence.
-
-### server\_name\_prefix
-
-If you want to have a static prefix for a random server name.
-
-### port
-
-Set the SSH port for the remote access.
-
-### openstack\_tenant
-
-Your OpenStack tenant id.
-
-### openstack\_region
-
-Your OpenStack region id.
-
-### availability\_zone
-
-Your OpenStack availablity zone.
-
-### openstack\_service\_name
-
-Your OpenStack compute service name.
-
-### openstack\_network\_name
-
-Your OpenStack network name used to connect to, if you have only private network
-connections you want declare this.
-
-### glance\_cache\_wait\_timeout
-When OpenStack downloads the image into cache, it takes extra time to provision.  Timeout controls maximum amount of time to wait for machine to move from the Build/Spawn phase to Active.
-
-### connect\_timeout
-Connect timeout controls maximum amount of time to wait for machine to respond to ssh login request.
-
-### read\_timeout
-### write\_timeout
-Expose read/write timeout parameters passed down to HTTP connection created via [excon](https://github.com/excon/excon). Default timeouts (from excon) are 60 seconds.
-
-### server\_wait
-
-`server_wait` is a workaround to deal with how some VMs with `cloud-init`.
-Some clouds need this some, most OpenStack instances don't. This is a stop gap
-wait makes sure that the machine is in a good state to work with. Ideally the
-transport layer in Test-Kitchen will have a more intelligent way to deal with this.
-There will be a dot that appears every 10 seconds as the timer counts down.
-You may want to add this for **WinRM** instances due to the multiple restarts that
-happen on creation and boot. A good default is `300` seconds to make sure it's
-in a good state.
-
-The default is `0`.
-
-### security\_groups
-
-A list of `security_groups` to join:
-
-```yaml
-security_groups:
-   - [A LIST OF...]
-   - [...SECURITY GROUPS TO JOIN]
-   ```
-
-### user\_data
-
-If your VMs have `cloud-init` enabled you can use the `user_data` in your
-kitchen.yml to inject commands at boot time.
-
-```
-    driver_config:
-      user_data: userdata.txt
-```
-
-Then create a `userdata.txt` in the same directory as your .kitchen.yml,
-for example:
-
-```
-#!/bin/sh
-echo "do whatever you want to pre-configure your machine"
-```
-
-### cloud\_config
-
-If your VMs have `cloud-init` enabled you can use `cloud_config` to generate userdata for use by cloud-init in the [cloud-config format](https://cloudinit.readthedocs.io/en/latest/topics/format.html#cloud-config-data). This provides a convenient way to specify cloud-init config inline. As the cloud-config format uses YAML the resulting userdata is essentially a copy+paste of `cloud_config` with the header line '#cloud-config'
-
-```
-    driver_config:
-      cloud_config:
-        hostname: my-hostname
-```
-
-This will pass the following user data to OpenStack:
-
-```
-#cloud-config
-hostname: my-hostname
-```
-
-The `cloud_config` and `user_data` options are mutually exclusive.
-
-### config\_drive
-
-If your VMs require config drive.
-
-```
-    config_drive: true
-```
-
-### network\_ref
+## Usage
 
-**Deprecated** A list of network names to create instances with.
-
-```yaml
-network_ref:
-   - [OPENSTACK NETWORK NAMES]
-   - [CREATE INSTANCE WITH]
-```
-
-### network\_id
-
-A list of network ids to create instances with.  Specifying the id instead of reference results in a faster create time.
-
-**Note** If the network UUID changes this value will need to be updated.
-
-```yaml
-network_ref:
-   - [OPENSTACK NETWORK UUIDs]
-   - [TO CREATE INSTANCE WITH]
-```
-
-### no\_ssh\_tcp\_check
-
-**Deprecated** You should be using transport now. This will skip the ssh check to automatically connect.
-
-The default is `false`.
-
-### no\_ssh\_tcp\_check\_sleep
-
-**Deprecated** You should be using transport now. This will sleep for so many seconds. `no_ssh_tcp_check` needs
-to be set to `true`.
-
-### private\_key\_path
-
-**Deprecated** You should be using transport now. The guest image should use `cloud-init` or some other method to fetch key from meta-data service.
-
-### public\_key\_path
-
-**Deprecated** You should be using transport now. The guest image should use `cloud-init` or some other method to fetch key from meta-data service.
-
-## Disk Configuration
-
-### <a name="config-block_device_mapping"></a> block\_device\_mapping
-
-#### make\_volume
-
-Makes a new volume when set to `true`.
-
-The default is `false`.
-
-#### snapshot\_id
-
-When set, will make a volume from that snapshot id.
-
-#### volume\_id
-
-When set, will attach the volume id.
-
-#### device\_name
-
-Set this to `vda` unless you really know what you are doing.
-
-#### availability\_zone
-
-The block storage availability zone.
-
-The default is `nova`.
-
-#### volume\_type
-
-The volume type, this is optional.
-
-#### delete\_on\_termination
-
-This will delete the volume on the instance when `destroy` happens, if set to true.
-Otherwise set this to `false`.
-
-#### creation\_timeout
-Timeout to wait for volume to become available.  If a large volume is provisioned, it might take time to provision it on the backend.  Maximum amount of time to wait for volume to be created and be available.
-
-#### attach\_timeout
-If using a customized version of Openstack such a VMWare Integrated OPenstack (VIO), it may mark a volume active even though it is still performing some actions which may cause test kitchen to attach the volume to early which results in errors. Specify in seconds the amount of time to delay attaching the volume after its been marked active. Default timeout is 0.
-
-#### Example
-
-```yaml
-block_device_mapping:
-  make_volume: true
-  snapshot_id: 00000-111111-0000222-000
-  device_name: vda
-  availability_zone: nova
-  delete_on_termination: false
-  creation_timeout: 120
-  attach_timeout: 240
-```
-
-## Network and Communication Configuration
-
-### floating\_ip
-
-A specific `floating_ip` can be provided to bind a floating IP to the node.
-Any floating IP will be the IP used for Test Kitchen's Remote calls to the node.
-
-### floating\_ip\_pool
-
-A `floating_ip_pool` can be provided to allocate a floating IP from
-the pool to the instance. If `allocate_floating_ip` is true, the IP will be allocated,
-otherwise the first free floating IP will be used.  It will be the IP used for
-Test Kitchen's Remote calls to the node. If allocated, the floating IP will be
-released once the instance is destroyed.
-
-### allocate\_floating\_ip
-
-If true, allocate a new IP from the specified `floating_ip_pool` and release is afterwards.
-Otherwise, if false (the default), an existing allocated IP.
-
-### \[public\|private\]\_ip\_order
-
-In some complex network scenarios you can have several IP addresses designated
-as public or private. Use `public_ip_order` or `private_ip_order` to control
-which one to use for further SSH connection. Default is 0 (first one)
-
-For example if you have openstack istance that has network with several IPs assigned like
-
-```
-+--------------------------------------+------------+--------+------------+-------------+----------------------------------+
-| ID                                   | Name       | Status | Task State | Power State | Networks                         |
-+--------------------------------------+------------+--------+------------+-------------+----------------------------------+
-| 31c98de4-026f-4d12-b03f-a8a35c6e730b | kitchen    | ACTIVE | None       | Running     | test=10.0.0.1, 10.0.1.1   |
-
-```
-
-to use second `10.0.1.1` IP address you need to specify
-
-```yaml
-  private_ip_order: 1
-```
-assuming that test network is configured as private.
-
-### use_ipv6
-
-If true use IPv6 addresses to for SSH connections. If false, the default, use
-IPv4 addresses for SSH connections.
-
-### network\_ref
-
-The `network_ref` option can be specified as an exact id, an exact name,
-or as a regular expression matching the name of the network. You can pass one
-
-```yaml
-  network_ref: MYNET1
-```
-
-or many networks
-
-```yaml
-network_ref:
-  - MYNET1
-  - MYNET2
-```
-
-The `openstack_network_name` is used to select IP address for SSH connection.
-It's recommended to specify this option in case of multiple networks used for
-instance to provide more control over network connectivity.
-
-Please note that `network_ref` relies on Network Services (`Fog::Network`) and
-it can be unavailable in your OpenStack installation.
-
-
-### disable\_ssl\_validation
-
-```yaml
-  disable_ssl_validation: true
-```
-
-Only disable SSL cert validation if you absolutely know what you are doing,
-but are stuck with an OpenStack deployment without valid SSL certs.
-
-## Example
-
-The following could be used in a `.kitchen.yml` or in a `.kitchen.local.yml`
-to override default configuration.
-
-```yaml
----
-driver:
-  name: openstack
-  openstack_username: [YOUR OPENSTACK USERNAME]
-  openstack_api_key: [YOUR OPENSTACK API KEY] # AKA your OPENSTACK PASSWORD
-  openstack_auth_url: [YOUR OPENSTACK AUTH URL]
-  openstack_domain_id: [default is 'default'; otherwise YOUR OPENSTACK DOMAIN ID]
-  require_chef_omnibus: [e.g. 'true' or a version number if you need Chef]
-  image_ref: [SERVER IMAGE ID]
-  flavor_ref: [SERVER FLAVOR ID]
-  key_name: [KEY NAME]
-  read_timeout: 180
-  write_timeout: 180
-  connect_timeout: 180
-
-transport:
-  ssh_key: /path/to/id_rsa #Path to private key that matches the above openstack key_name
-  connection_timeout: 10
-  connection_retries: 5
-  username: ubuntu
-  password: mysecreatpassword
-
-platforms:
-  - name: ubuntu-14.04
-  - name: ubuntu-15.04
-  - name: centos-7
-    transport:
-      username: centos
-  - name: windows-2012r2
-    transport:
-      password: myadministratorpassword
-
-suites:
-# ...
-```
+See https://kitchen.ci/docs/drivers/openstack/ for documentation.
 
 ## <a name="development"></a> Development
 

data/lib/kitchen/driver/openstack.rb

@@ -82,14 +82,16 @@ module Kitchen
         disable_ssl_validation if config[:disable_ssl_validation]
         server = create_server
         state[:server_id] = server.id
-        info "OpenStack instance with ID of <#{state[:server_id]}> is ready."
 
         # this is due to the glance_caching issues. Annoying yes, but necessary.
-        debug "Waiting for VM to be in ACTIVE state for a max time of:#{config[:glance_cache_wait_timeout]} seconds"
+        debug "Waiting for a max time of:#{config[:glance_cache_wait_timeout]} seconds for OpenStack server to be in ACTIVE state"
         server.wait_for(config[:glance_cache_wait_timeout]) do
           sleep(1)
+          raise(Kitchen::InstanceFailure, "OpenStack server ID <#{state[:server_id]}> build failed to ERROR state") if failed?
+
           ready?
         end
+        info "OpenStack server ID <#{state[:server_id]}> created"
 
         if config[:floating_ip]
           attach_ip(server, config[:floating_ip])

data/lib/kitchen/driver/openstack_version.rb

@@ -23,6 +23,6 @@ module Kitchen
   #
   # @author Jonathan Hartman <j@p4nt5.com>
   module Driver
-    OPENSTACK_VERSION = "6.1.0"
+    OPENSTACK_VERSION = "6.2.0"
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: kitchen-openstack
 version: !ruby/object:Gem::Version
-  version: 6.1.0
+  version: 6.2.0
 platform: ruby
 authors:
 - Jonathan Hartman
@@ -9,7 +9,7 @@ authors:
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2021-07-02 00:00:00.000000000 Z
+date: 2022-06-14 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: test-kitchen
@@ -174,7 +174,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.2.15
+rubygems_version: 3.2.3
 signing_key:
 specification_version: 4
 summary: A Test Kitchen OpenStack Nova driver