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

Saravanan KR skramaja at redhat.com
Tue Nov 17 06:21:31 UTC 2015


Thanks Matthias for educating me. As there is no universal solution to 
this issue, I will check if launch instance page strategy will work out 
for this case.

Regards,
Saravanan KR

On 11/04/2015 03:47 PM, Matthias Runge wrote:
> 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
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>




More information about the OpenStack-dev mailing list