Hi @ecnahc515,

I liked the idea you mentioned  that - I do not have to worry about redirects with AJAX calls; and saw it now.

(1)
I was suggested to use complete FQDN's to refer to clusters, nodes,etc in a feedback from ganeti community, but GWM:  `clusters/views.py`  uses  a cluster slug in urls to filter a cluster? 
Should I switch to using slugs instead? Are slugs unique for each cluster for sure? (I had also noticed before that using slugs causes problems when I use IP addresses for cluster names.)

(2) 
About simply re-loading the page. (after data at backend is updated)-
I am not sure, but I think this shouldn't cause any performance issues? Acc. to me most js/css files should be cached; so its only the cluster data which will be re-fetched (including syncing with ganeti at the backend) that takes the greatest share of the 'refresh' time.

But if I switch to using the `refresh()` in 'clusters/views.py` I may have no option of reloading this page via a redirect (since I cannot alter the original view's redirect which is used at other places within GWM) So I will have to adopt  the idea you suggested ie. 'redrawing of the graph' after the refresh at back-end is performed. Now, this will take up more hooks & code on the front-end side.

To summarize  (2) - I feel, its like removing some code from back-end, to add more code on the front end without changing the total run time appreciably. (perhaps a very small improvement)

What is your opinion about this? Should I switch to the solution you mentioned?