updated from ci periodically (right now * */3 * * *)
commited/tagged/pushed to "cloud" git repo at sf.net if there is a change (can monitor commit logs) to be notified of a change
tag has build number and job name

Image maintenance

Upgrades for new Mifos versions

If a new point release of Mifos comes out (e.g. 2.1.9):

modify the AMI generation script for that Mifos release to use the new point release version. (We would modify imaging/mifos_2_1_bi_1_2.sh to get the 2.1.x Mifos version along with BI 1.2).
update the "mifosversion" variable in the script to be 2.1.9 (commit and push)
rerun the hudson job "cloud-mifos_2_1-bi_1_2-image" to create a new AMI with the updated Mifos war (the name of the new AMI will be in the console log output on of the hudson job).
follow the groovy script usage below using the new AMI generated in the previous step.

Statefiles with lists of latest packages are created periodically (see above).
An administrator must keep track of security releases in upstream Ubuntu packages.
A groovy script is available to move a customer from one image to the next (it could be an upgrade or just a security update), this script should only be used if the mfi deployment for the environment already exists, volumes created, elastic ips associated etc. It can be invoked like so

...