Hi Olivier, Restarting clearwater-infrastructure shouldn't ever rewrite the /etc/clearwater/config file. When you reboot your machine though, the clearwater-auto-config-generic/aws.init.d scripts are run as well. This does rewrite the /etc/clearwater/config file as you've found. If this is a problem for you, you can remove the clearwater-auto-config-generic/aws packages, but they will need to be reinstalled if the IP address of your machine changes.
Ellie -----Original Message----- From: DURECU, OLIVIER (OLIVIER) [mailto:[email protected]] Sent: 14 May 2014 16:19 To: Eleanor Merry; [email protected] Subject: RE: "Elite" release For my first question, it was indeed after a reboot Olivier -----Message d'origine----- De : Eleanor Merry [mailto:[email protected]] Envoyé : mercredi 14 mai 2014 16:44 À : DURECU, OLIVIER (OLIVIER); [email protected] Objet : RE: "Elite" release Hi Olivier, On your first question: What command did you run when you restarted Clearwater-Infrastructure? Did you reboot your machine? On your second question: Yes, Homestead now reads the field hss_hostname directly from /etc/clearwater/config and creates the connection on start up. You can alternatively now set an hss_realm in /etc/clearwater/config which homestead will try to resolve using NAPTR and SRV resolution in order to make connections to multiple HSSs. Ellie -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of DURECU, OLIVIER (OLIVIER) Sent: 12 May 2014 16:35 To: Graeme Robertson; [email protected] Subject: Re: [Clearwater] "Elite" release Hi all, Updating to Elite, 2 questions raised: - it seems that the restart of Clearwater-infrastructure changes my "/etc/clearwater/config" file. sprout_hostname value (that contains the name sprout.doamin.com) is replaced by the IP address. Why does this happen ? This is not specific to Elite release but I discovered it at this occasion :-) - homestead.conf no more contains ConnectPeer parameter for external HSS connection. Does this mean that HomeStead reads the Hss external name directly from "/etc/clearwater/config" file? Thanks for your help Olivier DURECU Bell Labs / IP Platform Research Villarceaux Center Tel: +33(0) 160402759 GSM: +33(0) 683776482 -----Message d'origine----- De : [email protected] [mailto:[email protected]] De la part de Graeme Robertson Envoyé : jeudi 1 mai 2014 13:45 À : [email protected] Objet : [Clearwater] "Elite" release The release for the sprint "Elite" has now been cut. This release contains the following new features and bug fixes: New features: * Homestead and ralf support multiple diameter connections to a realm, and full NAPTR/SRV resolution of that realm. * We now support RFC 4320 Bug fixes: * Chronos crashes do not trigger a diags dump (https://github.com/Metaswitch/chronos/issues/29) * Trunking support mandates TCP (https://github.com/Metaswitch/sprout/issues/493) * NOTIFY for reg-event does not contain mandatory "Event" header field (https://github.com/Metaswitch/sprout/issues/490) * Timer handler should always acquire timers with the same ID (https://github.com/Metaswitch/chronos/issues/7) * Timer wheel moves into the future too quickly (https://github.com/Metaswitch/chronos/issues/8) * Crash in pj_atomic_inc_and_get called from ConnectionPool::create_connection (https://github.com/Metaswitch/sprout/issues/11) * Development.md contains incorrect instructions for running sprout (https://github.com/Metaswitch/sprout/issues/450) * Ralf returns 404 Not Found when call-id contains one or more "/" characters (https://github.com/Metaswitch/ralf/issues/34) * sprout doesn't encode icid-value correctly in P-Charging-Vector (https://github.com/Metaswitch/sprout/issues/510) * chef should set sensible S-CSCF config by default (https://github.com/Metaswitch/chef/issues/106) * Bono and Sprout do not send INTERIM or STOP ACRs to Ralf (https://github.com/Metaswitch/sprout/issues/513) * Ralf crashes when receiving a START/EVENT without a peers field (https://github.com/Metaswitch/ralf/issues/37) * Ralf does not forward billing records received from Sprout to the CDF (https://github.com/Metaswitch/ralf/issues/36) * Hostname in record-route and service-route headers prevents load balancing using SRV records (https://github.com/Metaswitch/sprout/issues/458) * After a traffic run on a simplex Clearwater Core system, Chronos sometimes crashes (https://github.com/Metaswitch/chronos/issues/19) * Sprout crashes when running traffic at a rate of 10 cps or higher (https://github.com/Metaswitch/sprout/issues/509) To upgrade to this release, simply run "sudo clearwater-upgrade" on each node. If you have created your Clearwater deployment through the Chef automation system, you should also follow our "Updating the Chef server" instructions at https://github.com/Metaswitch/chef#updating-the-chef-server and then run "sudo chef-client" on each node. The BGCF configuration format has changed in this release, so before upgrade you'll need to change each entry in the 'route' field in /etc/clearwater/bgcf.json on your sprout nodes to a SIP URI. Restarting sprout during upgrade will pick this change up. This has changed so that you can define which transport to use when routing to a SIP trunk. To configure an HSS realm for homestead, you'll need to add an hss_realm field to /etc/clearwater/config and set it to the HSS realm. The old hss_hostname field is optional. To configure a billing realm for ralf, you'll need to add a billing_realm field to /etc/Clearwater/config and set it to the billing realm. In both cases, you'll then need to run "sudo service Clearwater-infrastructure restart" and "sudo monit restart homestead/ralf" for the changes to take effect. Homestead and Ralf will then attempt to set up multiple (2 by default) diameter connections. If you don't want anything to change with your current diameter connections, you don't need to do anything here. 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 _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
