Open Stack

Hi All,

Could you please reply to below mail...

Thanks
Nidhi

From: Nidhi Mittal Hada (WT01 - Product Engineering Service)
Sent: Thursday, January 07, 2016 12:42 PM
To: 'OpenStack Development Mailing List (not for usage questions)' <openstack-dev at lists.openstack.org>
Subject: RE: [Openstack-dev][Manila] status=NONE when share is created

Hi All,

Could someone please reply to the mail below ..

Is this an expected state to get created share status as None?

As we are intentionally not creating "share instance" while creating
share..

For details please see mail below..

Thanks
Nidhi


From: Nidhi Mittal Hada (WT01 - Product Engineering Service)
Sent: Wednesday, January 06, 2016 1:23 PM
To: OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: [Openstack-dev][Manila] status=NONE when share is created

Hi All,

https://bugs.launchpad.net/manila/+bug/1526284


stack at controller:~/devstack$ manila create NFS 1 --name share5 --share-type GENERAL_Storage
+-----------------------------+--------------------------------------+
| Property | Value |
+-----------------------------+--------------------------------------+
| status | None >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> |
| share_type_name | GENERAL_Storage |
| description | None |
| availability_zone | None |
| share_network_id | None |
| export_locations | [] |
| share_server_id | None |
| host | None |
| snapshot_id | None |
| is_public | False |
| task_state | None |
| snapshot_support | True |
| id | 6572a26a-2313-4a1d-8765-4a031ec0ae3a |
| size | 1 |
| name | share5 |
| share_type | 961b767b-b8e4-4769-884f-7214af944f29 |
| created_at | 2015-12-15T11:31:23.818642 |
| export_location | None |
| share_proto | NFS |
| consistency_group_id | None |
| source_cgsnapshot_member_id | None |
| project_id | 0e15488bc7a14ce5b530920c95357457 |
| metadata | {} |
+-----------------------------+--------------------------------------+

status should be "creating".. but it's being shown as "NONE" which is not right.

I am working on this bug. I have a doubt. code is as below.
In file manila/share/api.py

try:
234             share = self.db.share_create(context, options,
235                                          create_share_instance=False)>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
236             QUOTAS.commit(context, reservations)
237         except Exception:
238             with excutils.save_and_reraise_exception():
239                 try:
240                     self.db.share_delete(context, share['id'])
241                 finally:
242                     QUOTAS.rollback(context, reservations)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------

Where we are intentionally giving create_share_instance=False that means in db function
share_create(), share Instance will not be created And status is a field in share_instances table only.

Hence it will come as "None" only till instance is created.

Is this an "intentional step" to show status as "None"..

is this bug not valid?

Please suggest.

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160112/d13dfb8a/attachment-0001.html>