Skip to content
lloydie edited this page Feb 14, 2019 · 15 revisions

Caveats

  • NOT production quality.
  • BROKEN, only developers looking to assist with debugging should test !
  • DONT USE ON DISKS WITH DATA YOU HAVEN'T BACKED UP

Status

  • setting up testing environment. "nearly done"
    • apt cache setup in vagrant machine to act as "cache server"
    • apt cache is provisioned in one script.
    • from their the zfs-install script can run as normal. "Failing, but that is the goal"
    • this makes each test-cycle much faster using the cache and doesn't change the script in any way that it won't run "standalone"
    • Travis, "no support for virtualbox, that sucks". Docker images but that's all.
    • adding support for Triton,GCP,AWS adds additional complexity of Vault and probably Consul at a minimum. And the cost is a consideration obviously.

Todo

  • initial portability refactor, waiting code review.

  • beta ubuntu/bionic64 "first os"

  • various TODO and FIXME in zfs-install.sh

  • Vagrantfile

  • Packer

  • beta release.

Install

** please run in virtual machine or test machine. **

$ zfs-install.sh on machine. or $ /test/vagrant up

Packer

  • I'm new to packer but this tool is awesome. Just going through docs etc.
  • Consideration of the potential of this tools capabilities in relation to this project needs further investigation.
  • It provides all the hooks necessary and is well hashicorp well respected code quality etc. Any and possible all "scripted" code would be well served being moving into the hashicorp work flow, with all the benefits, providers etc furthermore once i understand the entire capabilities i believe additional capabilities not even an option in the standard "script" environment are simple available. Primarily the integration with the entire hashicorp suite provide the "right" path moving forward.
Clone this wiki locally