Infrastructure

For production 1.0.4 release:

Packages:
d1_portal v1.0.2
d1_portal_servlet v1.0.2
d1_mercury_common v1.0.3
d1_mercury_ui v1.0.4
d1_identity_manager v1.0.2
d1_cn_common v1.0.2
d1_cn_approve_node v1.0.2
d1_cn_index_common v1.0.2
d1_cn_index_generator v1.0.2
d1_cn_index_processor v1.0.2
d1_cn_noderegistry v1.0.2
d1_cn_service v1.0.3
d1_log_aggregation v1.0.2
d1_synchronization v1.0.2
d1_solr_extensions v1.0.3
d1_process_daemon v1.0.3

Products to be Released:

dataone-cn-index v1.0.3
dataone-cn-metacat v2.0.4
dataone-cn-os-core v1.0.3
dataone-cn-portal v1.0.3
dataone-cn-processdaemon v1.0.3
dataone-cn-rest-service v1.0.3
dataone-cn-solr v1.0.3
dataone-mercury v1.0.4

Staging:

1) snapshot UNM and UCSB -DONE
2) bring ORC back to life - DONE
3) build out ORC, with latest stable software packages - IGNORE
4) snapshot ORC -IGNORE
5) upgrade Java, (UMN/UCSB DONE)
6) Update /etc/apt/sources.list to pull from stage channel, (UMN/UCSB DONE)
7) upgrade machines, (UMN/UCSB DONE)
8) reconfigure metacat, (UMN/UCSB DONE)
9) test branches; if failures modify branches and goto 7
10) build stable channel
11) upgrade Java
12) test Release upgrade process

Production
1) Upgrade Ubuntu Packages
a) remove indexing and processing daemons from runtime level
b) if stable packages have already been released into stable channel, then comment out stable channel
c) take machine out of RR
d) upgrade ubuntu packages
e) reboot
f) put machine back in RR
g) only UCSB restart indexing and d1-processing, on ORC and UNM only restart indexing
2) Update Machines by add in new Java packages on each machine, taking each out of RR in turn
3) unComment dataone stable channel if previously removed (see 1.b)
4) Update Machines by adding in 1.0.4 release, following upgrade procedure http://epad.dataone.org/ProductionRolloutProcedure
5) reconfigure metacat