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: Ia69fba6d0ed8d1fc47bcabfea817f263dbd4d66d
This is 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: I2542bf23435d3dbe5e399f1c938f3c9d879ed9ba
Tweaked tox.ini to invoke snapstack, and added test_snapstack.py to
tests dir.
Also added neutron.sh to neutron/tests, as part of the plan to move
those scripts from snap-test to the individual snaps.
Change-Id: Ie0e7d3211b99ace8f5c19e2781d928f3a589acce
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: Iaac052b25bf2509bdb57161086a7be59d58de15f
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: I2a985ecea36c82f9b08f145015219911e0ec0616
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: Icc3747268d0d0c7609681a877f67a7cc8a5d9ba2
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: I4f339ae90c08d6f624793020690d067b82af4029
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: Ibe68ab3a252067421169effd99fc5b14d490136b
This is a work-around for https://bugs.launchpad.net/bugs/1675479,
where namespace packages aren't installed correctly.
Change-Id: Ie4b8898ad79a6958bdd58dccdc668441848bff78
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, neutron configs are installed in $SNAP_COMMON/etc/neutron
which has a symlink at /etc/neutron.
The neutron apps then use the traditional directories when running
commands and services.
Change-Id: I392ba95cfaad1509b58beb2f82ba865b73971d5a
OpenDev Sysadmins