README.md in dev-lxc-1.2.2 vs README.md in dev-lxc-1.3.0
- old
+ new
@@ -343,17 +343,46 @@
```
dev-lxc up chef
```
+### Adhoc Clusters
+
+dev-lxc can also manage an adhoc cluster of servers.
+
+An adhoc cluster is just a set of managed servers cloned from the specified platform
+image. The servers have SSH server running, a "dev-lxc" user with "dev-lxc" password and
+passwordless sudo access.
+
+This is particularly useful when you want to use something else, such as chef-provisioning,
+to configure the servers.
+
+The number of servers, their names and their IP addresses can be changed to fit your
+particular requirements.
+
+The "adhoc" template provides an example cluster configuration suitable for creating a
+Chef Delivery cluster.
+
+```
+mkdir -p /root/dev/clusters/delivery
+cd /root/dev/clusters/delivery
+dev-lxc init adhoc > dev-lxc.yml
+cluster-view
+dl up
+```
+
### Managing Node Containers
#### Manually Create a Platform Image
Platform images can be used for purposes other than building clusters. For example, they can
be used as Chef nodes for testing purposes.
+Platform images have openssh-server installed and running with unique SSH Host Keys.
+
+Platform images have a "dev-lxc" user with "dev-lxc" password and passwordless sudo.
+
You can see a menu of platform images this tool can create by using the following command.
```
dev-lxc create
```
@@ -632,9 +661,13 @@
This image provides the chosen OS platform and version (e.g. p-ubuntu-1404).
A typical LXC container has minimal packages installed so `dev-lxc` makes sure that the
same packages used in Chef's [bento boxes](https://github.com/opscode/bento) are
installed to provide a more typical server environment.
A few additional packages are also installed.
+
+ Platform images have openssh-server installed and running with unique SSH Host Keys.
+
+ Platform images have a "dev-lxc" user with "dev-lxc" password and passwordless sudo.
*Once this platform image is created there is rarely a need to delete it.*
2. Shared Image