[openstack-dev] [Horizon] Handling of 202 response code

Matthias Runge mrunge at redhat.com
Wed Nov 4 10:17:00 UTC 2015


On 04/11/15 09:25, Saravanan KR wrote:

> There may be multiple solutions:
> 1) Waiting for the synchronous and then respond
> 2) Do not trigger page refresh and respond with Operation in progress
> 3) If there is a mechanism to know delete in progress, do not list the
> interface
> 
> To decide on the solution, it is important to know how 202 responses
> should be handled. Can anyone can help with understanding?

Asynchronous operations are handled in horizon as synchronous
operations. To illustrate that: launch an instance, you'll get
immediately a feedback ("launch instance issued").
But, you don't get a status feedback directly. Horizon pulls nova api
for status updates via ajax calls.

So: there is no solution yet for this. You could duplicate the same
update strategy as in launch instance (on instances page), create a
volume (on volumes table), etc.

In ideal case, one would use something like a message bus to get
notified on changes.

Matthias





More information about the OpenStack-dev mailing list