README.md in beaker-hostgenerator-1.18.1 vs README.md in beaker-hostgenerator-2.0.0

@@ -57,39 +57,39 @@
 Below are some example usages of `beaker-hostgenerator`.
 
 ### Simple two-host layout
 
 ```
-$ beaker-hostgenerator centos6-64mdca-32a
+$ beaker-hostgenerator centos9-64mdca-64a
 ```
 
 Will generate
 
 ```yaml
 ---
 HOSTS:
-  centos6-64-1:
+  centos9-64-1:
     pe_dir:
     pe_ver:
     pe_upgrade_dir:
     pe_upgrade_ver:
     hypervisor: vmpooler
-    platform: el-6-x86_64
-    template: centos-6-x86_64
+    platform: el-9-x86_64
+    template: centos-9-x86_64
     roles:
     - agent
     - master
     - database
     - dashboard
-  centos6-32-2:
+  centos9-64-2:
     pe_dir:
     pe_ver:
     pe_upgrade_dir:
     pe_upgrade_ver:
     hypervisor: vmpooler
-    platform: el-6-i386
-    template: centos-6-i386
+    platform: el-9-x86_64
+    template: centos-9-x86_64
     roles:
     - agent
 CONFIG:
   nfs_server: none
   consoleport: 443
@@ -97,26 +97,26 @@
 ```
 
 ### Single host with Arbitrary Roles
 
 ```
-$ beaker-hostgenerator centos6-32compile_master,another_role.ma
+$ beaker-hostgenerator centos9-64compile_master,another_role.ma
 ```
 
 Will generate
 
 ```yaml
 ---
 HOSTS:
-  centos6-32-1:
+  centos9-64-1:
     pe_dir:
     pe_ver:
     pe_upgrade_dir:
     pe_upgrade_ver:
     hypervisor: vmpooler
-    platform: el-6-i386
-    template: centos-6-i386
+    platform: el-9-x86_64
+    template: centos-9-x86_64
     roles:
     - agent
     - master
     - compile_master
     - another_role
@@ -131,11 +131,11 @@
 ```
 
 ### Two hosts with multiple hypervisors and arbitrary host settings
 
 ```
-$ beaker-hostgenerator centos6-64m{hypervisor=none\,hostname=static-master}-redhat7-64a{somekey=some-value}
+$ beaker-hostgenerator centos9-64m{hypervisor=none\,hostname=static-master}-redhat7-64a{somekey=some-value}
 ```
 
 Will generate
 
 ```yaml
@@ -144,11 +144,11 @@
   static-master:
     pe_dir:
     pe_ver:
     pe_upgrade_dir:
     pe_upgrade_ver:
-    platform: el-6-x86_64
+    platform: el-9-x86_64
     hypervisor: none
     roles:
     - agent
     - master
   redhat7-64-1:
@@ -169,24 +169,24 @@
 ```
 
 ### Two hosts with arbitrary host settings with arbitrary lists
 
 ```
-$ beaker-hostgenerator centos6-64m{disks=\[16\]}-redhat7-64a{disks=\[8\,16\]}
+$ beaker-hostgenerator centos9-64m{disks=\[16\]}-redhat7-64a{disks=\[8\,16\]}
 ```
 
 Will generate
 
 ```yaml
 ---
 HOSTS:
-  centos6-64-1:
+  centos9-64-1:
     pe_dir:
     pe_ver:
     pe_upgrade_dir:
     pe_upgrade_ver:
-    platform: el-6-x86_64
+    platform: el-9-x86_64
     hypervisor: vmpooler
     disks:
     - 16
     roles:
     - agent
@@ -285,24 +285,24 @@
 The term "custom" in this case signifies that it's not a built-in hypervisor
 (like `vmpooler`), which means we'll have to provide all the configuration
 ourselves as there isn't any built-in configuration for our hypervisor.
 
 ```
-$ beaker-hostgenerator --hypervisor=custom --global={custom_api=http://api.custom.net} centos6-64
+$ beaker-hostgenerator --hypervisor=custom --global={custom_api=http://api.custom.net} centos9-64
 ```
 
 Will generate
 
 ```yaml
 ---
 HOSTS:
-  centos6-64-1:
+  centos9-64-1:
     pe_dir:
     pe_ver:
     pe_upgrade_dir:
     pe_upgrade_ver:
-    platform: el-6-x86_64
+    platform: el-9-x86_64
     hypervisor: custom
     roles:
     - agent
 CONFIG:
   nfs_server: none
@@ -326,32 +326,32 @@
 - `]` is `%5D`
 
 For a full URL encoding reference see: http://www.w3schools.com/tags/ref_urlencode.asp
 
 ```
-$ beaker-hostgenerator centos6-64mcd-aix53-POWERfa%7Bhypervisor=aix%2Cvmhostname=pe-aix-53-acceptance.delivery.puppetlabs.net%7D
+$ beaker-hostgenerator centos9-64mcd-aix53-POWERfa%7Bhypervisor=aix%2Cvmhostname=pe-aix-53-acceptance.delivery.puppetlabs.net%7D
 ```
 
 Is equivalent to
 
 ```
-$ beaker-hostgenerator centos6-64mcd-aix53-POWERfa{hypervisor=aix,vmhostname=pe-aix-53-acceptance.delivery.puppetlabs.net}
+$ beaker-hostgenerator centos9-64mcd-aix53-POWERfa{hypervisor=aix,vmhostname=pe-aix-53-acceptance.delivery.puppetlabs.net}
 ```
 
 And will generate
 
 ```yaml
 ---
 HOSTS:
-  centos6-64-1:
+  centos9-64-1:
     pe_dir:
     pe_ver:
     pe_upgrade_dir:
     pe_upgrade_ver:
     hypervisor: vmpooler
-    platform: el-6-x86_64
-    template: centos-6-x86_64
+    platform: el-9-x86_64
+    template: centos-9-x86_64
     roles:
     - agent
     - master
     - dashboard
     - database
@@ -386,21 +386,21 @@
 behavior under specific conditions. An example of such a test fixture is as
 follows:
 
 ```yaml
 ---
-arguments_string: "--pe_dir /opt/hello centos6-64mdc"
+arguments_string: "--pe_dir /opt/hello centos9-64mdc"
 environment_variables: {}
 expected_hash:
   HOSTS:
-    centos6-64-1:
+    centos9-64-1:
       pe_dir: "/opt/hello"
       pe_ver: 
       pe_upgrade_dir: 
       pe_upgrade_ver: 
       hypervisor: vmpooler
-      platform: centos-6-x86_64
-      template: centos-6-x86_64
+      platform: el-9-x86_64
+      template: centos-9-x86_64
       roles:
       - agent
       - master
       - database
       - dashboard