cantzakas / gpdb-packaging Goto Github PK

When targeting VirtualBox, if an image is already running with the same name, it will fail to create the new VM. It also (how?) manages to mess up the base OS image, which means it has to be re-built (by answering yes to the "rebuild?" question). Ideally this should be detected and warned about without causing the corruption. Maybe this should be reported to Packer?

Might be worth adding a timestamp to all image names, but is this something we want when distributing VMs?

Greg Chase commented that a lot of partners ask for a way to spin up a VM with some pre-loaded demo data. If there were an optional hook in this library to do that, there might be value in that.

REFRESH_TOKEN='**********' ./build.sh fails on first execution. Investigate whether it was connection problem on downloading the GPDB binary file or need to update instructions to include --force-download

This might be why it returns a non-zero exit status, so fixing the warnings should let us remove the || true on that line (maybe)

Add support for exporting as a docker container

Discuss again security concerns but also consider gpadmin is the "standard" user account used for connecting into the VM via SSH, start and stop the database, etc.

This was requested recently and I did a first-pass implementation in f199bb0 but it currently requires an enterprise license of VMWare and I'm not sure if the second stage even works (it can build a base image but I wasn't able to test the actual Greenplum build with a non-licensed copy of VMWare Fusion)

There are hints online that there is a free version of VMWare (somewhere) which can be used, but it seems like it might not be able to export? Needs somebody with more familiarity with VMWare's ecosystem.

Also worth noting that VMWare support in Packer is currently in a state of flux (see hashicorp/packer#7168)

For now the basic framework for supporting multiple formats is ready, but more experiments are needed to make it useful.

break down #16 into smaller tasks