Update Use Cases

Use Cases for update scenarios

Motivation

Improve experience of Geonode and Mapstory from a developer's perspective, and establish story for clients seeing to evolve deployments over time with minimal risk:

supporting someone updating GeoNode to include storyscapes type functionality.
development of Geonode extensions - potentially to extend MapStory - e.g. gazetteer and linked data suppport.

Deployed GeoNode version update

Preconditions

A version of GeoNode and related extensions has been deployed in a production context.
A new version of GeoNode has been released

Postconditions

Production GeoNode updated to new version with no loss of content
Any testing environments updated.
Rollback option provided in case of failure.
Failures and warnings logged.
Optional site registration (denoting usage of version) updated?

Description

Geonode site owner decides to update to a newer version of Geonode.
(In all likelihood they will run and test update on a staging environment before committing to deployment upgrade)
They initiate an automated check to see if the plug-in extensions they require are available for the new version.
If necessary they initiate testing and upgrade of extensions against new version.
A backup of the site is created.
Temporary site maintenance messages are deployed.
site is updated
installed plugins are updated
automated tests are run
If failures user offered option to ignore or cancel, with rollback.
user initiates further testing as required

Mapstory (or other extension) deployment to GeoNode environment

Preconditions

Geonode deployed with data.
Module version published and tested as compatible with version

Postconditions

The extension module is deployed, tested and confirmed working in deployment

Description

GeoNode environment owner decides to download and configure a module to provide extended functionality to the deployed environment. Via administration interface selects modules to install. Dependencies on other modules and underlying libraries are checked against installed versions. If compatible site owner initiates upgrade Backups performed Modules installed and automated tests reported (may involve configuration) User performs additional configurations, non-automated tests and familiarity exercises.

GeoNode Extension Module Update

Preconditions

An extension module for GeoNode has been released against a version of GeoNode.
A new version of GeoNode has been released
Update instructions for developers migrating from previous version to new versions of Geonode code base published

Postconditions

The extension module is tested and confirmed working against the new release
If the new version is not compatible with the previous release the old version is still accessible
Release map showing compatible versions updated

Description

Developer examines the key changes in the GeoNode version to identify likely effects on extension module.

Developer performs the prescribed update migration for GeoNode codebase and runs the tests provided to make sure the base component is functioning in development deployment. Implements changes in extension module and runs extension modules tests. Publishes extension module update. System performs tests and updates release version details.