You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 12, 2021. It is now read-only.
That sounds like an awesome idea! We don't make extensive (or any?) use of the metadata for our production setup, which is why we haven't bothered. That said, patches are more than welcome!
Cool, that's awesome. I will start working on this soon.
Would you prefer a dynamic way of declaring what to extract from metadata and sysinfo in e.g. a yaml config file, or would you prefer an openstack-specific option like "openstack.extract_metadata=true"
(I guess the first one is the way to go, just checking if you'd agree)
Both approaches are fine by me, actually. Maybe we could start off with a simple command line flag and only switch over to a dynamic approach if it turns out we're gaining more feature requests like these.
Alternatively, maybe there's a way in which we can convert all metadata in a way that doesn't require any explicit configuration or knowledge of OpenStack?
Nice project!
For us I'm looking for the ability to add more labels based on the
<metadata>
or<sysinfo>
parts of the dom xml.This is in my case to extract additional (openstack) information like instance uuid, flavor, name, creation date, project + user uuid etc.
Maybe I will implement this if the patch is welcome.
The text was updated successfully, but these errors were encountered: