| 2016-01-11 12:16:50 |
Eva Balycheva |
description |
Look how flavor creation is made in python-zaqarclient:
https://github.com/openstack/python-zaqarclient/blob/master/zaqarclient/queues/v1/pool.py#L46
Now imagine a situation:
The user asks python-zaqarclient to create a flavor like this:
tasty_flavor = self.client.flavor('tasty', pool='burger')
But Zaqar server already has a flavor named 'tasty' with 'broccoli' pool group.
The situation result:
The user might think he created a flavor with name 'tasty' and pool group 'burger',
when in reality he didn't created anything. Even worse, 'tasty' flavor has pool group 'broccoli'.
The user would never expect such betrayal from python-zaqarclient.
Same problem exists for creation of pools and maybe other resources.
The possible solution must be discussed. |
Look how flavor creation is made in python-zaqarclient:
https://github.com/openstack/python-zaqarclient/blob/master/zaqarclient/queues/v1/pool.py#L46
Now imagine a situation:
The user asks python-zaqarclient to create a flavor like this:
tasty_flavor = self.client.flavor('tasty', pool='burger')
But Zaqar server already has a flavor named 'tasty' with 'broccoli' pool group.
The situation result:
The user might think he created a flavor with name 'tasty' and pool group 'burger', when in reality he didn't created anything.
Even worse, 'tasty' flavor has pool group 'broccoli'.
The user would never expect such betrayal from python-zaqarclient.
Same problem exists for creation of pools and maybe other resources.
The possible solution must be discussed. |
|
