In order to realize the function of SPICE over SSL, these two weeks, first I get familiar with freeaSPICE-3.7.7-final.apk, to have an idea how to connect ovirt’s SPICE Console.

After I can connect ovirt’s SPICE Console successfully by freeaSPICE, I got the necessary parameter that connect ovirt’s SPICE Console. And then I begin to check bVNC’s source code ( the freeaSPICE mentioned before is the author modified bVNC source and compile and got it). Also I test it, and find freeaSPICE do not support passing parameters(SPORT,SUBJECT,CA_FILE) in URL.

I tried to contact the author but didn’t get any feedback, and then I modify bVNC according the method that author offered how to modify bVNC into aSPICE. But I have no idea how to compile libspice.so and libgstreamer_android.so, so I copy lib document of freeaSPICE-3.7.7-final.apk, and compile aSPICE successfully.Howerve it only works while I rename the package name of aSPICE APP as the same name of the package of freeaSPICE-3.7.7-final.apk.

The following interface show successfully compiled aSPICE:


After compile aSPICE successfully, I Extend aSPICE’s URI parameters supported by RemoteCanvasActivity(added support for
TlsPort, CaCertPath and CertSubject parameter) .
And then modify movirt, first got and save TlsPort and CertSubject these two parameters, which got from REST API through movirt, and then check whether it already download CA file before calling aSPICE, if not remind user download CA file. Finally, add TlsPort, CaCertPath and CertSubject these three parameters in calling aSPICE’s URL.

Calling aSPICE to connect SPICE Console successfully is showed as below:



Get Started–First Week

It has been two weeks since the project begin, these two weeks I mainly get familiar with the relevant knowledge about this project.

First getting familiar with the process that movirt getting data from the server and save the data in local database. Also I restudy SQL and relevant API about Android operation system’s sqlite database.

For the code part, showed as the following picture:
1.Add activate and maintenance actions for host details activity:

图片12.Optimized actions display for vm and host details activity
(1)while vm in the down state,menu only display run action,as followed:



(2)while vm in up state,menu display stop, reboot and console action, as followed:



(3)while host in up state,menu only display maintenance action, as followed:


(4) while host in maintenance state,menu only display run action, as followed:



As this week I’ve back to China and waste few days in travel, and the following part is unfinished as planed:
Enrich the VM general view by some data, at least:
– cluster (with version) / datacenter on which this VM is
– If the VM is running than the Host on which it is running

To make up the delay, next week I will word harder to make the progress as planed.