The release for Project Clearwater sprint "Farfetch'd" has been cut. The code 
for this release is tagged as release-99 in Github.

Project Clearwater supports I-CSCF, but this function isn't available by 
default - users need to actively enable it on their system. However, an IMS 
deployment should have an I-CSCF; we've therefore decided that our default 
configuration is the wrong way round. From this release, I-CSCF is now enabled 
by default.

If you already use I-CSCF, then this change won't affect you.

If you don't already use I-CSCF, we recommend you switch over to using one. 
You'll need to add some configuration:

*         Before upgrading, add DNS records for your I-CSCF.

*         You will need at least an A/AAAA record, e.g.:

o   icscf.sprout.<your dns zone>` (A and/or AAAA) - cluster record for sprout, 
resolving to all sprout nodes that provide I-CSCF function.

*         You may also wish to add NAPTR/SRV records, e.g.

o   _sip._tcp.icscf.sprout. your dns zone>` (SRV) - cluster SRV record for 
sprout, resolving to port 5052 on each of the per-node records

o   icscf.sprout.<your dns zone>` (NAPTR) - service `SIP+D2T` maps to 
`_sip._tcp.icscf.sprout.

*         Then do the upgrade as normal (details at the end of this email).

If you don't use I-CSCF, and really want to continue not using I-CSCF, you'll 
need to change some different configuration:

*         Before upgrading, work out your S-CSCF URI. This is either the value 
of scscf_uri if you've set it in your /etc/clearwater/shared_config file (note 
that this isn't the default setting), or it's 
"scscf.<sprout_domain>:5054;transport=tcp"

*         Then on one node in /etc/clearwater/shared_config set:

o   icscf=0

o   upstream_hostname=<your S-CSCF uri>

o   upstream_port=5054

*         Then upload this configuration to all nodes by running 
/usr/share/clearwater/clearwater-config-manager/scripts/upload_shared_config, 
and wait for all nodes to pick up the new configuration (you can use 
/usr/share/clearwater/clearwater-queue-manager/scripts/check_restart_queue_state
 for this).

*         Then do the upgrade as normal (details at the end of this email).

This release includes the following bug fixes:

*         CHECK_PJ_TRANSPORT_THREAD crashes 
(https://github.com/Metaswitch/sprout/issues/1442)

*         SPROUT_REMOTE_VBUCKET_ERROR doesn't clear 
(https://github.com/Metaswitch/sprout/issues/1422)

*         Sprout does not fully recover from a brief overload condition. 
(https://github.com/Metaswitch/sprout/issues/1234)

*         ENT log not issued when sas_server not set 
(https://github.com/Metaswitch/sprout/issues/1226)

*         Sprout requests to Homestead can take over a second 
(https://github.com/Metaswitch/sprout/issues/1090)

*         Message loop when no routes found 
(https://github.com/Metaswitch/sprout/issues/870)

*         Load Monitor should SAS log and trace more detail 
(https://github.com/Metaswitch/cpp-common/issues/507)

*         Python-common doesn't have complete code coverage 
(https://github.com/Metaswitch/python-common/issues/50)

*         poll-tcp (and scripts that call it) take a minimum of 2 seconds 
(https://github.com/Metaswitch/clearwater-infrastructure/issues/273)

*         The alarm agent doesn't have a log cleanup script 
(https://github.com/Metaswitch/clearwater-snmp-handlers/issues/145)

*         MVS believes there is always an unknown alarm raised. 
(https://github.com/Metaswitch/clearwater-snmp-handlers/issues/144)

*         Juju hook failed: "install" for  unmet dependencies for - 
libboost-filesystem1.54.0 
(https://github.com/Metaswitch/clearwater-juju/issues/42)

*         GR system has persistent TOO_LONG_CLUSTERING alarm 
(https://github.com/Metaswitch/clearwater-etcd/issues/289)

*         AlarmsTest causes intermittent crashes 
(https://github.com/Metaswitch/cpp-common-test/issues/16)

*         Logging does not work 
(https://github.com/Metaswitch/libnss-ato/issues/5)


For upgrading to this release, follow the instructions at 
http://docs.projectclearwater.org/en/stable/Upgrading_a_Clearwater_deployment.html.
 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.

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

Reply via email to