Infrastructure

Every dataone debian package will need to be pinned (or otherwise held back from upgrading) in debian. The version numbers may be found in the Packages.gz file prepared during the hudson build process.

For development and sandbox, download the http://dev-testing.dataone.org/ubuntu-unstable/dists/lucid/universe/binary-amd64/Packages.gz file, open it and read in the latest release versions. These versions should be used for pinning the packages.

For stage2, the endpoint is http://dev-testing.dataone.org/ubuntu-stage/dists/lucid/universe/binary-amd64/Packages.gz

For stage and prod, the endpoint is http://dev-testing.dataone.org/ubuntu-stable/dists/lucid/universe/binary-amd64/Packages.gz

Please note, that we have a hierarchy of dependencies, such that any top-level playbook should run upgrades in an order consistent with the different levels:

Top level (no other d1 dependencies)
dataone-solr
dataone-jetty
dataone-zookeeper
dataone-cn-version-tool
dataone-cn-os-core

Second Tier ( has top-level dependencies)
dataone-solr-jetty -> dataone-solr, dataone-jetty
dataone-cn-metacat -> dataone-cn-version-tool, dataone-cn-os-core
dataone-cn-portal -> dataone-cn-version-tool, dataone-cn-os-core
dataone-cn-monitor -> dataone-cn-version-tool, dataone-cn-os-core
dataone-cn-rest-service -> dataone-cn-version-tool, dataone-cn-os-core

Third Tier ( has Second-Tier dependencies)
dataone-cn-solr -> dataone-cn-version-tool, dataone-cn-os-core, dataone-cn-metacat
dataone-cn-audit-index -> dataone-cn-os-core, dataone-solr-jetty, dataone-zookeeper

Fourth Tier ( has Third-Tier dependencies)
dataone-cn-index -> dataone-cn-version-tool, dataone-cn-os-core, dataone-cn-metacat, dataone-cn-solr
dataone-cn-processdaemon -> dataone-cn-version-tool, dataone-cn-os-core, dataone-cn-metacat, dataone-cn-solr
dataone-mercury -> dataone-cn-version-tool, dataone-cn-solr