Kevin,

Ellie's away for the next week or so, so I'm replying in her absence.

Please can you share the logs from Ellis (below /var/log/ellis) and 
Homestead-Prov (below /var/log/homestead-prov) that are generated when you see 
this failure?  This will tell us which URL on Homestead-Prov failed, and 
hopefully why - then we can figure out what configuration needs to be 
reinstated in Cassandra.

Regarding Ellis and app server provisioning, the way this works is that

*         when you tick an app server in the Ellis UI, Ellis reads the IFC from 
app-server.json and writes it to Homestead

*         when you reload the page, Ellis reads the IFCs from Homestead, sees 
if any match the app servers in app-server.json and marks the checkboxes as 
ticked/unticked accordingly

*         if you untick an app server in the Ellis UI, Ellis finds the IFC that 
corresponds to it and removes it

*         crucially, if an IFC doesn't match any app server, Ellis just ignores 
the IFC - it doesn't display it in the Ellis UI and it doesn't modify the IFC.

As a result, the best way to change an app server's IFC is either to

*         find all the subscribers with the old IFC, uncheck that app server in 
the Ellis UI, modiy the IFC in app-server.json and then recheck the app server 
or

*         not modify the IFC in app-server.json and instead just introduce a 
new app server (e.g. "app server v2") in app-server.json and then, on a 
per-subscriber basis, uncheck the old app server and check the new one.

I admit this is a bit clunky - unlike components like Sprout and Homestead, 
which are built to be carrier-grade, Ellis is a tool for easy provisioning for 
demos and testing, but does have a few rough edges!

Please let me know about the logs.

Thanks,

Matt

From: Clearwater [mailto:[email protected]] On 
Behalf Of Kevin High (khigh)
Sent: 19 January 2016 21:55
To: Eleanor Merry <[email protected]>; 
[email protected]
Subject: Re: [Clearwater] Syncing Ellis with Homestead have rebuild of a 
Homestead

Hi Ellie,

I was having issues with Originating Triggers in the IFC for my App server, so 
I change the IFC (app-server.json) in Ellis  and that didn't fix the issue.  
Looking at the logs I noticed that it was still my old IFC.  So I unchecked and 
re-checked the App server in the Ellis configuration as well as restarting 
Ellis.  I then noticed that I was getting looping, and again digging into the 
logs I saw that I had two triggers now.  I dug into Cassandra on Homestead and 
saw both the triggers in the database.  I deleted the entries in Cassandra (not 
using truncate) and Ellis stopped letting me see the numbers because of the

BAD GATEWAY - The server, while acting as a gateway or proxy, received an 
invalid response from the upstream server it accessed in attempting to fulfill 
the request.
(XHR): GET Error.

I figured that perhaps if I terminate my Homestead and Homer servers and 
rebuild them from scratch that it would rebuild the databases from Ellis.  But 
looking back I guess I didn't take into consideration that even though you 
populate the numbers in Ellis prior to installing Homer and Homestead, you 
don't create the users, which is what would be different right now.  So 
needless to say at this point, that didn't work.

I just ran your updated script and it populated the Cassandra databases on 
Homestead, but I am still getting the BAD GATEWAY error trying to look at my 
previous numbers.   So presuming something is still missing.  I have restarted 
all the services.

Just to note, this is a manual install with each components bono, sprout, 
homer, homestead and ellis running on individual servers.

Thanks
Kevin

From: Eleanor Merry [mailto:[email protected]]
Sent: Tuesday, January 19, 2016 10:10 AM
To: Kevin High (khigh) <[email protected]<mailto:[email protected]>>; 
[email protected]<mailto:[email protected]>
Subject: RE: [Clearwater] Syncing Ellis with Homestead have rebuild of a 
Homestead

Hi Kevin,

How did you lose the Homestead/Homer nodes? I ask because if you truncated the 
databases then Cassandra automatically takes a backup before it does the 
truncating, so you could restore from that.

We don't have a supported method in Project Clearwater for restoring 
Homer/Homestead data from Ellis. We recommend instead that users take periodic 
backups of the persistent data stores - please see 
http://clearwater.readthedocs.org/en/latest/Backups/index.html for more details.

That said, I've taken a look at the repop scripts, and fixed up initial runtime 
errors. If you take the latest scripts from the dev branch of Ellis then you 
should be able to use these to repopulate Homestead/Homer (they'll fill in 
default values for anything Ellis doesn't know, e.g. the IFCs, and they'll 
reset the subscriber passwords). Please note that this isn't our supported 
method though, and hasn't gone through a full QA.

Ellie

From: Clearwater [mailto:[email protected]] On 
Behalf Of Kevin High (khigh)
Sent: 17 January 2016 00:12
To: 
[email protected]<mailto:[email protected]>
Subject: [Clearwater] Syncing Ellis with Homestead have rebuild of a Homestead

Due to user error, I had to recreate the my Homestead and Homer instances.  I 
was hoping that they would automatically resync with Ellis, but that doesn't 
appear to be the case.  I see this script in Github 
https://github.com/Metaswitch/ellis/blob/dev/scripts/repop_hs.py, but I don't 
see the script on the Ellis instance.  I am not sure if this is even what I 
need.  I did copy the source to a file on Ellis and tried to run it similarly 
to how you would run the create_numbers.py, but just ran to into a bunch of 
errors.

Looking for some help to re-sync the Homer and Homestead databases from Ellis.

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

Reply via email to