On 06/27/2014 07:15 PM, Wen Wang wrote:
Now let me elaborate above.
Now our strategy for long time operation is using task which the
browser needs to check up-to-date task status time by time until
the task ends. It's time consuming and less efficient. Also there
exists several problems when locating each task when doing debug
generating and storage pool as well as some new features that
might use task strategy in the future.
As talked with Sheldon and Zhengsheng, we came up with a solution
that avoid browser checking status every 200ms. Also, we might
need some more labels in each task to provide more information
when getting the task like we might need to indicate which
operation triggered certain task. What's in our mind is to use the
strategy that allow the server inform browser about the task
information. Our proposal is designed as follows.
1) Browser needs to register to the back end to indicate which
part the result needs to reply to when the task finished.
2) The back end use broker to manage message distribution: when a
task is finished or experiencing an error, back end inform the
browser certain part of work is finished or error.
3) Using websocket of cherrypy to accomplish the message transfer.
For Browser, it can be an event loop worker.
It can subscribe event message that users care to the back end
listen the events from the broker and take some action for the
The broker should collect and store the events from everywhere.
The broker should dispatch the message to the client who subscribes
For some event, broker should determined whether it should dispatch
Such a VM shutdown event, the broker just send it to the user who
has the access permission. （Yu Xing's suggestion）
We had better define the event message format.
We had better to find an existing python lib for it. If no we should
code it for ourself.
care VM | ^
libvirt event -------------\ shutdown | | VM
event 1 -------- -------------------------->[ broker ]
event 2 ------------/ | |
subscribe | V
There's also an issue about it.
The websocket is the pipe to connect the broker of the UI event
We should support websocket proxying directly from the cherrypy
server on its given port.
Zheng Sheng is working on it. It can work on cherrypy. Seems
something wrong with nginx.
Kimchi-devel mailing list
Thanks and best regards!
IBM Linux Technology Center