LAVA is migrating to packaging for installation and upgrades. There have already been notices posted about the migration and the availability of packages and package updates on this list.
http://staging.validation.linaro.org and http://playground.validation.linaro.org have already been migrated. The time has come to merge the packaging support into the master git branch and this has known consequences for installations using lava-deployment-tool. lava-deployment-tool production installs remain supported until validation.linaro.org is migrated to packaging during a scheduled downtime window which is likely to be at the end of this month (June 2014). lava-manifest will be end-of-life at the same time. lava-deployment-tool *developer mode* is end-of-life today. lava-manifest is being updated to stop upgrading passed versions at the last supportable commits for developer mode. Once validation.linaro.org is migrated, all lava-deployment-tool instances will be stopped from upgrading beyond the last commit prior to the merge. There are particular concerns with developer mode and local buildouts: Any buildout based on upstream LAVA git repositories (or rebased to pull in upstream LAVA git) *will* break the existing LAVA instance. This is unavoidable and entirely predictable - lava-deployment-tool is unable to migrate LAVA from django1.4 to django1.6 and there is no lava-deployment-tool support for LAVA development beyond this point. Please remove all local buildouts from lava-deployment-tool instances and do *not* update or rebase the buildout to latest LAVA git master after today. lava-deployment-tool is gaining a check to fail any upgrade where local buildouts exist, until those buildouts are removed. Developer mode instances using lava-deployment-tool will get no further code updates. There is no need to actually migrate from developer mode back to production mode, the necessary migration is to packaging. Production mode instances using lava-deployment-tool will only get hot fixes via the release branch until the migration of validation.linaro.org. At that point, the master branch will be merged into release and this will mark the formal end of support for lava-deployment-tool. Please take time to read the migration notes and to decide on how your lava-deployment-tool instances should be upgraded. https://staging.validation.linaro.org/static/docs/migration.html Once upgraded, tools are provided to build updated packages based on local code as well as binary packages being uploaded to Debian (then migrating into Ubuntu Unicorn). There are two options currently: Debian Jessie (testing) - the recommended upgrade as this is the path which the LAVA team will follow. staging and playground are already running this install. Development in LAVA is now based on Debian. Latest updates are based on Debian unstable and changes are migrated into Jessie (current testing) intermittently. staging is already running Jessie with packages updated based on unstable. Ubuntu Trusty Tahr 14.04LTS - A lot of LAVA dependencies were not included into Trusty, so unlike Jessie, users who choose Trusty are recommended to consider upgrading to Unicorn which will receive updates of these dependencies via Debian. More information and detailed guides on how to migrate are available in the migration documentation on staging. https://staging.validation.linaro.org/static/docs/migration.html -- Neil Williams ============= http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
_______________________________________________ linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation
