Re: [Project Clearwater] Issues with clearwater-docker homestead and homestead-prov under Kubernetes

in some PRs Because you've got a fairly long list of things below, I've interspersed comments and answers as best I can. Hope this helps :) Cheers, Adam From: Davis, Matthew [mailto:matthew.davi...@team.telstra.com] Sent: 14 August 2018 05:41 To: Adam Lindley mailto:adam.lind...@metaswitch.com

Re: [Project Clearwater] Issues with clearwater-docker homestead and homestead-prov under Kubernetes

ret turn_workaround=secret ellis_api_key=secret ellis_cookie_key=secret From: Davis, Matthew [mailto:matthew.davi...@team.telstra.com] Sent: 04 June 2018 09:24 To: Adam Lindley ; clearwater@lists.projectclearwater.org Subject: RE: [Project Clearwater] Issues with clearwater-docker homestead and homes

Re: [Project Clearwater] Issues with clearwater-docker homestead and homestead-prov under Kubernetes

that is not needed in these containers. You can safely ignore this output. Good luck, and let us know where you get with debugging. Cheers, Adam From: Davis, Matthew [mailto:matthew.davi...@team.telstra.com] Sent: 30 May 2018 08:27 To: Adam Lindley ; clearwater@lists.projectclearwater.org Subject: RE: [Projec

Re: [Project Clearwater] Issues with clearwater-docker homestead and homestead-prov under Kubernetes

) Cheers, Adam From: Davis, Matthew [mailto:matthew.davi...@team.telstra.com] Sent: 25 May 2018 08:30 To: Adam Lindley <adam.lind...@metaswitch.com>; clearwater@lists.projectclearwater.org Subject: RE: [Project Clearwater] Issues with clearwater-docker homestead and homestead-prov under Kube

Re: [Project Clearwater] Issues with clearwater-docker homestead and homestead-prov under Kubernetes

Hi Matthew, I've had a look into your issues deploying under kubernetes, and think I've narrowed down the search a good amount. Details below. First though I'll take a run through the smaller questions you've raised below, as I think we can knock some of them off fairly quickly. Other

Re: [Project Clearwater] Unable to contact the etcd cluster

Hi Sunil, I’m afraid the steps you’ve taken are not supported in Project Clearwater deployments. Both changing the ‘local_ip’ of a node, and removing nodes just by deleting the VMs. On the first point, you need to be able to give your VMs permanent static IP addresses. On the second, by

Re: [Project Clearwater] SIP registeration cw-aio virtualbox

Hi Jaber, I'd recommend taking a look at our documentation on setting this up, over at http://clearwater.readthedocs.io/en/stable/Making_your_first_call.html If you've followed those steps, you should be able to make a first pass at diagnosing your problems with some help from

Re: [Project Clearwater] Issue with Clearwater deployment on Stackube

Hi Chirag, I'm afraid I can't help that much from just that log snippet, without knowing what containers you're seeing them in, or other information/logs. I've taken a look at some of the logs on one of our test set ups, and find a number of instances of the "CRIT Supervisor running as root (no

Re: [Project Clearwater] 502 Bad Gateway and other errors while running live tests

ch ONAP's heat templates are based, may be by changing this repo URL? I will have a look at current heat template on Clearwater GitHub but I think those won't be ONAP compatible. From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Adam Lindley Sent: Tuesday, De

Re: [Project Clearwater] 502 Bad Gateway and other errors while running live tests

...@lists.projectclearwater.org] On Behalf Of Adam Lindley Sent: 12 December 2017 16:41 To: clearwater@lists.projectclearwater.org<mailto:clearwater@lists.projectclearwater.org> Subject: Re: [Project Clearwater] 502 Bad Gateway and other errors while running live tests Hi Kedar, I've ju

Re: [Project Clearwater] 502 Bad Gateway and other errors while running live tests

Hi Kedar, I've just had a look around for the templates on the ONAP wiki; I wasn't aware they had their own copies of them. I found https://wiki.onap.org/display/DW/Clearwater+vIMS+Onboarding+and+Instantiation . Is this what you've been working from? When deploying with the templates, have

Re: [Project Clearwater] Making calls: cannot get two-way media

Hey Alice, I’m not sure what’s causing the issue from just the wireshark trace, though I think the record-route header `` looks unusual. Can you enable debug logging, and then get the bono and sprout debug logs from the node when you try to run the

Re: [Project Clearwater] Installation of ClearWater vIMS via OSM/OpenStack

From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Adam Lindley Sent: 02 November 2017 12:05 To: clearwater@lists.projectclearwater.org Subject: Re: [Project Clearwater] Installation of ClearWater vIMS via OSM/OpenStack Hi Joe, Sorry we’re so late to respond here

Re: [Project Clearwater] Installation of ClearWater vIMS via OSM/OpenStack

