These settings are less performant, but more universally compatible.
A seperate task would be to expose these settings via the snap config,
in some sensible way. For now, this means that microstack will "just
work" in more places.
This fixes an issue where we weren't creating a netplan config and/or
and entry in /etc/network/interfaces for br-ex, and thus losing
external access to our virtual networks after reboot.
Since we don't actually want to touch the host system's networking
config, we just drop a oneshot daemon into place that sets br-ex up
each time the snap services are started.
It appeared to merely be an issue of ensuring that the daemon started before the server.
Also the version on one of the files that we download for another serivce. (Fragile code is still fragile, but fixing it is a separate TODO.)
* Fix some common errors when starting up.
Added more polls for services that we want to make sure are up and running.
Fixed issue where launch script wouldn't run when /snap/bin wasn't in the PATH.
* Added very basic resiliance to launch.sh script.
Tears down a machine and attempts to rebuild it if the build drops into an error state.
Added microstack.launch command.
Provides a quick way to launch an m1.tiny instance.
Extendable in the future to be a bit more like the multipass launch or lxc launch commands.
* Preseed mysql data dir with something useful
* Configure fernet keys on first install
* Update missing instances directory
* Updated mysql.tar.xz
* Folded configure command into configure hook.
Fixed dashboard errors.
Added a proper uwsgi script with matching .ini templates.
Added django settings files that fix issues with Django attempting to write files to the read only snap filesystem, and generally make things work well in the snap.
Fixed snap-openstack.yaml entries so that our file and directory setup is accurate.