Closed tcrivat closed 9 years ago
I know that the web-interface was working a while ago, because I used it. We didn't change the scalaris service itself. So somebody must have broken the web-interface.
Who is @jan--f? His commit 18a3760b46bf6db4bab3329c836d088481063ea0 from 6 months ago broke the web-interface for Scalaris. I will fix it tomorrow morning.
He is a student of mine. He was supposed to add usage infomation to the command-line interface based on the XtreemFS client.
Are you sure that this commit broke the web-interface? When I commited d73189d969a04b3ef17844dfd1b5ae5caafee452, I believe the web-interface was still working.
Anyway, can you simply revert the patch? Tomorrow, I will try to add usage information from the working version.
I will fix it tomorrow. I assumed that an issue can be assigned to two people. Sorry for that.
Commit f125535dc88427f1e52f1d199d706129d2682944 should fix the issue. I tested the client and web-interface.
Now, the command-line client should work as expected.
Hi @tschuett,
I tested your patches and indeed, the Scalaris service works fine now. I tested it on Amazon EC2, OpenNebula and inside the Nutshell, using both the frontend web-interface and the command line tools (cpsclient.py and cps-tools). There are still some small glitches when using cps-tools, but it seems that (at least) some of them are not specific to the Scalaris service because they happen to other services as well. I will open a different issue on that.
This can now be closed. Thanks!
When the Scalarix service is started and becomes running, the frontend does not show anything regarding the service, not even the IP addresses of the nodes:
Thus it is not possible to add more nodes, remove nodes or stop the service using the frontend. Other than that, the service works fine. The command line interface works fine and allows adding/removing nodes or stopping the service.