These are instructions for runnning the demo that we're planning on
running at the Denver Openstack summit. It walks the user through
deploying microstack, and then deploying a functioning kubernetes
cloud on top of it.
Dropped a command to change the endpoints from localhost to 10.20.20.1
in the configure hook.
This is a temporary solution, pending automation of the database
update. (I was burning too much time getting a manual dump to work for
now.)
Updated the mysql tarball, which has the localhost -> 10.20.20.1
update.
Test for pinging Internet was failing due to not waiting long enough,
so added a proper retry strategy.
Addresses the issue where services such as a juju controller cannot
access endpoints from within an instance.
Updated all references to localhost to 10.20.20.1, and added the
address to ALLOWED_HOSTS.
Also updated version of qemu lib.
This is a little messy -- it's a bash script with some outside
dependencies, and it makes assumptions about the capabilities of the
environment that it's being run in. But it does basically work, and
provides contributors with some basic reassurance that they have built
a working snap.
Fixes lp#1812415
Prior to this fix, instances spun up by microstack could not
successfully route to and from the Internet. Setting a rule for ipv4
forwarding and iptables rules for the nat fix the issue.
This is a bandaid for
https://github.com/CanonicalLtd/microstack/issues/39, where switching
to the material theme can get your GUI stuck in an errored
state. We'll re-enable everything once that bug is fixed.
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.
Ryan Beisner
Pete Vander Giessen
Pete Vander Giessen
Nicolas Pochet
James Page
Chris Morgan