README.md in foreman_bootdisk-9.0.0 vs README.md in foreman_bootdisk-10.0.0

@@ -42,10 +42,11 @@
 | >= 1.8          | ~> 5.0         |
 | >= 1.9          | ~> 6.0         |
 | >= 1.11         | >= 6.1, < 8.0  |
 | >= 1.12         | ~> 8.0         |
 | >= 1.13         | ~> 9.0         |
+| >= 1.15         | ~> 10.0        |
 
 # Usage
 
 ## Configuration
 
@@ -65,10 +66,14 @@
 On VMWare compute resources it is possible to create a new host with a cd-drive
 preconfigured and have a per-host image attached before first boot. This allows
 a fully automated provisioning of hosts via ISO boot. This feature can be used by
 selecting the Bootdisk Based provisioning method under the OS tab when creating
 the host, or by setting provision_method: "bootdisk" using the API.
+Foreman will create an ISO image as part of the orchestration. This image is then
+uploaded to a VMWare datastore and attached to the VM.
+The user you configured during compute resource setup needs the permissions
+`Datastore > Browse Datastore` and `Datastore >  Low level file operations`.
 
 ## Templates
 
 An OS iPXE provisioning template is required, see the list below for the name.
 Ensure the OSes are ticked under the Associations tab and that the
@@ -119,11 +124,11 @@
     <td>No</td>
   </tr>
   <tr>
     <td>Full host image</td>
     <td>No</td>
-    <td>Yes</td>
+    <td>No (*)</td>
     <td>No</td>
     <td>Yes</td>
     <td>Yes</td>
   </tr>
   <tr>
@@ -141,9 +146,11 @@
     <td>No</td>
     <td>Yes</td>
     <td>No</td>
   </tr>
 </table>
+
+(*) - Foreman 1.14 or older do require DHCP
 
 ### Per-host images
 
 Using the host and subnet data in Foreman, per-host images can be created with
 fully static networking.  The behaviour is dynamic, as the image chainloads