Changes between Version 11 and Version 12 of NeoContainers
- Timestamp:
- Jul 13, 2015 11:13:42 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
NeoContainers
v11 v12 21 21 }}} 22 22 The {{{UB14-CHEF12}}} image is not required, but speeds things up a bit. 23 For each container in the experiment, specify {{{image_os}}}, {{{image_type}}}, {{{ mage_name}}}, and optionally an {{{image_url}}} via the {{{tb-add-node-attribute}}} syntax. Details on each attribute is given below.23 For each container in the experiment, specify {{{image_os}}}, {{{image_type}}}, {{{image_name}}}, and optionally an {{{image_url}}} via the {{{tb-add-node-attribute}}} syntax. Details on each attribute is given below. 24 24 25 25 * {{{image_os}}} - This is really just to distinguish Windows from non-Windows nodes. If the {{{image_os}}} starts with "{{{windows}}}", the image will be treated as a Windows node. Otherwise it'll be assumed to be some sort of Unix-y container. 26 26 * {{{image_type}}} - This setting describes the containerization tech of the node. Currently this is *always* set to "{{{vagrant}}}" as Vagrant is the only package used to spin up the containers. 27 * {{{image_name}}} - The name of the image. The name identifies an OS, virtualization platform, and version. This name is based on the Vagrant naming scheme. The standard, "baked in" image names are:27 * {{{image_name}}} - The name of the image. The name identifies an OS, virtualization platform, and version. This name is based on the Vagrant naming scheme. The standard, "baked in" image names (and types) are: 28 28 * chef/centos-7.0 (virtualbox, 1.0.0) 29 29 * chef/freebsd-10.0 (virtualbox, 1.0.0)