This helps us not break when transitioning to using the new version of
snapstack, with the config files for each snap in the individual
steps, rather than in a config step.
Change-Id: I9b06966dcadffd92d4006c184067f744f57613aa
Part of a transition to storing the config files in the snap, rather
than in snapstack.
Also updated .gitignore to ignore emacs temp files and snapcraft
cruft.
Change-Id: Ic32b6e6b3665db9a43878b91c9288a408c8a8c0e
Switched to using cirros images rather than ubuntu cloud images, as
they are smaller, and thus better for testing. They should also go
through the zuul reverse proxy.
Update env variables to work with the tweaks to snapstack.
Change-Id: I989f1d2eacefebd2a72f75897e09b2c8b9e856ef
Tweaked tox.ini to invoke snapstack, and added test_snapstack.py to
tests dir.
Also added glance.sh to glance/tests, as part of the plan to move
those scripts from snap-test to the individual snaps.
Change-Id: Ifbd53392c394ee36cf61d1a07dba825f7b7097b8
The current snaps now have well-known aliases defined at install time
for commands [1]. This means we can drop the manual alias definition
from snapcraft.yaml and the instructions for setting it up.
When building/installing locally users can still create the alias
with 'snap alias'.
[1] https://forum.snapcraft.io/t/auto-aliases-for-openstack-base-snaps/1146/6
Change-Id: Ib34183ded789775fa76d701bd78a168bccb5fa08
The following are included in the switch to strict confinement:
* Set snapcraft.yaml confinement to strict and restore/update plugs
* Drop building of python as it's not required for strict snaps
* Switch back to running apps under root
Change-Id: I4704cac75230df5514ce42cdd6cde2b7ad9ed9b3
Enable the ability for default config files to be overridden.
Also refresh the README while documenting how default config files can
be overridden.
Change-Id: I792475bd20adda2626bbf3775924a21c811df15e
The symlinks setup key is dropped, and SNAP_COMMON is used as the
root directory where setup dirs, templates, and copyfiles are
installed. This aligns better with how snaps should behave.
Change-Id: Ie9c6ba930798dcb6c0bfd43a6504d3fdb357befa
Classic python snaps require python to be compiled from source.
Additionaly, move away from using the environment dictionary
until it is fully supported by snapd. Finally, use a fixed python
path in order to get the correct site-specific config.
These changes were recommended in the following bug:
https://bugs.launchpad.net/snapcraft/+bug/1675479
Change-Id: I134a9b7dc2366eeb7d07d3ae07deecdd173cb4a6
This is a work-around for https://bugs.launchpad.net/bugs/1675479,
where namespace packages aren't installed correctly.
Change-Id: Ib078b974b56418c907a6150175cc083f94f0c711
Classic confinement allows the snap to behave like a traditionally
packaged application with full access to the system, and enables the
use of traditional directories such as /etc and /var/log.
We will continue to store all of the snap's files in $SNAP* directories.
This enables the snap to cleanup after itself if it is removed. However,
traditional directory locations are symlinked to their corresponding
$SNAP* directories.
For example, glance configs are installed in $SNAP_COMMON/etc/glance
which has a symlink at /etc/glance.
The glance apps then use the traditional directories when running
commands and services.
Change-Id: Ic763f9c8f34ab3096e8592520db00cdf81b0d9ef
Add aliases for glance-manage -> glance.manage.
Update requirements and bindep to use snapcraft from packages until
installation from git is functional.
Change-Id: Idc7032404a46e2a6877aceb02632e7305dbc281d
OpenDev Sysadmins