JYH,
Are you asking for this to be a blanket rule? It seems to me that this
could be a case by case basis, but I question making it a blanket rule.
For example, the os_shutdown_timeout property [1] seems very workload
specific. In your proposal, this would mean that the operator would have
to
When I played with metadata, I had have constant feeling it had mess
together few things:
1. H/W requirements for images.
2. Accounting requirements (good CPU for good price, HDD for cheap)
3. Licensing restrictions (run this one only on the hosts with licenses)
4. Administrative management
Hi,
There are some discussion and disagreement on the requirement from
flavor and image metadata at nova spec https://review.openstack.org/#/c/138937/
and I want to get more input from the community.
When launch a VM, some requirements may come from image metadata and
flavor.
