On Mon, Jan 12, 2015 at 3:33 PM, Angus Salkeld asalk...@mirantis.com
wrote:
On Mon, Jan 12, 2015 at 10:17 PM, Konstantin Danilov
kdani...@mirantis.com wrote:
Boris,
Move from sync http to something like websocket requires a lot of work
and not directly connected
with API issue. When
On Mon, Jan 12, 2015 at 10:17 PM, Konstantin Danilov kdani...@mirantis.com
wrote:
Boris,
Move from sync http to something like websocket requires a lot of work and
not directly connected
with API issue. When openstack api servers begin to support
websockets - it would be easy to change
Konstantin,
I believe it's better to work on server side, and use some modern approach
like web sockets for async operations. So we won't need to retrieve 100500
times information about object. And then use this feature in clients.
create_future = novaclient.servers.create_async()
Hi all.
There a set of openstack api functions which starts background actions
and return preliminary results - like 'novaclient.create'. Those functions
requires periodically check results and handle timeouts/errors
(and often cleanup + restart help to fix an error).
Check/retry/cleanup code
Boris,
Move from sync http to something like websocket requires a lot of work and
not directly connected
with API issue. When openstack api servers begin to support
websockets - it would be easy to change implementation of monitoring thread
without breaking compatibility.
At the moment periodical
