You can deploy Searchlight
(https://wiki.openstack.org/wiki/Searchlight) and it can handle this
and more complex metadata querying (it is backed by elastic search and
supports all of the expressive power of elastic search queries).
There's a limit to how much query functionality can go into a
We have an user demand that volumes should be filtered by some operation
with metadata(or tag):
1. key1=value1
2. key1=value1 and key2=value2
3. key1=value1 or key1=value2
4. key1=value1 or key2=value2
5. not key1=value1
6. not key1=value1 and not key1=value2
7. not key1=value1 and not key2=value2
On 3/27/2017 9:59 AM, Duncan Thomas wrote:
On 27 March 2017 at 14:20, 王玺源 > wrote:
I think the reason is quite simple:
1. Some users don't want to use key/value pairs to tag volums. They
just need some simple strings.
On 27 March 2017 at 14:20, 王玺源 wrote:
> I think the reason is quite simple:
> 1. Some users don't want to use key/value pairs to tag volums. They just
> need some simple strings.
>
...and some do. We can hide this in the client and just save tags under a
metadata item
On Mon, Mar 27, 2017 at 03:13:59PM +0800, 王玺源 wrote:
> Hi cinder team:
>
> I want to know what's your thought about adding tags for volumes.
>
> Now Many resources, like Nova instances, Glance images, Neutron
> networks and so on, all support tagging. And some of our cloud customers
>