logo

Sprint Ulmo release note

The release for Project Clearwater sprint “Ulmo” has been cut. The code for this release has been tagged as release-129 in GitHub.

This release includes a couple of substantial pieces of work:

Improved Configuration Management

We’ve altered the workflow for making changes to Clearwater Settings – this will help avoid window conditions where the live configuration on an individual node is out of sync with the rest of the deployment, or if multiple updates are attempted simulatenously.

See http://clearwater.readthedocs.io/en/stable/Modifying_Clearwater_settings.html for more details

Users wishing to make changes to shared_config across their deployment should now:

  • Run `cw-config download shared_config` to get a copy of the latest shared_config file
  • Make changes to the downloaded copy
  • Run `cw-config upload shared_config` when the configuration is ready to be uploaded.

Users wishing to make changes to the static DNS overrides across their deployment should now:

  • Run `cw-config download dns_json` to get a copy of the latest dns.json file.
  • Make changes to the downloaded copy
  • Run `cw-config upload dns_json` when the configuration is ready to be uploaded.

Users wishing to make changes to a JSON file across their Sprout nodes should now:

  • On one of their Sprout nodes run `cw-config download {scscf|bcgf|enum|rph}_json` to get a copy of the latest JSON file
  • Make changes to the downloaded copy
  • Run `cw-config upload {scscf|bcgf|enum|rph}_json` when the configuration is ready to be uploaded.

Users wishing to make changes to an XML file across their Sprout nodes should now:

  • On one of their Sprout nodes run `cw-config download {shared|fallback}_ifcs` to get a copy of the lastest XML file
  • Make changes to the downloaded copy
  • Run `cw-config upload {shared|fallback}_ifcs` when the configuration is ready to be uploaded.

Astaire / Rogers

We’ve split apart the proxying function from Astaire into a new component, Rogers.

This was done to avoid the memcached proxying, replication and topology hiding functionality provided by Rogers from being impacted by resynchronization operations performed by Astaire.

Vellum nodes will now run Rogers in addition to Astaire. This should automatically be installed on upgrade.

Resource Priority Headers

We’ve added support for Resource Priority Headers. If a Resource Priority Header is present, and Clearwater is configured to honour it, requests with that resource priority will be prioritised when Clearwater is overloaded.

See http://clearwater.readthedocs.io/en/stable/Clearwater_Configuration_Options_Reference.html#rph-config for more detail on configuring RPH values.

SIP Graylisting and Lazy Targeting

This release improves SIP target selection to incorporate graylisting and lazy targeting, in a similar manner to the existing support for HTTP documented at http://www.projectclearwater.org/http-graylisting/

This release also includes a substantial number of bug fixes which improve Clearwater’s performance at load, overload and with latency during call flows.

To upgrade 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.

Richard Whitehouse is a Software Engineer at Metaswitch Networks. Prior to Project Clearwater, he worked on Metaswitch’s Unified Communication products. When not working, he enjoys travelling, food, drink and computer games.

Leave a Reply

*

captcha *