Releases: 128technology/blaster
Releases · 128technology/blaster
v.1.2.1
v1.2
- Introduced database schema versions - no more need to manually handle tables on upgrades (including this one)
- Allow toggling of ISO post install behavior between default "shutdown" and "reboot" - useful when using a default quickstart
- Simplified NFS setup - hopefully eliminate any NFS issues mounting ISOs
- Support for bootstrap scripts - place pre- and/or post- bootstrap scripts into an ISO so they will be run during bootstrapping
- Docker containers start automatically after a host reboot
- new setup script - allows for easier turn up of blaster
v1.1.2: Merge pull request #39 from 128technology/develop
v1.1.1
There was a mistake in release v1.1 where I reverted changes that were actually needed.
v1.1: Merge pull request #21 from 128technology/develop
- Improved memory usage when downloading ISOs
- Added button to search all conductors for assets matching hardware identifiers and automatically associate quickstarts
- Proxy server support
- Ability to disassociate a quickstart from a node after an association has been made
- Ability to define custom passwords for root and t128 user to override ISO defaults
- Update to handle new 128T Combined ISO format
- Self-documentation in web UI
- Update Manage nodes page to improve workflow of assigning quickstarts to nodes
Initial Release
Baseline functionality for enabling PXE booting and quickstart hosting:
- Upload and manage PEM certificate
- Download ISOs from yum server or upload directly
- Stage ISOs for PXE booting
- Detect UEFI or legacy BIOS booting and assign correct configuration through DHCP
- Append base kickstart to POST system serial number as a new node
- Configure conductors in order to retrieve quickstart file through API
- View nodes on configured conductors and allow downloading of kickstart by clicking a link
- Manual upload of quickstarts also supported (non-encrypted)
- Create association between system identifier (serial number, typically) and a specific kickstart
- During OTP bootstrapping, offer the specific kickstart that was assigned to the system identifier