Hi Joe, Sorry we’re so late to respond here. We haven’t done anything using OSM here ourselves; though it does look interesting. We did see a demo of the capabilities of OpenMano at MWC 2016 though, and you should be able to see a write up of this at

Re: [Project Clearwater] RFC 2617 - nextnonce parameter support (3.2.3)

Hi Trey, Project Clearwater currently does not support the nextnonce parameter in Authentication-Info Headers. Though of course there’s nothing stopping you adding support for it yourself; let us know if you are working on this! Cheers, Adam From: Clearwater

Re: [Project Clearwater] Installation from source

Hi Abraham, In a way, it is just as simple as building all of the code, and running a manual install. However, as we do have a fair number of different components, you will need to make sure you've built all of the different packages you need. We have basic installation documentation at

Re: [Project Clearwater] only homestead_process and homestead-prov_process status is not running

Hi Devendra, Have you taken a look in the process logs? Our processes will write logs under /var/log/, generally in a directory under their process name, such as /var/log/homestead/homestead_. These should give you a much clearer idea of what is causing your processes to fail. If that doesn’t

Re: [Project Clearwater] Clearwater training dataset

Hi Emerson, I don’t think we are going to be able to help provide anything here; Clearwater does not get involved with the media flows in a deployment, only the SIP signalling. If you are interested in more media control, Metaswitch does have a fully-fledged P-CSCF product, Perimeta, which can

Re: [Project Clearwater] Manual installation -Help

Hi Abraham, >From the looks of things you have a number of issues with your installation. >In particular, as you've highlighted, with Bono, but a number of other >processes are being reported as failing in the `monit summary` checks. The >check on bono is reporting that there is no

Re: [Project Clearwater] Clearwater training dataset

Hi Emerson, Can you provide some more information on the sort of data you’re after here? With an idea of the sort of behaviours you are looking to train for, someone on here may be able to provide what you’re after, or we can point you at how to run your own Project Clearwater deployment to

Re: [Project Clearwater] etcd cluster is unavailable or misconfigured

Hi Devendra, It looks like your etcd cluster is in a bad state. The fact that the error output states “Joining an existing cluster, not joining an unhealthy cluster” suggests this node was once part of a healthy cluster, but since that point the cluster has lost quorum. Are you able to provide

Re: [Project Clearwater] Need tech support on Clearwater installed on EC2

Hi Rohit, This mailing list is a great place for you to ask technical questions and get to grips with Project Clearwater. I’d recommend you sign up for the list so that your messages don’t get caught in our moderator filter though. Then just send round your question with some technical

Re: [Project Clearwater] Clearwater on ARM Ubuntu 16.04 VMs

name=192.168.122.49 hs_hostname=192.168.122.41: hs_provisioning_hostname=192.168.122.41:8889 #ralf_hostname=ralf.cavium.obu-enfield.test:10888 #xdms_hostname=homer.cavium.obu-enfield.test:7888 turn_workaround=secret On Oct 6, 2017, at 9:47 AM, Adam Lindley <adam.lind...@metaswitch.com<mailto:

Re: [Project Clearwater] Clearwater Digest, Vol 54, Issue 7

Hi Ajit, Taking a look at your first problem, with your Ellis Node, it looks like your etcd cluster is in a bad state. As etcd is what we use to form the rest of our clusters, I believe that the error “Failed to update server” is occurring because your other nodes are also in a bad state;

Re: [Project Clearwater] Fail to install

Hi Nhi, I’ve taken a look at the repository, and can’t see anything on our side that might be causing this issue. I also briefly tested setting up a completely blank machine in EC2, and was able to install the packages successfully following the manual install instructions at

Re: [Project Clearwater] Clearwater on ARM Ubuntu 16.04 VMs

Hi Carl, Interesting problem. We don’t have many people looking at running clearwater up on ARM, so it’ll be good to work out what’s going on here. As a first step, could you provide the following pieces of information: · The steps you took when installing the Java and Cassandra

[Project Clearwater] Release note for sprint Nazgûl

Hi all, We have cut the latest Project Clearwater Release: Nazgûl. The code for this release has been tagged as release-128 in GitHub. This release includes a couple of substantial pieces of work: We've created a more clear distinction between data that Homestead is caching and data which is

[Project Clearwater] Release note for sprint Kíli

Hi all, We have cut the latest Project Clearwater Release: "Kíli". The code for this release has been tagged as release-127 in GitHub. This release includes the following bug fixes: · Crest build failure due to cryptography 2..0 release, and setup.py ignoring pinned dependencies ·

[Project Clearwater] Release note for sprint Fingolfin

The release for Project Clearwater sprint "Fingolfin" has been cut. The code for this release is tagged as release-123 in GitHub. This release we're upgrading etcd to the latest and greatest version. This version isn't directly compatible with the etcd used in the previous release, so after