Open Stack

On 12/22/2015 12:26 AM, nidhi.hada at wipro.com wrote:
> Hi all.
>
> I am working on bug 1503390. (status=None while delete is in progress
>
> )
>
> I was doing analysis of problem and found that yes its there.
>
> I reproduced it.
>
> Now the two solutions proposed..
>
> 1)Either say the status as deleting for such snapshots ?
>
> 2)lets not list such snapshots in list ..
>
> I see that
>
> If we implement solution1 .. then it doesn’t work as …..
>
> we reach the same Situation of (snapshot present but snapshot_instance
> absent)
>
> in two cases
>
> When snapshot is deleted and when snapshot is created …
>
> Now if I set status as deleting(to be shown in list for snapshots with
> no snapshot_instances)
>
> it will be a wrong information when we are creating the snapshot.
>
> And list function – can not differentiate state (snapshot present but
> snapshot_instance absent)
>
> whether its due to creation or deletion.  PCIIMW…
>
> Another way to do this is .. let create delete path set the status to a
> special state .
>
> which if list operation obtains .. can understand how to interpret it …
>
> But setting status also is not possible as status resides in
> snapshot_instances table ..
>
> row for which is not created yet in create path .. we can not set staus …!!!
>
> Do you think that
>
> STATUS_NEW = 'new'
>
> STATUS_CREATING = 'creating'
>
> STATUS_DELETING = 'deleting'
>
> STATUS_DELETED = 'deleted'
>
> STATUS_ERROR = 'error'
>
> STATUS_ERROR_DELETING = 'error_deleting'
>
> STATUS_AVAILABLE = 'available'
>
> STATUS_ACTIVE = 'active'
>
> STATUS_INACTIVE = 'inactive'>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
> STATUS_MANAGING = 'manage_starting'
>
> STATUS_MANAGE_ERROR = 'manage_error'
>
> STATUS_UNMANAGING = 'unmanage_starting'
>
> STATUS_UNMANAGE_ERROR = 'unmanage_error'
>
> STATUS_UNMANAGED = 'unmanaged'
>
> STATUS_EXTENDING = 'extending'
>
> Do you think that setting state as *_some neutral state like
> state_inactive .._*
>
> will help?
>
> it will be same in both creation and deletion path ?
>
> so should we go with 2^nd solution ? lets not show such shares in list ?

I like the second solution. Rather than making up a neutral state, just 
don't list snapshots with no instances. If the snapshot was getting 
deleted, then very soon there won't be anything to show, and if the 
snapshot was just getting created, the client can retry the query later 
and see the snapshot after a short time.

-Ben


> Thanks
>
> Nidhi
>
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s)
> and may contain proprietary, confidential or privileged information. If
> you are not the intended recipient, you should not disseminate,
> distribute or copy this e-mail. Please notify the sender immediately and
> destroy all copies of this message and any attachments. WARNING:
> Computer viruses can be transmitted via email. The recipient should
> check this email and any attachments for the presence of viruses. The
> company accepts no liability for any damage caused by any virus
> transmitted by this email. www.wipro.com
>
>
> __________________________________________________________________________
> 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
>