- Sown-monitor service dependencies (orchard)
- Updating SOWN Zone file (daveruss)
- Work on package management system
When modifying config files, invalidate the hash and last_modified ... otherwise changes due to code (and not changes in the database) won't be pulled down. update_sown_config reset the root password to be the homenode root password.
VPN or-not check should be based on a client-certificate SSL conversation with sown-auth.ecs.soton.ac.uk All nodes are assumed to be tunelled, if a node is plugged into the sown-vlan, we can manually configure the routing.
Kohana debug logs are found at: /srv/auth/www/kohana/application/logs/<year>/<month>/<day>.php
- Work on comprehending the package management system :
Leth and SjH have been working on the problem from different directions, and won't ever meet in the middle.
Leth's work is a node-focused package-management framework that lacks a complete database schema. SjH's work is a gui focused framework for managing the database.
Leth's code is all on auth, and has a database on auth, but it also reads from the live database. Leth's models/code is in /srv/www/auth/kohana/applications/classes/models/new All of Leth's models are prefixed with 'new', we don't know why. Leth's code is version controlled. SjH's code lives on dev, and has a database on dev called 'sown_admin'.
We have modified SjH's schema to contain the features we need from Leth's work, and reflect how we see the package-management working. We will continue with Leth's code/models, but point them at SjH's database, with our schema modifications.