v0.4.5-4.4-extra

Included extra.tar.gz kernel drivers, i.e. ALL supplied with kernel for max hardware list support what may be useful when something goes wrong with default image on bare metal (like exactly in my case happened)

v0.4.5-4.4

Moved to Ubuntu-4.4.0-23.41-rancher kernel for newer BTRFS version first of all (since BTRFS is relatively young but is developed quite intensively)

v0.4.5-kvm-btrfs-luks-lvm2-nfs-iscsi

Added BTRFS, LUKS (dm-crypt/cryptsetup), LVM2, NFS, iSCSI

Just appropriate buildroot packages has been added. No special scenario/conception support for Rancher OS exactly is implemented yet. But I am going to deploy both of below on my diskless stateless servers (booting Rancher OS via iPXE to RAM only since our server disks are LUKS encrypted) wrapping it into ros and extra tiny docker images based on this os-base and configured as Rancher OS system service (example here 1 and here 2) but built in into initrd without downloading heavy ubuntu base images to RAM in our case. And I will to get back here soon with updates to decription/code:

• LUKS (dm-crypt/cryptsetup) requested here. While it's not yet fully supported by ros to find/mount it automatically or setting manually via cloud-config and I can not find clear conception about it mentioned anywhere for Rancher OS exactly, but I see adding it support to base image quite useful for scenario of booting RancherOS diskless stateless via network (local vi PXE or internet via iPXE/iSCSI) or from unencrypted hardisk partion or another local media, then SSH and going something like googling "encrypted root dropbear", as well as goot start point/playground for playing with some new scenarios/conceptions more actual/adopted for Rancher OS (first what comes to my mind - is to scan all block devices if they are LUKS and to ask passphrase on unlock command execution from SSH
• BTRFS should work same as with ext4 but passing fs type to (1) ros install command line (e.g-t generic-btrfs or separate --fstype btrfs or to (2) kernel param or cloud-config as rancher.state.fstype. Extra BTRFS options like subvolumes, multiple devices (raid) could be passed same way.
• LVM2, iSCSI, NFS - same as BTRFS above but I am not going to test/use them in the nearest future since BTRFS + LUKS themselfes do all I need. But may be someone else will find it useful and will get back with feedback/contributions