Hi Joe, Can you give some examples of what that data would be used for ?
It sounds on the face of it that what you’re looking for is pretty similar to what Extensible Resource Tracker sets out to do (https://review.openstack.org/#/c/86050 https://review.openstack.org/#/c/71557) Phil From: Joe Cropper [mailto:cropper....@gmail.com] Sent: 07 June 2014 07:30 To: openstack-dev@lists.openstack.org Subject: [openstack-dev] Arbitrary "extra specs" for compute nodes? Hi Folks, I was wondering if there was any such mechanism in the compute node structure to hold arbitrary key-value pairs, similar to flavors' "extra_specs" concept? It appears there are entries for things like pci_stats, stats and recently added extra_resources -- but these all tend to have more specific usages vs. just arbitrary data that may want to be maintained about the compute node over the course of its lifetime. Unless I'm overlooking an existing construct for this, would this be something that folks would welcome a Juno blueprint for--i.e., adding extra_specs style column with a JSON-formatted string that could be loaded as a dict of key-value pairs? Thoughts? Thanks, Joe
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
