OpenStack in a snap!

Go to file

Pete Vander Giessen d34a98ad15 Remove iptables part This change prevents builds in the gate from timing out while pulling the iptables part, which was happening with increasing frequency. The part was originally added in an attempt to isolate ourselves better from the host system, despite being classically confined. This approach was unreliable -- it doesn't work particularly well for commands requiring sudo. We can back off this change (especially since we've removed the special pathing that pointed us at the snapcraft built iptables anyway -- I think that the part is superfluous). In addition to the automated tests, I have verified that the following work: 1. xenial and eoan installs 2. clustering 3. refresh from beta and edge Change-Id: I7d314eccc0433e54a800ed47add684c2e0fa6565 Closes-bug: 1854081		2019-11-26 20:27:09 +00:00
patches	Align ovs version with Stein UCA	2019-10-18 15:40:41 +00:00
snap/hooks	Refresh now sets missing config values	2019-11-21 08:46:41 +01:00
snap-overlay	Fixed dashboard_allowed_hosts config setting.	2019-11-21 08:47:04 +01:00
snap-wrappers	Delay creating external bridge until we are initializing	2019-11-12 23:19:51 +00:00
tests	Added refresh tests	2019-11-20 21:35:51 +00:00
tools	Fixed dashboard_allowed_hosts config setting.	2019-11-21 08:47:04 +01:00
.gitignore	Added testing for control nodes	2019-10-16 15:44:38 +00:00
.gitreview	Added automated testing via tox and zuul.	2019-07-24 08:04:38 +01:00
.zuul.yaml	Ported and updated launch script	2019-10-23 01:09:42 +00:00
CONTRIBUTING.md	Updated "Building MicroStack" section of CONTRIBUTING.md	2019-11-14 17:36:25 +00:00
DEMO.md	Ported and updated launch script	2019-10-23 01:09:42 +00:00
README.md	Update README since doc publication	2019-11-04 15:23:51 +00:00
snapcraft.yaml	Remove iptables part	2019-11-26 20:27:09 +00:00
test-requirements.txt	Added testing for control nodes	2019-10-16 15:44:38 +00:00
tox.ini	Added refresh tests	2019-11-20 21:35:51 +00:00

README.md

MicroStack

MicroStack is a single-machine, snap-deployed OpenStack cloud.

Common purposes include:

Development and testing of OpenStack workloads
Continuous integration (CI)
IoT and appliances
Edge clouds (experimental)
Introducing new users to OpenStack

Currently provided OpenStack services are: Nova, Keystone, Glance, Horizon, and Neutron.

MicroStack is frequently updated to provide the latest stable updates of the most recent OpenStack release.

Requirements: You will need at least 2 CPUs, 8 GiB of memory, and 100 GiB of disk space.

See the full MicroStack documentation.

Installation

At this time you can install from the --beta or --edge snap channels:

sudo snap install microstack --classic --beta

Initialisation

Initialisation will set up databases, networks, flavors, an SSH keypair, a CirrOS image, and open ICMP/SSH security groups:

sudo microstack.init --auto

OpenStack client

The OpenStack client is bundled as microstack.openstack. For example:

microstack.openstack network list
microstack.openstack flavor list
microstack.openstack keypair list
microstack.openstack image list
microstack.openstack security group rule list

Creating an instance

To create an instance (called "awesome") based on the CirrOS image:

microstack.launch cirros --name awesome

SSH to an instance

The launch output will show you how to connect to the instance. For the CirrOS image, the user account is 'cirros'.

ssh -i ~/.ssh/id_microstack cirros@<ip-address>

Horizon

The launch output will also provide information for the Horizon dashboard. Its credentials are:

username: admin
password: keystone

Customising and contributing

To customise services and settings, look in the .d directories under /var/snap/microstack/common/etc. You can add services with your package manager, or take a look at CONTRIBUTING.md and make a code based argument for adding a service to the default list.

Reporting a bug

Please report bugs to the MicroStack project on Launchpad.