Skip to content

Allows for use of (SMBIOS) UUID as a node ID

Compare
Choose a tag to compare
@tjmcs tjmcs released this 28 Aug 21:14
· 46 commits to master since this release

This release of the Hanlon Microkernel (v1.1.0) is designed to work with the same release (v1.1.0 and later) of Hanlon in order to enable the use of the (SMBIOS) UUID of a node as its the hardware_id. It enables the use of this UUID (and continues to support the old MAC-address-based scheme for identifying nodes) by including two new parameters (the uuid and mac_id) instead of the single parameter used previously (the hw_id) in its checkin and registration requests.

As was the case with the old hw_id parameter, these two new parameters are reported as query string parameters in the URI used for the checkin requests and as fields in a (JSON) hash map that is included in the body of the registration requests. With these changes in place, Hanlon is now able to identify nodes using either scheme (SMBIOS-UUID-based or MAC-address-based) as needed.

Also, as was the case with previous versions of the Hanlon Microkernel, three are three pre-built ISO files provided (below) as part of this release. These three ISOs are intended to be used in three different ways:

  • hnl_mk_debug-image.1.1.0.iso -- This (debug) microkernel will auto-login the tc user at the console once it completes booting. It is suitable for developers who are debugging issues with the microkernel boot/checkin process and what quick access to the microkernel once it has completed booting. Remote access (via SSH using the builtin tc password) is also enabled. This microkernel should not be used in production environments. It is meant to be used only for development purposes.
  • hnl_mk_dev-image.1.1.0.iso -- This (development) microkernel differs from the debug microkernel only in that the tc user is not automatically logged into the console when the microkernel completes the boot process. Access to the microkernel by the tc user is still allowed (both locally on the console and remotely via SSH) using the builtin tc password. As was the case with the debug microkernel, this microkernel should not be used in production environments. It is meant to be used only for development/test purposes.
  • hnl_mk_prod-image.1.1.0.iso -- This (production) microkernel is meant to be used in production environments. Access to the microkernel (both locally via the console and remotely via SSH) are disabled. In fact, in this microkernel the SSH daemon isn't even included as part of the microkernel image.

Please use the ISO that is most suitable for the environment in which you are deploying/using Hanlon (and the Hanlon Microkernel).