Tags for ontap objects like shares, volumes, qtrees to improve documentation and researches

[bjoern_shd]

If I have more than 500 volumes and many shares or exports, it would be more convenient if I could tag some objects with company-internal attributes.

For some objects I can use the option "-comment", but it would be simpler if ontap cli or the system manager by default want to support tagging in a separate field. This makes it easier for me to research my surroundings.

[donny_lang]

OnCommand Unified Manager supports Annotations, which might be helpful. You can define custom Annotation Rules to dynamically categorize storage objects. Once objects are associated, you can view in the Admin>Annotations section of OCUM all objects that match a specific annotation, whether associated manually or dynamically (you cannot, however, use custom Annotations as criteria for filtering searches for OCUM objects, FYI). 

https://docs.netapp.com/ocum-95/index.jsp?topic=%2Fcom.netapp.doc.onc-um-ag%2FGUID-3991EE2A-B938-49E5-A736-BC1BAD1664E6.html

[guido77]

Did you ever get an answer on this?

[elementx · Accepted solution]

That question is already answered in ONTAP documentation - volumes and clusters can be tagged for now - and for other objects you may use OnCommand Unified Manager as explained above.

https://docs.netapp.com/us-en/ontap/assign-tags-volumes-task.html

https://docs.netapp.com/us-en/ontap/assign-tags-cluster-task.html

[guido77]

Thanks for your fast reply Elementx!

There is also this in the documentation: https://docs.netapp.com/us-en/ontap/fabricpool/assign-new-tag-volume-creation-task.html   

https://docs.netapp.com/us-en/ontap/fabricpool/object-tagging-user-created-custom-tags-task.html

But it is part of the documentation of Fabricpool. The way the documentation is written it seems to me that it will change or influence the behaviour of volumes and moreover it could change the way objects are moved to fabricpool.

This makes me hesitant to use tags because we just want to tag a volume but we don't want to influence the way the cold data is tiered off to StorageGrid.

take a look at this too: https://docs.netapp.com/us-en/ontap/fabricpool/check-object-tagging-status-task.html

[elementx]

From the intro page related to FabricPool and volume tags they say the purpose is "to enable you to classify and sort objects for easier management.".

So it impacts only the ability to classify (filter when showing) or sort (sort by name, date of creation, size, maybe tag, etc).

It doesn't say that it changes FP tiering behavior which is still set in the usual place. It may make that process easier - for example you may query and filter all volumes tagged with "tier01" and set those to Snapshot-only,

But in 9.14 volume tagging has no ability to change how volume tiering is already configured, as far as I can tell. I don't see any indication that FP-related behavior may be modified with volume tags.