Notes for Sprint-2012.44-Block.6.2
----------------------------------

Rob
---
Roger
-----
Chris B.
--------
Bruce
-----
Skye
----
Ben
---
Robert
------
Matt
----
Chris
-----
Dave
----

20121116
- working on docs for Bill and Rebecca
- Still wrapping up mutation doc
- starting on new ssl debugging / diagnostic doc
- wrote a datagram to websocket gateway for realtime browser notifications (integrated with statsd for long term stats collection)
- Working on formalizing member node checklist
- Indexing etherpad docs to a SOLR instance

20121109 
- finalizing details on mutbility doc. General approach requires adding an "alternate identifier", most likely to system metadata. The AID would refer to the obsolescence tree for an object family. May be able to get away with only one new method, which would be to resolve an AID -> list of PIDs

- Installing instance of GMN at KU. will be serving up spatial data layers (geotiff), about 200 GB or so.

- Need to setup cn-sandbox-2.test.dataone.org as a single CN environment for MN testing / demo purposes

- Catching up after storm outages etc
- Writing up mutability proposal
  - working on mutability documentation
  2012107 - Still working on mutation docs. Path is clearer, but likely to touch system metadata
  
- Docs for Bill and Rebecca
- Evaluating issues with hazelcast (code review), especially potential latency concerns. Troubling quote (https://groups.google.com/forum/?fromgroups=#!topic/hazelcast/opOY3gC3CUo) from Fuad (one of the Hazelcast bosses):
  "By the way is not a good idea to have a cluster across WAN. Hazelcast is best suited to run in a datacenter. At least across the datacenters where there is low latency"

  WAN replication is handled by a different mechanism: http://www.hazelcast.com/docs/1.9.4/manual/multi_html/ch09.html

Also relevant:
  https://groups.google.com/forum/?fromgroups=#!topic/hazelcast/uwHbifnPHOE
  http://hazelcast.googlecode.com/svn/trunk/hazelcast/src/main/java/com/hazelcast/impl/wan/WanNoDelayReplication.java
  
Issue 3375.
  Looked at 2.4 release and outstanding bugs. There are outstanding defects especially client connection issue. maybe fixed in 2.4.1. They have a tag for 2.4.1.