[openstack-dev] [nova] How to use resource_providers for shared disk resources (NFS)

Shewale, Bhagyashri Bhagyashri.Shewale at nttdata.com
Mon Jan 30 10:55:28 UTC 2017


Hi nova devs,

How can I use placement api's if my instance path is mounted on shared storage server (e.g. NFS)?

I am trying to set multinode setup with NFS shared storage for all nodes to share disk resources along with placement services. As of now it is creating resource providers for each of the compute node and adds the DISK_GB for each resource provider.

For example below are my environment details:

NODE A: compute
NODE B: controller + compute

Following entries are made in resource_providers table:

+---------------------+---------------------+----+--------------------------------------+------------------------+------------+----------+
| created_at          | updated_at          | id | uuid                                 | name                   | generation | can_host |
+---------------------+---------------------+----+--------------------------------------+------------------------+------------+----------+
| 2017-01-30 06:49:17 | 2017-01-30 09:12:06 |  1 | 6cbbaf2b-5b8c-4f38-8b34-ee23791056a6 | openstack-VirtualBox   |          3 |        0 |
| 2017-01-30 09:02:29 | 2017-01-30 09:11:03 |  3 | bad71c26-8f36-43ea-abf4-bdbeffda9e54 | openstack-VirtualBox-1 |          2 |        0 |
+---------------------+---------------------+----+--------------------------------------+------------------------+------------+----------+

Following are the entries of inventories tables, of which 89 indicates the DISK_GB (size of shared storage):

+---------------------+---------------------+----+----------------------+-------------------+-------+----------+----------+----------+-----------+------------------+
| created_at          | updated_at          | id | resource_provider_id | resource_class_id | total | reserved | min_unit | max_unit | step_size | allocation_ratio |
+---------------------+---------------------+----+----------------------+-------------------+-------+----------+----------+----------+-----------+------------------+
| 2017-01-30 06:49:19 | 2017-01-30 09:10:37 |  1 |                    1 |                 0 |     1 |        0 |        1 |        1 |         1 |               16 |
| 2017-01-30 06:49:19 | 2017-01-30 09:10:37 |  2 |                    1 |                 1 | 11210 |      512 |        1 |    11210 |         1 |              1.5 |
| 2017-01-30 06:49:19 | 2017-01-30 09:10:37 |  3 |                    1 |                 2 |    89 |        0 |        1 |       89 |         1 |                1 |
| 2017-01-30 09:02:31 | 2017-01-30 09:11:03 |  7 |                    3 |                 0 |     1 |        0 |        1 |        1 |         1 |               16 |
| 2017-01-30 09:02:31 | 2017-01-30 09:11:03 |  8 |                    3 |                 1 | 10253 |      512 |        1 |    10253 |         1 |              1.5 |
| 2017-01-30 09:02:31 | 2017-01-30 09:11:03 |  9 |                    3 |                 2 |    89 |        0 |        1 |       89 |         1 |                1 |
+---------------------+---------------------+----+----------------------+-------------------+-------+----------+----------+----------+-----------+------------------+

However still I am able to create the instances over the size of actual shared storage.

Please let me know how to configure resource_providers in case of shared storage servers are used for disk resources.

Thank you,

Bhagyashri

______________________________________________________________________
Disclaimer: This email and any attachments are sent in strictest confidence
for the sole use of the addressee and may contain legally privileged,
confidential, and proprietary data. If you are not the intended recipient,
please advise the sender by replying promptly to this email and then delete
and destroy this email and any attachments without any further use, copying
or forwarding.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170130/779dd3a1/attachment.html>


More information about the OpenStack-dev mailing list