To the best of my knowledge, while we do have a landing page of the object storage itself in OCI, not much more than that is inventoried or visible in the WEB-UI.
Instead, everything flows semi-directly into the DWH. So there is no possibility to annotate objects (like buckets) on the OCI server/Web-UI.
I don't know to which extent, but I suspect that much of what you can annotate via the rich annotation capabilities of the object storage itself will magically make it into the DWH. But this is really just a bit speculative on my part right now. To know for sure, I'd either have to find it documented somewhere or test it out.
But I think it would be worth a try though. Use the annotation capabilities of the object storage itself and see if those annotations make it into the DWH.
I won't promise, but if I can test it, I'll follow up un this thread. Unless someone else beats me to it.
We are already tag the things inside the object storage. What we want, we want to set annotations to the object storage itself (e.g. Data Center, Region). Also via the power shell cmdlets the annotation could not be set.
I am sorry to say, but I don't think that is possible. OCI doesn't really expose a whole lot of information about the object storage itself via the Web-UI or REST queries. Instead the data flows into the datawarehouse, where it can be accessed for reporting purposes.
For instance, if you compare the expands of a regular storage:
you will notice there's no annotations exposed. Or anything else much, as a mattaer of fact.
So I think the best approach for achieving the dsired outcome with the capabilites as they are right now, is to tailor your report such that the addiional information you would otherwise apply as annotations on the OCI instance, is taken into account from a purely reporting-perspective.
If this is for some reason impracticable, I'd be happy to take this offline and discuss any optios with you in a more direct manner. On the phone, maybe.
Unfortunately, in the current version of OCI you cannot annotate object storage systems in the same manner you can 'standard' block or file storage systems. The best workaround at the moment is to create a custom table in the data warehouse under dwh_custom, then join the metadata in the custom table to the capacity info in the built-in dwh tables.