Re: [Project Clearwater] Error in Manual Installation of Ellis

Looks like your computer name (or hostname) is ‘ellis’ This will conflict with the installation of `ellis` package. Change your computer name to ellis-1 or otherelse will do the trick. From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Hrishikesh Karanjikar

Re: [Project Clearwater] Is the clearwater-stress test available for version of repo 84?

Hi Seb. Thank for you advice, I would like to try option 2 and 3, May I ask you where to find the older stress scripts? And another problem is the step of bulking provision number of subscribers.

[Project Clearwater] Is the clearwater-stress test available for version of repo 84?

Dear developers, I would like to do the stress test for my deployment followed by http://clearwater.readthedocs.io/en/stable/Clearwater_stress_testing.html However, my current Clearwater deployment is based on repo84, And I found something quite different

Re: [Project Clearwater] Regarding sprout-node installation time.

Hi Seb, I’m interesting in this topic too, I would like to know what’s the meaning of “clean” sprout you said before. Is It means I should install sprout packages without configure local_config, and take the snapshot for this VM? Would you give us more detail step to create a clean sprout node

Re: [Project Clearwater] Clearwater integration into SDN network

Hi, Abraham Although I'm not the developer of Clearwater, I think Clearwater is not integrated with any SDN controller now. If you want to make your Clearwater system to communicate to SDN controller. You can use rest-ful api, if your SDN controller supports so. But in this way, you have to

[Project Clearwater] How to tell the maximum sip-call from SIP stress test result.

Dear All, I am using the clearwater-sip-stress to benchmark my clearwater deployment. But I have trouble to figure out what’s the maximum sip-call my deployment can bear. Is there any value shows in sip.1.out that can tell me this information? Thank you. Jace. --

Re: [Project Clearwater] etcd_process execution failed on each node.

Hi Ellie, Thanks for your reply, Recently I reinstalled my deployment with newest version Porygon. (Origionaly Onix). But the issues still appears. Even I tried reboot the nodes and use monit restart . · Can you send me the clearwater-etcd.log? My clearwater-etcd.log (on node

[Project Clearwater] How to reconfigure the cluster members?

Dear All, I recently changed the IP of VMs (use manual installation if Clearwater) I change the etcd_cluster in /etc/clearwater/local_config and reboot the node so that etc_process will get the new config. But seems like it is still gets the old config as the clearwater-etcdctl cluster-health

Re: [Project Clearwater] etcd_process execution failed on each node.

Hi Richard, I think my problem here is not the issue you mentioned in last mail. As my clearwater-etcd.log is quite different with that one. And my clearwater version is already the latest Onix, release 108. PS: I followed the manual

[Project Clearwater] etcd_process execution failed on each node.

Dear All, Recently I found out my 6 VMs of each node have trouble of executing etcd_process I think I did the config file right, because at first their etcd_process was running well and the “clearwater-etcdctl cluster health” shows all healthly. But somehow they suddenly I tried “monit restart

[Project Clearwater] How to get the source code of clearwater-auto-config-docker?

Hi community, I would like to know the process of Clearwater-docker deployment, especially the config step of each containers. I think the package “clearwater-auto-config-docker” does the job, so how do I get the source code of this package? BTW: I failed with the command “apt-get source

[Project Clearwater] Is clearwater-docker supports elastic scaling?

Hi community, I am interested in if Clearwater-docker supports elastic scaling or not. First I made a call based on the minimal distributed Clearwater-docker. Then I added a new sprout container named sprout_2. Finally I deleted the original sprout node. Until now the communication was still OK.