The release for sprint "Anna Karenina" has been cut.  The code for this release 
is tagged as release-68 in github.



This release we have moved all our documentation from the existing Wiki over to 
http://clearwater.readthedocs.org/en/latest/index.html. The Wiki is now 
deprecated. The most exciting thing about this change is that the new Read the 
Docs platform has search capabilities!



We've also been doing the following development work.



*         Speeding up scale up and scale down.  We've removed the requirement 
to wait for the re-registration period in the middle of each scaling operation. 
 Updated instruction for resizing your deployment with Chef can be found in 
https://clearwater.readthedocs.org/en/latest/Clearwater_Elastic_Scaling/index.html.

*         Improving high level diagnostics when running Project Clearwater 
alongside a Metaswitch Service Assurance Server.

*         Adding support for multiple DNS and ENUM servers. See 
http://clearwater.readthedocs.org/en/latest/Clearwater_DNS_Usage/index.html#resiliency
 and 
http://clearwater.readthedocs.org/en/latest/ENUM/index.html#enum-and-sprout for 
more details.

*         Making enhancements to our Monit scripts in order to improve the 
stability of Project Clearwater.

*         Doing some work towards supporting Project Clearwater on Ubuntu 14.04.



This release also includes the following fixes.



*         Deregistration requests that have an invalid URI cause Sprout to 
crash (https://github.com/Metaswitch/sprout/issues/966)

*         Sprout always abort-restarts 
(https://github.com/Metaswitch/sprout/issues/960)

*         poll_sprout is too aggressive after sprout failure 
(https://github.com/Metaswitch/sprout/issues/956)

*         Bad ENUM rules crash BGCF sproutlet 
(https://github.com/Metaswitch/sprout/issues/951)

*         Sprout RegStore deserialization isn't very robust 
(https://github.com/Metaswitch/sprout/issues/922)

*         Sprout generates sas http events during user registrations but not 
visible when clicking View (https://github.com/Metaswitch/sprout/issues/918)

*         Interactive options are out of date again 
(https://github.com/Metaswitch/sprout/issues/851)

*         P-Charging-Vector icid-value parameters are rejected unnecessarily 
(https://github.com/Metaswitch/sprout/issues/486)

*         Homestead restart when shutdown is slow causes subsequent Monit 
failures (https://github.com/Metaswitch/homestead/issues/149)

*         DnsCachedResolver deadlocks 
(https://github.com/Metaswitch/cpp-common/issues/253)

*         HttpConnection does not retry if a target server does not accept a 
connection.  (https://github.com/Metaswitch/cpp-common/issues/200)

*         Failure to connect to Cassandra has an unhelpful error message 
(https://github.com/Metaswitch/cpp-common/issues/186)

*         Log spam (and bug) when Diameter connection fails 
(https://github.com/Metaswitch/cpp-common/issues/107)

*         Monit monitoring has been disabled 
(https://github.com/Metaswitch/chronos/issues/97)

*         Exceptions in the homer logs when trying to change a subscriber 
config (https://github.com/Metaswitch/crest/issues/84)

*         Ellis development docs are out of date 
(https://github.com/Metaswitch/ellis/issues/97)

*         Chef can't spin up OpenIMSCore HSS 
(https://github.com/Metaswitch/chef/issues/156)

*         Chef doesn't spin up deployments containing ralf 
(https://github.com/Metaswitch/chef/issues/151)

*         monit restarts Cassandra too aggressively 
(https://github.com/Metaswitch/chef/issues/28)

*         poll_cassandra polls the node's local IP address rather than the 
Cassandra hostname 
(https://github.com/Metaswitch/clearwater-cassandra/issues/22)

*         Cassandra Thrift port is no longer monitored 
(https://github.com/Metaswitch/clearwater-cassandra/issues/19)

*         Cassandra locks up due to running out of heap space 
(https://github.com/Metaswitch/clearwater-cassandra/issues/8)

*         Monit causes install to fail if the hostname is the same as a process 
(https://github.com/Metaswitch/clearwater-infrastructure/issues/139)

*         clearwater-infrastructure.init.d status command is confusing, and 
sometimes fails 
(https://github.com/Metaswitch/clearwater-infrastructure/issues/105)

*         Clearwater diags collection causes repeated restarts under load 
(https://github.com/Metaswitch/clearwater-infrastructure/issues/96)

*         snmpd crashes when no statistics available over 0MQ 
(https://github.com/Metaswitch/clearwater-snmp-handlers/issues/49)

*         Astaire scalar statistic OIDs should end in .0 
(https://github.com/Metaswitch/clearwater-snmp-handlers/issues/48)

*         UTs do not have 100% code coverage 
(https://github.com/Metaswitch/clearwater-snmp-handlers/issues/43)

*         Jenkins builds do not run the UTs. 
(https://github.com/Metaswitch/clearwater-snmp-handlers/issues/42)

*         Gemini is not sufficiently explicit about sending to native devices 
(https://github.com/Metaswitch/gemini/issues/20)

*         Gemini uses "+sip.phone" to indicate running on the same device as 
its twin (https://github.com/Metaswitch/gemini/issues/15)

*         Gemini could fork twice to the same contact 
(https://github.com/Metaswitch/gemini/issues/14)

*         Nginx doesn't recover if slaves processes not killed 
(https://github.com/Metaswitch/memento/issues/32)

*         SAS::term() takes 30 seconds if SAS is unreachable 
(https://github.com/Metaswitch/sas-client/issues/37)



For upgrading to this release, follow the instructions at 
http://clearwater.readthedocs.org/en/latest/Upgrading_a_Clearwater_deployment/index.html.
 Note that Project Clearwater recently changed the format of data stored in 
memcached, from a custom binary format to JSON. More detail and background can 
be found on the Project Clearwater blog - 
http://www.projectclearwater.org/changing-the-format-of-data-in-memcached. 
Seamless upgrade is only possible if you are upgrading from the Zelda release 
(which is tagged as release-67 in github). Upgrades from earlier releases will 
result in loss of service (loss of active registrations, and disruption to Rf 
billing on active calls).



If you are deploying an all-in-one node, the standard image 
(http://vm-images.cw-ngv.com/cw-aio.ova) has been updated for this release.



Thanks,
Graeme

_______________________________________________
Clearwater mailing list
[email protected]
http://lists.projectclearwater.org/listinfo/clearwater

Reply via email to