foreman_bootdisk 2.0.3 → 2.0.4

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: ada1629fb10bac22102cbd9eefade4131d825734
4
- data.tar.gz: d3c3d123abc34f9d80b7aabb533a413402787820
3
+ metadata.gz: 3dbe2e8426146b25ce78dea249b33ba9f35293b1
4
+ data.tar.gz: 0741b50ad7795889f4f694687c25fef87f1c39fa
5
5
  SHA512:
6
- metadata.gz: 85bf056ee2b9ffafb0ab4ac605a65a9c5e9e400e9f920c93f66c270a949ed3d7f47fca3322e3d9ffa21a48cf62e6141a94210f20edc155dd93c0a5fe925d13da
7
- data.tar.gz: d8e071b412f3db4636a7379154f408864149e3019e34b084f066ccb0115e2e0eda3c8d0e21fa99f3c15012c444c4c0b04a279c288281acfaaf5e15366a8246e5
6
+ metadata.gz: c8c7dd29e0e76766b8408a1611bf5c7a5d18d54adb7fa4961929f8d642418a853b271c85d2b3c2db69179f053c4b29ddad10aae05a8b5dd3f4cd5f8c42653e2b
7
+ data.tar.gz: 99eabe8b84e51cb47ca8a7503a2d2663c92d6a27ea7409116ed3594c5a1f0cc62165d8d01d98275c43d4e81cff30992214e32ccaf7f99f259bbd411446122734
data/CHANGES.md CHANGED
@@ -1,5 +1,9 @@
1
1
  # Changelog
2
2
 
3
+ ## v2.0.4
4
+ * fix Foreman 1.5 host show page compatibility
5
+ * updates to README
6
+
3
7
  ## v2.0.3
4
8
  * fix Foreman 1.5 auth system compatibility (#4893)
5
9
  * fix filename of generic ISO image in rake task
data/README.md CHANGED
@@ -42,13 +42,9 @@ gPXE images are unsupported due to lack of initrd support.
42
42
 
43
43
  ## Configuration
44
44
 
45
- Some configuration is set under Administer>Settings>Bootdisk in the Foreman UI.
46
-
47
- * `bootdisk_ipxe_dir` points to the directory containing ipxe.lkrn
48
- * `bootdisk_syslinux_dir` points to the directory containing syslinux images
49
- * `bootdisk_host_template` is the name of the per-host boot disk template
50
- * `bootdisk_generic_host_template` is the name of the generic boot disk template
51
- * `bootdisk_mkiso_command` is the name of genisoimage/mkisofs on your OS
45
+ With all image types, hosts have to be registered to Foreman prior to booting
46
+ the image. Hosts will be identified by their MAC or IP address to provide
47
+ the correct provisioning template if the host is in build mode.
52
48
 
53
49
  For per-host images, ensure host IP addresses and subnets are populated, and
54
50
  the subnet's gateway, subnet mask and DNS resolver(s) are correctly configured
@@ -57,11 +53,7 @@ under Infrastructure>Subnets in Foreman.
57
53
  To permit access to images for non-admin users, add the "Boot disk access" role
58
54
  to a user or the "download_bootdisk" permission to an existing role.
59
55
 
60
- ### Templates
61
-
62
- The templates used on the boot disks themselves are read-only so they can be
63
- updated in new versions of the plugin. To customise, copy the contents to a
64
- new template and set the name in Administer>Settings>Bootdisk.
56
+ ## Templates
65
57
 
66
58
  An OS iPXE provisioning template is required, see the list below for the name.
67
59
  Ensure the OSes are ticked under the Associations tab and that the
@@ -70,14 +62,45 @@ iPXE template is selected under the Templates tab on the OS.
70
62
  * Kickstart (EL/Fedora) OSes, use "Kickstart default iPXE"
71
63
  * Preseed (Debian/Ubuntu) OSes, use "Preseed default iPXE"
72
64
 
73
- Lastly, the OS provision template (i.e. kickstart/preseed) should provide the
74
- static IP details required to configure the OS. For a kickstart file, the
75
- following configuration will do this:
65
+ Standard templates for the kickstart/preseed and optionally finish script
66
+ still need to be associated, as bootdisk only handles bootstrapping.
67
+
68
+ * EL clones or Fedora should use "Kickstart default" as the "provision"
69
+ template
70
+ * RHEL should use "Kickstart RHEL default" as the "provision" template
71
+ * Preseed (Debian/Ubuntu) OSes, use "Preseed default" as the
72
+ "provision" template and "Preseed default finish" as the "finish" template
73
+
74
+ If you're not using Foreman's default kickstart or preseed provisioning
75
+ templates, then ensure your versions provide the static IP details required to
76
+ configure the OS. For a kickstart file, the following configuration will do
77
+ this:
76
78
 
77
79
  network --bootproto <%= @static ? "static" : "dhcp" %> --hostname <%= @host %> <%= "--ip=#{@host.ip} --netmask=#{@host.subnet.mask} --gateway=#{@host.subnet.gateway} --nameserver=#{@host.subnet.dns_primary},#{@host.subnet.dns_secondary}" if @static %>
78
80
 
79
81
  Foreman's default kickstart and preseed files are ready to use.
80
82
 
83
+ ### Customising boot disk templates
84
+
85
+ The templates used on the boot disks themselves are read-only so they can be
86
+ updated in new versions of the plugin. To customise, copy the contents to a
87
+ new template and set the name in Administer>Settings>Bootdisk.
88
+
89
+ * `bootdisk_host_template` is the name of the per-host boot disk template
90
+ * `bootdisk_generic_host_template` is the name of the generic boot disk template
91
+
92
+ These templates are baked into the downloaded ISO files and generally don't
93
+ need to be modified.
94
+
95
+ ## Settings
96
+
97
+ Some more advanced settings are available under Administer>Settings>Bootdisk in
98
+ the Foreman UI.
99
+
100
+ * `bootdisk_ipxe_dir` points to the directory containing ipxe.lkrn
101
+ * `bootdisk_syslinux_dir` points to the directory containing syslinux images
102
+ * `bootdisk_mkiso_command` is the name of genisoimage/mkisofs on your OS
103
+
81
104
  ## Available images
82
105
 
83
106
  The image types have trade-offs, but are all meant for environments without
@@ -126,10 +149,10 @@ Optionally set `OUTPUT=/path/foo.iso` to change the output destination.
126
149
 
127
150
  ### Generic image
128
151
 
129
- This provides a single ISO that can be used by all hosts, but since IP details
130
- can't be stored inside, it requires a DHCP pool on the network to bootstrap.
131
- It will boot and contact Foreman for template of a registered host matching a
132
- MAC address or the IP the host was assigned by DHCP.
152
+ This provides a single ISO that can be used by all registered hosts, but since
153
+ IP details can't be stored inside, it requires a DHCP pool on the network to
154
+ bootstrap. It will boot and contact Foreman for template of a registered host
155
+ matching a MAC address or the IP the host was assigned by DHCP.
133
156
 
134
157
  The installation can continue on either the DHCP or static IP depending on how
135
158
  the OS iPXE template is configured, and could configure the assigned IP
@@ -5,7 +5,7 @@ module Bootdisk::HostsHelperExt
5
5
  alias_method_chain :host_title_actions, :bootdisk
6
6
  end
7
7
 
8
- def host_title_actions_with_bootdisk(host, vm)
8
+ def host_title_actions_with_bootdisk(*args)
9
9
  title_actions(
10
10
  button_group(
11
11
  select_action_button(_('Boot disk'), {},
@@ -14,7 +14,7 @@ module Bootdisk::HostsHelperExt
14
14
  )
15
15
  )
16
16
  )
17
- host_title_actions_without_bootdisk(host, vm)
17
+ host_title_actions_without_bootdisk(*args)
18
18
  end
19
19
 
20
20
  end
@@ -1,3 +1,3 @@
1
1
  module Bootdisk
2
- VERSION = '2.0.3'
2
+ VERSION = '2.0.4'
3
3
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: foreman_bootdisk
3
3
  version: !ruby/object:Gem::Version
4
- version: 2.0.3
4
+ version: 2.0.4
5
5
  platform: ruby
6
6
  authors:
7
7
  - Dominic Cleal
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2014-03-27 00:00:00.000000000 Z
11
+ date: 2014-04-09 00:00:00.000000000 Z
12
12
  dependencies: []
13
13
  description: Plugin for Foreman that creates iPXE-based boot disks to provision hosts
14
14
  without the need for PXE infrastructure.