The release for sprint "Birdsong" has been cut.  The code for this release is 
tagged as release-69 in github.

This release contains the following new features.

•       Speeding up scale down.  In the “Anna Karenina” release we announced a 
new quick method for scaling a deployment up or down (see 
https://clearwater.readthedocs.org/en/latest/Clearwater_Elastic_Scaling/index.html
 for details). This has the restriction that scaling down using the quick 
method can cause timers to be lost. In this release we have started the Chronos 
work to make scaling down preserve all timers. Soon all scaling operations will 
be quick!
•       We added the ability to easily spin up a deployment on Openstack using 
Openstack Heat (https://wiki.openstack.org/wiki/Heat). Instructions for this 
can be found in https://github.com/Metaswitch/clearwater-heat.

This release also includes the following fixes.

•       Bono uses `billing_cdf` rather than `cdf_identity` 
(https://github.com/Metaswitch/sprout/issues/984)
•       Misleading SAS log when wrong password used 
(https://github.com/Metaswitch/sprout/issues/983)
•       Sprout stuck in infinite loop inside registrar 
(https://github.com/Metaswitch/sprout/issues/977)
•       sprout uses Perl-Compatible regular expressions for ENUM 
(https://github.com/Metaswitch/sprout/issues/950)
•       Sprout rejects ENUM servers that are hostnames 
(https://github.com/Metaswitch/sprout/issues/689)
•       SAS logging of AS chains is probably wrong 
(https://github.com/Metaswitch/sprout/issues/127)
•       python-common logging is inconsistent with cpp-common 
(https://github.com/Metaswitch/python-common/issues/12)

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,
Alex.
_______________________________________________
Clearwater mailing list
[email protected]
http://lists.projectclearwater.org/listinfo/clearwater

Reply via email to